ABDM defines a clear, staged path from basic patient identification to full health data interoperability. Know exactly where you stand and what's next.
Your milestone map
Three stages to interoperability
M1 → M2 → M3: progress you can measure
M1
Identity
M2
Records
M3
Exchange
Every facility moves through three milestones — M1, M2, M3 — each unlocking deeper integration with India's digital health network.
ABHA creation and verification establish patient identity.
FHIR-linked records make health history retrievable.
Consent-based sharing unlocks network interoperability.
Every facility moves through three milestones. Each one unlocks deeper integration with India's digital health network.
Patients get a verified 14-digit ABHA ID during registration, via Aadhaar or mobile OTP.
What's required
ABHA creation flow at intake, ID verification, and basic demographic linking.
Outcome
Every patient has a portable digital health identity.
Prescriptions, lab reports, discharge summaries, and diagnostic data are structured in FHIR format and linked to the patient’s ABHA.
What's required
FHIR-compliant record generation, HFR registration, and HPR verification for doctors.
Outcome
Patient history becomes structured, retrievable, and shareable.
Consented data flows both ways: your facility can request records from other providers and share yours through the Consent Manager framework.
What's required
Consent Manager integration, HIP/HIU role setup, and real-time data exchange APIs.
Outcome
Records follow the patient across the entire network.
| Capability | M1 · Foundation | M2 · Structuring | M3 · Exchange |
|---|---|---|---|
| Patient ID | ABHA created | ABHA + linked records | ABHA + records + exchange |
| Data structure | N/A | FHIR-structured | FHIR + shareable |
| Facility role | Basic registration | HFR registered | Active HIP/HIU |
| Doctor identity | N/A | HPR verified | HPR verified + active in exchange |
| Data sharing | No | Limited / internal | Full, consent-based, network-wide |
Milestones make the value of ABDM visible to your clinical, operations, and leadership teams instead of leaving compliance as an abstract technical project.
Faster insurance claims as records get more structured
Higher trust and discoverability with each stage
AB-PMJAY and corporate empanelment often require M2/M3
Reduced duplicate testing and records as exchange matures
Use this checklist to align product, engineering, operations, and compliance before your next milestone review.
Explore integration capabilitiesFacility and professional identity readiness
ABHA creation, verification, and linking
Consent request and approval journeys
FHIR-aligned record exchange
Sandbox validation and production checks
Audit visibility for important events
Audit your current workflows, count the checks you can answer “yes” to, and use the result as your starting point.
Audit
Is ABHA creation part of your registration flow?
Audit
Are your records FHIR-structured and HFR/HPR registered?
Audit
Can you request and share data via Consent Manager?
A well-defined ABDM roadmap gives every team a shared language for progress, risk, readiness, and what comes next.
Built for dependable progress
Yes. The milestones are sequential; each stage builds on the previous one.
It varies by facility size and readiness, but a phased rollout over weeks to a few months is common.
M3 is not mandatory for every facility today, but it is increasingly expected for the full benefits of interoperability.
Yes. The same integration layer supports M1 through M3 progressively, so you can start with the next practical step.
We'll assess where your facility stands today and map the fastest path to full ABDM integration.