ABHA and ABDM explained for clinics

ABDM is one of those programmes every clinic has heard of and few can explain. Strip away the acronyms and it's a simple idea: give every patient a portable health identity, and give providers a standard way to exchange records, with the patient's consent. Here's what it means for a clinic, in plain terms.

If the acronyms blur together, the quick disambiguation:

Acronym	What it is	Who it's for
ABDM	The national digital health mission and rails, run by the NHA	India's health system as a whole
ABHA	A patient's 14-digit health ID, plus an easy-to-share ABHA address	Patients
HFR	The Health Facility Registry of verified facilities	Clinics and hospitals
HPR	The Healthcare Professionals Registry	Doctors and practitioners

ABDM, in one paragraph

The Ayushman Bharat Digital Mission (ABDM), run by the National Health Authority, is India's effort to build the rails for digital health, the way UPI built rails for payments. It doesn't run your clinic; it sets the standards and registries that let records move between providers when a patient agrees.

The pieces you'll actually hear about

• ABHA number, the Ayushman Bharat Health Account: a unique health ID a patient can create (a 14-digit number, plus an easy-to-share ABHA address). It ties a person's health records together across providers.
• Health Facility Registry (HFR): a directory clinics and hospitals register in, so they're discoverable as verified facilities.
• Healthcare Professionals Registry (HPR): the equivalent for doctors and practitioners.
• Consent and exchange: the framework that lets records be requested and shared only with the patient's explicit, revocable consent.

What it means for a clinic, practically

You don't have to adopt everything at once. The usual path is:

1. Register your facility in the HFR (and your practitioners in the HPR).
2. Create or link an ABHA for patients who want one; many already have one.
3. Link records to that ABHA so the patient can carry their history.
4. Share on consent when another provider requests records, and only then.

The patient benefit is real: a child's vaccination record, a diabetic's past labs, a referral letter, all available to the next doctor without a folder changing hands.

How sharing actually works (consent and exchange)

The part that trips people up is how a record moves. ABDM never copies your data into a central government vault. Records stay where they were created. What moves is a one-time, consented pull, requested by the provider who needs it and authorised by the patient.

In practice it's a four-party handshake:

• The clinic that holds the record is the HIP (Health Information Provider).
• The clinic that wants to read it is the HIU (Health Information User).
• The patient's consent manager (an app tied to their ABHA) is where they approve or refuse.

The flow reads left to right. A new doctor (HIU) requests, say, the last six months of lab reports for an ABHA. The patient gets a notification on their consent manager and approves a specific, scoped request, this record type, this date range, for this long. Only then does the holding clinic (HIP) release that slice directly to the requester. The consent is an artefact the holding clinic checks every time, so an expired, paused, or revoked consent simply returns nothing. The patient can withdraw it later from the same app, and future pulls stop. You share a defined window of records for a defined purpose, not blanket access to a chart.

Should your clinic adopt ABDM now, or wait?

It depends far more on how patients move through your practice than on your size. ABDM pays off where records cross a boundary.

Lean in now if you:

• Send or receive referrals regularly, ABHA-linked records save the "please carry your old reports" phone call.
• Run chronic and follow-up care (diabetes, cardiac, antenatal, dialysis), where the value is a longitudinal record the next visit can build on.
• See multi-provider patients who also visit hospitals, labs, or specialists and expect their history to follow them.
• Are going digital anyway, adopting ABHA linking during setup is cheaper than retrofitting it later.

It's fine to wait if you:

• Run a single-doctor, single-visit practice (a walk-in skin or dental clinic) where most encounters are self-contained.
• Have no structured records yet, fix that first; portability is only useful once there's something clean to port.

There's little downside to the foundation step either way: registering on the HFR and keeping records structured and exportable costs you nothing and leaves every option open.

Common myths, cleared up

• "ABDM registration is a licence to run a clinic." No. HFR registration makes your facility discoverable in a national directory. It is not a clinical establishment licence, a GST registration, or any other statutory permission, those are separate and unchanged.
• "An ABDM badge means I'm NHA-certified." Not necessarily. Listing on a registry, or a vendor's "ABDM-ready" claim, is not the same as NHA's formal milestone certification of software. Ask what specific milestone, if any, has actually been cleared.
• "ABHA is health insurance / PM-JAY." No. ABHA is a health ID that links records; it carries no financial cover. PM-JAY is the separate insurance scheme with its own eligibility. A patient can hold an ABHA and have no PM-JAY cover at all, and vice versa.

What ABDM is not

It's not a clinic management system, and it's not mandatory for running a practice. It's an interoperability layer. Your day-to-day work (records, billing, scheduling) still runs in your software; ABDM is the bridge to the wider ecosystem.

How ABHA shows up in Avinya Plus

ABHA/ABDM support in Avinya Plus is an early, opt-in capability, not a headline feature, and we're deliberate about not overstating it. We do not claim to be "ABDM certified". Certification is a specific process run by the NHA, and we'd rather tell you precisely where we are than wave a badge. What we do build for, today, is the foundation ABDM rewards: a single, structured patient record and data you can export, so nothing about going digital with us traps your information.

The honest summary: treat ABDM as the direction of travel. Choose tooling that keeps your records structured and portable now, adopt ABHA linking when it helps your patients, and don't let anyone sell you a compliance badge as a substitute for an open, exportable record.

See how Avinya Plus approaches ABHA and a portable patient record, or book a demo from the menu to walk through it on your own workflow.