The complete guide to ABHA ID — what every clinic must know before 2027

If you run a clinic or hospital in India and haven't started linking patients to ABHA IDs yet, you're running out of runway. The National Health Authority has been tightening ABHA requirements steadily since 2023, and by 2027, it's expected to be mandatory for all government-empanelled facilities and strongly incentivised for private ones.

But talk to clinic owners in Indore or Patna, and most will tell you the same thing: "I've heard of it, but I don't really know what to do." This guide is for them.

What is ABHA, in plain terms?

ABHA stands for Ayushman Bharat Health Account. It's a 14-digit unique health ID — think of it as Aadhaar, but specifically for healthcare. Every Indian citizen can create one, and it's meant to be the single identifier that links all their health records across every hospital, clinic, and lab they ever visit.

The idea is simple: when a patient walks into your clinic with their ABHA ID, you can (with their consent) pull up their past prescriptions, lab reports, and discharge summaries from other facilities. And when you treat them, your records get added to their ABHA-linked profile so the next provider can see them too.

ABHA is the backbone of the Ayushman Bharat Digital Mission (ABDM), which is essentially the government's plan to create a "UPI for health records."

As of early 2026, over 55 crore ABHA IDs have been created — largely through government drives, Aadhaar-linked auto-creation, and insurance enrolment processes. Many patients already have one. They just don't know it, and their clinic doesn't ask for it.

Why clinics need to care — three concrete reasons

1. Government scheme empanelment is getting strict

If your hospital is empanelled under PM-JAY (Ayushman Bharat), CGHS, or ESI, you've probably noticed that NHA is increasingly asking for ABDM compliance during renewal. Several state health departments have already made ABHA-linked patient registration a condition for new PM-JAY empanelment. By late 2026 or early 2027, this is expected to become universal.

Translation: if you bill government schemes and can't link patients to ABHA, you risk losing empanelment — and the revenue that comes with it.

2. Insurance companies are moving to ABHA-linked claims

Major TPAs have started accepting (and in some cases preferring) ABHA-linked claim submissions. The logic for insurers is clear: ABHA reduces fraud by linking treatment records to a verified identity. Within 12-18 months, expect ABHA-linked claims to get faster processing and lower rejection rates. Clinics that can't submit ABHA-linked claims will be at a disadvantage.

3. Patients are starting to ask

This one is slower but real. Patients in urban areas — particularly those who've been through a government hospital recently — are showing up with ABHA cards or ABHA numbers on their phones. When your clinic can't scan or verify it, it feels like a bank that doesn't accept UPI. It's a small trust signal, but it matters.

How to create and link ABHA IDs — the practical steps

Creating a new ABHA for a patient

There are two authentication methods:

Aadhaar OTP: Patient provides their Aadhaar number, receives an OTP on their registered mobile, and the ABHA ID is created instantly. This is the most common method and works for 90%+ of patients.

Demographic auth (driving licence): For patients without Aadhaar or those who don't want to use it, ABHA can be created using driving licence details plus demographic information. This takes slightly longer and requires manual verification.

The process should take under 2 minutes per patient at the registration desk. If it takes longer, your staff will skip it during rush hours — and that's where most clinics fail.

Linking an existing ABHA to your system

Many patients already have an ABHA ID (created through government drives or other facilities). When they visit your clinic, you need to:

1. Ask for their ABHA number or scan their ABHA QR code 2. Verify the ABHA against NHA's system 3. Link it to the patient record in your HMS 4. Obtain consent for record sharing (this is legally required under DISHA)

Pushing records to ABDM

Once a patient is ABHA-linked, every clinical document you generate — prescriptions, lab reports, discharge summaries — should be converted to FHIR R4 format and pushed to the ABDM Health Information Exchange. The patient (or another provider they consent to) can then access these records.

This sounds technical, but your HMS should handle the FHIR conversion automatically. If you're doing this manually, you're doing it wrong.

The seven most common ABHA mistakes clinics make

1. Not asking for ABHA at registration. The biggest failure point. If your reception desk doesn't have a field for ABHA ID in the registration form, it won't get captured. Make it a standard field — even if it's optional for now.

2. Treating it as a one-time project. ABHA linking needs to happen for every patient, every visit. It's an ongoing workflow change, not a one-time implementation.

3. Not training reception staff. The receptionist needs to know how to create an ABHA (Aadhaar OTP flow), verify an existing ABHA, and handle common issues like "my OTP isn't coming" (usually a wrong mobile number linked to Aadhaar). Budget 30 minutes for training and do 5 practice runs.

4. Skipping consent management. Under DISHA and ABDM rules, you cannot share patient records without explicit digital consent. Your system must implement the ABDM consent framework — not just a paper form that says "I agree."

5. Using outdated ABDM APIs. NHA updates the ABDM specifications regularly. If your integration was done once and never updated, it may be generating errors or pushing records in deprecated formats. Use an HMS that maintains ABDM compliance as part of its regular updates.

6. Not verifying ABHA at every visit. A patient might have created an ABHA at another facility with different demographic details. Cross-verify at each visit to ensure the ABHA record matches your patient record.

7. Ignoring the PHR (Personal Health Record) app. Patients can download the ABHA app (formerly NDHM Health Records) and see all their linked records. If your clinic pushes records correctly, patients see your prescriptions and reports in their app — which builds trust and makes them more likely to return.

What it costs to get ABHA-ready

If you're using a modern HMS with built-in ABDM integration, the cost is essentially zero beyond your subscription. The NHA APIs are free to use. There's no licensing fee for being a Health Information Provider.

If you're on a legacy system or paper, you'll need either: (a) an HMS with ABDM support, or (b) a standalone ABDM integration middleware — which typically costs ₹50,000-1,50,000 for setup plus annual maintenance.

The practical takeaway: if you're already evaluating HMS options, make sure ABDM/ABHA support is built in, not bolted on. It will save you a separate integration project down the line.

For clinics looking for a system with ABDM built into the core — not as an add-on — MedOS includes ABDM-ready architecture on all plans, with full ABHA verification and FHIR R4 support on Professional and Enterprise. Try it free for 14 days at med-os.in.