ABDM Milestones Explained: M1, M2 & M3 for Health Software

When health software says it’s “ABDM integrated,” the real question is: to which milestone? The NHA certifies software in three stages — M1, M2 and M3 — and they mean very different things. Here’s the plain-language breakdown.

Why ABDM has milestones at all

The Ayushman Bharat Digital Mission (ABDM) certifies health software (HMIS, LMIS, EMR systems) through its sandbox in three progressive milestones. Each milestone adds a deeper level of integration, so buyers can tell how “ABDM-ready” a product really is instead of trusting a brochure.

Milestone 1 (M1) — ABHA creation & verification

M1 means the software can create, verify and link a patient’s ABHA (via Aadhaar or mobile OTP) during registration. This is the entry ticket: the clinic can identify patients by their national health ID. What M1 does not guarantee is that any records actually flow anywhere.

Milestone 2 (M2) — linking digital health records (HIP)

M2 is where ABDM becomes real. The software acts as a Health Information Provider (HIP): it can convert visits into structured digital records (prescriptions, diagnostic reports, discharge summaries) and link them to the patient’s ABHA so they appear in the patient’s PHR app and can be shared, with consent, with other providers.

In short: M1 identifies the patient; M2 makes their records portable. Under current ABDM guidance, government incentive programs for digital records have also centred on M2-enabled transactions — which tells you where the mission’s priorities lie.

Milestone 3 (M3) — using records & claims (HIU)

M3 adds the consuming side: the software can act as a Health Information User (HIU), requesting and displaying a patient’s records from other providers (with consent), and supports scheme/claims-related workflows relevant to programs like PM-JAY. M3 matters most for hospitals dealing with insurance and government scheme patients.

Which milestone does your clinic actually need?

  • Every clinic: M1-level ABHA linking at registration — patients increasingly expect it.
  • Any clinic serious about digital records: M2-level record linking, so consultations, lab and pharmacy data actually reach the patient’s ABHA.
  • Hospitals with scheme/insurance flows: M3 capabilities on top.

The question to ask your software vendor

Don’t ask “are you ABDM integrated?” — ask “which ABDM milestone does your system support in the live product, and can I see ABHA linking in a demo?” A structured, connected EMR underneath is what makes M2 possible; see what that looks like in our guide to ABHA interoperability solutions and on the VixitAi EMR page.

Frequently asked questions

What is ABDM M2?

ABDM Milestone 2 (M2) is the certification stage where health software acts as a Health Information Provider (HIP) — it can create structured digital health records (prescriptions, reports, discharge summaries) and link them to a patient’s ABHA so they can be viewed and shared with consent.

What is the difference between ABDM M1, M2 and M3?

M1 = the software can create/verify/link a patient’s ABHA ID. M2 = the software can link digital health records to that ABHA as a Health Information Provider (HIP). M3 = the software can also consume records from other providers as a Health Information User (HIU) and support scheme/claims workflows.

What do HIP and HIU mean in ABDM?

HIP (Health Information Provider) is a system that generates and shares health records — e.g. a clinic’s HMIS linking a prescription to an ABHA. HIU (Health Information User) is a system that requests and views those records with patient consent — e.g. a hospital pulling a referred patient’s history.

Does a small clinic need ABDM M3?

Usually not immediately. A small OPD clinic gets the most value from M1 (ABHA linking at registration) and M2 (records reaching the patient’s ABHA). M3 matters more for hospitals handling insurance and government scheme claims.

VixitAi HMS plans & pricing

Every plan includes free setup support, data migration and built-in ABHA/ABDM readiness — no per-user charges, no lock-in. Click a plan to sign up directly:

Prefer the details first? See the full pricing page or the live price table with the monthly/yearly toggle.

Want records that actually flow — not just an ABHA checkbox?
VixitAi HMS pairs built-in ABHA linking & consent capture with a fully structured EMR across OPD, lab, pharmacy & IPD. Plans from ₹1,999/month.
Get Started → Compare Plans →

Read next

← Back to all articles