The building blocks of ABDM
| Component | What it is | What it means for a hospital |
|---|---|---|
| ABHA | Ayushman Bharat Health Account: a patient's 14-digit health ID and ABHA address | Created or verified at registration and linked to the hospital's UHID |
| HFR | Health Facility Registry | The hospital registers itself and receives a facility ID |
| HPR | Healthcare Professionals Registry | Doctors and other professionals register individually |
| HIP | Health Information Provider | A facility that shares the records it creates, with consent |
| HIU | Health Information User | A facility that requests and views records from other providers, with consent |
| Consent manager | Service through which patients approve or deny record requests | Every record exchange is backed by a patient consent artefact |
The integration milestones (M1, M2, M3)
Software that connects to ABDM is built and tested against milestones in the ABDM sandbox before it receives production access. Integrators commonly describe them as follows:
| Milestone | Capability | Typical features |
|---|---|---|
| M1 | ABHA and identity | ABHA creation and verification, ABHA card and QR, scan-and-share registration |
| M2 | Health Information Provider (HIP) | Linking visits as care contexts, responding to consent requests, sharing records as FHIR R4 bundles |
| M3 | Health Information User (HIU) | Requesting consent, fetching and displaying records from other providers |
Milestone scope and sandbox exit criteria are set by the NHA and change over time. Check the current ABDM sandbox documentation before planning a project.
Insurance claims are exchanged separately through the National Health Claims Exchange (NHCX), which builds on the same digital-health stack.
How ABDM works at the registration counter
- The patient gives an existing ABHA (or scans the facility's QR code to share it), or staff create a new ABHA.
- The HMS verifies the ABHA and links it to the hospital UHID.
- Each OPD visit or admission is linked to the ABHA as a care context.
- When another provider requests the records, the patient approves or denies consent.
- With consent, the HMS shares the records in the standard format; without it, nothing is shared.
Steps for a hospital to get started
- Register the facility in HFR and the doctors in HPR.
- Choose an HMS that supports ABHA, care-context linking and consent-based sharing.
- Train front-desk staff on ABHA creation and verification.
- Decide which record types you will share (prescriptions, lab reports, discharge summaries).
- Inform patients how consent works and how their data is protected.
Questions to ask your HMS vendor
- Which milestones does the software support today, and are they live in production?
- Is ABHA linked to our UHID automatically, and how are duplicates handled?
- Which record types are shared, and in what format?
- What happens to ABDM requests when our internet is down?
- How are consents and data exchanges logged for audit?
HealthSysAdmin supports ABHA creation and lookup, care-context linking and consent-based sharing as a HIP, and queues gateway requests so outages do not drop them.
Frequently asked questions
What is ABDM integration?
ABDM integration connects a hospital's software to the Ayushman Bharat Digital Mission so it can create and verify ABHA numbers, link patient visits to ABHA, and share or receive health records with the patient's consent.
What is the difference between HIP and HIU?
A Health Information Provider (HIP) shares the records it creates when a patient consents. A Health Information User (HIU) requests and views records created by other providers, also with consent. A hospital can be both.
What are ABDM milestones M1, M2 and M3?
They are the stages software is tested against in the ABDM sandbox. M1 covers ABHA creation and verification, M2 covers sharing records as a Health Information Provider, and M3 covers requesting and viewing records as a Health Information User.
Can a patient refuse to share records through ABDM?
Yes. Records are shared only when the patient approves a consent request, and the patient can deny or revoke consent.