A digital token system for a small doctor clinic in Rajasthan does not need the government's iHMS platform - that covers state hospitals, and a private clinic is not on it. What a small clinic can run instead is a three-level setup that costs almost nothing: a manual token pad first, a QR-plus-WhatsApp flow second, and a screen showing the live number third. Each level solves the same problem from a different budget; a Jodhpur clinic can reach level two by the weekend. The waiting room empties not because patients stop coming, but because they stop arriving earlier than needed.
Key takeaways
- iHMS is for government hospitals; a private clinic is not on it and should build its own lightweight booking and token flow.
- Level 1 is a manual token pad; level 2 adds a printed QR that issues tokens via a short form and WhatsApp.
- Level 3 puts the live number on a screen at the waiting area, which stops the 'how much longer' questions.
- Flow first, hardware last: a laptop browser and an existing TV deliver most of the benefit before any purchase.
Private clinics are not on iHMS - and that is fine
Patients often ask why their clinic cannot do what SMS Hospital does. The reason is structural: iHMS is the Rajasthan government's platform for state hospitals, covering online appointments and lab reports at facilities on the system. A small private clinic in Jodhpur sits outside it, and the options a clinic actually has are its own booking number, WhatsApp, or a lightweight queue tool. That is not a limitation so much as a different scale of problem: a clinic seeing 40-80 patients a day does not need a state platform; it needs every arriving patient to have a number, and every waiting patient to know their position. The good news is that this can be built in three levels, and the first level costs one notebook.
It also means the clinic keeps control of its own rules: the booking number, the priority policy and the way waits are quoted all stay with the doctor. Patients should treat the clinic's own booking channel as the source of truth, because portal advice written for government hospitals does not apply here.
Level 1: the manual token pad
Before any technology, establish the sequence. A numbered pad at the reception gives every arrival a token - A-01, A-02 - and the doctor or attendant calls numbers in order. Two rules make it work: exceptions (emergencies, senior citizens) are stated out loud so they feel like policy rather than favouritism, and the receptionist quotes an honest wait when handing the token ("about 25 minutes" - not "five minutes"). A whiteboard showing the number being served answers the waiting-room question silently. This level genuinely works for small clinics, and it is worth running for two weeks before adding anything, because it forces the clinic to see its own flow - where tokens pile up, which consultations run long, how many tokens are never served. The mechanics are covered in OPD queue management in India.
Two weeks on a pad also reveal which consultations overrun, which is the information a clinic needs before it quotes waits to patients. Numbered slips in a small bowl at the desk cost almost nothing and still end the argument about who was next.
Level 2: the QR plus WhatsApp flow
Level 2 moves the token from paper to the patient's phone, and it is the level most Jodhpur clinics are adopting.
- Print a QR code at the clinic door that opens a short form: name, phone number, reason for visit.
- The patient scans, submits, and receives a token number - by on-screen confirmation and a WhatsApp message.
- The clinic sends a turn update when the patient is two or three numbers away, so they can wait in the car or at home.
- Reception serves in token order and stops taking walk-ins directly into the cabin.
The whole flow runs from a phone the clinic already owns; the printed QR is the only new object in the building. Family members can also scan and submit on behalf of a parent, which keeps elderly patients out of the standing queue entirely.
Keep a paper pad next to the QR for patients who prefer it, then enter their token into the same order so nobody is served out of sequence. Print two QRs, one at the door and one at the reception desk, because patients who decide to join after entering rarely walk back out to scan.
Run a one-week pilot before paying for anything, and track the number that matters most: how many patients actually join the queue remotely on your busiest day. Whichever tool you keep, keep the paper fallback working, because the day the internet drops is the day a waiting room notices.
Level 3: the live number on a screen
Level 3 is visibility: any old TV or monitor in the waiting area, showing the token number being served and the honest estimated wait. This is what removes the last twenty interruptions of the day - the patients who ask the attendant, who asks the doctor, who loses ninety seconds of consultation time answering. The screen can be as simple as a browser window on a laptop.
- The token number being served, large enough to read from the far chair.
- An honest wait estimate derived from the last patients' actual waits.
- The cabin or department each token heads to, where more than one doctor runs.
- One line of priority policy: emergencies and senior citizens, stated openly.
When the clinic is ready for booking as well as tokens, a lightweight tool puts the same queue, an online booking page and reminders in one place - that is what SWIQ provides, and it is built to run from the clinic's existing phone. Whichever tool a clinic chooses, it should be able to demonstrate the flow on the clinic's busiest day before anything is paid for.
Refresh the screen at the start of every consultation rather than trusting a stuck page, because a stale number creates exactly the doubt the screen was meant to remove. One line on the screen about emergencies and senior citizens answering priority prevents arguments before they form. If the clinic runs more than one doctor, showing the cabin against each token saves the attendant from being the directory.
Choosing tools honestly
Two honest notes for clinic owners. First, vendors - including us - describe their products in the best light; ask any queue-tool provider to run a one-week pilot on your busiest day before committing, and to name one clinic of similar size you can call. Second, patient-facing processes change: the iHMS arrangements for government hospitals, QR flows and counter rules all move over time, so verify anything you publish for patients on the official portal or app on the day, and update your printed QR when the flow changes. For the wider clinic picture, how digital token systems improve clinic efficiency explains the numbers behind each of these three levels, and the digital front desk for Indian clinics covers what to take paperless first.
Frequently asked questions
Can a small private clinic use Rajasthan's iHMS?
No - iHMS serves government hospitals. A private clinic uses its own booking number, WhatsApp, or a lightweight queue tool. The same outcome (numbered queue, visible order, honest waits) is achievable without the state platform.
What does a QR token flow need to start?
A printed QR at the door linked to a short form, a way to issue a token number on submission, and a phone to send the confirmation and turn updates. A laptop browser and any existing TV screen complete the setup.
Will elderly patients manage a QR token?
Most manage it with one assist from reception on the first visit; keep a token pad alongside the QR for anyone who prefers paper. Mixing both streams into one numbered order is what matters, not which one the patient used.
How many patients a day justify a queue system?
Around 40-plus a day, or any clinic where the receptionist answers 'how much longer?' more than a few times an hour. Below that, a token pad and a whiteboard may be all you need.
See SWIQ in action
SWIQ gives a small clinic a live token queue, an online booking page and WhatsApp reminders that run from one phone - launch the SWIQ web app to try it.
Launch the SWIQ web app