ABDM explained: a plain-language guide for hospital owners

The Ayushman Bharat Digital Mission (ABDM) is the Government of India's programme for a national digital health system. It gives every citizen a health account called ABHA, lists hospitals in the Health Facility Registry and clinicians in the Healthcare Professionals Registry, and lets health records move between providers only with the patient's consent. For a hospital, joining ABDM means using software that can create ABHA IDs, link records to them and answer consent requests.

This guide is for the owner or administrator of a private hospital, nursing home or clinic who keeps hearing the acronyms and wants to know what they mean in practice. It stays away from API details. If you want those, the ABDM sandbox has them.

What are the building blocks of ABDM?

ABDM is a set of registries plus a set of rules for moving records between them. The official ABDM site describes each part. The table below puts them in hospital terms.

How does consent actually work?

The patient, not the hospital, controls sharing. A doctor at another facility raises a request through their software: which records, for what purpose, for how long. The patient sees the request in the ABHA app or another ABDM app and approves or rejects it. Only then does your system send the records, and it sends only what the consent covers. The patient can revoke consent later, and the request, the approval and the transfer are all logged.

This is the point most owners find reassuring once it is explained. ABDM does not put your patient database on a government server. Your records stay with you. What ABDM adds is a standard way for a patient to say yes.

What changes at the hospital?

Less than the brochures suggest, and mostly at three points.

• Registration. One new field, ABHA number, and one new button, create or verify ABHA. The patient gives an OTP. The desk does not need to open a separate website.
• Documentation. Prescriptions, discharge summaries and lab reports need to be structured, because ABDM shares them in HL7 FHIR format rather than as scanned PDFs. In good software this feels like filling a form, not a change in how doctors work.
• Consent handling. When another facility asks for records, someone at your hospital sees a notification. The patient's approval is what releases the record. That is the whole workflow.

Everything else, billing, pharmacy, inventory, payroll, MIS, is untouched by ABDM. A hospital that never creates a single ABHA still runs exactly as before.

Why should a private hospital bother?

• Government schemes and empanelments increasingly ask for HFR and HPR IDs, and some state programmes ask for ABHA-linked records. Having them ready avoids a scramble later.
• Patients arrive with history. A discharge summary from another city, seen before the consultation, saves repeated tests and repeated questions.
• Your own records become portable. If you ever change software, records linked to an ABHA are in a standard format, not a vendor's private one.
• It costs nothing extra if your HMIS already has it. The registries are free. The certification cost is the vendor's, not yours.

Where should a hospital owner start?

1. Ask your software vendor which ABDM milestones they have cleared, M1, M2 or M3, and ask to see the certificates. The difference is explained in what ABDM integration involves for a 30-bed hospital.
2. Register the facility in the HFR and get your doctors on the HPR. Both are done on the National Healthcare Providers Registry and both are free.
3. Train the front desk to create an ABHA with Aadhaar OTP. It becomes a routine task once they have done it ten times.
4. Switch on record linking for discharge summaries first, since those are the documents other hospitals ask for most.
5. Put a one-line notice on your registration form so that patients know their records can be linked to their ABHA only with their approval.

Healthixio has cleared all three NHA milestones and does ABHA creation, HFR and HPR registration from inside the software, so the list above is part of onboarding rather than a project. If you want to see it on a live system, ask for a demo.

Frequently asked questions

Is ABDM compulsory for private hospitals?

Participation in ABDM is voluntary for private facilities, but empanelment under government schemes and some state programmes increasingly ask for HFR and HPR IDs. Treat it as a low-cost step to take now rather than a rule to wait for. The registries are free, and an ABDM-integrated HMIS makes the rest routine.

Does ABDM mean the government can see my patient records?

No. Records stay in your hospital's own system. ABDM only moves a record when the patient consents to a specific request, for a stated purpose and period, and every transfer is logged. The registries hold your facility and doctor details, not clinical data. Your HMIS should show you each consent request and exactly what was shared.

What is the difference between an ABHA number and an ABHA address?

The ABHA number is the 14-digit identifier assigned to a person. The ABHA address is a readable handle, similar to an email ID, that the patient uses to receive and approve consent requests. A patient has one number and can use it with an ABHA address of their choice. Your software stores both on the patient record.