ABDM and ABHA for hospitals: what to implement and what to defer
ABDM integration is becoming a condition for PMJAY and CGHS empanelment. Here's what hospitals should implement now and what can wait.
The Ayushman Bharat Digital Mission (ABDM) defines the national digital health infrastructure: ABHA IDs for patients, Health Information Provider (HIP) and User (HIU) roles for hospitals, consent-based data exchange, the Health Facility Registry (HFR) and the Health Professional Registry (HPR).
For most tier-2/3 hospitals, the question is not "should we integrate" — PMJAY and CGHS empanelment are increasingly tied to ABDM participation. The question is "what do we implement now and what can wait?"
Implement now: ABHA linkage at registration. This is a consent-gated field on the patient master. The patient provides their ABHA number, you verify it and store the link. No data exchange happens yet — you're just linking the ID. This is low-risk and high-signal for empanelment.
Implement now: HFR registration. Your hospital should be in the Health Facility Registry. This is a one-time process through the ABDM portal.
Implement now: HPR for doctors. Doctors should be registered in the Health Professional Registry with their NMC registration number.
Defer (but prepare): HIP consent-based data exchange. This requires sandbox clearance, integration testing and production onboarding. The payload format (FHIR R4 resources) should be ready in your ERP, but the live pipe can wait until the sandbox process completes.
Defer: HIU role (pulling data from other providers). This is operationally complex and most hospitals don't need it immediately.
OneCity's approach: ABHA linkage is built into patient registration. FHIR R4 payloads are generated and stored for discharge summaries, prescriptions and diagnostics. Live exchange enables after HIP onboarding — we don't claim it's live when it isn't.
