Updated on 22 June 2026
OPD management software for Indian hospitals — workflow, features and compliance
A practical guide to OPD management software for Indian hospitals — patient registration with ABHA, appointment scheduling, token and queue management, consultation workflow, electronic prescription with drug interactions, lab and radiology ordering, integrated billing with GST, NABH compliance requirements and ABDM integration.
OPD is the front door of every Indian hospital. It handles the highest patient volume, creates the first impression, and is where billing errors are most immediately visible to the patient. A busy 100-bed hospital sees 200–500 outpatients per day. Each patient touches between four and seven departments in a single visit: registration, queue, consultation, prescription, laboratory or radiology (if ordered), pharmacy, and billing. The sequence takes 45 minutes in a well-run hospital and 3 hours in a poorly run one. The difference is almost entirely a function of how well the software manages the workflow.
Most Indian hospitals outside metro chains run their OPD on a combination of paper token systems (numbered slips torn from a pad), register books (the "OP register" — a large bound ledger with handwritten patient entries), standalone billing software (often a desktop application that handles invoicing but nothing else), and disconnected department systems (the lab has its own software, the pharmacy has its own, each with its own patient ID). This arrangement collapses at scale: above 150 patients per day, the queues become unmanageable, duplicate registrations multiply, missed charges accumulate, and the data required for NABH quality indicators is either unavailable or requires days of manual collation to produce.
This guide covers what OPD management software must do for an Indian hospital — the complete patient flow, the queue management problem, the compliance requirements under NABH and ABDM, the integration architecture, and the practical criteria for vendor evaluation.
The eight-step OPD patient flow
A complete OPD system manages the patient from arrival to departure across eight linked stages. Gaps at any stage create manual workarounds that negate the purpose of the software.
Step 1 — Registration
First visit: create a new patient record with a unique hospital ID (UHID). Capture demographics (name, age, gender, address, phone), emergency contact, insurance or TPA details, known allergies (critical for later drug interaction checking), and ABHA ID if available. For ABDM-linked registration, the system verifies the ABHA number or address against the ABDM gateway and auto-fills demographics — eliminating re-keying and reducing registration time to under 30 seconds for verified patients.
Returning patients: search by UHID, phone number, ABHA ID, or name. The system displays the complete visit history, any outstanding bills, pending lab results, and the last consultation notes. Registration for a returning patient should complete in under 45 seconds — if it takes longer, the system is slower than the paper register it replaced.
NABH AAC.1 requires a standardised registration process with mandatory fields. The system must enforce these mandatories — not allow the registration operator to skip emergency contact or allergy history because the queue is long.
Step 2 — Appointment and queue
Walk-in patients receive a token in the doctor's queue, sequenced by arrival order with priority flags for emergencies and elderly patients (NABH AAC.6 — priority for vulnerable populations). Appointment patients — booked via phone, the hospital website, WhatsApp, or a patient app — receive a confirmed time slot with an estimated wait time, and are placed in the queue at their scheduled position.
The scheduling engine must handle: multiple doctors with overlapping or staggered schedules, doctor-specific slot durations (a cardiologist may need 20 minutes per patient, a general physician 8 minutes), department-specific clinic days (orthopaedics on Monday/Wednesday/Friday, gynaecology on Tuesday/Thursday), emergency walk-in priority insertion without disrupting the entire queue, and real-time queue status communication to waiting patients.
Step 3 — Triage and vitals
Before the consultation, a nurse records vitals: blood pressure, pulse rate, temperature, SpO2, weight, and height (for BMI calculation and paediatric dosing). For certain specialties — diabetes clinic, cardiac rehab, antenatal — additional measurements apply (blood glucose, ECG, fundal height). The vitals must be available on the doctor's consultation screen before the patient enters the room.
Step 4 — Consultation
The doctor sees the patient's complete history on one screen: vitals (just recorded), previous visit summaries, current medications, allergy list, last lab and imaging results, and any referral notes. The doctor records: chief complaint, clinical notes (structured template or free text — structured is better for NABH COP.2 compliance), diagnosis (ICD-11 coded), prescription (selected from the hospital formulary with drug interaction and allergy checking), laboratory and radiology orders, procedure orders (if any), and follow-up date.
The consultation screen is the most used screen in the entire hospital system. It must load in under 3 seconds on a 2 Mbps connection. If it takes 8 seconds, the doctor will go back to paper prescriptions within a week — and the entire investment in the system loses its clinical value. Speed is not a technical detail; it is the adoption determinant.
Step 5 — Prescription
The electronic prescription flows immediately to the pharmacy dispensing queue. The pharmacist sees: the prescribed drugs with dose, route, frequency and duration; the patient's allergy list; any drug interaction alerts the doctor may have acknowledged and overridden; and stock availability per drug. For Schedule H1 drugs, the system forces the pharmacist to capture the register fields (prescriber, patient, drug, quantity) at dispensing. For NDPS drugs, the narcotics register is updated automatically. The patient collects medicines from the pharmacy counter.
Step 6 — Laboratory and radiology orders
Lab orders flow electronically to the laboratory information system. The LIS generates barcode labels, the phlebotomist collects the sample (at a dedicated OPD phlebotomy station or at the lab), and results flow back to the doctor's dashboard after pathologist validation. Radiology orders flow to the RIS for scheduling. The patient does not carry paper request forms between departments.
Step 7 — Billing
All charges from the visit — consultation fee, procedure charges, pharmacy items, lab tests, radiology — aggregate on a single bill. The system auto-applies: the consultation fee per doctor category, the correct GST rate per line item (pharmacy at 5% or 12%, diagnostics at 18%, consultation exempt or taxable depending on hospital structure), TPA and insurance discount schedules, and package billing for health check-ups. The bill prints as the correct document type — Tax Invoice or Bill of Supply per CGST Rule 49 — based on whether any taxable items are present.
Step 8 — Payment and follow-up
Payment modes: cash, UPI (static QR at the billing counter), card (POS terminal integration), or TPA/insurance settlement. The system generates a receipt showing payment mode, GST breakup, and any outstanding balance for TPA patients (co-pay tracking).
The system schedules the follow-up appointment and enters it into the reminder workflow. An automated reminder goes to the patient 24 hours before the appointment via SMS or WhatsApp.
Fig 1. The eight-stage OPD patient flow. Each stage is linked — no paper handoffs between departments.
Queue management — reducing the wait
The single largest patient complaint in Indian hospital OPDs is wait time. Software cannot eliminate the wait (that requires more doctors or shorter consultations), but it can make the wait predictable, transparent and manageable — which changes the patient experience fundamentally.
Real-time queue display. A screen in the waiting area — or a WhatsApp message pushed to the patient's phone — showing the current token number being seen, the number of patients ahead, and the estimated wait time. A patient who knows they have a 40-minute wait can visit the canteen, step outside, or use the time productively instead of sitting anxiously in a crowded corridor.
Smart slot allocation. Not all consultations take the same time. A medication review follow-up takes 5 minutes. A new patient with multiple complaints and investigations to review takes 20 minutes. A first-visit geriatric patient may need 30 minutes. The scheduling engine should support variable slot durations by visit type — first visit, follow-up, review, procedure — rather than fixed 10-minute slots that cause systematic delays by mid-morning.
Doctor delay management. When a doctor is running 30 minutes behind schedule (because a complex case took longer, or because rounds ran over), the system should auto-notify the upcoming 5–10 patients via SMS or WhatsApp: "Dr. Sharma is running 30 minutes behind schedule. Your revised estimated time is 11:45 AM. Would you like to reschedule?" This requires real-time integration between the consultation module (which knows when the doctor finishes each patient) and the queue notification system.
Multi-department routing. A patient who needs registration → consultation → lab → pharmacy → billing touches five departments. Each has its own queue. The system should generate a routing slip (printed or mobile) showing the sequence, the location of each department, and the estimated time at each stop. This prevents patients from wandering the hospital asking "where is the lab?" and reduces the feeling of being lost in a bureaucratic process.
NABH 6th edition requirements for OPD
NABH 6th edition has specific objective elements under AAC (Access, Assessment and Continuity of Care) and COP (Care of Patients) that apply directly to OPD operations.
AAC.1 — Registration process. The hospital must define and display a standardised registration process. The software must enforce mandatory fields — patient name, age, gender, contact number, emergency contact, and allergy history. A registration screen that allows the operator to skip allergy history because the queue is long creates a patient safety gap that the NABH assessor will find.
AAC.3 — Assessment timeframe. Patients must be assessed within a defined timeframe from registration. The standard for most hospitals is 30 minutes for routine OPD and 15 minutes for urgent cases. The system must track the actual time-from-registration-to-consultation for every patient and generate reports showing: average wait time by day and by doctor, percentage of patients seen within the target timeframe, and trend data over weeks and months. If the system cannot produce this report, the hospital cannot demonstrate AAC.3 compliance to the assessor.
COP.2 — Structured clinical assessment. The consultation note must follow a defined structure — not unstructured free text. At minimum: chief complaint, relevant history (medical, surgical, drug, allergy, family), physical examination findings, working diagnosis (ICD-11 coded), plan (investigations, medications, procedures, referrals), and follow-up instructions. Template-driven consultation notes ensure consistency and make quality auditing possible.
COP.7 — Medication orders. Every medication order must be complete (drug name, dose, route, frequency, duration), legible (electronic prescriptions are inherently legible), and verifiable (the pharmacist can read the order without calling the doctor to decipher handwriting). Electronic prescriptions from the OPD module satisfy all three requirements by design. Paper prescriptions satisfy none of them reliably.
ABDM integration in OPD
The OPD registration desk is the primary ABDM touchpoint in the hospital. ABDM integration in OPD means three things:
ABHA verification at registration. The patient provides their ABHA number or ABHA address. The system verifies it against the ABDM gateway, matches demographics (name, gender, year of birth), and auto-fills registration fields. This eliminates duplicate patient records across hospitals and reduces registration data entry.
HIP data push. After the consultation, the system generates a structured OPD record — as a FHIR R4 Composition resource — and registers it as available for sharing through the ABDM Health Information Exchange. The patient controls who sees their data through the ABDM consent framework. The hospital does not share data without explicit patient consent.
HIU data pull. The consulting doctor can request the patient's health records from other ABDM-linked hospitals — previous prescriptions, lab results, discharge summaries, imaging reports — with the patient's consent. This is critical for continuity of care when patients move between hospitals (which happens frequently in tier-2/3 cities where patients may see a local doctor for routine care and travel to a city hospital for specialty consultations).
Teleconsultation as an OPD extension
The NMC Telemedicine Practice Guidelines 2020 (published as Appendix 5 of the Indian Medical Council Regulations) made teleconsultation legally permissible for registered medical practitioners in India. For OPD software, teleconsultation should be a native workflow mode — not a separate application.
The patient books a video consultation slot through the same scheduling engine. The doctor accesses the same patient history, prescribes from the same formulary (with NMC restrictions — Schedule X drugs cannot be prescribed via teleconsultation, and certain Schedule H drugs are restricted for first consultations), and the bill follows the same GST logic. The consultation record is stored in the same EMR as an in-person visit, with a flag indicating it was conducted via teleconsultation.
For tier-2/3 hospitals, teleconsultation extends specialist reach to patients in surrounding rural areas who cannot travel for a 10-minute follow-up. The practical requirement: the video must work on the patient's phone (Android, 4G) and the doctor's tablet. Browser-based WebRTC (no app install required) is the minimum. Recording and storage must comply with DPDP Act 2023 consent requirements.
Patient engagement and follow-up compliance
The OPD visit is a 10–20 minute interaction. The patient's care journey between visits — medication adherence, diet compliance, exercise, follow-up attendance — happens entirely outside the hospital. OPD software can bridge this gap through automated engagement workflows.
Appointment reminders: SMS or WhatsApp 24 hours before a scheduled follow-up. Simple, low-cost, and effective — no-show rates drop 15–25% with automated reminders.
Medication reminders: For chronic patients (diabetes, hypertension, epilepsy), daily or weekly medication reminders via WhatsApp. Optional — requires patient consent.
Lab test due alerts: For protocol-driven chronic care — quarterly HbA1c for diabetics, annual lipid profile for cardiac patients, annual eye screening for diabetics, periodic LFT for patients on hepatotoxic medications — the system should track whether the protocol tests have been done within the prescribed interval and alert both the patient and the clinician if they are overdue.
Follow-up compliance tracking: Scheduled follow-ups vs completed follow-ups per department and per doctor. Lapsed patients — those who have not visited within the expected follow-up window — should be identified and flagged for outreach. A re-engagement workflow: WhatsApp at 7 days overdue, SMS at 14 days, phone call task assigned to the CRM team at 30 days.
Follow-up compliance rate is itself a NABH quality indicator. The system that tracks it automatically also generates the evidence for accreditation — a dual benefit from a single data point.
What to ask an OPD software vendor
Register a new patient in under 60 seconds, including allergy capture. Show me an ABHA verification at registration. Display the queue management screen — current token, estimated wait, doctor delay notification. Load the consultation screen over a throttled 2 Mbps connection — if it takes more than 3 seconds, the system will not be adopted by your doctors. Generate a prescription with a drug interaction alert firing — is the alert graded by severity? Write an order for a lab test and show it arriving in the lab module without paper. Generate a multi-department OPD bill with correct GST per line item — Tax Invoice and Bill of Supply switching automatically. Show me the NABH AAC.3 report: average registration-to-consultation time by day and by doctor for the last 3 months.
If the registration takes 3 minutes, the consultation screen takes 10 seconds, the queue is just a token number display, or the billing requires manual GST rate entry — the system will slow your OPD down, not speed it up. The comparison benchmark is paper: if the software is not measurably faster and more accurate than the paper workflow it replaces, it has no business being in production.
OneCity's OPD module covers the complete eight-stage flow — ABHA-linked registration, smart queue management with WhatsApp notifications, sub-3-second consultation screen, electronic prescription with interaction alerts, electronic lab and radiology ordering, integrated billing with GST auto-application, and NABH evidence generation — designed to work at 2 Mbps on Android tablets. See it in a walkthrough →
Frequently asked questions
What is OPD management software?
OPD management software handles the complete outpatient workflow in a hospital — patient registration (including ABHA ID verification), appointment scheduling, token and queue management, doctor consultation with structured clinical documentation, electronic prescription with drug interaction checking, laboratory and radiology ordering, pharmacy dispensing, and integrated billing with correct GST treatment — in a single system.
How does OPD software reduce patient wait time?
Through real-time queue display (screen in waiting area or WhatsApp notification showing current token and estimated wait), smart slot allocation based on visit type (follow-up vs new patient), doctor delay auto-notification to upcoming patients, and multi-department routing that sequences the patient through registration, consultation, lab, pharmacy and billing with estimated times at each stop.
What NABH 6th edition requirements apply to OPD?
NABH 6th edition requires: standardised registration with mandatory fields including emergency contact and allergy history (AAC.1), patient assessment within a defined timeframe with tracking (AAC.3), structured clinical documentation following a defined template (COP.2), and complete legible medication orders — satisfied by electronic prescriptions (COP.7). OPD software must generate evidence for all four.
Is ABHA ID verification mandatory in hospital OPD registration?
ABHA verification is not universally mandatory as of 2026. However, it is becoming a condition for PMJAY empanelment and is expected for CGHS-empanelled facilities. ABDM integration at OPD registration eliminates duplicate patient records across hospitals, enables health record sharing through the consent framework, and prepares the hospital for the expected mandate.
Can OPD software handle teleconsultation under NMC guidelines?
Yes, if the system supports teleconsultation as a native workflow — same scheduling engine, same clinical history access, same formulary, same billing logic. NMC Telemedicine Practice Guidelines 2020 (Appendix 5 of IMC Regulations) permit teleconsultation for follow-ups and certain first consultations, with restrictions on Schedule X drug prescribing and certain Schedule H drugs for first consultations.