How the milestones fit together
ABDM integration is staged. M1 covers ABHA creation and verification. M2 makes you a Health Information Provider. M3 makes you a Health Information User. You can pursue them in order and go live on one before starting the next. This checklist assumes you have read the integration overview.
Before you start any milestone
- ✓Register your facility and confirm your registry identifiers.
- ✓Get sandbox access and confirm which test credentials and environments you have.
- ✓Name an owner on both the hospital side and the technical side.
- ✓Decide where integration logs, secrets and keys will live, and who can see them.
M1 — ABHA creation and verification
- ✓Registration screens that can create or verify an ABHA.
- ✓Mapping between ABHA profile fields and your patient master.
- ✓Handling of failures, retries and duplicates. See the ABHA workflow guide.
- ✓Audit logging of every ABHA action.
M2 — Health Information Provider
- ✓Care-context creation and linking rules.
- ✓Conversion of your record types to FHIR R4 following the Indian profiles.
- ✓Consent notification handling and secure, encrypted data transfer.
- ✓Test cases covering approval, denial, expiry and revocation of consent.
M3 — Health Information User
- ✓Consent request creation with clear purpose and date range.
- ✓Receipt, decryption and validation of incoming FHIR bundles.
- ✓Storage, display and deletion rules that respect the approved purpose.
- ✓Clinician-facing screens that make external records easy to read.
Moving from sandbox to production
Teams typically run a test plan in the sandbox, record the results and then follow the onboarding process published by the National Health Authority for production access. Requirements change, so verify the latest steps rather than relying on older write-ups. Our guide to the HIP and HIU roles helps decide the order.
Frequently asked questions
Do we need to complete M1 before M2?
In practice yes, because linking records requires verified ABHA identities captured in your system.
Can the sandbox be used for load testing?
Sandbox environments are meant for functional testing. Plan performance testing on your own infrastructure.
Who certifies the integration?
Production access follows the onboarding and verification process run by the National Health Authority. Check the current process before planning dates.
Need help with this in your hospital?
Tell us your systems and your goal. We'll map it to a scoped plan.
Talk to our team →This guide is general information for engineering and planning purposes. It is not legal advice, and regulations and specifications change; confirm current requirements with the relevant authority or qualified counsel.
