ABDM Explained: ABHA, Milestones M1–M3, and What Integration Means

What ABDM is trying to build

The Ayushman Bharat Digital Mission (ABDM) is India's national programme to build the digital backbone of healthcare — the health equivalent of what UPI did for payments. Its ambition is a connected system where a patient's records can follow them, with consent, from one hospital to the next, from a lab to a specialist, from a government scheme to a private insurer, without paper and without re-registration.

ABDM does not run hospitals; it defines the standards and the shared infrastructure — identity, registries, consent and data exchange — that lets independent systems interoperate. For a hospital, "being on ABDM" means its software speaks this national language, so that its records are portable and its claims and referrals can flow through the ecosystem instead of dead-ending in a proprietary silo.

ABHA: the patient's health identity

At the centre of ABDM is the ABHA — the Ayushman Bharat Health Account, a unique health identity for each individual. An ABHA is what lets records from different providers be linked to the same person reliably, the way a single identity ties together accounts across banks. It is created with the patient's participation and can be linked to their health records only with their consent.

For a hospital, ABHA changes registration from a local act into a national one. When a patient's encounter is linked to their ABHA, the record becomes part of their longitudinal health history and can be shared — on consent — with other ABDM participants. This is also the identity layer that makes structured claims and referrals trustworthy, because the record is anchored to a verified person rather than a name typed into a form.

The milestones: M1, M2 and M3

ABDM certifies a hospital's software through a series of milestones that build on each other. Milestone 1 (M1) is about identity and connectivity — the system can create and verify ABHA and securely connect to the ABDM network. This is the entry point: the hospital can identify patients in the national scheme, but deep record exchange is not yet in play.

Milestone 2 (M2) is where the record becomes interoperable. The system can create and share FHIR-compliant health records — structured, standardised documents like prescriptions, diagnostic reports and discharge summaries — through the consent framework, so a patient can actually pull their records across providers. Milestone 3 (M3) extends this into advanced interoperability, the readiness that underpins richer exchanges such as structured insurance claims through NHCX. Each milestone is a certification, and together they describe how deeply a hospital is wired into the ecosystem.

What "ABDM-integrated" should mean when you buy

Because "ABDM-ready" is a phrase every vendor uses, it pays to ask exactly which milestones a system is certified for and whether its records are genuinely FHIR-structured or merely PDFs stamped with an ABHA number. Real integration means the clinical data is captured in a structured, standardised form during care — which is the same discipline that makes NHCX claims clean and NABH evidence demonstrable. These are not three separate projects; they are the same well-structured record serving three purposes.

That convergence is the point of building on a single operating layer. Presco HOS is ABDM-integrated across M1, M2 and M3, NABH-aligned and NHCX-ready precisely because it captures one governed, FHIR-friendly record that identity, compliance and claims all draw from. For a hospital, the value of ABDM integration is not a certificate on the wall — it is records that travel with the patient, claims that settle faster, and a place in the national health network as it comes fully online.