HealthcareABDMHealthixio
What ABDM integration actually involves for a 30-bed hospital
Every HMIS vendor in India now says 'ABDM integrated'. Here is what the three milestones are, what changes at your front desk, and what to ask before you sign.
- Author
- Kentron Technologies
- Published
- Reading time
- 4 min read
The Ayushman Bharat Digital Mission is the national programme that gives every Indian a health ID (ABHA) and lets health records move between providers with the patient's consent. Every hospital software vendor now prints 'ABDM integrated' on the brochure. The phrase covers a wide range of realities, from a button that opens the ABHA website in a browser to a system that has passed all three of the National Health Authority's certification milestones. This article explains the difference in plain words, from the point of view of a 30-bed hospital.
The three milestones, in plain words
The NHA certifies software against three milestones. Each is a set of automated and manual test cases run against a sandbox, followed by a review. A vendor that has cleared a milestone has a certificate for it, and you can ask to see it.
| Milestone | What the software must do | What it means for you |
|---|---|---|
| M1 | Create and verify ABHA IDs using Aadhaar, mobile or driving licence, and link the ABHA to your patient record. | Front desk can create an ABHA for a walk-in patient in under a minute, with the patient's OTP. |
| M2 | Act as a Health Information Provider: package OPD prescriptions, discharge summaries and lab reports as FHIR bundles and link them to the patient's ABHA on request. | Records you generate become visible in the patient's ABHA app, once they consent. |
| M3 | Act as a Health Information User: request records from other providers with consent and display them. | A doctor can see a patient's discharge summary from another hospital before the consultation. |
M1 is the easy one and the one most vendors stop at. M2 is where the real engineering sits, because it requires your software to produce structured clinical documents in HL7 FHIR R4 format, not PDFs. M3 closes the loop. Healthixio has cleared all three; the NHA lists it, and the certificates are on the product page.
What changes at the front desk
- Registration gets one extra field, ABHA number, and one extra button, create ABHA. The patient gives a mobile OTP. That is the entire workflow.
- Discharge summaries and prescriptions need to be entered as structured data, not typed into a free-text box, because M2 packages them as FHIR documents. Good software makes this feel like filling a form, not coding.
- Consent requests appear as notifications. Staff approve or reject them; nothing leaves the system without a matching consent artefact.
What does not change
Nothing about ABDM makes a hospital share data by default. The patient owns the consent, and each request has a purpose, a date range and an expiry. Your billing, pharmacy and inventory are untouched. A hospital that never creates a single ABHA still works exactly as before; the integration is there for the patients who want it, and the government schemes that increasingly require it.
Registries: HFR and HPR
Two registries sit alongside the milestones. The Health Facility Registry (HFR) lists your hospital; the Health Professional Registry (HPR) lists your doctors. Both are needed for records to be linked under your facility's name, and both are free to register. A vendor that has done it before can complete your HFR entry in an afternoon. Ask whether it is included in onboarding; in Healthixio it is.
Consent, the DPDP Act and where data lives
ABDM's consent model predates the Digital Personal Data Protection Act 2023 but fits it well: purpose limitation, explicit consent, withdrawal at any time. What the Act adds is obligations on you as a data fiduciary: a grievance mechanism, breach notification and reasonable security. Your HMIS should help with the last one through audit logs, role-based access and data stored in India. Ask where the servers are; the answer should be a city in India, not 'the cloud'.
What to ask a vendor before you sign
- Which milestones have you cleared, and can I see the NHA certificates?
- Can you show me an ABHA being created on a live system, with a real OTP?
- Show me a discharge summary as a FHIR bundle. If they cannot, M2 is not real.
- Is HFR and HPR registration part of onboarding?
- Where is patient data stored, and who has access to the servers?
- What happens to my data if I leave? Ask for the export format in writing.
None of this is exotic. It is a few hours of questions that save a year of regret. If you want to see the answers on a running system, ask for a Healthixio demo.