ABDM Compliance

Overview

Yes, NICE HMS is fully ABDM-certified. The Ayushman Bharat Digital Mission (ABDM) is India's national digital health ecosystem. NICE HMS has been certified by the National Health Authority (NHA) across all three milestones — M1, M2, and M3.

In plain terms: your patients can create and link their ABHA Health ID, you can share their health records with other ABDM-connected providers, and you can pull in records from other hospitals — all with patient consent.

M1: Health ID (ABHA)

What it does: Creates and links ABHA (Ayushman Bharat Health Account) numbers to patient records in your NICE HMS.

Capability	How It Works in NICE HMS
Create ABHA via Aadhar	Patient provides Aadhar number → OTP verification → ABHA created
Create ABHA address	Patient chooses a username@abdm address (e.g., ramesh.kumar@abdm)
Link existing ABHA	Enter existing ABHA number or address → OTP verification → linked to patient record
View ABHA profile	Fetch and display patient's ABHA profile (KYC photo, demographics)
ABHA address suggestions	Auto-suggest available ABHA addresses during creation

Patient workflow:

Registration desk opens patient record in NICE HMS
Clicks "Link ABHA" or "Create ABHA"
Patient provides Aadhar and receives OTP on their registered mobile
OTP verification completes the linking/creation

M2: HIP (Health Information Provider)

What it does: Shares patient health records with other ABDM participants when the patient gives consent.

Capability	How It Works in NICE HMS
HIP-initiated linking	When a clinical document is finalized (OPD consultation, prescription, discharge summary), NICE HMS automatically generates a link token, registers the care context with ABDM, and notifies the patient's PHR app that new records are available
Discovery (patient-initiated) linking	Patient initiates linking from their PHR app — ABDM sends a discovery request to NICE HMS, which matches the patient and returns available care contexts for the patient to approve
Care context management	Define what health records to share (OPD visits, IPD admissions, lab reports) — each encounter and composition becomes a discoverable care context
Health record sharing	On patient consent, push FHIR-compliant health records to the requesting HIU
Notify	Send notifications to HIUs when new or updated health records are available under an existing care context

How HIP-initiated linking works:

Doctor finalizes a clinical document (e.g., OPD consultation record) in NICE HMS
NICE HMS automatically generates an ABDM link token and registers the encounter as a care context
If the patient has an ABHA address, NICE HMS notifies ABDM that new health data is available
The data flows to the patient's PHR app automatically and immediately — no manual action needed

How discovery (patient-initiated) linking works:

Patient uses their PHR app to search for their records at your facility
ABDM sends a discovery request to NICE HMS
NICE HMS matches the patient and returns available care contexts
Patient authenticates and approves linking from their PHR app — data then flows automatically to the PHR app

M3: HIU (Health Information User)

What it does: Pulls patient health records from other ABDM-connected facilities, with patient consent.

Capability	How It Works in NICE HMS
Discover care contexts	Search for patient's linked health records across the ABDM network
Request consent	Patient receives a consent request in their PHR app
Fetch records	On consent approval, pull FHIR bundles containing the patient's history
View imported records	Display pulled records within the patient's NICE HMS record

Use case: A patient with diabetes comes to your hospital. They were previously treated at another ABDM-connected hospital. With their consent, you pull their past HbA1c results, medications, and discharge summaries directly into NICE HMS — no phone calls, no missing reports.

Certification Status

NICE HMS is integrated with all three ABDM gateway instances:

Gateway	Purpose	Protocol Versions
M1	Health ID services	V3
M2	HIP (health record sharing)	V3
M3	HIU (health record access)	V3

All 12 mandatory ABDM APIs are implemented and functional. The platform has been tested in the ABDM sandbox environment and is live with multiple facilities.

Technical Notes for IT Teams

ABDM API communication uses HMAC-signed JWT authentication
Patient consent tokens are managed per session
FHIR R4 is the data exchange format for health records
All ABDM calls are logged for audit and troubleshooting
Callback URLs are managed through the ABDM bridge

FAQ

Q: Does NICE HMS support ABDM? A: Yes, fully. NICE HMS is NHA-certified for M1 (Health ID creation and linking), M2 (HIP — sharing health records), and M3 (HIU — pulling patient records from other providers).

Q: Is ABDM mandatory for Indian hospitals? A: With NHCX in place, ABDM is unavoidable for any hospital processing insurance claims. NHA mandates ABDM compliance for government scheme empanelment, and private insurers are increasingly requiring it through the NHCX network. NICE HMS makes compliance straightforward.

Q: How do patients give consent for record sharing? A: Through their ABHA/PHR mobile app or via OTP-based authentication. The patient controls exactly what records are shared and with whom.

Q: Can we use NICE HMS for ABDM without linking all patients? A: Yes. ABDM features are opt-in per patient. You can link only the patients who need ABDM services.