25 August 2026 · TechSlideITS
ABDM and ABHA: what it practically means for a small hospital
There is a lot written about India's digital health stack and very little about what a fifty-bed hospital actually has to do.
India's digital health programme generates a lot of explanation aimed at policy readers, and not much aimed at someone running a fifty-bed hospital who wants to know what changes on Monday.
Here is the practical shape of it. Treat this as orientation rather than compliance advice — the specifics evolve, and they should be confirmed against current official guidance for your facility type.
The three pieces
ABHA is a health account identifier belonging to the patient. It is theirs, not any hospital's, and it lets records from different providers be associated with the same person.
Facility and practitioner registries are where hospitals and clinicians are listed, so that a record can be attributed to a verifiable source.
The exchange layer is how records move between providers, with the patient's consent, when someone requests them.
The important design point: records are not centrally stored. Providers keep their own, and share on request with consent.
What changes at your registration desk
Practically, one step: offering to capture or create the patient's ABHA alongside your own registration.
Your own patient identifier does not go away. The ABHA sits alongside it as a link to the wider system. Patients can decline, and that has to be handled gracefully rather than treated as an exception.
The realistic friction is time at a busy counter. Anything that adds meaningful seconds per patient will be skipped when there is a queue, which is worth testing before committing to a workflow.
What is genuinely optional, and what is not
This is where most confusion sits, and where the answer changes over time.
Broadly: registering your facility and being able to associate records with an ABHA are the foundational steps. Full record-sharing capability is a larger undertaking and is generally approached in stages.
What applies to your facility depends on its type, its location, and current policy. Any vendor telling you a single flat answer is oversimplifying, and any vendor claiming full certification should be asked to show precisely what they are certified for and when.
Questions worth asking a software vendor
- Can we capture and verify an ABHA at registration today, and what does that add to counter time?
- Is our facility registration something you assist with, or entirely ours?
- What specifically is implemented — identifier capture, or record sharing with consent?
- How do you handle a patient who declines?
- When policy changes, is updating this part of support or a chargeable change?
The last question is the one that separates a maintained integration from a one-off build.
The honest recommendation
For most small hospitals, the sensible position is to get your own records in order first.
A hospital whose OPD, pharmacy, lab and billing are already connected around one internal patient identifier is in a good position to add ABHA linkage, because the hard part — one coherent record per patient — is already done.
A hospital still running departments on separate systems will find digital health integration hard for the same reason it finds discharge billing hard. Fixing the internal picture first is not a delay; it is the prerequisite.
If you want to see how patient records are held together, see MediNexus, or MediNexus Lite for smaller facilities. Or talk to us.
Frequently asked questions
ABHA is a health account identifier that belongs to the patient, not to any hospital, and lets records from different providers be associated with the same person. Your own patient identifier does not go away — the ABHA sits alongside it as a link to the wider system.
Practically one step: offering to capture or create the patient's ABHA alongside your existing registration. Patients can decline and that must be handled gracefully. The realistic friction is counter time, so test the workflow at a busy hour before committing to it.
No. Providers keep their own records and share them on request with the patient's consent, through an exchange layer. That is a deliberate design choice and it is why your internal record-keeping still matters as much as it did.
Whether ABHA can be captured and verified at registration today and what it adds to counter time, whether facility registration is assisted, what specifically is implemented — identifier capture or full record sharing with consent — how a declining patient is handled, and whether policy updates are covered by support or charged as changes.
Usually after getting its own records in order. A hospital whose OPD, pharmacy, lab and billing already share one internal patient identifier is well placed to add ABHA linkage, because the hard part is done. One still running departments on separate systems will struggle for the same reason discharge billing is slow.