ABHA and ABDM readiness,
stated honestly
Ayushman Bharat Digital Mission is changing what Indian hospitals are expected to support. Here is what ABHA and ABDM actually mean for your facility, exactly what iHospital365 does today, and exactly what is still on our roadmap — separated, so you can make a buying decision on facts rather than a compliance badge.
What ABHA and ABDM actually are
ABDM — the Ayushman Bharat Digital Mission — is the Government of India programme building a national digital health infrastructure: a way for a patient's records to move between the hospitals, clinics, labs and pharmacies that treat them, with the patient controlling who sees what.
ABHA — Ayushman Bharat Health Account — is the piece your front desk meets first. It is a health ID that belongs to the patient, not to your hospital. Records created anywhere can be linked to it, and the patient grants or revokes access through a consent manager.
Software connects to this through the ABDM Sandbox, in milestones: M1 covers ABHA creation and verification, M2 covers the professional and facility registries, and M3 covers consent-based health information exchange. A vendor that says "ABDM compliant" without naming a milestone is telling you nothing — that is the question to ask us, and every other vendor you shortlist.
Where iHospital365 stands
Two columns, no blurring between them. The left column is running in the product now. The right column is work we have committed to and have not finished.
Available today
Shipped and in use by hospitals running iHospital365.
ABHA ID on the patient record
Every patient profile carries a unique ABHA / iH365 ID field with family grouping, so the identifier is captured and searchable from the day you start using the system.
One record per patient, across departments
OPD visits, IPD admissions, prescriptions, reports and bills sit on a single patient timeline — the prerequisite for sharing anything meaningfully later.
Role-based access and audit trails
Granular RBAC decides which staff member sees which part of a record, with audit trails on edits — the access discipline ABDM and the DPDP Act both assume.
Data stored in India
Records are held on managed cloud infrastructure inside India, with AES-256 encryption at rest and TLS in transit.
On the roadmap — not available yet
We are working towards ABDM Sandbox integration. None of the below is live, and we publish no date for it.
ABDM Sandbox — Milestone 1 (ABHA)
ABHA number and ABHA address creation and verification through the ABDM sandbox, so a patient without an ABHA can be enrolled at your front desk.
Milestone 2 — Healthcare Professional Registry
Linking your registered practitioners to the HPR, and the facility itself to the Health Facility Registry.
Milestone 3 — Health Information Exchange
Consent-based exchange of health records with other ABDM-registered providers through the HIE-CM, so a patient's history follows them between facilities.
What we are not claiming
iHospital365 is not ABDM-certified, is not connected to the ABDM production gateway, and holds no security certification. ABDM and the DPDP Act 2023 are alignments we have built toward, not compliance we have been granted. If ABDM integration is a hard requirement for your facility today, tell us on the demo call and we will say so plainly rather than sell you a roadmap.
What a hospital should do before ABDM arrives
The work that makes ABDM integration easy later is work worth doing anyway — and almost none of it depends on the gateway being live.
Get off paper registers, so there is a structured record to link at all
Collect ABHA IDs at registration now — the field already exists on the patient profile
De-duplicate patients, so one person is one record rather than four
Put role-based access in place before records become shareable outside your walls
Ask us the hard ABDM questions
Book a walkthrough and bring your compliance checklist. We will show you what runs today and tell you what does not.
ABHA integration and ABDM-ready hospital software in India
Hospitals evaluating an HMS in 2026 keep hitting the same question: is this software ABDM compliant? The honest answer for most vendors is more complicated than their website suggests. Here is what the standard actually requires, and where iHospital365 is.
What does 'ABDM compliant hospital software' mean?
There is no single ABDM compliance badge. Integration happens through the ABDM Sandbox in milestones — Milestone 1 for ABHA number and address creation and verification, Milestone 2 for the Healthcare Professional Registry and Health Facility Registry, Milestone 3 for consent-based Health Information Exchange. A vendor is only ever compliant with specific milestones, in a specific environment (sandbox or production).
So the useful question is not 'are you ABDM compliant?' but 'which milestones have you cleared, in sandbox or production, and can I see it working?' Ask every vendor on your shortlist, including us.
Where iHospital365 is today
Today, iHospital365 captures the ABHA / iH365 ID on the patient profile with family grouping, keeps every visit on one de-duplicated patient record, enforces role-based access with audit trails, and stores data on managed cloud infrastructure in India. ABDM Sandbox integration across Milestones 1, 2 and 3 is on our roadmap and is not live.
We are not ABDM-certified and we are not connected to the ABDM production gateway. If national health record exchange is a requirement for your facility this financial year, we would rather tell you that on the demo call than after the invoice.
- Available now: ABHA ID field on the patient record, family grouping, duplicate detection
- Available now: role-based access, audit trails, data stored in India, AES-256 at rest
- Roadmap: ABDM Sandbox M1 (ABHA creation and verification)
- Roadmap: M2 (HPR / HFR registration) and M3 (consent-based health information exchange)
Getting your hospital ready before the gateway is live
Almost all the preparation for ABDM is preparation you want regardless: structured digital records instead of paper registers, one patient ID per human being rather than four duplicates, and access control that can answer who read a record and when. A facility that has done that work can adopt ABHA linking as a configuration change. A facility still on registers cannot, no matter which vendor it buys.
Frequently asked questions
Is iHospital365 ABDM compliant?
No — not yet, and we will not claim otherwise. ABDM Sandbox integration for Milestone 1 (ABHA), Milestone 2 (Healthcare Professional Registry) and Milestone 3 (Health Information Exchange) is on our roadmap. What works today is the ABHA / iH365 ID on the patient record, one unified patient timeline, role-based access with audit trails, and data stored in India.
Can we record ABHA IDs for our patients right now?
Yes. The patient profile carries a unique ABHA / iH365 ID field with family grouping today, so you can start collecting ABHA numbers at registration immediately. Creating or verifying an ABHA through the ABDM gateway from inside the software is roadmap, not current functionality.
What is the difference between ABHA and ABDM?
ABDM (Ayushman Bharat Digital Mission) is the national digital health programme. ABHA (Ayushman Bharat Health Account) is the health ID it issues to each patient. Records linked to an ABHA can be shared between providers with the patient's consent, so ABHA is the identifier and ABDM is the infrastructure around it.
What should we ask an HMS vendor about ABDM?
Ask which ABDM Sandbox milestones they have cleared, whether that is in sandbox or production, whether they can demonstrate ABHA creation live, and how consent artefacts are stored. Any vendor answering only 'we are ABDM compliant' has not answered the question.
Is iHospital365 DPDP Act 2023 compliant?
iHospital365 is built to DPDP Act 2023 principles — privacy by design, role-based access, audit trails, encryption at rest and in transit, data held in India — but is not certified compliant, and we hold no security certification. See the security standards page for the current status of each item.