The patient flow that actually happens in a clinic

Ask a clinic manager to describe the patient journey and you will get a clean line: arrive, register, see the doctor, leave. Stand in the waiting room for an hour and you will see something else — a patient who has been called for vitals but wandered to the pharmacy, a walk-in who has been waiting longer than the 3 p.m. appointment sitting next to them, and a receptionist answering the same question forty times.

The gap between those two pictures is where queue management earns its keep. Not by making the line shorter — by making it legible.

Where a clinic queue usually breaks

1. Walk-ins and appointments are two queues pretending to be one

Most clinics run a booking system and a waiting room, and the two do not speak. The 3 p.m. appointment arrives at 2:50 and joins a room full of people who arrived at 2:15 without one. Whoever is loudest tends to win.

The fix is not to favour one over the other. It is to give both a token from the same pool, with a rule that says what happens when they collide — an appointment gets priority within a fifteen-minute window of its slot, and reverts to walk-in order outside it. Written down once, applied every time, visible to everyone on the board.

2. The second stop is invisible

A patient who has finished with vitals is not finished. They need a doctor, and often a lab or a pharmacy after that. If each stop issues a fresh ticket, the patient effectively rejoins the back of a new queue at every door, and the total visit time is the sum of four separate waits.

Carrying one token through the whole visit changes the arithmetic. The lab knows the patient is coming before they arrive, and the token keeps its place in the sequence.

3. Nobody knows what “soon” means

A wait feels twice as long when it is unquantified. The single cheapest intervention in any clinic is a screen that shows the token being called and the room to walk to. It does not reduce the wait by a second. It reliably reduces complaints about the wait.

What the flow looks like with AxisQMS

The patient scans a code at the entrance, or touches a kiosk, or is checked in by reception — whichever suits your front door. They pick what they came for. A token is issued with a prefix that identifies the service, and it lands on their own phone.

From then on, the token is the patient. It appears on the wall display when called, moves between departments without restarting, and closes when the visit is done. At the moment it closes, a one-tap survey goes to the same phone.

What to measure in the first month

• Wait by service, not by clinic. An average across the whole practice hides the one service that runs forty minutes long.
• Handling time by practitioner. Not to rank people — to staff correctly. A doctor who genuinely needs eighteen minutes per patient should be scheduled for eighteen.
• The abandonment hour. The slot where tokens are issued and never served tells you exactly when the room gives up.
• Score against counter. Satisfaction that drops at one station is an operational problem, not a mood.

A note on privacy

Names do not belong on a waiting-room screen. Tokens exist precisely so that a room full of strangers can be organised without announcing who is seeing which specialist. Keep the display to token and room, keep the identity in the console behind role-based access, and keep the audit log for the people who need it.