Around 86.6 crore ABHA accounts existed as of March 2026. Roughly 2.57 lakh facilities were actively using ABDM-enabled software. Both numbers are large. The ratio between them tells you where the problem is: creating the identity was the easy half.
The hard half happens at a registration counter with four people waiting.
What ABHA is, precisely
A 14-digit number that identifies one person across every health facility in India. It is not a file, an insurance policy, or a card that must be produced. It is a key that lets records created in one place be found from another — with the patient's consent each time.
Two things follow from that, and both matter at the desk:
- It is voluntary. A patient can decline and must still be treated normally.
- It is not proof of anything. It does not establish eligibility, entitlement or payment. Staff who think of it as a scheme ID will use it wrongly.
Where the thirty seconds goes
Watch a receptionist do this and the time breaks down predictably.
Asking. If the script is "Do you have an ABHA number?", most patients say no — including many who have one, because they do not recognise the term. "Do you have an Ayushman health ID? It may be linked to your Aadhaar number" recovers a meaningful share of them.
Finding. Patients rarely have the number memorised. Verification by mobile number and OTP is faster than anything involving the patient searching their phone for a screenshot.
Waiting. An OTP round trip is ten to thirty seconds of dead time with a queue forming. The fix is not a faster API — it is not blocking registration on it. Register the patient, start the queue, resolve ABHA alongside.
Failing. OTP not received, mobile not linked, name mismatch. This is where adoption dies. If a failure leaves the receptionist stuck on a modal with no way forward, they will stop asking within a fortnight.
Design rules that survive contact with a queue
Never block registration. ABHA capture should be a field that can be filled now, later, or never. A patient with no ABHA must move through registration at exactly the same speed as one who has it.
One clear escape. Every ABHA screen needs a visible "skip for now" that returns the receptionist to the patient record. No dead ends.
Defer, do not discard. A skipped ABHA should leave a flag on the patient record so it can be picked up on the next visit, when the counter is quieter.
Make the failure legible. "OTP not received — the mobile number may not be linked to this ABHA" tells the receptionist what to do next. "Error 400" does not.
Do not re-ask a linked patient. Once captured, it is captured. Prompting the same patient every visit trains staff to click past the prompt.
The follow-up visit is the real opportunity
First visits are the worst possible moment: the queue is longest, the patient is new, the paperwork is heaviest. Follow-ups are the opposite — the patient is known, registration is a lookup, and there is slack in the interaction.
Clinics that capture ABHA on follow-up rather than first registration tend to see it work, because they are asking at the moment when thirty seconds is genuinely available.
A note on consent
Linking a record to an ABHA and sharing a record are different acts. Creating or verifying an ABHA at your desk does not, by itself, entitle anyone to read that patient's history from elsewhere. Fetching outside records requires the patient's explicit consent for that request.
Front-desk staff should be able to state this in one sentence, because patients ask. "Your records stay yours — nobody sees them unless you approve it each time" is accurate and usually sufficient.
Measuring whether it is working
One number: share of registrations with an ABHA captured, tracked weekly.
If it climbs and plateaus, you have found your ceiling of willing patients — fine. If it climbs and then falls, your staff have found the skip button and stopped asking, and no amount of training will fix a flow that is fighting them.
Bringing your clinic online?
See how Qlinikit and the Qlinio platform fit your workflow — book a short walkthrough.