The Uttar Pradesh gap: what 15.3 crore ABHA accounts in one state reveals about the other twenty-seven.

India's Ayushman Bharat Digital Mission crossed 90 crore ABHA health accounts in mid-2026 — up from 14.7 crore when the mission launched in 2021, a trajectory few digital identity systems anywhere have matched. But the number that matters more than the total is its distribution. Uttar Pradesh alone accounts for over 15.3 crore of them — more than double Rajasthan or Maharashtra's 7.1 crore each, and nearly triple Bihar's 6.3 crore.

That's not a story about Uttar Pradesh having more ambitious health policy than Bihar or Kerala. ABHA is a national mandate; every state is working from the same rules, the same registration app, the same eligibility criteria. What varies is facility-level integration, registration workflows at the point of care, and frontline capacity to actually process the sign-up — the layer a central mission can specify but can't build state by state. Bihar's own "Scan & Share" rollout for digital OPD registration shows the pattern in miniature: individual states adopting the same national tool through very different local implementations, with very different results.

What "facility-level integration" actually means

On paper, ABHA registration takes under two minutes: a facility scans a QR code or enters a name, date of birth, and mobile number, and an account is issued. In practice, that two minutes depends on a chain of things a national mission has no direct control over — whether the facility's front desk has a working device and connection at that moment, whether the person staffing it has been trained on the workflow or is filling in for someone who was, whether the facility's own registration system is wired to ABDM at all or bolted on as an afterthought, and whether creating the account is treated as the actual point of the visit or as an optional extra competing with a queue of patients. Multiply that chain by every primary health centre, sub-centre, and urban dispensary in a state, and the aggregate ABHA count becomes less a measure of policy intent and more a measure of how well that chain was engineered, district by district.

This is also why the gap doesn't close on its own with time. A state that started slow because of weak facility-level integration doesn't automatically catch up as the national number grows — it needs someone to go district by district and fix the actual chain, the same way Uttar Pradesh's own rollout had to.

Why the KPI a Health Secretary should track isn't the one usually reported

For a Health Secretary, the real KPI isn't whether the mission is technically live in the state — it almost certainly is. It's whether it's actually being used at the facility a citizen walks into today. A state can report near-universal ABDM "coverage" in the sense that every facility has been onboarded to the platform, while the on-the-ground registration rate at half those facilities tells a completely different story. Closing that gap is a workflow design, frontline training, and district-level integration-debugging problem. It has very little to do with writing better policy, because the policy was never the bottleneck — it's identical in every state.

This is precisely the layer Technology Advisory and Training & Enablement are built to work on together: the first to define the district-by-district KPI framework that actually measures adoption rather than nominal rollout, the second to close the facility-level training and workflow gaps once they're visible. Neither is a policy exercise — both are the unglamorous, district-by-district engineering work that turns a national mandate into a number that means what it claims to mean.