OPD management software: a 2026 checklist for Indian hospitals

Software demos start at the registration screen. Patients start earlier, with a phone call at a quarter to nine, and finish later, when the follow-up date comes round. The parts of the day before and after the counter are where patients slip away unnoticed, and where software is often thinnest.

So don’t judge it by its feature list. Follow one patient through a normal visit, write down every hand-off, and ask the vendor to show you each step on screen with your own doctors loaded.

What should OPD management software cover?

For most Indian OPDs, a visit has nine steps:

1. A phone call, a walk-in at the counter, or a scan of a QR poster.
2. A token, and an idea of when to come.
3. The wait, and news if the doctor is late.
4. The doctor’s queue and the consultation.
5. The prescription.
6. The bill: cash, card, UPI, a government scheme or a TPA.
7. The pharmacy.
8. The follow-up visit, and a reminder before it.
9. Behind all of it, the reports your managers read.

The sections below take them in turn, with the questions to ask at each.

Booking: does every way in reach the same diary?

By phone. For many patients the visit starts with a call, and a call nobody answers leaves no trace in any register. There is no published Indian figure for how many hospital booking calls go unanswered. For a sense of scale, NHS Lothian in the UK, with staff on its outpatient booking lines, saw callers give up on 30.1% of 4,46,012 calls in a year. Ask:

• Who answers at a quarter to nine, when twenty people ring at once, and who answers at 9 pm?
• Is there a list of the calls nobody answered, with the number and the reason for each?
• Does a phone booking see exactly the same free times as the counter?

If an AI receptionist will answer the phone, test it first with these 15 calls in Hindi and Hinglish.

Walk-ins. Many OPDs run on them. Ask the vendor to register one in front of you with a stopwatch running: name, age, mobile number, doctor. Ask whether reception can overbook a full session, and whether that is recorded. A walk-in should join the same queue as booked patients, with a token and a waiting estimate of their own.

QR posters. A poster at the counter lets patients book or check in from their own phone. The government says a study by the Indian Institute of Health Management Research found its ABDM Scan and Share service cut the wait at registration from about an hour to 2 to 5 minutes, with over 23.21 crore tokens issued by June 2026. Ask whether the patient needs an app or a login, whether it works in Hindi, and who helps the patient without a smartphone.

Whatever the way in, every booking must land in one diary, the one the doctor’s queue reads from. Two diaries mean double bookings.

Tokens and waiting times: can patients see when to come?

Crowds build when everyone comes early. At AIIMS New Delhi, 79% of OPD patients arrived before 10 am, and only 19% of them had been seen by 10 am. Studies at Indian tertiary hospitals keep finding long waits for short consultations:

The question patients ask at every counter is “मेरा नंबर कब आएगा?” (when will my turn come?). A token screen is only hardware; the useful part is the answer behind it. Ask:

• How is the wait worked out: from the bookings alone, or from the doctor’s actual pace today?
• Does the patient see a range or an exact time? An exact time that turns out wrong does more harm than an honest range.
• When the doctor is late, who presses what, and which patients are told?
• When a doctor takes leave, what happens to the patients already booked?
• If the vendor quotes an accuracy figure for its waiting times, where and how was it measured?

The doctor’s queue and the prescription

Ask what the doctor’s screen shows: who is next, who has arrived, who has waited longest. Each doctor should see only their own patients. The doctor should be able to call the next patient without an attendant shouting names down the corridor, and the prescription should open from the same screen with the patient’s details already filled in.

The prescription needs its own checklist, from generic names in capitals to the patient’s copy. We cover it in E-prescription software in India: what to look for.

Billing, pharmacy and follow-ups: where do patients fall through?

Billing. Find out where the bill is made: in this software or in your HIS. If it’s the HIS, the patient should reach the billing counter already known, with name, registration number, doctor and visit type, not be registered all over again. Ask how scheme, panel and TPA patients are handled, and if the software takes payments, whose account the money goes into and who reconciles it.

Pharmacy. The prescription should reach your own pharmacy without the patient carrying paper across the building. Ask who confirms each order, and whether the patient can reorder from the same prescription later.

Follow-ups. On average about 23% of appointments are missed, in a review of 105 studies worldwide. At an Indian tertiary hospital’s OPD, the leading reasons patients gave were forgetting, and getting no reminder. Ask:

• Does the follow-up date the doctor writes become a reminder on its own?
• Which channel does the reminder use, and is it sent only to patients who agreed?
• Can the patient confirm or cancel from the reminder itself?
• Does reception get a list of the patients who didn’t come?

Reports. Ask which numbers you can see every week without asking anyone: calls and how they ended, bookings by phone, walk-in and QR, no-shows, average wait and patients per doctor.

What should “works alongside your HIS” mean?

Nearly every vendor says it works with your HIS. Ask which of these four things they mean:

Then settle four practical points:

• One owner for each record. Decide which system owns the patient’s registration number, the doctors’ schedules and the bill. If both hold a schedule, they will drift apart.
• Matching patients. Families often share one mobile number, and a name can be spelt five ways. Matching by mobile number alone can mix up a mother and her son.
• Who builds it and who pays. A connection needs work on both sides. Get both vendors to confirm in writing who builds it, who pays for it and who fixes it when it breaks.
• When one system is down. Ask what each does while the other is offline, and how they catch up.

Patient data and the DPDP Act: what to ask

Under the Digital Personal Data Protection Act, 2023, your hospital is the data fiduciary: it decides why and how patient data is used. The software vendor is a data processor, handling that data on your behalf. The Rules were notified on 14 November 2025 with an 18-month phase-in, and the main duties of data fiduciaries, including notice, consent, security safeguards, breach reporting and erasure, apply from 13 May 2027. Failing to keep reasonable security safeguards can cost up to ₹250 crore, and failing to report a breach up to ₹200 crore. A patient’s request to see, correct or erase their data must be answered within 90 days.

Ask every vendor:

• Where is the data hosted, and who at your company can see it? Is that access logged?
• How long is each kind of data kept (call text, bookings, prescriptions), and can you delete one patient’s data on request?
• Which other companies handle our data, for calls, messages or hosting?
• How is each patient’s yes to messages recorded?
• How many hours after a breach will you tell us? Put the number in the contract.

Treat badges for foreign privacy laws as marketing. The law your hospital answers to is India’s.

How to run a two-week trial

Before day one: measure a normal week

Pick one OPD with two or three doctors and a real crowd, and avoid a festival week or a week when a doctor is on leave. For one normal week, write down bookings by phone, walk-in and QR, patients seen, no-shows, and the wait for 20 patients a day, from arrival to the doctor, timed with a watch. If your phone system logs calls, note the unanswered ones too.

Week one: set it up and try to break it

1. Load your real doctors, sessions, fees and the answers to common questions.
2. Have reception put their hardest day through it: a rush of walk-ins, a late doctor, a doctor on leave, a patient who books twice.
3. Keep a list of everything that went wrong, and check what the vendor has fixed by the end of the week.

Week two: use it for real

1. Put every booking for that OPD through it, every day.
2. Spend fifteen minutes each evening with the front desk on what went wrong.
3. Measure the same things as in your normal week.

At the end, compare the two weeks number by number, and ask reception and the doctors one question: would you keep it? Before you sign, get in writing everything the trial depended on: support hours, data export, deletion and the exact scope of any HIS connection.

Where DrMate fits

DrMate’s front desk is designed around this day. Live today: every doctor’s OPD on one screen (booked, arrived, with the doctor, to call back), walk-ins in seconds, a call-back list with emergencies on top, waiting times patients see on their phone (a range before the day, then worked out from the doctor’s actual pace), a running-late button that moves every later patient’s time, and a 7- and 30-day report. Built: self check-in by QR, and doctors grouped by department for big hospitals. Optional: an online booking page and a QR poster. The AI receptionist books phone callers into the same diary.

It doesn’t make bills, take online payments or book on WhatsApp; there is an optional link to your hospital’s own UPI ID, and reception marks the payment as received. DrMate keeps its own OPD schedule, which your staff use alongside your HIS. The one connection that exists today is for prescriptions: DrMate Rx can send each signed prescription to your system as a FHIR R4 document. If you’d like your HIS connected too, talk to us, and we’ll tell you honestly what it takes.