ABDM & ABHA — India's health stack

In one line

The Ayushman Bharat Digital Mission (ABDM) is India's national digital-health infrastructure: not one giant database, but a federated network that lets a citizen's records — held wherever care happened — be found and shared with their consent. ABHA (Ayushman Bharat Health Account) is the 14-digit health ID that ties it together.

The building blocks

• ABHA — the citizen's portable health identity, to which records are linked.
• Registries — the Healthcare Professionals Registry (HPR) and Health Facility Registry (HFR): verified directories of who and where.
• Health Information Exchange & Consent Manager (HIE-CM) — the heart of it: a patient grants time-bound, purpose-specific consent, and data flows from a Health Information Provider (HIP) to a Health Information User (HIU) — and only then.
• Standards layer — built on FHIR R4 with NRCeS national profiles (India's profiling), SNOMED CT and LOINC.

Why it's a big deal

It's public digital infrastructure for health at population scale — the same "India stack" philosophy as Aadhaar and UPI, applied to care. Consent is architectural, not bolted on, which dovetails with the DPDP Act. For builders, ABDM compliance (M1/M2/M3 milestones) is the gateway to India's health market.

The integration milestones (M1 → M3)

ABDM certifies health solutions in graded milestones, each unlocking more of the network:

• M1 — ABHA & Scan-and-Share. Create and verify an ABHA, and let a patient scan a QR at a facility to share their token. The entry-level integration — enough for an HMIS, LIMS, PHR or teleconsultation app to participate.
• M2 — link care contexts. A provider (HIP) registers the records it holds so they become discoverable and linkable to a patient's ABHA, ready to be requested.
• M3 — health-record exchange. The full consent loop: a HIU requests records, the patient consents through the HIE-CM, and reports/EMR data flow — and only then. Solutions also pass security testing (e.g. WASA) to earn certification.

Build for it — the Sandbox

You don't integrate against production first: you build and test in the ABDM Sandbox, the official developer environment exposing the ABHA, registry (HPR/HFR) and HIE-CM APIs. An app integrates by becoming a HIP/HIU, registering with the gateway, and speaking FHIR with NRCeS profiles over the consent flow — then submits for certification. The FHIR and terminology labs here are the groundwork; India-specific ABDM exercises build directly on them.