Skip to main content

Lost OPD Tokens and Late Arrivals: Restore the Visit, Explain the Queue

When a patient loses an OPD token, find and verify the existing arrival before printing a replacement. A reprint should identify the same visit and should not silently change queue position, create another consultation or charge another fee. Late arrival after a missed call is a separate decision that needs an explained clinic policy and a route for clinical concerns.

By Bractis · Updated · 8 min read

For Indian reception teams replacing paper slips, managing missed calls and supporting patients who step out during a busy OPD.

A token, a patient file and a visit serve different purposes

A token helps call a person in a session. A patient file connects their longitudinal records. A visit identifies today's episode of service. Treating all three as one number creates avoidable confusion when a patient returns in the evening, sees another doctor or brings yesterday's slip.

Print enough context to interpret the token: clinic or branch, session or date, and the number staff will call. Avoid placing a diagnosis or sensitive reason for attendance on a slip that can be dropped in a shared waiting area. If a code opens an online record, investigate access and expiry separately; a replacement piece of paper should not become an unrestricted access credential.

WHO's 2007 identification guidance recommends matching patients to the correct care using more than one identifier. A queue token alone cannot establish that match. Use the clinic's identification process without demanding a mobile number or exact birth date that the patient does not have.

Source: WHO: Patient Identification (2007)

Recover the existing arrival before issuing anything new

Ask for identifying details discreetly, then search the current session as well as the patient file. A patient may know a family member's shared mobile number but not their clinic number. Confirm the selected record against the person in front of you before displaying details or reading their history aloud.

Check whether the visit is waiting, already called, in consultation, completed or cancelled. A replacement token for a completed morning visit should not silently place the person in an evening queue. Ask what service they are returning for, and route that request appropriately without making reception decide the clinical significance.

If the existing arrival cannot be confidently found, use the clinic's unresolved-identity process and involve the designated staff member. Do not manufacture certainty by choosing the closest name. The unresolved case needs an owner and a way to reconcile the record later; immediate clinical needs follow the clinical pathway while registration is clarified.

  1. Locate the patient using the clinic's agreed identity checks.
  2. Locate the relevant arrival by date, session and service.
  3. Inspect its current state and any previous calls or transfers.
  4. Replace the token for that arrival, or explain why a new service request needs a different action.
  5. Confirm the calling method and what the patient should do if they miss it.

Keep reprinting separate from returning to the queue

The printing action should not choose a queue policy. A patient can lose a slip while still present, return after a missed call, or return after formally leaving. Those situations need different decisions even if all three result in a fresh piece of paper.

Document the explanation rather than a judgemental label. 'Returned from outside at 11:20; previous call at 11:08' is more useful than 'late again'. A person may have needed a toilet, an interpreter, wheelchair assistance or a quiet place to settle a child. Staff can offer help without making arbitrary promises about the next position.

Use an agreed local policy for routine missed calls, with a named escalation route for exceptions. This guide deliberately gives no universal grace period or number of places to move backward. The appropriate rule depends on staffing, service design and the patient's circumstances.

On a narrow screen, scroll the table horizontally to read all columns.

Token exceptions that should produce different actions
What happenedRecord actionWhat staff explain
Slip lost; patient still waitingReprint the same arrival and retain its stateThe visit and calling position are unchanged
Called while briefly awayRecord return; apply the agreed missed-call ruleWhere the patient will rejoin and how they will be called
Consultation already startedConfirm with the treating roomA reprint does not create a second consultation
Earlier visit completedClarify the new request and link the earlier encounter if relevantWhether this is report review, new assessment or another service
Identity or session uncertainAssign an exception owner; do not guessHow the record will be resolved and who can help

Count patients and visits, not pieces of paper

Reprints are useful operational events, but they should not inflate arrivals, consultation counts or collection totals. In a fictional session with 48 unique arrivals, six replacement prints produce 54 printed slips. The arrival count remains 48. The reprint-event rate is 6 divided by 48, or 12.5 events per 100 arrivals.

That rate is not necessarily the proportion of patients who lost a token. If one person needed two replacements, fewer than six people were affected. Keep the denominator and the event being counted explicit; otherwise staff may draw the wrong conclusion about patient behaviour or printer reliability.

Encounter identifiers and status history are distinct concepts in FHIR R4. The practical implication for a purchase demonstration is simple: ask whether printing again changes the underlying visit identifier or status. A vendor should be able to show the answer with a fictional record, not only describe the print button.

Source: HL7 FHIR R4: Encounter definitions

Give reception a short explanation that does not promise priority

Patients usually need to know whether they have lost their place, whether they must pay again and what happens next. Answer those points in the language they understand. Avoid making them retell clinical details in public to justify a replacement.

For a missed call, state the factual position and the clinic's rule, then explain the exception route. Do not say that a doctor will definitely see them in five minutes unless the responsible team can make that commitment. A rough operational estimate should be labelled as an estimate and updated when circumstances change.

Where hearing, vision or mobility makes the ordinary announcement unreliable, agree a workable calling method. Record the assistance needed at the appropriate access level. A relative's possession of a token does not, by itself, authorise disclosure of the patient's clinical record.

Test the cases that a simple reprint demo misses

Use fictional cases for a shared family phone, two identical names, the same token number in two sessions and a visit already completed. Try reprinting from two desks and verify that neither action creates a second arrival. Inspect the daily activity report as well as the screen shown to reception.

Include a printer failure after the software records the print request. Staff need to retry printing without re-registering the patient. If the printer produces two copies after a delayed response, the internal record should still identify one visit. Mark or explain a replacement where that helps staff avoid treating two slips as two people.

Finally, rehearse a patient who returns distressed or reports a new clinical concern. Reception should know how to seek clinical help without litigating the token rule first. Queue fairness and access to assessment are related but different responsibilities; a paper dispute should not become a clinical decision.

Fictional clinic example: token 27 is not a new arrival

A patient registered at 10:05 loses token 27 while still in the waiting area. Reception confirms the existing visit and reprints at 10:12, preserving arrival time and queue state. Another patient holding morning token 27 returns at 18:00 to show a report after their morning consultation was completed. Staff clarify that request instead of treating the matching token number as proof of an active evening visit. The difference is the visit context, not the ink on the slip.

Token recovery and return policy

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Number meanings
Can staff distinguish patient number, visit reference and session token when the same number appears twice?
Return rule
What is the routine missed-call policy, who can approve an exception, and how is the explanation recorded?
Replacement test
Do repeat prints preserve one arrival, one visit state and the original waiting clock?
Accessible calling
How will someone who cannot hear, read or reach the desk be called without exposing clinical information?

Questions doctors ask

Does a lost token require a new registration?

Usually the existing arrival should be recovered after identity verification. A different service or completed earlier visit may require another workflow, but a missing slip alone is not a reason to duplicate the patient or consultation.

Should a replacement token always keep the same queue position?

A replacement print by itself should not change position. Returning after a missed call is a separate decision under an explained clinic policy, with clinical concerns referred to the appropriate staff.

What if the patient has no mobile phone?

Use the clinic's alternative identity checks and arrival search. Do not insert a dummy phone or select a relative's patient record merely to print the slip.

Should reprinting create another consultation charge?

A print retry should not create a new service charge. Any actual additional service and applicable fees need separate, transparent handling under the clinic's policy.

What if the old slip is found after a replacement is printed?

Both pieces of paper should point to the same arrival. Staff should use the visit state to avoid calling or serving the same person as two separate arrivals.

Sources and scope

Updated on . Original reception guidance for Indian clinics. Queue rules, assistance arrangements and fee decisions must be defined locally; the source references do not prescribe a national token policy. No independent clinical or legal review is claimed.

  • WHO: Patient Identification (2007)

    Global patient-safety guidance, May 2007; identity-matching recommendations, not an Indian token policy. Primary text checked 25 October 2026.

  • HL7 FHIR R4: Encounter definitions

    Version 4.0.1, a fixed technical reference rather than the latest release or an Indian legal standard. Checked 25 October 2026; actual implementations differ.

Try the workflow
with Bractis.

Try a lost slip, a missed call and a token reused in another session with fictional patients. Inspect both the queue and the daily counts to confirm how replacements behave.

Request a clinic demo