The registries beneath ABHA: what Health Facility & Health Professional adoption actually measures.

Every figure on this site so far about the Ayushman Bharat Digital Mission has been about ABHA — the patient-side health account, now well past 90 crore. It's the number everyone cites, and it's real. But ABHA is only one of three registries ABDM is actually built on. The other two — the Health Facility Registry, which records which hospitals, clinics, and diagnostic centres are verified and onboarded, and the Health Professional Registry, which does the same for doctors, nurses, and allied health workers — are the supply side of the same system. An ABHA number identifies a patient. It means very little operationally unless the facility that patient walks into and the professional who treats them are also registered, verified, and actually exchanging data through the network.

As of 6 February 2025, government reporting put ABHA at 73.98 crore accounts, HFR registrations at 3.63 lakh facilities, and HPR registrations at 5.64 lakh professionals — with 49.06 crore health records linked to an ABHA account. By August 2025, later reporting citing the same government source put HFR at roughly 4.19 lakh facilities and HPR at roughly 6.80 lakh professionals. Both registries grew. Neither grew anywhere close to the pace of ABHA itself, and neither is remotely close to India's actual count of health facilities and licensed health professionals, which run into the tens of lakhs and low crores respectively.

The number inside the number: 1.59 lakh, not 3.63 lakh

The more consequential figure in the same February 2025 reporting is easy to miss next to the headline registry counts: of the 3.63 lakh facilities registered on HFR at that point, only about 1.59 lakh — under half — were reported as actually using ABDM-enabled software. Registering a facility on HFR verifies that it exists and qualifies for the network. It does not, on its own, mean the facility's own systems are wired to actually transact through ABDM — issue a digital prescription that flows into a patient's ABHA-linked record, or pull up a patient's existing history at the point of care. A facility can sit on the registry as a verified entry for months without a single one of its encounters ever touching the interoperability layer it's nominally part of.

This is the same registration-versus-adoption gap the Uttar Pradesh brief describes on the patient side, playing out on the supply side instead. An ABHA account issued at a facility's front desk is a real, countable outcome. A facility "onboarded" to HFR that isn't running ABDM-enabled software is a real registration and a largely notional participant in the network it's registered to. Both look identical in a coverage report. Only one of them means a patient's record actually moves.

Why this is an interoperability problem, not a registration problem

The gap between HFR registration and live ABDM-enabled software use isn't primarily a sign-up problem — the registration step itself is free and takes minutes. It's an integration problem: a facility's existing hospital or clinic management system, if it has one at all, has to actually be built or configured to speak to ABDM's APIs, and a facility running a legacy system, a paper-based workflow, or no dedicated software at all has nothing to integrate in the first place. Closing this gap facility by facility is exactly the kind of architecture and integration work that doesn't show up in a registry count, because the registry only measures the step before it.

For a state health department, the practical implication is that "our facilities are on HFR" is not the same claim as "our facilities are interoperable," and a rollout plan that treats registration as the finish line will under-deliver on exactly the promise ABDM is meant to keep — a patient's record actually following them between facilities. This is squarely Tech Infra Advisory's territory: HMIS and registry integration that gets a facility from a registered entry to an actively transacting node on the network, not just a name on a list.