Home · About · Services · Industries · Projects · Products · Process · Blog · Glossary · FAQ · Contact
ABDM and ABHA integration: what Indian health software needs What Indian clinic and hospital software needs for ABDM: registries, ABHA creation and linking, consent-based sharing, FHIR records and certification.
A multi-specialty clinic’s owner brings a request to the software vendor. Patients keep asking to scan a QR code at registration, and whether their lab reports will appear in their ABHA app. The vendor’s developers open the ABDM sandbox documentation and find a gateway, three milestones, several registries, FHIR profiles and an encryption scheme. They are not sure where to begin.
ABDM integration is a set of distinct capabilities, and you build them in order. First, create and verify ABHA for patients. Next, act as a health information provider that links records and shares them when the patient consents. Then, optionally, act as a health information user that requests records from elsewhere. Behind all three sit registries, FHIR-based record formats and a certification path. Plan each as its own piece of work.
The building blocks of ABDM The Ayushman Bharat Digital Mission, run by the National Health Authority, provides shared digital infrastructure rather than a central medical records database. Records stay with the hospitals, clinics and labs that create them. ABDM provides identity, registries and a consent-based way to move records between them.
The main building blocks are these.
ABHA, the Ayushman Bharat Health Account. Each person can have a 14-digit ABHA number and one or more ABHA addresses, which are memorable, username-style identifiers. Health Facility Registry (HFR). A registry of hospitals, clinics, labs, pharmacies and other facilities, each with a facility ID. Healthcare Professionals Registry (HPR). A registry of doctors, nurses and other professionals. The ABDM gateway and Health Information Exchange with Consent Manager (HIE-CM). They route requests between systems and record patient consent. Personal health record apps, such as the ABHA app, where patients see linked records and approve consent requests. Your software talks to the gateway through APIs. It never talks directly to another hospital’s system.
Roles your software can play ABDM describes integrating systems by role. A hospital information system or clinic EMR usually plays more than one.
A Health Information Provider (HIP) creates records and shares them when a patient consents. A clinic issuing prescriptions and a lab issuing reports are both HIPs.
A Health Information User (HIU) requests records created elsewhere, with consent, to support care. A doctor wanting a patient’s past discharge summaries acts through an HIU.
Integration work is commonly organised into three milestones, often called M1, M2 and M3.
M1: ABHA creation and verification. Register patients with ABHA, or verify an existing ABHA, and store it on the patient record. M2: HIP functions. Link care contexts, such as a visit or a lab order, to the patient’s ABHA, respond to discovery requests and share records under consent. M3: HIU functions. Raise consent requests, receive approvals and fetch records from other providers. Most clinic software starts with M1 and M2. M3 matters when doctors actually need records from outside.
M1: creating and verifying ABHA ABHA creation is usually done with Aadhaar-based OTP verification, or with other supported methods such as a mobile number. Existing ABHA holders can be verified by OTP or by an ABHA address with authentication. The flows change from time to time, so build against the current sandbox documentation rather than older tutorials.
At the front desk, the experience matters as much as the API. Scan and Share lets a patient scan a facility’s QR code with their ABHA app to share their profile. Registration staff then do not type details. That requires the facility to be registered in HFR and the software to handle the incoming profile share.
Store the ABHA number and address as separate fields on the patient record, with the verification status and date. Handle patients without ABHA gracefully. ABHA is voluntary, and registration must not stall without one.
M2: linking records and sharing them Linking connects the records you create to the patient’s ABHA, so they can be discovered and shared later. A care context is the unit of linking: one OPD visit, one admission, one lab test order.
There are two ways linking happens. The HIP can link a care context to a known ABHA, for example right after a consultation. Or the patient can discover records through their app, which sends a discovery request through the gateway. Your system then matches the patient by demographics and identifiers, and confirms the link with an OTP.
When an HIU later requests data and the patient grants consent, the gateway notifies your system. You assemble the records in the consented date range and for the consented record types. You then encrypt them for the requester and send them to the HIU’s data push URL.
Records are exchanged as FHIR R4 bundles following profiles published by NRCeS, the National Resource Centre for EHR Standards. Record types include OP consultation notes, prescriptions, diagnostic reports, discharge summaries, immunisation records and general health documents. A heavily simplified skeleton of a prescription bundle:
{
"resourceType": "Bundle",
"type": "document",
"timestamp": "2024-04-20T10:15:00+05:30",
"identifier": { "system": "https://example-clinic.in/bundles", "value": "rx-55120" },
"entry": [
{ "fullUrl": "Composition/1", "resource": { "resourceType": "Composition",
"status": "final", "title": "Prescription record",
"subject": { "reference": "Patient/1" }, "author": [{ "reference": "Practitioner/1" }] } },
{ "fullUrl": "Patient/1", "resource": { "resourceType": "Patient" } },
{ "fullUrl": "Practitioner/1", "resource": { "resourceType": "Practitioner" } },
{ "fullUrl": "MedicationRequest/1", "resource": { "resourceType": "MedicationRequest",
"status": "active", "intent": "order" } }
]
}Real bundles need coded values, identifiers and profile declarations. Validate them against the published profiles with a FHIR validator before testing with the gateway. Structured coding, such as SNOMED CT for clinical terms, makes records useful to the receiver, not just legible.
Consent and encryption Consent is at the centre of ABDM. A consent artefact states who may access which record types, from which providers, for which date range, for what purpose and until when. The patient approves or denies it in their app, and can revoke it.
Your system must respect the artefact exactly. Share only the record types and dates it covers. Stop serving data when it expires or is revoked. Keep a log of every consent notification and every data transfer, linked to the artefact ID.
Data moves end to end encrypted between HIP and HIU. ABDM specifies an elliptic-curve key exchange so the two systems derive a shared key, and the gateway cannot read the content. Reference implementations exist. Use them, and test against the sandbox’s test HIU, rather than writing cryptography from scratch.
Engineering concerns that are easy to miss Asynchronous APIs. Many gateway calls return an acknowledgement, and the real answer arrives later on a callback URL. Design request tracking with correlation IDs and timeouts from the start. Public callback endpoints. Your system must expose HTTPS endpoints the gateway can reach. Secure them by validating gateway tokens, and keep them separate from internal admin interfaces. Patient matching. Discovery depends on matching demographics reliably. Poor data quality at registration causes failed links later. Multi-facility setups. A hospital chain may register each branch separately in HFR. Your data model needs a facility ID per record. Mapping legacy data. Old records may lack the structure FHIR profiles expect. Decide which historical records to link, and how to represent them, possibly as general health documents. Data protection. Treat health data with strict access control, audit logging and encryption at rest, whatever the integration requires. The path to production Integration follows a defined route.
Register for sandbox access and receive client credentials. Build and test each milestone against the sandbox and its test apps. Complete functional testing with the ABDM team, demonstrating the flows. Commission a security audit, typically a web application security audit by a CERT-In empanelled auditor, and fix findings. Receive production credentials and go live, with facilities registered in HFR and doctors in HPR. The government’s Digital Health Incentive Scheme has offered incentives to eligible facilities and digital solution companies for ABDM-linked transactions. Check its current terms with NHA, since eligibility and rates are set by notification.
APIs, versions and certification requirements evolve. Treat the official ABDM sandbox documentation as the source of truth throughout.
A planning checklist Decide which roles you need: M1 only, HIP, HIU or all three. Get facilities registered in HFR and practitioners in HPR early. Add ABHA fields, verification status and facility IDs to your data model. Design asynchronous request tracking and secure callback endpoints. Map your record types to NRCeS FHIR profiles and validate generated bundles. Implement consent enforcement and full logging of transfers. Use reference implementations for encryption. Budget time for functional testing and the security audit. Start with M1 at the registration desk. It is visible to patients, simple to verify and lays the foundation for everything after it.
Infigini IT Services · GSTIN 05AAIFI1118B1Z3 · 11 Shree Ram Puram Lane No.2, Kanwali Road, Dehradun, Uttarakhand 248001, India · info@infigini.com · +91 95684 87789 · LinkedIn