HPR and HFR Registration: A Guide for Indian Doctors and Clinics
Prepare HPR and HFR registration with a two-clinic identity map, document-query example, verification evidence and a practical ownership handover.
ABDM Scan and Register, previously called Scan and Share, supports OPD registration by letting a patient share an ABHA profile through a facility QR code and a supported application. Reception still needs to match the attending person to the correct chart, select the visit and manage the queue. A registration token does not establish a consultation slot, clinical priority or permission to read the patient’s entire medical history.
Indian clinic reception leads planning QR-assisted registration alongside walk-ins, appointments and assisted check-in.
A clinic considering Scan and Share should first identify the current problem. Is reception repeatedly typing demographic details, creating duplicate returning-patient records or struggling to identify which arrivals still need registration? Those problems require related but different acceptance checks.
The Ministry’s published description explains a facility-specific QR code, a supported personal health record application, profile sharing and a registration token used at the counter. It describes a registration workflow. It should not be stretched into a guarantee that every later part of the OPD visit is complete.
The Ministry’s 7 August 2026 announcement uses the name Scan and Register and explicitly identifies Scan and Share as the earlier name. Older posters and manuals may therefore use the older wording for this registration service. Confirm the actual supported flow at your desk; a naming update alone is not evidence that your software configuration, token rules or downstream queue behaviour changed.
Map the handover after profile receipt. Staff need to know which person is present, whether an existing chart matches, which doctor or service they intend to see and whether a booking already exists. If those decisions remain unclear, a faster demographic transfer can simply move the bottleneck further along the desk.
Keep a clear completion definition. For example, the clinic may regard check-in as complete when the patient is matched, the correct visit is identified and the arrival appears in the appropriate queue. That is an original operational definition to adapt, not a universal ABDM token rule.
Source: MoHFW: Scan and Share OPD registration facility, parliamentary reply
Source: MoHFW: Scan and Register service announcement, 7 August 2026
Confirm the product’s supported Scan and Share scope and prerequisites with its provider. Obtain a demonstration in the stated environment before displaying a QR code at the working desk. A poster containing an attractive code does not prove that profile receipt, chart matching or token handling is configured.
Identify which facility and registration destination the displayed code represents. If the clinic moves premises, adds a desk or changes provider, review whether the code and destination remain correct. Avoid copying a code from another branch or an old demonstration simply because it scans.
Place the instructions where a patient can read them without exposing someone else’s screen. Use clear language and an assisted option. A person should not have to announce private health details across the waiting room to ask why a registration attempt failed.
Assign the desk owner and the support route for profile-receipt or token problems. Staff should be able to describe the failed stage, the non-sensitive reference and the time, rather than send a screenshot of an entire patient list to a public support channel.
A phone can contain more than one family member’s profile, and the person holding it may be accompanying the patient. Reception should confirm whose details were shared and whose visit is being registered. The phone holder and the patient are not automatically the same person.
Search for an existing clinic chart before creating a new one. A returning patient may have earlier records from a visit without ABHA or under an older contact arrangement. The new identifier is a reason to investigate a possible match, not to hide the earlier history in a duplicate chart.
When details conflict, preserve the uncertainty and use the clinic’s identity-resolution process. Do not silently overwrite a chart’s name or birth information because one incoming profile is easier to import. Similarly, do not merge two family members merely because they share a mobile number.
Once the patient is matched, identify the intended encounter. A booked patient arriving at reception should not automatically receive an unrelated new walk-in visit. Confirm the correct doctor, service and relevant booking before putting the arrival into the queue.
On a narrow screen, scroll the table horizontally to read all columns.
| What happened | What staff can establish | What still needs a decision |
|---|---|---|
| QR code scanned | A registration flow was opened | Whether the intended profile was shared |
| Profile received | The system has the supplied identity details | Whether those details match this person and an existing chart |
| Token issued | A registration reference exists in the supported workflow | The intended service, encounter and queue handling |
| Arrival recorded | The patient is present in the agreed clinic workflow | Clinical assessment and any doctor-directed priority |
A patient may scan again after seeing no clear confirmation. Reception may also try manual entry while the first profile share is still pending. The result can be two references for one intended arrival unless the clinic checks the existing attempt before creating more work.
Teach staff to distinguish “not received,” “received but not matched,” “matched but not checked in” and “already checked in.” These are investigation questions, not claims that every product exposes those exact labels. Each leads to a different next action.
Inspect the configured behaviour for token validity and repeat scans. Do not copy a universal token duration from an old screenshot. Determine what staff see when a token is no longer usable, whether a new attempt connects to the same patient and how earlier references remain understandable.
When a delayed profile arrives after manual registration, reconcile it with the existing visit. It should not trigger a second consultation, duplicate bill or extra appointment automatically. Record unsupported behaviour as an implementation gap before widening use.
Fictional test Q-16 concerns a father attending a 10:30 booking, B-9, in existing chart C-204. His daughter carries the phone. At 10:12, she mistakenly shares her own profile, creating reference T-41. At 10:14, reception identifies the father through its approved assisted process and establishes that he is the person booked. The test labels are local teaching references, not ABDM identifier formats.
A correct profile-sharing attempt for the father is still waiting to appear at the desk, so reception completes the authorized manual check-in at 10:15 and records arrival A-17 against B-9. The delayed reference T-42 appears at 10:17. Staff now have two profile references but only one intended consultation for the father. Their job is to reconcile references, not produce another chart because another message arrived.
Treat T-41 as the wrong profile for this intended visit. Do not relabel the daughter’s profile with the father’s name or merge their records. T-42 needs a confirmed link to the already established father and visit through the supported process. If that linkage cannot be demonstrated, assign an exception to the reception lead while keeping the verified arrival visible under the clinic’s normal queue policy.
On a narrow screen, scroll the table horizontally to read all columns.
| Observed event | What it means | Reception action |
|---|---|---|
| 10:12 — T-41 received | The daughter’s details were shared for a visit intended for her father. | Do not create or update the father’s chart with that profile; handle the mistaken submission through the supported correction route. |
| 10:14 — father and B-9 matched | The attending person and existing appointment are established through the assisted process. | Retain C-204 and the intended booking; no new chart solely because the QR path is incomplete. |
| 10:15 — A-17 checked in | The father’s arrival exists against B-9 using the authorized fallback. | Keep one queue entry and explain the ordinary appointment policy. |
| 10:17 — T-42 arrives late | A correct-profile reference may now relate to an arrival already recorded. | Verify and reconcile with A-17 using supported controls; do not create another visit or bill from the delayed receipt. |
The next receptionist needs to know which arrival already exists and which reference still needs reconciliation. “QR problem” is too vague: it does not distinguish a wrong person, a delayed message or an already completed check-in. Record the event time, intended service, verified local encounter and the unresolved reference in the approved internal task system.
A technical support request usually needs the failed stage, environment, relevant non-sensitive reference and observed result. Where patient-specific evidence is necessary, use the approved secure route and access limits. Do not send a full waiting-list screenshot or ask the daughter to share her personal authentication code with the vendor.
If the desk cannot establish that two references describe the same intended arrival, avoid forcing a match to clear the queue. The responsible reception lead should resolve identity or reference ambiguity through the established process. Meanwhile, use the verified registration and the clinician’s escalation route for care needs; an unresolved technical reference must not masquerade as a clinical priority decision.
Some patients will arrive without a usable smartphone, with a discharged battery, with an unfamiliar app or with a caregiver whose phone cannot complete the flow. Design the assisted route as part of reception, not as an exception that leaves the person stranded.
Use the clinic’s approved registration and identification method. If an assisted ABDM function is available, explain it and follow its actual authorization process. Do not require staff to take over private accounts or collect credentials to make the queue move.
Keep the purpose of assistance narrow. A patient who needs help registering has not thereby asked for all medical records to be retrieved or agreed to every optional digital service. Explain any separate action through its appropriate process.
Measure the experience of assisted patients as well as successful QR users. If only the QR queue becomes visible while manual arrivals remain on a loose notebook, the clinic now has two incomplete queues instead of one reliable view.
A QR token should connect to the clinic’s existing arrival and appointment policy. Explain how booked patients, walk-ins, late arrivals and people returning with reports are handled. The registration mechanism should not silently override those decisions.
Clinical urgency remains a matter for the responsible clinical team. Do not describe a registration sequence as automated triage, or promise that the first token will always be seen first regardless of circumstances. Staff need a clear escalation route when a person needs prompt clinical assessment.
Keep displayed information proportionate to queue coordination. A public display may need a token or limited arrival information rather than clinical details. Review what patients can see from the waiting area and what the reception role can access.
If the doctor is delayed, update the ordinary queue communication. A successfully issued registration token cannot guarantee an exact consultation time, and it should not prevent staff from explaining the delay through the clinic’s normal process.
For an original fictional trial, 40 people attempt QR registration. Thirty complete profile sharing unaided, six need assistance and four use the clinic’s manual route. Report those groups separately: unaided completion is 30 of 40, or 75%, not 100% of the successful attempts.
Assume each person in that trial has one intended arrival and there are four additional scan attempts caused by retries. The log then contains 44 scan attempts for 40 intended arrivals. Thirty-six people complete profile sharing, including the six assisted completions: 36 of 40, or 90%. The four manual fallbacks remain part of the reception outcome. Scan attempts, successful shares and distinct arrivals must not be used as interchangeable denominators.
Then check whether all 40 intended arrivals are accounted for once. Count unresolved matches, duplicate visits and people who needed a fallback. These measures reveal problems that a token-generation total does not show.
If measuring time, define the interval: starting the scan, receipt at the desk, completed check-in or consultation start. A shorter scan-to-token interval does not by itself establish a shorter total wait. Include failed and assisted attempts rather than selecting only the fastest examples.
Use the results to decide what needs adjustment: instructions, staff help, matching behaviour or the queue handover. The numbers above are illustrative arithmetic, not adoption statistics or a Bractis performance claim.
Consider a separate fictional timing observation: scanning starts at 10:02, the token appears at 10:03, check-in completes at 10:11 and the consultation starts at 10:45. Scan-to-token time is one minute. Scan-to-check-in time is nine minutes. Check-in-to-consultation time is 34 minutes, and the observed scan-to-consultation interval is 43 minutes. Reporting only the first interval would omit most of this patient’s observed journey.
This example does not tell us how much time the patient spent before starting the scan. If the clinic wants total arrival-to-consultation time, it must record arrival separately. Likewise, if the doctor’s clinic started late, that delay should be recorded as context rather than attributed entirely to registration. A QR pilot should identify where time accumulated before claiming to have reduced it.
Compare like encounters and retain exceptions: booked versus walk-in, first visit versus returning patient, and assisted versus unaided registration. Record the sample and observation period beside any summary. Review matching errors and missing arrivals alongside timing; a fast check-in to the wrong chart is not an improvement. The figures in this guide are teaching examples, not benchmarks for Indian clinics or evidence of Bractis performance.
A fictional adult daughter brings her father to a clinic and initially shares her own profile from the phone. Reception notices the mismatch before creating an encounter, uses the supported correction or assisted path and locates the father’s existing chart. A later repeat scan is reconciled with that arrival. The clinic records one intended visit for the father, without merging family histories or turning two tokens into two bills.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
The Ministry’s 7 August 2026 announcement identifies Scan and Register as the service earlier known as Scan and Share. Older materials may use the former name. Verify the actual registration workflow and supported behaviour in your clinic’s configuration.
Find the verified existing chart, booking and arrival first. Reconcile the delayed reference through the supported process instead of creating another consultation or bill. Keep an uncertain match assigned to an owner rather than guessing.
It is a registration reference in the supported workflow. Confirm the clinic’s booking, service selection and queue policy separately.
Do not treat demographic registration as the complete health-record exchange process. Evaluate the relevant record request, permission and receipt separately.
Provide the clinic’s approved assisted or manual registration route and account for that arrival in the same operational queue.
Check the earlier attempt and existing arrival before creating another visit. Reconcile repeated or delayed references using the product’s supported process.
No. Define the time interval and include assisted, failed and fallback attempts. Token generation alone does not measure consultation waiting time.
Updated on . The desk procedures and trial figures are original planning aids. No universal token validity, complete integration, waiting-time reduction or clinical triage capability is asserted. No independent clinical or legal review is claimed.
31 March 2023 description of QR, profile sharing, token and OPD slip; checked 28 October 2026. Historical figures are not used as current clinic results.
Explicitly identifies Scan and Share as the earlier name and describes consented profile sharing; checked 28 October 2026. National volumes and promotional waiting-time claims are not presented as local outcomes.
First-party scope; confirm current configuration, prerequisites and supported exceptions.
Prepare HPR and HFR registration with a two-clinic identity map, document-query example, verification evidence and a practical ownership handover.
Plan mixed clinic queues with explicit arrival rules, usable capacity and a six-visit example separating waiting, lateness and missing timestamps.
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
Trace a fictional QR arrival through the correct chart and booking, then repeat the scan and use the assisted path without duplicating the visit.
Request a clinic demo