Clinic front-desk readiness checklist

Clinic software projects rarely fail in the software. They fail at the front desk, in the first fortnight, over things nobody wrote down: which number a patient is, who is allowed to give a discount, what the receipt series was before and what it is now, and whether the nurse is still keeping her own notebook because the screen does not show her what she needs.

Everything below can be done with a pen and your existing registers, before you talk to any vendor. Every answer you write down now is an answer you will otherwise have to invent under pressure on go-live morning, with a waiting room full of people.

1. Decide your numbering before anyone types a single record

Numbering is the skeleton. Get it wrong and every report, every reconciliation and every argument with a patient about a bill from March becomes archaeology.

• Patient ID: one scheme, never reused, never recycled when a file is closed. Decide whether it carries meaning (year, branch, department) or is simply a running number. Running numbers age better.
• Token or queue number: per day, per doctor, or per department? Decide what resets at midnight and what does not.
• Invoice series: one series or one per department, and does it reset at the start of your financial year or run continuously? Whatever you choose, it must be sequential with no reuse.
• Receipt numbering: separate from invoice numbering. One invoice can collect three payments, and each payment needs its own receipt number.
• Lab and procedure numbering: linked to the visit, not to the patient, so a repeat test is a new record rather than an overwrite.
• The old numbers: decide today whether existing patient IDs carry across or are replaced with a cross-reference. Write the decision down and tell every member of staff.

2. Write down what your registers actually hold

For each register in use, note three things: which fields are really filled in (not which are printed on the page), who writes in it, and when it is closed and reconciled. That is the specification for the screen that replaces it.

• OP register: name, age, sex, contact number, referred by, complaint, doctor seen, fee taken. Note which of these are frequently left blank — those are the fields that must not be mandatory on the new screen, or the queue stops.
• Appointment book: how far ahead you take bookings, how walk-ins are slotted between them, and who is allowed to overbook a doctor.
• Daily collection or cash book: who counts, at what time, against what, and who signs.
• Pharmacy stock register, if you dispense: batch, expiry, and whether you track by strip or by unit. This one decision determines how painful stock will be forever.
• Lab register: sample number, collection time, report ready time, who handed the report over.
• Referral register: which doctors and which clinics send you patients. If nobody is keeping this, start today on paper.
• Staff attendance and duty roster, especially if you run more than one shift.

3. Roles: who is allowed to do what

Write this table out for your own clinic before a vendor writes it for you. The right-hand column is the one that matters, and it is the one nobody fills in until after something goes wrong.

4. The billing and tax details you will be asked for on day one

Collect these into one sheet now. Every one of them will be asked for during setup, and hunting for them mid-configuration is how clinics end up with a live system carrying a typo in the registered name.

• The legal entity name exactly as registered, plus the trade name if they differ. The invoice must carry the registered one.
• Your tax registration number, if you have one, and the exact format it must be printed in.
• Your place of supply — state, or emirate — because it decides how tax is presented on the invoice.
• Which of your services are taxable and which are exempt in your jurisdiction, confirmed by your accountant in writing. Do not let a software vendor decide this for you, and do not let this checklist either.
• The invoice header: address, phone, registration numbers, and any statutory line your accountant requires.
• Payment modes you actually accept — cash, UPI, card, bank transfer, insurance or corporate credit — and who is allowed to record each.
• Discount authority: the maximum a front-desk staff member can give without approval, and who approves the rest.

5. The records you already have

• How many active patients do you have? Decide what "active" means first — seen in the last twelve months is a reasonable default — because the answer changes the migration by an order of magnitude.
• What form are they in: paper files, an Excel sheet, an old system, or all three in different rooms?
• If there is an old system, can it export? Ask that question before anything else. Answer it before you sign with anyone new.
• Do you hold scans, photographs or documents attached to patients, and are those files retrievable separately from the records?
• What comes across and what gets archived? Decide per category, not as one decision.
• Who checks a sample after migration? Name that person now, and pick twenty records they personally know.

6. The week before go-live

• Decide how many days you run both systems in parallel, and keep it short. Anything past a week and staff quietly stop doing one of them, usually the new one.
• Name who is physically on the floor on day one, all day, whose only job is the software. Not the owner, who will be pulled away.
• Print the paper fallback and put it in a drawer at the desk. Everyone should know where it is before they need it.
• Warn patients that day one will be slower. A sign at the desk removes more pressure from your staff than an extra terminal would.
• Freeze the old system at a stated date and time, and tell everyone that time. "We'll stop using it gradually" is how two sets of records get created.
• Name the one person who has the authority to say stop and go back to paper, and agree in advance what would make them say it.

7. What good looks like at day 30

• Every visit is billed the same day, not caught up on Saturday.
• The cash count matches the system's day-end without an adjustment entry.
• No two patients share an ID, and nobody has a second file under a different spelling of their name.
• The doctor stops asking the front desk to find a file.
• Nobody is keeping a shadow register.

That last one is the real test. If a nurse is still keeping her own notebook a month in, the software is failing to do something she needs. Go and find out what it is before you decide she is being difficult — she is almost always right about the thing, and wrong only about whether it can be fixed.