Rolling Out a Queue System Across a Hospital OPD: A Department-by-Department Plan

Start by counting the queues, not the patients

The first number a hospital administrator quotes is daily footfall: 300 OPD patients, 500, 800. The number that decides the rollout is smaller and harder to get: how many separate lines form in the hall each morning. General medicine, orthopaedics, obstetrics, paediatrics, ENT, a sample collection counter, a pharmacy window. Each is its own queue with its own pace, and a queue management system for a hospital has to hold each one apart from the others.

Walk the OPD block at 9:30 on a weekday and write down every place a line forms, who manages it, and what a patient has to know to join it. That list is the plan. Most 200-bed hospitals come back with six to nine entries, and at least one surprise, usually a counter that nobody owns.

Give every department its own token series

Numbers that share a series cause the confusion patients remember. If medicine and orthopaedics both call "number 14", two people stand up. Each department gets a letter and its own count: M014 for the fourteenth medicine patient, OR007 for the seventh in orthopaedics. The letter also tells a lost patient which board to watch.

In TOKENN a department is a few minutes of setup: a name, a letter, its hours, its room or floor, and a QR code to print for its counter. The hospital page has a worked six-department example with the letters and the morning sequence. Set every department up before go-live, even the ones you will switch later, so the routing question on WhatsApp lists the right choices from day one.

Decide how patients reach the right department

A hospital queue fails at the door if a first-time patient cannot tell which line is theirs. Two routes cover almost everyone. A patient who knows where they are going scans the QR at that department's counter and lands in that queue. A patient who messages the hospital's WhatsApp number is asked one question, which department, and placed accordingly. Patients with no phone, or no patience for either, get a token from the counter in two taps.

Print the department QR large, at the counter and at eye level, with the department name in English and the local language. In Tamil Nadu that means Tamil, and the assistant replies in Tamil or Tanglish to anyone who writes that way. The enquiry desk is still there for the patient who needs a human, but it stops being the place everyone queues to find out where to queue.

Switch two departments first, then the rest

The rollout that works is boring. Pick one high-volume department and one quiet one, run both on the new queue for a week while the others stay on paper, and fix what the week shows: a counter staff member who issues tokens into the wrong department, a QR hidden behind a plant, a TV that nobody switched on. Then add departments two or three at a time.

The rollout that fails is the one where the whole hall changes on a Monday because the vendor was in town. Six departments, ten counter staff, and a lobby of patients learning a new system at once produces a bad morning, and a bad morning becomes the story the staff tell about the system for a year. Give the first two departments their week.

Every counter sees every queue

Larger OPDs run more than one registration desk: the main lobby counter and a satellite counter near a busy department, sometimes on another floor. If the satellite desk can only see its own department, a patient who walked up to the wrong counter is sent across the building, and the desk has become a second enquiry counter.

The rule is simple: a token issued at any counter appears on every board and on every desk at once, and any desk can issue a token into any department. Staff at the satellite desk should be able to answer "what number is orthopaedics on?" without a phone call to the lobby.

One display per floor, not one display per hospital

A single board at the main entrance listing every department's now-serving number is useful for the lobby, and useless to the patient sitting outside gynaecology on the second floor. Each floor, or each busy department, needs its own screen showing its own tokens and calling them out loud. In a hospital hall, the audio call matters more than in a small clinic: three rows back, nobody is reading a screen.

This is where the hardware budget goes, and it is small. Any TV or tablet already in the building opens the board in its browser; the TV display setup page under Features covers the three ways to do it. There is no kiosk, no LED board and no maintenance contract, which is also why a department can be added to the rollout in an afternoon.

Plan for referrals and parked patients from day one

The step that breaks most hospital token systems is "go get an ECG and come back". On paper the patient pulls a fresh number and starts again. In the rollout, decide before go-live that a referred patient keeps their token: the desk parks it in an awaiting-return lane, the patient goes to the sample counter or the ECG room, and rejoins the same queue, in turn, when the report is in hand. Clinics use the same lane for lab report reviews.

The same applies to emergencies and priority patients. A department needs a way to put someone at the front without rewriting the whole series, and the staff need to know on day one that it exists, or they will go around the system the first time an ambulance arrives. The priority token guide covers how that works at the desk.

Tell patients the doctor is late before they ask

The hardest OPD morning is not the busiest one. It is the morning a consultant is held up on the ward and forty patients are sitting outside a closed door. A paper system goes silent. A WhatsApp queue can tell every waiting patient in that department that the doctor is running late, add the delay to every estimate, and let the ones who live nearby go home and come back. Build this into the counter staff's routine: the moment a department knows it is late, it says so, once, to everyone in the queue.

What it costs, by footfall

A hospital rollout is usually priced by the vendor as a project: hardware per floor, an integration with the hospital information system, an annual contract. A queue that runs beside the HIS rather than inside it avoids most of that. TOKENN has no monthly fee and no per-department charge: one booking credit covers one patient token or appointment, bought as prepaid plans that never expire. An OPD seeing 100 patients a day uses about 2,600 credits a month, which one ₹2,999 plan covers; the hospital page has the table for 250 and 500 a day.

What TOKENN does not do is as important for the plan: it is not a hospital information system, does not manage IPD admissions, billing or records, and does not integrate with the HIS. It holds the OPD queue and talks to the patient. If the hospital needs the queue inside its HIS, that is a different and much longer project, and the queue is usually the part such suites do worst.

A rollout checklist

Before go-live: every department created with its letter, hours and room; a QR printed and posted at each counter; a TV per floor opened to its board; every counter login able to see and issue into every department; the awaiting-return lane and priority tokens explained to counter staff. Week one: two departments live, the rest on paper, one person collecting what went wrong. Week two onward: add departments two or three at a time, and start reading the numbers, average wait per department, no-shows, and how many patients arrived close to their turn. The OPD that measures those for a month usually finds its 11 o'clock crush is one department, not the whole hall, and staffs for it.

Frequently asked questions

Related guides

How to Manage Walk-in Emergencies Without Upsetting the Queue →

Lab Report Review Queues: How to Stop Issuing a Second Token →

3 Proven Strategies to Reduce OPD Wait Times in Indian Clinics →