ABDM INTEGRATION

From ABHA Creation to
Consent-Driven Health Records

Connect your HIMS with India's digital health ecosystem through a secure, consent-based workflow that enables patient identification, health record discovery, linkage, and controlled sharing.

M1

ABHA Creation & Patient Identification

Create or identify the patient's ABHA and establish a digital health identity that can be used across the entire ABDM ecosystem.

01 — Patient Identification
Patient provides required demographic details through the native HIMS registration workflow.
Rahul Sharma | Male | 34 Yrs
02 — ABHA Verification / Creation
HIMS securely connects to ABDM gateways to identify an existing ABHA or initiate creation.
ABHA Status Inquiry: Initiating New Creation
03 — Identity Verification
Aadhaar / Mobile OTP •••••• Verified
04 — ABHA Generated
ABHA Number Generated
91-4455-6677-8899
05 — Link ABHA With HIMS Patient
The digital identity is permanently tethered to the local hospital medical record.
M1 Result
Patient now has a verified digital health identity connected with the HIMS patient profile.
HIMS DATABASE
UHID: P-98210
Local Record Active
ABHA
Health Identity Number
91-4455-6677-8899
Rahul Sharma
Identity Verified
PATIENT IDENTITY
+91 98*** ***12
OTP Authenticated
M2

Health Record Linkage & Discovery

Discover and connect eligible digital health records with the patient's digital identity through the ecosystem, subject to participating systems.

01 — Patient Initiates Discovery
Find My Health Records
02 — Health Record Discovery
ABDM gateway queries authorized Health Information Providers (HIPs).
Hospital A Lab B Clinic C
03 — Available Records Identified
OPD Consultation Oct 2025
Lab Report (CBC) Nov 2025
04 — Record Matching & Linkage
ABHA Health Record
Linked
M2 Result
Relevant digital health records discovered and linked to the patient's digital health identity.
ABHA
HOSPITAL A
Discharge Sum.
PATH LAB B
Blood Report
CLINIC C
Prescription
M3

Consent Management & Secure Information Sharing

Give patients complete control over how their health information is requested, accessed, and shared through a secure, consent-driven workflow.

01 — Consent Request
A healthcare provider requests access to specific health records for a defined clinical purpose.
02 — Patient Reviews Consent
Patient receives notification and reviews exactly what data is requested, by whom, and for how long.
03 — Consent Granted
Status
Active
Validity
30 Days
04 — Health Information Exchange
Authorized encrypted data exchange occurs through the ABDM ecosystem.
05 — Consent Lifecycle
Active Expiring Revoked/Expired
M3 Result
Health information is accessed or shared strictly through the patient's authorization governing the permitted use.
CONSENT DASHBOARD
Health Information Access
Requested By
City Care Hospital
ACTIVE
Purpose
Clinical Consult
Duration
30 Days
Requested Info
Lab Reports Prescriptions

Connected Digital Health Experience

A seamless architectural flow ensuring compliance, interoperability, and security at every data touchpoint.

M1
ABHA
Digital Identity
M2
DISCOVERY
Record Linkage
M3
CONSENT
Secure Sharing
WhatsApp