Quick answer

ABDM is the framework — the overall Ayushman Bharat Digital Mission. ABHA is the patient's health ID inside that framework. HPR is the doctor's professional registry. HFR is the clinic / facility registry. UHI is the open network protocol. They are not competing systems — they are pieces of one architecture, the way IFSC, account number, and UPI are pieces of the Indian banking system.

ABDM — the framework

The Ayushman Bharat Digital Mission was operationalized by the National Health Authority (NHA), a body under the Ministry of Health and Family Welfare. ABDM is not software; it is a set of standards, registries, and protocols that together let Indian healthcare exchange data digitally.

Think of ABDM as the umbrella term. When someone says "we need ABDM compliance," they typically mean: "we need to participate in some combination of the registries (HPR, HFR) and the data exchange protocols defined by ABDM."

ABDM does not run a clinic. ABDM does not store a patient's medical record itself. It defines:

How patients are identified (ABHA)
How doctors are identified (HPR)
How facilities are identified (HFR)
How records are exchanged (FHIR R4 over the Health Information Exchange and Consent Manager)
How third-party apps plug in (Unified Health Interface)

Everything else — the clinic management software, the EMR, the pharmacy POS, the lab software — is built on top.

ABHA — Ayushman Bharat Health Account

ABHA is the patient's health ID. It comes in two forms:

ABHA Number — a 14-digit numeric identifier. Like a bank account number.
ABHA Address — a human-readable identifier like name@abdm. Like an email address or UPI VPA.

A patient can have one ABHA Number and link multiple ABHA Addresses (one personal, one for an employer-sponsored health plan, etc.).

ABHA is the stable cross-provider key for a patient's records. When the patient visits Clinic A, the visit is associated with their ABHA. Six months later when they visit Clinic B in a different city, Clinic B can request the prior records through ABDM using the same ABHA — and with the patient's consent — see the relevant history.

ABHA is free to create. A patient can self-register at https://abha.abdm.gov.in or have it created during a clinic visit.

HPR — Health Professional Registry

HPR is the doctor's registry. Each registered doctor has an HPR ID and a profile containing:

Name
Medical council registration number (MCI, state council)
Qualification (MBBS, MD, MS, DM, MCh, BDS, BAMS, etc.)
Specialty
ABHA-linked identity (so the doctor is also a patient in the system)

Patients can verify a doctor's credentials by looking up their HPR profile. Hospitals and clinics can verify their hired staff against HPR. Insurance companies can verify claim signatures against HPR.

HPR registration is the doctor's individual act. It is independent of any specific clinic. A doctor practicing at two clinics has one HPR registration; the two clinics each link their relationship to that HPR.

HFR — Health Facility Registry

HFR is the registry of healthcare facilities — clinics, hospitals, labs, pharmacies, diagnostic centres. Each facility has an HFR ID and a profile with:

Facility name
Address
Type (clinic / hospital / lab / pharmacy / diagnostic centre)
Owner / managing entity
Services offered

HFR is the facility-side counterpart to HPR. A clinic with three doctors has one HFR entry and three HPR-linked doctors.

Patients can search HFR to find ABDM-onboarded facilities near them. Public visibility is one of the main early-stage benefits of HFR registration for a clinic.

UHI — Unified Health Interface

UHI is the open network protocol layer. It is to ABDM what UPI is to banking. UHI lets any healthcare app — booking app, telemedicine app, lab booking — interact with any ABDM-connected provider without bilateral integration.

For most clinics in 2026, UHI is "not yet relevant" — adoption is still ramping. But as more booking aggregators (Practo, Lybrate, Tata 1mg, Apollo 247, etc.) plug into UHI, the long-tail benefit is: your clinic can receive bookings from any aggregator without separate integration work.

How they fit together in a real clinic visit

Consider a patient who walks into your clinic with a fever:

1.Reception scans the patient's ABHA Address. The patient says "my ABHA is priya@abdm." Reception types it into the clinic software.
2.Clinic software requests prior records via ABDM. The Consent Manager sends a consent request to the patient's phone: "Healthcare with AI - Dr. X's Clinic wants to view your records from the last 6 months for this visit. Approve?"
3.Patient approves consent on their phone. Records flow into the clinic software: last lab report, last prescription, last visit summary from a different clinic.
4.Doctor consults with full context. Doctor sees the patient was on the same antibiotic last month and chooses a different one this time.
5.Doctor approves a new prescription. The clinic software:

Stores the visit in its EMR with the patient's ABHA
Pushes the visit summary (FHIR R4 document) into ABDM through the Health Information Provider (HIP) interface
Sends the prescription to the patient on WhatsApp

1.Next clinic (if the patient visits another doctor) can request the just-pushed record from ABDM with new consent.

All of this requires HPR (doctor's identity), HFR (clinic's identity), ABHA (patient's identity), and the FHIR exchange (the record format).

What clinics commonly get wrong

Thinking "ABDM compliant" means just one thing. It is a spectrum (see Rungs 0-4 in the ABDM compliance guide).
Confusing ABDM with insurance. ABDM is digital health infrastructure. Ayushman Bharat Pradhan Mantri Jan Arogya Yojana (PMJAY) is government health insurance. They are separate (though they share branding).
Claiming ABHA support without consent management. If a clinic stores an ABHA in their EMR but cannot exchange records over ABDM with consent, they have linked the ID but are not actually using ABDM.
Assuming patients will know their ABHA. Most patients do not yet. Generating an ABHA at the clinic during a visit takes 2-3 minutes; offering this is a good service.

Frequently asked questions

Do I need separate HPR registration for each clinic I practice at?

No. HPR registration is per doctor, not per clinic. You register once, then each clinic adds you as a practicing professional.

Is HFR mandatory for private clinics?

Not in 2026, but increasingly expected for hospitals and growing in adoption among private clinics. Government insurance schemes (PMJAY in some regions) prefer HFR-registered facilities.

Can a patient generate an ABHA at my clinic during their visit?

Yes. The patient gives consent and provides Aadhaar verification. The ABHA is generated and linked to the visit. This is a normal workflow for ABDM-onboarded clinics.

How does ABDM relate to DPDP Act?

ABDM is consent-based by design, which aligns with DPDP requirements for explicit consent before processing health data. ABDM does not replace DPDP — clinics still need DPDP-aligned data handling for everything else.

Where can I track ABDM developments?

The official ABDM dashboard at https://dashboard.abdm.gov.in shows registered facilities, professionals, ABHA creations, and record exchange volumes by state.

Closing note

ABDM, ABHA, HPR, HFR, UHI — five letters and acronyms, one architecture. For a practicing doctor, the action items are simpler than the vocabulary:

1.Get your ABHA (as a citizen)
2.Register on HPR (as a professional)
3.Get your clinic on HFR (as a facility)
4.Ask your clinic software vendor about FHIR exchange (as a tech requirement)

Steps 1-3 are free and take a working day. Step 4 is your vendor's job. Most modern Indian clinic management platforms — including Healthcare with AI — are ABDM-ready as of 2026, even if certification timelines vary.

The ABDM network is small today and large tomorrow. Doctors who register early get the visibility and operational advantages before the rush.

ABDM vs ABHA vs HPR: What Indian Doctors Actually Need to Know (2026)