HMIS module
OPD management software
built around the queue.
Outpatient departments fail at the joins: booking that does not know the doctor is on leave, a counter that retypes the same patient every visit, and a bill assembled from three separate registers. The OPD module in Polynexus HMIS keeps all of it on one record.
In short
OPD management is the set of workflows that carry an outpatient from booking to billing: slot scheduling, registration and check-in, the consultation queue, vitals, clinical notes and diagnoses, investigation orders, prescriptions, and the final bill. In Polynexus HMIS these are modules of one system, so the consultation a doctor writes is the same record the lab, the pharmacy and the billing counter act on.
Capabilities
What the OPD module covers
Slot templates & scheduling
Define a doctor’s consulting pattern once and generate bookable slots from it. Blocking leave withdraws those slots so the front desk cannot book into a session that is not running.
Records: Doctor, SlotTemplate, Slot.
Appointments & waitlist
Book, reschedule, cancel, check in, start consult, complete or mark no-show — each as an explicit status. When a clinic is full, patients go on a waitlist that can be confirmed into a freed slot.
Records: Appointment, Waitlist.
Registration
Patient master with lookup so returning patients are found rather than duplicated, plus paperless registration where the patient submits their own details before arriving.
Records: Patient, PaperlessRegistration.
Live doctor queue
Once a patient checks in they join the doctor’s queue, which reflects actual check-ins rather than the order people happened to sit down in.
Vitals & clinical notes
Vitals recorded against the encounter, then clinical notes and diagnoses written during the consult. Notes and diagnoses are finalised explicitly, so a draft is never mistaken for a signed record.
Records: Encounter, VitalsReading, ClinicalNote, Diagnosis.
Orders & prescriptions
Investigation orders raised from the consultation become laboratory or radiology orders; prescriptions go to pharmacy against tracked stock. Neither is re-keyed at the next counter.
Records: InvestigationOrder, Prescription.
Workflow
An outpatient visit, step by step
- 01
Enquiry or direct booking
A patient calls, walks in, or submits a web enquiry that arrives through a lead webhook. Staff either book straight into an open slot or add the patient to the waitlist for a full clinic.
- 02
Slot booking against a real schedule
Slot templates generate each doctor’s bookable slots, and blocked leave removes them. The booking is made against an actual free slot, not a notional queue position.
- 03
Registration and check-in
A new patient is registered — or completes paperless registration before arriving — and then checks in. The appointment status changes to checked-in and the patient joins the doctor’s live queue.
- 04
Vitals and consultation
Vitals are recorded against the encounter. The doctor starts the consult, writes the clinical note, records the diagnosis and raises investigation orders or a prescription from the same screen.
- 05
Diagnostics and pharmacy
Investigation orders become lab or radiology orders; results are verified before release. Prescriptions are dispensed from pharmacy stock against a tracked batch.
- 06
Billing and follow-up
The bill is assembled from what actually happened — consultation, investigations, pharmacy — and settled. Afterwards the CRM sends a feedback request, and a no-show or follow-up task is raised if needed.
Reporting
What the OPD data tells you afterwards
Because bookings, consultations and bills sit in one system, these come out as reports rather than as a monthly reconstruction.
- OPD snapshot — current outpatient volume and status.
- Department and doctor volume — who is actually seeing how many patients.
- Doctor revenue and revenue by source — what each consultant and each acquisition channel brings in.
- No-show effectiveness — whether reminders and callbacks are changing attendance.
- Enquiry funnel — how many enquiries became appointments, and where the rest were lost.
The last two come from the hospital CRM sharing a database with the OPD schedule — which is why they can be produced at all.
FAQ
OPD management — common questions
- What does OPD management software actually do?
- It runs the outpatient department end to end: publishing each doctor’s bookable slots, taking appointments, registering and checking in patients, holding the live queue, recording vitals and the consultation, raising investigation orders and prescriptions, and passing the visit to billing. In Polynexus HMIS all of that is one record rather than a booking tool bolted to a billing package.
- How are doctor slots generated?
- From slot templates. You define a doctor’s pattern once — days, timings, consultation length — and the system generates the bookable slots from it. Blocking leave removes those slots, so the front desk cannot book into a session the doctor is not running.
- What happens when a clinic is full?
- The patient goes on a waitlist against that doctor. When a slot frees up through a cancellation, the waitlist entry can be confirmed into it rather than the slot silently going unused.
- Can patients register before they arrive?
- Yes. Paperless registration lets a patient submit their own details ahead of the visit, so the counter is verifying a record rather than typing one from scratch while a queue builds behind them.
- How are no-shows tracked?
- No-show is an explicit appointment status, not an absence of data. Because it is recorded, the no-show effectiveness report can show whether reminders and callbacks are actually reducing them.
Watch an OPD visit run end to end
We will book, register, consult, order, dispense and bill on a live system — using your clinic's own sequence.