Buyer's Guide

Running a Clinic on Excel: When to Switch

A guide for clinics still keeping patient records in a spreadsheet — where Excel still works, where it starts to expose you, and how to tell which side of the line you're on.

The Short Answer First

Excel is workable for a clinic with one doctor, modest patient volume, and nobody else editing the file. The moment to switch isn't when Excel breaks — it's when any one of four things becomes true: more than one person edits the same file, you start paying DF to employed doctors, you open a second branch, or a patient exercises a PDPA right.

The reason to move isn't that Excel can't do the work. It's that patient records are sensitive data under the law, and a spreadsheet makes it very hard to prove who opened what. That responsibility sits with the clinic, not with whoever built the file.

What Excel Genuinely Does Well

Before arguing for a change, it's worth saying plainly that starting in Excel is a sensible decision. It costs nothing extra, everyone already knows how to use it, you can restructure it the moment you want to, and nobody has to install anything for you.

For a new clinic that doesn't yet know what its real workflow looks like, starting in a spreadsheet and migrating later is usually cheaper than buying a large system on day one and discovering it doesn't match how you actually work.

So this guide isn't an argument that Excel is bad. It's an attempt to show clearly where the line sits.

Five Signals It's Time to Move

One: more than one person edits the same file. The symptom is filenames ending in final, final-real, use-this-one. At that point nobody can say with certainty which file holds the truth.

Two: you've started paying DF to employed doctors. Calculating it means pulling what the patient actually paid, splitting by procedure, applying each doctor's agreed percentage, then handling withholding tax. A spreadsheet can do it, but it must be redone every month, and a mistake here is a mistake about money owed to a doctor.

Three: you've opened a second branch. Two spreadsheets don't mean two branches — they mean two sets of data that must be merged by hand every time you want the full picture, and patient numbers usually start colliding in the first month.

Four: patients start asking for their history. When someone returns after two years, searching files split by year or month takes longer than a patient will wait at the counter.

Five: someone exercises a PDPA right — asking to see their data, correct it, or have it deleted. These requests have to be answered within the timeframe the law sets, and answering means knowing everywhere that data lives. That's a hard question when files have been forwarded through chat.

What PDPA Makes Hard to Prove in a Spreadsheet

PDPA does not prohibit keeping patient data in Excel. It requires the data controller to have appropriate security measures — and to be able to demonstrate them. It's the demonstrating part where spreadsheets struggle.

Try answering these about the file you use today: who has opened it in the past month; who changed this number, and when; which other machines hold a copy; if a staff member left today, could they still open the copy sent to them in chat; and if a patient asked you to delete their data, how would you be confident every copy was gone.

These are hard to answer with a spreadsheet — not because anyone was careless, but because the file was never built to record what was done to it. Software designed to hold patient records logs every access and change on its own, sets permissions per person, and when access is revoked it is genuinely revoked.

Excel and Clinic Software, Side by Side

This table isn't saying either side is useless. Excel still wins on flexibility and cost. Clinic software wins where several people need the same data, where you must be able to look back and verify, and where the same task repeats every month and has to be right.

The useful way to read it is to find the rows that describe a problem you actually have right now. If none of them do, it isn't time yet.

Only the things a clinic actually hits day to day
Excel / spreadsheetClinic software
Monthly costEffectively noneA subscription fee
Several people at onceConflicts, merged by handWorks concurrently
Knowing who changed whatNo recordLogged every time
Per-person permissionsLimitedSet by role
Finding old patient historyFile by fileFound immediately
DF and withholding taxBy hand, every monthCalculated automatically
Combining branchesMerged manuallyConsolidated view
Answering PDPA requestsChase every copyAn auditable record exists

The Cost That Isn't in the File

Excel's visible cost is zero. Its real cost is the time spent on work that repeats every month, plus risk that is hard to price until the day it happens.

Time it honestly for one month and compare: closing off daily totals, calculating DF for each doctor, digging out old patient histories, merging files from different machines, and redoing work when a file is corrupted or overwritten.

Multiply those hours by the hourly cost of whoever does that work, then compare it with a monthly subscription. A fair number of clinics find the two figures are closer than expected — and that still leaves the risk to patient data unpriced.

How to Migrate Off Excel

Don't move everything at once. Start with patient records and appointments, because they're used daily and show results fastest. Historical reporting can follow later.

Keep the old spreadsheets as read-only for about three months rather than deleting them. During that time, all new work goes into the new system only. If people keep editing the old files too, you're back to two versions of the truth.

Put one person in charge of the move, and pick a quieter week to start. With SyncEdge Clinic, Solo and Starter are set up free and the trial runs 14 days with no credit card — enough to import a hundred real records and test the workflow before committing.

Has Your Clinic Reached the Switching Point?

  • More than one person needs to edit the same file each day
  • There is more than one file with "final" in the name
  • You've started paying DF to employed doctors
  • You have a second branch, or will open one this year
  • Finding an old patient's history takes longer than they'll wait
  • Patient data files have been sent by chat or copied to a USB drive
  • You can't say who viewed patient data last month
  • A patient has asked to see, correct, or delete their data

Frequently asked questions

Is keeping patient data in Excel against PDPA?

Not in itself. PDPA doesn't specify which software to use; it requires appropriate security measures that you can demonstrate. The difficulty with spreadsheets is proving who accessed the data and controlling copies once they've spread. That responsibility sits with the clinic as data controller.

How small does a clinic have to be to stay on Excel?

If it's one doctor, no employed doctors requiring DF calculation, one person editing, one branch, and the file lives on a password-protected machine that's backed up regularly, Excel can still work. The tipping point usually isn't patient numbers — it's how many people need the same data.

Can I bring old Excel data into clinic software?

Yes, if the file has reasonable structure. Line up the columns first — name, surname, phone, date of birth, patient number — then import. With SyncEdge Clinic, Solo and Starter include free setup; Pro carries a one-time ฿15,000 migration fee.

Is clinic software much more expensive than Excel?

Subscriptions start in the hundreds to low thousands of baht per month for a small clinic. SyncEdge Clinic starts at ฿990 per month for Solo, excluding 7% VAT. The number to compare isn't Excel's zero — it's the hours spent on repeated work each month multiplied by the cost of the person doing it.

Would Google Sheets solve this instead?

It genuinely helps with concurrent editing and backups, and it beats files forwarded through chat. But it still doesn't address per-patient access control, a record of who viewed what, or clinic-specific work like DF calculation and issuing medical certificates.