ABDM's health-locker — a pragmatic guide for clinics
What ABHA actually does for your practice today, and what it'll do in 2027. Honest take from a clinical software vendor in the rails — without the marketing varnish.
Most articles on the Ayushman Bharat Digital Mission (ABDM) treat it as either a transformational national infrastructure or a slow-moving compliance burden. Both takes are right, depending on your seat. We sit on the software-vendor side of the rails and have been integrating ABDM endpoints since early 2024. Here's what's actually true about ABDM today, what's promised, and what works in practice.
What ABDM actually is
ABDM is a set of standards and APIs maintained by the National Health Authority (NHA) for connecting healthcare actors in India. Three things to remember:
- It's federation, not centralisation. Patient records don't live in a national database. ABDM is the protocol for linking records held by different providers — clinics, hospitals, pharmacies, labs — to a patient identifier (ABHA), with the patient controlling consent.
- ABHA is the patient's identifier. A 14-digit number (or a "username@abdm" handle) that any registered provider can use to attach records to that patient's longitudinal health graph.
- HFR and HPR are the provider identifiers. Health Facility Registry for clinics, Health Professional Registry for doctors. Without these, you can't push records into the rails.
Concretely, when a patient gives consent, your clinic's records for that patient become discoverable by other registered providers — with the patient's explicit per-encounter consent each time. The patient can also pull all their records into an app of their choice.
What it does for a clinic today
This is the part most marketing copy gets wrong. As of mid-2026, ABDM gives a typical clinic three real, concrete capabilities:
1. E-prescribe to ABDM-connected pharmacies. If you're registered (HFR + HPR), every signed Rx can flow to the patient's ABHA wallet within seconds. The patient walks into any ABDM-connected pharmacy, presents their ABHA QR, and the pharmacist pulls the Rx down without paper. ~14,000 pharmacies are ABDM-connected as of Q1 2026 — heavily concentrated in Maharashtra, Karnataka, Tamil Nadu, and Delhi-NCR.
2. Pull labs from ABDM-connected diagnostic chains. If your patient gets an HbA1c at any of the ~1,800 ABDM-connected labs, that report can flow into your chart with one consent tap from the patient. No more "send me the photo on WhatsApp" round-trips. SRL, Dr Lal, Thyrocare, Metropolis, and Apollo Diagnostics are all in the rails. Smaller regional labs are catching up.
3. Receive a patient's longitudinal record on first visit. A new patient walks in. They share their ABHA. With consent, you see their last 6 months of clinical history — past Rx, lab values, hospital discharge summaries — across every other ABDM-connected provider they've used. This is the most powerful feature of all and the one most under-utilised because the consent flow is currently a bit clunky.
What it doesn't do (yet)
Equally important to be honest about:
- It's not a full EHR. ABDM is the rails between EHRs, not an EHR itself. You still need software in your clinic to write notes, manage queue, run billing. ABDM doesn't replace that.
- It doesn't cover every clinical activity. Imaging (DICOM) is just starting to flow through the rails in 2026. Genomics, pathology slides, advanced ECG/EEG — not yet.
- Pharmacist coverage is patchy. The ~14,000 ABDM pharmacies sound like a lot, but India has roughly 850,000 pharmacies. If your patient lives in a small town, your e-Rx may still need to be printed.
- Consent UX is a work in progress. The patient consent flow goes through a separate "Consent Manager" app right now. It works, but it's a context-switch the patient has to navigate. Better UX is on the NHA roadmap.
What the registration looks like in practice
If you're registering your clinic for ABDM today:
- HFR (Health Facility Registry). One per facility. You upload registration certificates, address proofs, photos. Approval takes 2–4 weeks if your paperwork is clean. Some districts are faster than others.
- HPR (Health Professional Registry). One per doctor. Upload medical-council registration, ID proof. Usually 1–2 weeks.
- Connect via a registered HMIS. You can't talk to ABDM directly — you do it through a vendor (us, or any of the other registered ones). Once your HFR and HPR are approved, your vendor enables the rails for your account.
The whole process is do-able in a month if nothing goes wrong, but plan for two if it's your first time. We help every clinic through this and the most common delay is wrong document scans — a blurry photo of a registration certificate gets rejected.
We have a commercial interest in clinics signing up for ABDM via MediSero+, because it makes us stickier. We're trying to be straight about the limitations anyway, because pretending they don't exist would erode the only currency we actually trade in (your trust).
What's coming in 2026 and 2027
Three roadmap items worth knowing about:
UHI (Unified Health Interface). Beyond record exchange, UHI lets a patient discover and book any ABDM-registered provider through any ABDM-registered consumer app. Think Ola/Uber for healthcare bookings. Live in pilot in 4 states; national rollout late 2026. For clinics, this means your booking widget is no longer the only path to your slots — UHI can route patients to you from any partner app.
HCX (Health Claims Exchange). Insurance claims processing on ABDM rails. The pitch: cashless OPD becomes possible because the insurer can pull the visit + Rx automatically with consent, no manual claim form. Live in pilot with star insurers; broader availability through 2026.
Vaccination registry integration. Currently, vaccinations live in CoWIN (for COVID) and various state-level registries (for childhood immunisation under IAP). ABDM is consolidating these into a unified vaccine record on each patient's ABHA. Useful for any clinic that does primary care or paeds — auto-due reminders become trivial when the data is in one place.
Should you bother today?
Honest answer, based on the clinic profile:
If you're a primary-care GP / family physician: Yes. Get the labs flowing in, get the e-Rx out. The patient experience improvement alone — patient walks in, you already have last quarter's HbA1c — is worth the registration friction.
If you're a specialist seeing referred patients: Yes, double yes. The longitudinal record from other providers is exactly what you want before a first consult. Saves you 5–10 minutes per new patient and avoids re-ordering tests.
If you're a single-specialty walk-in clinic with mostly first-time patients (think dental, derm): Less critical today. The longitudinal record advantage is smaller because you're often the patient's only provider for that specialty. Still worth registering for the e-Rx flow if your nearby pharmacies are ABDM-connected.
If you're a hospital or large group: Already mandated in most states. The question is how much you let it actually shape your software, vs treating it as a checkbox.
The deeper bet
The best argument for taking ABDM seriously today is that the network effect compounds. Every clinic that registers makes the next one's value proposition better. The labs are joining at scale. The pharmacies are catching up. The patient app penetration is growing. By 2027 it's plausible that not being on ABDM will be a meaningful competitive disadvantage.
Also: the consent model is genuinely good. Patient owns the data, providers borrow access with explicit consent per encounter, every access is logged on the patient's side. As a foundation for digital health it's substantially better than the EHR-vendor lock-in of the US system. That's worth supporting on its own merits.
How MediSero+ does it
Concretely, on MediSero+ today:
- HFR and HPR setup is a guided in-app wizard. We don't do the actual registration — that's NHA's flow — but we walk you through it and validate documents before you submit.
- Once approved, ABDM is a switch in Settings · Compliance. Flip it and every signed Rx auto-pushes to the patient's ABHA.
- Pulling external records in is a per-patient consent flow at intake. The FD initiates from the patient's profile, the patient approves on their phone, the records flow into your chart within seconds.
- Audit trail of every ABDM transaction is exportable from Settings · Compliance · ABDM logs.
We added ABDM support in late 2024 and have iterated heavily on the UX since. If you're a clinic considering the move and want a walkthrough on real data, write to hello@medisero.com — we'll set up a 20-minute demo on a sandbox account.