All posts

·8 min read

ABDM and ABHA basics for hospital teams

Ayushman Bharat Digital Mission connects facilities, professionals and patients through registries and consent. This primer explains ABHA, HFR and what software must support without the jargon overload.

What ABDM is trying to solve

Ayushman Bharat Digital Mission (ABDM), led by the National Health Authority, builds a national digital health backbone so records can move between providers when the patient consents. The goal is less paper chase across hospitals, labs and clinics, and a standard way to identify people and facilities.

For a hospital admin, ABDM is not a replacement for your HMIS. It is the layer that lets your software talk to the national ecosystem. Your team still needs day to day OPD, IPD, lab and billing inside the hospital system.

ABHA: the patient identifier

Ayushman Bharat Health Account (ABHA) gives a person a unique health ID used to authenticate and to thread records across systems when consent exists. Without a shared identity, the same patient appears as three charts in three hospitals with no safe link.

Front desk and doctors should treat ABHA capture as optional but valuable: ask at registration, link when the patient is ready, and never block emergency care on missing ABHA. Software should store the link on the patient chart and support find or create flows defined by the national programme.

Health Facility Registry and professional registry

The Health Facility Registry (HFR) is the national list of verified public and private facilities (hospitals, clinics, labs, pharmacies and more). Facilities that enrol get a facility identifier used when connecting to ABDM services. The Healthcare Professionals Registry covers practitioners across systems of medicine.

Hospital IT or the admin owner should complete HFR onboarding for the site, then connect the facility ID inside the HMIS settings so outbound ABDM calls carry the right facility context. Doctor HPR identifiers, where applicable, belong on the staff profile for display and future linking.

Consent and record exchange in plain language

ABDM record sharing is consent first. A Health Information Provider (HIP) shares FHIR-style records when the patient authorises. A Health Information User (HIU) requests records the patient has allowed. Software milestones commonly labelled M1, M2 and M3 map to identity, provide and consume capabilities inside the NHA sandbox before production.

Your operational checklist: register the facility, pick ABDM-ready HMIS, train staff on ABHA linking, keep audit trails of share and view events, and keep PHI encryption and access control strong inside the tenant. Programme details evolve on the official ABDM site; always verify current sandbox and production steps there.