How Indian hospitals can prepare for the Digital Health ID mandate

If you run a hospital in India and you're not yet issuing ABHA (Ayushman Bharat Health Account) IDs to patients, the window for "we'll do it later" is closing. While there's no single date where a national mandate switches on overnight, the practical reality is that ABDM compliance is becoming required through multiple converging pressures — government scheme empanelment, insurance requirements, and patient expectations.

This guide covers the timeline as it stands in early 2026, what compliance actually means for a hospital, and a practical step-by-step preparation plan.

Where we stand: the "soft mandate"

India doesn't have a single law that says "all hospitals must use ABHA IDs by [date]." What India has is a series of policy moves that collectively make ABDM integration practically mandatory:

Government scheme empanelment

PM-JAY / Ayushman Bharat: The National Health Authority (NHA) has progressively tightened ABDM requirements for PM-JAY empanelled hospitals. As of early 2026: - New PM-JAY empanelments require ABDM registration as a Health Facility - Existing empanelled hospitals are expected to link claims with ABHA IDs - By end of 2026, ABHA-linked claim submission is expected to become the default path

CGHS (Central Government Health Scheme): CGHS empanelled hospitals in metro cities are being encouraged to register on ABDM. Electronic health record sharing is being piloted for CGHS beneficiaries.

ESI: The Employees' State Insurance Corporation has announced plans to integrate with ABDM, though the timeline is still evolving.

State government schemes: Multiple states — Rajasthan, Maharashtra, Tamil Nadu, Andhra Pradesh — are running their own health digitisation programmes that tie into ABDM.

Insurance and TPA requirements

Several major insurers and TPAs have started accepting or encouraging ABHA-linked documentation. While not yet mandatory for cashless claims, the direction is clear: digital health records linked to a unique patient ID will become the standard for claim processing.

NABH accreditation

NABH's latest edition of accreditation standards references digital health record systems and ABDM-compatible documentation. Hospitals pursuing or maintaining NABH accreditation are expected to demonstrate digital health record capability.

Patient adoption

Over 55 crore ABHA IDs have been created as of early 2026. Government drives at ration shops, vaccination centres, and PM-JAY registration points have given millions of Indians an ABHA ID — even if they don't fully understand it yet. When these patients walk into your hospital with their ABHA card and you can't link them, it creates a friction that didn't exist a year ago.

What "ABDM compliance" means for a hospital

Let's demystify this. ABDM compliance for a hospital means:

Level 1: Registration (minimum)

• Register your hospital on the **Health Facility Registry (HFR)** — the national directory of healthcare facilities
• You get a unique Health Facility ID
• This is a one-time registration that takes about 30 minutes
• Requirements: hospital registration certificate, address, contact details, facility type

Level 2: ABHA ID linking at registration

• When patients visit, create or link their ABHA ID
• New patients: create an ABHA ID using their Aadhaar or driving licence (2-minute process with OTP verification)
• Existing patients: link their existing ABHA ID to your hospital record
• The linked ABHA ID becomes the patient's unique identifier across the ABDM network

Level 3: Health Information Provider (HIP)

• Your hospital becomes a HIP — a facility that creates and shares health records on the ABDM network
• When you generate a prescription, lab report, or discharge summary, it's pushed to the ABDM network in FHIR R4 format
• Patients can then access these records via the ABHA app or share them with other providers

Level 4: Health Information User (HIU)

• Your hospital can pull records from other facilities (with patient consent)
• When a patient visits you for the first time, you can request their records from previous hospitals
• The patient approves via the ABDM consent manager
• Records are shared electronically — no paper referral letters needed

Level 5: Full integration

• Claims linked to ABHA ID (PM-JAY, insurance)
• ABDM consent manager for all data access
• Regular compliance reporting to NHA
• Quality audits aligned with ABDM standards

For most hospitals in 2026, Levels 1–3 are the practical target. Level 4 requires more mature integration. Level 5 is for hospitals already deep into government scheme billing.

Step-by-step preparation plan

Month 1: Foundation

Week 1: Register on Health Facility Registry

Visit the ABDM Health Facility Registry portal (facility.abdm.gov.in). Create your facility profile. You'll need: - Hospital registration certificate - Clinical establishment registration (if applicable in your state) - Authorised person's Aadhaar for verification - Facility address, contact, specialities, bed count

Processing time: 2–5 working days for verification.

Week 2: Ensure your HMS supports ABDM

This is the critical dependency. Your HMS software must have ABDM integration — specifically: - API connectivity to ABDM sandbox (and production) environment - ABHA ID creation and linking at patient registration - Document generation in FHIR R4 format - Consent manager integration

If your current HMS doesn't support ABDM: - Check with your vendor — they may have an ABDM update in the pipeline - If not, evaluate HMS platforms that are ABDM-ready (MedOS, for example, is built with ABDM from day one) - Don't try to build ABDM integration yourself or hire a freelancer — the NHA APIs have specific certification requirements and evolving specifications

Week 3–4: Staff training

Train three groups: 1. Registration staff: How to create ABHA IDs for new patients and link existing ones. This is a 2-minute process per patient — scan Aadhaar QR or enter ABHA number, verify with OTP, link to hospital record. 2. Doctors and clinical staff: No workflow change needed if the HMS handles FHIR document generation automatically. The doctor prescribes as usual; the system converts it to ABDM format in the background. 3. IT/admin: Understanding the ABDM dashboard, monitoring successful record pushes, handling errors.

Month 2: Go live with ABHA linking

Target: Link 50%+ of new OPD registrations with ABHA IDs in the first month.

Practical approach: - Make ABHA linking part of the registration workflow, not a separate step - If the patient has an ABHA ID (check by asking or scanning their ABHA card), link it - If the patient doesn't have one, offer to create one using Aadhaar OTP (takes 90 seconds) - Don't force it — some patients will decline. That's fine. Track the linkage rate and aim to increase it over time

Tip for staff: Frame it as a benefit to the patient: "Shall I create a Digital Health ID for you? It's free, and your reports will be accessible on your phone." This gets much better adoption than "Government regulation requires this."

Month 3: Enable document sharing

Target: Push prescriptions and lab reports to ABDM for ABHA-linked patients.

How it works: 1. Doctor writes prescription → HMS generates FHIR-formatted prescription document → pushed to ABDM → appears in patient's ABHA app 2. Lab releases report → HMS generates FHIR-formatted diagnostic report → pushed to ABDM → patient notified

The patient doesn't need to do anything extra. If they have the ABHA app, records appear automatically. If they don't, records are stored in ABDM and accessible when they eventually download the app or visit another ABDM-linked facility.

Month 4–6: Optimise and expand

• Track ABHA linkage rate and push success rate on your HMS dashboard
• Expand document types: add discharge summaries, immunisation records
• Address common errors: failed pushes, patient consent issues, duplicate ABHA IDs
• If empanelled under PM-JAY, start linking claims with ABHA IDs

Common challenges and solutions

"Patients don't have Aadhaar / don't want to share it"

ABHA can be created with a driving licence (not just Aadhaar). For patients who decline, respect their choice — ABHA creation is currently consent-based. Track these as "not linked" and offer again on subsequent visits.

"Our internet is unreliable"

ABDM APIs require connectivity. However, a well-designed HMS can cache ABHA creation requests and sync when connectivity returns. For the initial Aadhaar OTP step, you need live connectivity (OTP is real-time). If your facility has frequent outages, invest in a mobile hotspot as backup — it's ₹500/month for a 4G plan.

"NHA keeps changing the API specs"

True — and this is why building ABDM integration yourself is risky. Use an HMS vendor who is an ABDM partner and maintains the integration. When NHA updates the specs, the vendor updates the software. You shouldn't have to worry about API version changes.

"We're a small clinic — do we really need this?"

If you're a solo-doctor clinic on paper, ABDM isn't urgent today. But consider: - Patients are accumulating ABHA IDs and will increasingly expect providers to use them - If you ever want to empanel under PM-JAY or CGHS, ABDM is a prerequisite - Setting it up now (when it's simple and low-volume) is easier than doing it under pressure later

"What about patient data privacy?"

ABDM has a built-in consent framework. Your hospital cannot share records without patient consent. Patients control who sees their data, what data is shared, and for how long. This is actually more privacy-protective than the current system (where paper records have no access controls at all).

The cost of waiting

Hospitals that delay ABDM preparation face:

1. Loss of government scheme empanelment — PM-JAY, CGHS, and ESI are the most direct revenue risk 2. Higher implementation cost — rushing ABDM integration under deadline pressure costs more than doing it systematically 3. Staff resistance — staff trained gradually over 3 months adapt better than staff told "everything changes Monday" 4. Patient experience gap — as more hospitals go ABDM-ready, patients will notice when yours doesn't support their Digital Health ID

The cost of starting

Here's the honest cost for a typical hospital:

If your HMS already supports ABDM, the additional cost is literally zero. If you need to switch HMS to get ABDM support, the cost is the HMS subscription — but you're likely getting a better HMS in the process.

MedOS is ABDM-ready — ABHA creation, HIP registration, FHIR R4 document push, and consent management are built into every plan starting at ₹699/month. Start your 14-day free trial at [med-os.in](https://med-os.in) and be ABDM-ready before the mandate becomes mandatory.