The short version

ABDM, without the acronyms

The Ayushman Bharat Digital Mission is the Government of India's push toward a national, interoperable digital health ecosystem — one where a patient's records can follow them between facilities, with their consent. PatientOne's registration, clinical, and lab modules are built with this framework in mind rather than treating it as an add-on.

The building blocks

What PatientOne supports

ABHA

Patient health ID creation & linking

At registration, front desk staff can create a new ABHA (the patient's national digital health ID) or link an existing one — so records can later be shared with the patient's consent, not stored in isolation.

HFR / HPR

Facility & practitioner registries

Support for registering your facility in the Health Facility Registry and your doctors in the Healthcare Professionals Registry — a prerequisite for participating in ABDM exchanges as a recognised provider.

FHIR R4

Structured clinical records

Prescriptions, lab reports, and discharge summaries are structured around HL7 FHIR R4 — the format ABDM uses for health data exchange — rather than proprietary formats that need translating later.

Consent

Consent-based sharing

Records aren't pushed anywhere without the patient approving it through the consent flow — every grant and revocation is logged, so nothing moves on assumption.

How facilities usually adopt this

Two stages, in practice

Most facilities move through this in roughly this order — later stages (like consent-based record exchange and insurance claim integration through the National Health Claims Exchange) build on top of it.

Stage 1
Register & link. Your facility and practitioners are registered in the HFR/HPR, and patients can create or link an ABHA at the front desk.
Stage 2
Share records. Your facility becomes a Health Information Provider — discharge summaries, prescriptions, and lab reports can be shared to a patient's ABHA-linked locker, with consent.
Data protection

DPDP Act alignment

India's Digital Personal Data Protection Act applies to patient data regardless of ABDM participation. PatientOne is built around consent capture and an audit trail for every read and write against a patient record — who accessed it, when, and why — which matters for medico-legal reasons as much as regulatory ones.

ABHA READYCreation & linking at registration
HFR / HPRFacility & practitioner registry support
FHIR R4Structured, exchange-ready records
DPDP ALIGNEDConsent capture & audit logging

This is a general overview, not a certification claim — requirements differ by facility type (private clinic vs. PM-JAY empanelled hospital vs. state scheme) and continue to evolve. We'll walk through exactly what applies to your facility before you commit to anything.

Questions specific to your facility?

Let's go through your compliance checklist together

Bring your facility type, any state scheme you're empanelled under, and we'll map out what actually needs doing.