Scan & Share
The smallest piece of ABDM and by far the most used: scan a QR at the OPD desk, share your ABHA token, skip the registration queue. Why the humblest feature won.
In one line
Scan & Share lets a patient scan a QR code at a hospital's OPD counter and share their ABHA profile instantly — so registration becomes a scan instead of a queue. It is the simplest thing ABDM does, and the thing it does most.
The number that should reframe how you think about this
By 18 June 2026, Scan & Share had issued over 23 crore ABHA-linked OPD tokens. OPD registration waits at participating facilities fell from roughly an hour to two–five minutes.
Sit with that for a second. ABDM's most architecturally interesting component is the consent manager — federated, cryptographic, genuinely ahead of most of the world. Its most used component is a QR code that saves people from standing in a line.
Why the boring feature won
This is the most useful lesson in Indian digital health, and it generalises far beyond India.
It solved a problem people actually had. Nobody queues at an OPD desk wishing for longitudinal record interoperability. They wish the line were shorter. Scan & Share attacks the thing the patient is actually experiencing, at the moment they're experiencing it.
The value is immediate and personal. Federated record exchange pays off later, maybe, if you happen to need care elsewhere. Scan & Share pays off in the next four minutes, to you, today. Adoption follows felt benefit, and felt benefit beats architectural elegance every time.
It asks almost nothing. No app switching, no consent artefact to reason about, no understanding of what a HIP is. Point camera. Done.
It's the on-ramp. Every one of those 23 crore tokens is someone using their ABHA for a real reason. The identity layer that all the sophisticated machinery depends on gets adopted because of the unglamorous feature — not because anyone explained federation to them.
If you build health software, that is the design lesson: the feature that drives adoption is rarely the feature you're proudest of.
What actually happens
- The facility displays a QR code at the counter — tied to its HFR identity.
- The patient scans it in an ABHA-enabled app.
- Their ABHA profile is shared with the facility, and a token is issued for the OPD.
- Registration is pre-filled rather than re-keyed from a form.
Note what hasn't happened: no medical records moved. Scan & Share shares an identity and gets a queue token. Pulling the patient's history is the separate, consent-governed flow. This distinction matters and is routinely muddled — sharing who you are is not sharing what happened to you.
For builders
Scan & Share sits at M1, the entry-level ABDM milestone: create/verify an ABHA and accept a scanned token. It's the cheapest possible way for an HMIS, clinic system or PHR app to join the network, which is exactly why it's where most integrations start — and why you should build it first in the Sandbox before reaching for M2 and M3.
Start where the patient's pain is. The architecture can wait its turn.