Shared Patient-Intake Tablets: Privacy Between Every Session
Evaluate a waiting-room intake tablet across start, submission, timeout and reset, with a two-person privacy trial and an assisted alternative.
Move from physical tokens to a digital queue by defining what each queue state means, linking every entry to the correct patient and encounter, and rehearsing the point at which the new queue becomes authoritative. Reconcile people already waiting before switching, keep a usable interruption process and explain the calling method. A token tracks a place in a session; it is not proof of patient identity, payment or completed care.
Solo and small-team clinics replacing paper slips, plastic tokens or a handwritten OPD list with digital queue software.
A physical token often carries several meanings in staff conversation: the patient has arrived, registration is complete, the fee is paid or the doctor has seen them. Those meanings become dangerous if a digital system uses one 'done' action for all of them. Write down what the old process actually does before reproducing it.
Keep three references distinct: the person's stable patient record, today's encounter or service, and the queue position. A returning patient keeps the same identity while receiving a new session token. A patient needing another service may have more than one queue task without becoming two people in the register.
WHO's May 2007 patient-identification guidance supports using more than one identifier when matching a patient to care. A displayed token can help call someone discreetly, but the clinical team still needs its approved identity check before acting.
Do not make a smartphone a condition of joining an ordinary clinic queue unless the service's actual arrangements require it and provide an appropriate alternative. Reception should be able to explain the process to a walk-in with a paper file, a shared family number or no mobile data.
Source: WHO Collaborating Centre: Patient Identification, May 2007
Choose states that staff can observe. 'Arrived' can mean reception has recorded physical arrival; 'ready' can mean the agreed preparation is complete. Neither should automatically mean that the patient has been assessed or that a bill has been settled.
Specify who can make each transition and what happens if it was selected in error. Corrections need history and a clear current state, not silent deletion that makes the person disappear from the day's account. The exact labels may differ between products; their operational meaning should not.
Clinical prioritisation can change the order. Give authorised clinical staff a way to direct that change and reception a privacy-preserving explanation. A strict numerical sequence cannot decide urgency, and staff convenience should not be disguised as clinical priority.
On a narrow screen, scroll the table horizontally to read all columns.
| State | What it establishes | What it does not establish |
|---|---|---|
| Arrived | The patient has presented for the session | Identity and preparation are necessarily complete |
| Ready for clinician | The agreed preliminary steps are complete | A clinical assessment has occurred |
| Called | An attempt to invite the patient has been made | The patient heard it or entered the room |
| With clinician | The consultation has actually begun | The visit is clinically complete or paid |
| Next step pending | A specified service or administrative task remains | The patient can be removed from every worklist |
| Left or transferred | The observed disposition and destination are recorded | All clinical follow-through is finished |
Two independently edited queues create uncertainty about which one controls the room. During a rehearsal, compare the old and new views without treating both as live sources of truth. At the actual changeover, nominate the authoritative queue and record the time, session and people already waiting.
For a fictional cutover, 13 patients are already present: two are with clinicians, eight are ready, two are completing registration and one has stepped away under the agreed return arrangement. The total is 13. Enter each person's actual state; placing all 13 into a single waiting list would call some people twice and lose the return arrangement.
Use a cross-reference only as long as it is needed to reconcile physical tokens with the digital entries. Do not issue a second active token merely because the old number cannot be reused. Staff need to recognise the relationship and tell the patient which calling reference now applies.
After switching, a paper note made during a brief interruption must be incorporated through a named reconciliation process. It should not become a separate unofficial queue that one receptionist advances while another uses the screen.
Start with a manageable session and the real staff roles. The appropriate rollout duration depends on observed problems, training and available support. A universal three-day promise does not establish that a particular clinic is ready.
Include an early arrival, a late arrival, a patient who misses a call, two people with similar names, a person needing a quiet or visual call and someone returning from another service. These situations reveal more than a demonstration in which every patient appears exactly on time.
Define the step-away process before staff offer it. Record how the patient will return, what the clinic can promise about their place and what happens if the session changes. Any clinical concern about waiting or leaving should go to the responsible clinical team.
Do not expose diagnosis, full contact details or sensitive support information on a waiting-room display. A token and the minimum useful location cue may be sufficient for calling, while staff use a separate authorised view for identification and support.
Try an accidental double action and a connection interruption during check-in in the agreed synthetic environment. Staff need to establish whether the entry exists before creating another one. A disabled button or a spinner does not by itself prove that only one record was stored.
At consultation end, route the patient to the actual next step. A clinician finishing a note does not prove payment, a planned procedure or a follow-up booking has happened. The queue should make unfinished work findable without forcing clinically unrelated steps into one status.
At the end of the fictional pilot, 24 queue entries comprise 18 completed consultations, three still waiting at the chosen cutoff, two patients who left before consultation and one transferred for a different clinical pathway. The total is 24. The three waiting entries remain open; the transfer is a recorded disposition, not a completed consultation.
Compare the queue with the relevant encounter and service records. A person marked 'called' who has no consultation may have missed the announcement. A completed encounter still shown as waiting may indicate a missed state transition. Investigate differences instead of forcing the totals to match by deleting entries.
Review staff effort as well as patient flow: duplicate registrations, time spent finding a returning patient, repeated calls and work recorded during interruption. A digital queue is useful if it makes the real session more intelligible and recoverable, not merely if the display looks orderly.
Keep the fallback usable after rollout. Staff should know which minimum facts to record and how the recovered digital list will be reconciled. Review the process when another doctor, room or service is added; the first pilot may not have covered those interactions.
The original cutover example has two patients with clinicians, eight ready, two registering and one temporarily away. Entering them all as waiting would misrepresent the session. The later 24-entry close also separates completed consultations, waiting patients, departures and a clinical transfer.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
No fixed duration establishes readiness. Use a bounded rehearsal, resolve the observed problems and choose a changeover the staff can support.
No. The token identifies a position or task in a session. Use the clinic's approved identification process before care or document release.
Define one authoritative queue. Use comparison or temporary records through a controlled reconciliation process so two lists do not advance separately.
Record the observed situation and follow the explained calling/return process. A call attempt does not prove that the patient heard it or left.
Not necessarily. A procedure, payment, document or follow-up task may remain; track the actual next step with an owner.
Updated on . Original queue model and fictional counts. State names, recovery behaviour and clinical prioritisation must be agreed for the actual clinic. No independent clinical or legal review is claimed.
International identification guidance; a queue token and knowledge of demographics do not establish digital access authority.
Evaluate a waiting-room intake tablet across start, submission, timeout and reset, with a two-person privacy trial and an assisted alternative.
Separate actual OPD delays from uncertainty, use honest waiting updates and analyse a worked timing sample without promising a fixed improvement.
Design clinic patient numbers with stable identity, legacy aliases, duplicate resolution and readable formats; distinguish local UHIDs, visits and ABHA.
Rehearse a synthetic cutover with patients already in different states, a missed call and an uncertain check-in. Reconcile the close against encounters and inspect how an interrupted paper entry is recovered.
Request a clinic demo