India's national digital health ecosystem is not optional anymore. We help hospitals get ABDM-certified — from sandbox setup through M1, M2, and M3 milestone compliance — with clean integrations that work with your existing HMS.
ABHA ID creation, verification & patient registration integration
Care context linking, HIP registration & health record discovery
FHIR R4 bundles, consent management & HIU/HIP data sharing
STQC/CERT-IN testing support & Safe-to-Host certificate guidance
The Ayushman Bharat Digital Mission (ABDM) is India's government initiative to create a unified, interoperable digital health ecosystem. At its core is the ABHA (Ayushman Bharat Health Account) — a 14-digit unique health ID that links every patient's medical records across hospitals, labs, pharmacies, and clinics.
For hospitals, ABDM integration is no longer optional. It is mandatory for government empanelment under PMJAY, required for digital health record participation, and increasingly expected by patients who want their health data to travel with them — not sit locked in your server room.
The integration is structured as three progressive milestones — M1, M2, and M3 — each building on the last. DigiEn handles the full journey: from registering on the ABDM sandbox and building the API layer, to passing STQC certification and going live on production.
We integrate with your existing Hospital Management System (HMS) rather than replacing it — so your clinical workflows remain unchanged while your hospital becomes fully ABDM-compliant.
Government-empanelled hospitals — PMJAY and state scheme hospitals where M1/M2 is now mandatory
Private hospitals and nursing homes — increasing patient demand and future regulatory direction
Diagnostic labs and imaging centres — need to link reports to patient ABHA accounts
Clinics and polyclinics — OPD-based care contexts required for M2 compliance
HMS and HIS software vendors — want to offer ABDM-compliant product to hospital clients
Hospitals seeking NABH accreditation — ABDM compliance is increasingly part of the assessment framework
Each milestone builds on the previous one. You cannot achieve M2 without M1, or M3 without M2. DigiEn takes you through all three in sequence.
Creating and verifying patient digital health identities at registration
M1 is about giving every patient a unique digital health identity at the point of hospital registration. It connects your OPD or IPD registration system to the national ABHA infrastructure.
ABHA creation, Aadhaar/mobile OTP verification, demographic auth, HPR linking, HFR facility registration
Making your hospital a Health Information Provider in the ABDM network
M2 makes your hospital a Health Information Provider (HIP). Every visit, admission, lab report, and prescription becomes a "care context" linked to the patient's ABHA — discoverable by the patient and shareable with their consent.
Care context linking, patient discovery, HIP bridge callbacks, notification delivery, consent request handling
Serving and consuming health records across the ABDM ecosystem
M3 is the most complex milestone. Your hospital can now both serve health records to authorised requesters (HIP role) and request records from other hospitals (HIU role) — all through encrypted FHIR R4 bundles with patient consent.
Consent flow, health information request/response, FHIR bundle generation, encryption/decryption, HIU data fetch
Government-empanelled hospitals under Pradhan Mantri Jan Arogya Yojana are required to achieve M1 and M2 compliance. Non-compliant hospitals risk empanelment issues.
Hospitals with ABHA integration report significantly faster registration — patients scan their ABHA QR code and demographic data fills in automatically. No manual entry errors.
With M3, your doctors can pull a patient's records from any ABDM-linked hospital with patient consent — previous prescriptions, lab reports, discharge summaries — all in seconds.
ABDM compliance is increasingly part of quality accreditation frameworks. Getting compliant now positions your hospital well ahead of when it becomes a formal requirement.
ABDM's consent architecture means patient data is only shared when the patient explicitly approves. Every request is logged, auditable, and time-bound. Better than the alternative — paper records and phone calls.
Patients increasingly expect digital health services. A hospital that lets patients own and access their records is a hospital they come back to — and recommend.
We handle the full integration journey — not just the API code. That includes sandbox setup, HMS mapping, testing, and supporting you through STQC certification.
We review your existing HMS/HIS, identify integration points for ABHA, and map which care context types your system generates.
Register your software on sandbox.abdm.gov.in, set up your HIP bridge ID, and configure the ABDM gateway callbacks in your test environment.
Build and test ABHA creation, OTP verification, and HFR/HPR registration. Pass all NHA M1 test cases before moving to M2.
Implement care context linking, FHIR bundle generation, consent manager integration, and HIU/HIP data exchange flows.
Prepare your Safe-to-Host certificate application, support security testing by STQC/CERT-IN empanelled agencies, and submit documentation to NHA.
Register on the production ABDM environment, train your front-desk staff, and go live. We stay on for support during the transition period.
We build a middleware layer that sits between your existing HMS and the ABDM gateway. Your clinical workflows, database, and user interface stay exactly as they are. We add the ABDM API layer on top — handling all the complexity of FHIR formatting, encryption, consent management, and gateway callbacks.
This means zero disruption to your operations during integration. Your staff continue using the same HMS screens. The ABDM layer works in the background, automatically creating care contexts, handling consent requests, and responding to health information queries.
We build to the latest NHA API specifications and NRCeS FHIR R4 India profiles — so your certification is clean and your integration is future-proof.
ABDM Sandbox setup — full test environment configuration
HMS integration analysis — map your existing data to ABDM requirements
M1 + M2 + M3 API development — complete milestone stack
FHIR bundle templates — for all required care context types
NHA test case execution — pass all functional test cases
STQC certification support — documentation and security testing prep
Production deployment — go-live on live ABDM environment
Staff training — front-desk walkthrough for ABHA registration workflows
Full documentation — API references, integration diagrams, runbooks
Post go-live support — 3 months minimum, extended available
Talk to our team about your current HMS, your compliance deadline, and what a realistic integration timeline looks like for your hospital.