The milestone sequence
ABDM certification proceeds through three milestones (M1, M2 and M3), each with its own sandbox tests. The glossary defines each one. Planning around the milestones, rather than around the whole specification at once, is what keeps certification predictable.
Where integrations usually go wrong
The ABDM integration developer guide covers the parts that most often cause rework: ABHA verification, asynchronous webhook handling, FHIR R4 JSON bundle structure, and ECDH encryption of exchanged health information.
What the integration sprint includes
- A production-ready ABDM gateway microservice.
- FHIR R4 schema mapping for the documents you exchange.
- ABHA authentication and a cryptographic consent engine.
- M1/M2/M3 milestone compliance and certified sandbox audit sign-off.
The fixed-scope sprint runs four to six weeks. It suits HealthTech platforms, EMR and EHR vendors, and hospital chains that need milestone compliance.
Proof: iCare
iCare is a clinical registry and cold-chain inventory platform deployed across hospital networks in Punjab and Madhya Pradesh. Its case study covers the FHIR R4 compatibility in place and the ABDM alignment roadmap for the remaining work.