ABDM Scan and Share is a QR-code registration flow for OPD counters. The patient scans a facility QR with an ABHA or PHR app, shares their ABHA profile and demographic details, and gets a queue token, all without dictating name, age, and phone number to a front-desk operator. The clinic’s registration system reads those shared details straight into the record, so check-in for that patient becomes a scan instead of a conversation.
That is the whole idea in one paragraph. What follows is how the flow actually runs at the counter, what your clinic has to have in place for it to work, and where it genuinely helps versus where the marketing gets ahead of reality.
Key takeaways
- Scan and Share is a token workflow run by the NHA: patient scans a facility QR, shares ABHA + demographics, receives a queue token.
- It cuts front-desk typing and the transcription errors that come with it, and it links the visit to the patient’s ABHA at registration.
- Your facility needs an HFR registration (an ABDM facility ID) and a Scan-and-Share-enabled counter QR from an ABDM-integrated registration system.
- It only works for patients who have an ABHA and a smartphone app; everyone else still registers the normal way.
- It handles registration and queueing, not the clinical visit. Your EMR and clinicians still do the rest.
Key facts
- Patient scans a facility counter QR
- QR
- Profile + demographics shared, no re-keying
- ABHA
- Queue token issued for the OPD
- Token
Source: NHA Scan and Share (Token) service; confirm current details on the ABDM portal.
What Scan and Share actually does at the counter
Picture a busy OPD at 9am. The old flow: patient reaches the desk, the operator asks for name, father’s or spouse’s name, age, gender, mobile number, address, keys all of it into the registration screen, then hands over a token or slip. Repeat a few hundred times before lunch. Every entry is a chance to misspell a name or fat-finger a phone number.
Scan and Share replaces the keying step. Here is the sequence:
- The clinic displays a facility QR code at or near the registration counter. This QR is tied to the facility’s ABDM identity.
- The patient opens an ABHA-enabled app on their phone, or a PHR app such as the ABHA app, and scans that QR.
- The app asks the patient to share their ABHA profile. The patient consents and shares.
- The clinic’s registration system receives the ABHA number and demographic details, and issues a queue token back to the patient.
The patient walks away with a token. The operator never typed a character for that person. And because the registration is tied to the patient’s ABHA, the visit is linked to their digital health identity from the start, which is the point of the whole exercise from the NHA’s side. Confirm the exact steps and any app-specific behavior on the official ABDM Scan and Share page, because the service is run by the NHA and the details get updated.
What your clinic needs to switch it on
Three things, and none of them are optional.
An HFR registration. Your facility must be registered in the ABDM Health Facility Registry so it has a facility ID. The QR the patient scans is bound to that identity. No HFR entry, no valid facility QR. If you have not done this yet, it is the first step, and it is separate from any individual doctor’s registration in the Healthcare Professional Registry. We cover the provider side in the HPR registration guide for doctors.
A Scan-and-Share-enabled counter QR. The QR is generated through an ABDM-integrated registration system or a supported app, not printed off a generic QR generator. It has to speak the token workflow to the ABDM gateway so the share actually lands in your registration screen.
A registration system or HMS that supports the token workflow. This is the part clinics underestimate. The QR is only half of it. Your software has to be able to receive the shared ABHA profile, populate the registration record, and issue the token. If your current registration desk runs on a spreadsheet or a system with no ABDM integration, Scan and Share is not something you can bolt on by yourself. Your HMS vendor has to build and certify it. When you ask them, make them name the ABDM milestone and say whether it is live in production or only in the sandbox, the same discipline we lay out in the ABDM Milestone 2 explainer.
Behind all three sits the ABHA-linking step itself, which is worth understanding on its own if you are new to it. The ABHA linking clinic workflow post walks through what happens when a patient’s ABHA gets tied to a visit, and the ABHA number vs ABHA address explainer clears up the two identifiers patients routinely mix up.
The benefits that hold up
Let’s be specific rather than glowing.
Faster registration for enrolled patients. For a patient who arrives with an ABHA and a working app, check-in collapses from a minute or two of back-and-forth to a scan. On a heavy OPD day that adds up across the queue, and it takes pressure off the front desk during the morning rush.
Fewer data-entry errors. Demographics come from the patient’s own ABHA profile, not from an operator hearing a name over counter noise and typing it in. That means fewer misspelled names, fewer wrong phone numbers, and fewer mismatched records to clean up later. Cleaner registration data is quietly one of the biggest wins here.
ABHA linkage from the first touch. Because registration runs off the ABHA, the visit is connected to the patient’s digital health identity at check-in rather than as an afterthought. That linkage is what makes the downstream ABDM benefits possible, and it can matter financially: the NHA’s Digital Health Incentive Scheme offers incentives for eligible ABHA-linked digital transactions above a monthly baseline, which we get into in the ABDM incentives for doctors post. Treat the specific scheme figures as NHA-defined and subject to revision; check the current terms before you bank on them.
The honest limits
Scan and Share is useful, and it is also narrower than the pitch sometimes suggests.
It needs an ABHA and a smartphone. A patient without an ABHA, or an elderly patient who does not use a smartphone, or someone whose phone is out of battery, cannot use it. Those patients still register the old way. So your counter does not disappear; Scan and Share runs beside it. Plan for a mixed queue, not an all-QR one.
Adoption varies a lot. ABHA coverage and patient familiarity differ enormously across regions and patient mixes. A tech-forward urban clinic might see meaningful uptake; a rural OPD might see very little for a while. Do not size your front desk on the assumption that most patients will scan.
It registers and queues. It does not treat. This is the one clinics most often get wrong. Scan and Share gets the patient checked in with their ABHA linked and their details filled. The consultation, the clinical note, the prescription, the diagnostics, the follow-up, all of that still runs through your EMR and your clinicians. It is a front-desk convenience, not a clinical system. If you are separately weighing an ABDM-ready record system for the clinical side, the ABDM-ready EMR software guide is the better place to start.
The QR and the software have to be right. A patient can scan a QR and get nothing useful back if the facility is not properly registered or the receiving software does not handle the token flow. Test it end to end before you tell patients it works.
Where Patient Square fits, plainly
Straight answer: Patient Square is not ABDM-certified, HFR-integrated, or Scan-and-Share-enabled today, and we will not imply otherwise. ABDM integration, including the Scan-and-Share flow, is on our roadmap, not shipped. The QR-registration conversation is one you have with your HMS or registration-software vendor, because that is the system that has to speak the token workflow at the desk.
What Patient Square does is separate from registration. Our AI scribe listens during the consult and drafts a structured clinical note, ICD-10 suggestions, and a prescription draft in about two minutes, in clean clinical English, for the clinician to review and sign. The audio is processed in memory and discarded once the note is drafted; nothing is filed or prescribed until a clinician signs it. So if Scan and Share is about getting the patient to the doctor faster, our part is about getting the note off the doctor’s desk faster once the visit starts. The two solve different halves of the same busy-OPD problem. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
If you want to see how the note comes together on a real visit, explore the workflow and run it on a clinic day. For the data-handling side, including how we approach records with DPDP Act obligations in mind, the DPDP guide for clinics and our security page lay it out. And if the front-desk load is your real pain, the AI receptionist for clinics post covers the call and scheduling side of the same desk.
The short version
ABDM Scan and Share turns OPD check-in into a QR scan for patients who have an ABHA and an app. The patient shares their profile, your system fills the record and issues a token, and nobody re-keys the basics. To offer it you need an HFR registration, a proper counter QR, and an ABDM-integrated registration system. It saves time and cuts errors for enrolled patients, it links the visit to their ABHA, and it does exactly one job: register and queue. The visit itself still belongs to your EMR and your clinicians, and if a vendor tells you their product does more than that, ask them to prove it.