ABHA — the patient’s health ID
A 14-digit Ayushman Bharat Health Account that links a citizen’s records across every clinic, hospital and lab. The ABHA address (like name@abdm) lets patients share records without exposing the full number.
ABDM & ABHA
ABDM compliance for Indian hospitals: a practical guide
What the Ayushman Bharat Digital Mission asks of a hospital, how ABHA, HIP/HIU, FHIR and consent fit together, and how a modern hospital system puts them in place — in plain language for administrators, not only developers.
The building blocks
Three things every ABDM hospital needs
ABDM connects once-siloed records into one consented, interoperable network. Three entities do the work.
HIP & HIU
A hospital is a Health Information Provider when it creates records — prescriptions, reports, discharge summaries — and a Health Information User when it requests a patient’s history from elsewhere. One system is usually both.
Consent Manager
No record moves without the patient’s explicit, time-bound consent. They choose who sees what, for what purpose and for how long, and can revoke it any time. Data stays encrypted end to end; the gateway never reads it.
NHA sandbox
The three integration milestones
Certification is staged. Software is tested against the official ABDM APIs in the NHA sandbox before it reaches the live gateway.
M1 — ABHA
Create and verify ABHA accounts at the desk via Aadhaar or mobile OTP, and pull verified demographics so registration is error-free.
M2 — HPR & HFR
Link doctors to the Health Professional Registry and the facility to the Health Facility Registry, so every record carries verified credentials.
M3 — Records & consent
Act as HIP and HIU: link care contexts, run consent requests, and transfer encrypted FHIR records end to end.
Data standards
Records in FHIR R4, coded to national standards
ABDM never moves paper or custom tables — every record is a FHIR R4 document bundle, coded with terminologies any certified system can read.
That is the whole point: a prescription written in one clinic is readable, with consent, by a hospital across the country.
- e-Prescription, Diagnostic Report, Discharge Summary and Wellness bundles
- Diagnoses in ICD-10, labs in LOINC, documents in SNOMED-CT, AYUSH in NAMASTE
- Validated against the official HL7 / NRCeS FHIR profiles
Consent & security
Private by design, and auditable
- End-to-end encryption (ECDH on Curve25519, the ABDM Fidelius scheme) — no server in between can read the data
- Consent is explicit, purpose-bound, time-limited and revocable
- Every request, consent and transfer is logged with timestamps and user IDs under the DPDP Act, 2023
- The raw Aadhaar number is never stored — only the ABHA details UIDAI returns
Where Triovant stands
Triovant HMIS is built for ABDM
Our hospital system implements the ABDM workflows end to end — ABHA at the desk, HPR/HFR on records, FHIR R4 bundles and consented sharing — and we are completing NHA sandbox certification.
We are an independent software company, not a government portal. We say “ABDM-ready” because the integration is built and tested; we will say “certified” only once the NHA has certified it.
Talk to us about your hospital- ABHA creation & verification (Aadhaar / mobile OTP)
- HPR & HFR linkage on every record
- FHIR R4 records signed off by the treating doctor with HPR credentials
- HIP/HIU consent flows with Fidelius encryption
Planning ABDM for your hospital?
Tell us where you are — paper records, an existing HMS, or starting fresh — and we’ll map the path to ABDM.