ABDM

ABDM & ABHA Integration

The Ayushman Bharat Digital Mission (ABDM) defines the national digital health stack — ABHA IDs, Health Information Provider (HIP) and User (HIU) roles, consent-based exchange, the Health Facility Registry (HFR) and the Health Professional Registry (HPR). OneCity is built ABDM-native: every clinical record can flow to the patient's Personal Health Record (PHR) under the consent framework.

Why it matters

ABDM participation is increasingly a condition for government scheme empanelment (PMJAY, CGHS) and will be a differentiator for patient trust.

How OneCity covers it

ABHA Linkage

Patients are offered ABHA linkage at registration. The linkage is consent-gated and stored with the patient master. Records can then be pushed to the PHR.

HIP & HIU Roles

The hospital acts as a Health Information Provider (HIP), sharing records on consent, and optionally as a Health Information User (HIU), pulling records from other providers.

Consent Framework

Every data-sharing request goes through the ABDM consent manager. The hospital cannot push or pull without an active consent artefact.

HFR & HPR

The hospital is registered in the Health Facility Registry and its doctors in the Health Professional Registry, enabling discoverability.

FHIR R4

Clinical records (conditions, medications, diagnostics) are structured as FHIR R4 resources so they can be exchanged with any ABDM-compliant system.

Modules involved

Patient RegistrationOPDIPDLabPharmacyDischarge Summary

Questions

Is the ABDM integration live?+

Payloads are generated to ABDM specification and stored. Live exchange enables after HIP onboarding and sandbox clearance, which is a per-hospital process.

Is ABHA mandatory for patients?+

No. ABHA linkage is optional and consent-based. Patients without ABHA are served with a local UHID.

See ABDM compliance in the live system.

Book a walkthrough or start free up to 5 doctors.

Start free Book a demo