Waiting to In-Consultation to Done: A Simple OPD Queue Workflow for Solo Practices (2026)

Why a solo practice needs the simplest queue possible, not a schedule

Most queue-management pitches are built for a multi-doctor OPD juggling several consultation rooms and referral streams at once. A solo practice has a different, smaller problem: one doctor, one room, and a waiting area that fills up unevenly through the day. What that practice actually needs isn't a scheduling engine: it's a reliable, visible answer to "who is next," so reception isn't holding it in their head and patients aren't left guessing whether they were skipped.

That's a much simpler problem than appointment booking, and it should stay that way. A single doctor doesn't gain anything from time slots, calendar blocks or a portal for patients to self-schedule: those add setup and upkeep for a practice that mostly runs on walk-ins anyway. The fix that actually matches a solo practice's day is a queue with exactly three states, updated in real time, on the same device the front desk already uses for billing.

The three states: waiting, in-consultation, done

HealthFlow's OP queue for a single-doctor practice has one deliberately small idea at its centre: every patient sits in exactly one of three states at any moment.

Waiting
In consultation
Done

Waiting. The patient has arrived and been added to the queue at the front desk. They're visible in the queue in the order they came in. Nothing more is needed from reception than adding their name.
In-consultation. The doctor has called them in. Reception marks the change on the same screen, so anyone glancing at the queue (the doctor between patients, a relative in the waiting area, reception itself) can see who's actually being seen right now, not who was supposed to be seen at some earlier scheduled time.
Done. The consultation is over. The patient moves out of the active queue and the next waiting patient becomes first in line automatically.

Three states, one direction of travel, no branching logic to explain to staff on their first day. For the fuller picture of how this queue behaves across a whole OPD, including a busier, multi-doctor version of the same idea, see the OPD queue management overview.

A solo practice's day, walked through

Consider a fictional example: Dr. Meera runs a single-doctor general practice out of one consultation room, with one receptionist at the front desk. A patient, Ramesh, walks in without having called ahead. Reception adds him to the queue (name, and whatever basic details the practice keeps), and he shows up as waiting, third in line behind two patients who arrived earlier.

When Dr. Meera finishes with the patient ahead of him, reception marks that visit done and calls Ramesh in, marking him in-consultation. There's no separate step to "check him in" against a booked slot, because there was never a slot to check him in against. The queue only ever reflects who has actually arrived and in what order. When the consultation ends, reception marks it done, and the patient behind him is already next.

That's the entire mechanic. It scales down to exactly one doctor without leaving any unused complexity behind: there's no schedule to configure, no time-slot calendar sitting empty, and no separate booking flow a solo practice would have to maintain but never really use.

What happens the moment a consultation is marked done

Marking a visit done isn't the end of the workflow. It's what triggers the two things that actually need to happen next at the counter.

Billing. Reception raises the bill against a sequential bill number, on the same patient record the queue was already tracking. Nothing about the visit needs to be typed in twice.
Prescription print. The doctor prints the prescription on the practice's own letterhead, with the patient's and doctor's details already filled in on the printed page. There's no separate digital prescription system to log into. It's a print, not an e-prescription.

Both steps read off the same record the queue just updated, so a solo practice isn't reconciling three different screens for one visit: the queue, the bill and the printed prescription are the same underlying patient record, viewed three ways.

The free 7-day revisit, and why it matters for a solo practice specifically

A single-doctor practice sees the same patients come back for the same concern more often than a large OPD does (a follow-up two or three days later to check whether a fever has broken, or a dressing needs a look). HealthFlow detects this automatically: if a patient returns within 7 days of a consultation for the same concern, that revisit is recognised at billing and the consultation isn't charged again.

That's an automatic free-revisit window, not a reminder system. There's no message sent out to prompt the patient to come back, and no follow-up nudge scheduled on a calendar. It only acts when the patient walks back in on their own and reception adds them to the queue as usual; from there, the system recognises the return and applies the free window without reception having to remember the date of the last visit or dig through a paper register to check.

For a solo practice, that removes a genuinely fiddly bit of front-desk memory: "did this patient come three days ago, and was it for the same thing?" It does that without adding a scheduling layer the practice doesn't need.

What this queue is deliberately not

The gap between a walk-in queue and an appointment system is exactly where expectations go wrong, so here are the edges of it, stated plainly.

If a practice specifically wants online booking or a patient-facing portal, the honest answer is that it isn't part of the OPD queue as it works today. What the queue does well is the narrower, more common problem: a single doctor, a room full of walk-ins, and a front desk that needs to know (correctly, in real time) who's actually next.

Setting it up: no new hardware, no separate queue-management staff

Because HealthFlow runs as a web app in the browser, a solo practice doesn't need a token printer, a waiting-room display, or a person hired specifically to run the queue. The same desktop, tablet or phone reception already uses for billing runs the queue: adding a walk-in and marking a consultation done both happen on that one screen, alongside billing and the patient's record.

The same record also carries into the practice's diagnostics side where one exists. A solo practice with an in-house lab, or one that refers out, is working off the same patient history rather than two separate registers. See how that shared record works on the diagnostics side.

Where this fits into HealthFlow's plans

This three-state queue, clinic billing with sequential bill numbers, prescription print on letterhead and the automatic free revisit window are part of HealthFlow's Clinic product, starting with the Solo Practice plan built for exactly one doctor. If a practice later adds doctors, the same front-desk pattern extends rather than getting replaced. For a single doctor today, the queue stays this simple on purpose.

See HealthFlow's Clinic plans, starting at ₹399/mo →

Frequently asked questions

Is this an online appointment booking system for solo practices?

No. HealthFlow’s OP queue is a walk-in queue, not a booking calendar. There are no time slots, and nothing for a patient to book online or through an app. A patient is added to the queue at the front desk when they physically arrive, then moves through waiting, in-consultation and done in the order the practice actually sees them. If you’re looking for online appointment booking or a patient self-booking portal, that isn’t part of this feature.

What happens once a patient’s consultation is marked done?

The visit is already saved to their record, so nothing needs re-entering. Reception can raise the bill against a sequential bill number, and the doctor can print a prescription on the practice’s own letterhead with the patient’s and doctor’s details pre-filled. If the same patient returns within 7 days for the same concern, HealthFlow detects it automatically at billing and doesn’t charge the consultation again.

Do I need extra staff or new hardware to run a queue as a solo doctor?

No. The queue runs in the browser on whatever the front desk already has: a desktop, a tablet or a phone. There’s no token printer, no separate queue-management staff, and nothing to install. The same person who bills the patient adds them to the queue, and moves them from waiting to in-consultation to done on the same screen.

Waiting to in-consultation to done: a simple OPD queue workflow for solo practices