The rails the platform runs on
ABDM established a national digital health architecture: a unique health identity for every citizen, registries of facilities and professionals, and a consent-based mechanism for exchanging records between them. It is now among the largest digital health identity systems anywhere, with more than ninety crore ABHA identities created.
For RISE this is not an optional integration. A casualty air-evacuated from a disaster zone should arrive at a receiving facility with their record, their allergies and their consent status already present. That is only possible if both ends speak ABDM.
| Building block | Use in the platform |
|---|---|
| ABHA — Ayushman Bharat Health Account | Patient identity. Where a person holds an ABHA, their BAEMS record links to it, so their history follows them between facilities rather than restarting at each one. |
| HFR — Health Facility Registry | Receiving facilities, field clinics and staging medical posts identified against the national registry rather than a local list. |
| HPR — Healthcare Professional Registry | Clinician identity and credentialling, including surge and volunteer clinical staff whose credentials must be verifiable quickly. |
| Consent Manager | Consent-based record access. BAEMS consent events are enforced by smart contract and anchored to the ledger, and reconcile to the ABDM consent framework. |
| HIP / HIU — Health Information Provider and User | The platform operates in both roles: providing records generated in emergency care, and consuming records held elsewhere. |
| FHIR R4 · NRCeS profiles | Clinical exchange across fifteen core resource types, conformant to the India profile set rather than to base FHIR alone. |
| PM-JAY linkage | Coverage and Claim resources carry the linkage that allows an emergency presentation to be reimbursed without a separate paper trail. |
The three integration milestones
- Milestone M1 — Identity
- ABHA creation and verification within the platform, and linkage of the platform record to the citizen's health account. This is the foundation milestone; without it, records cannot follow a patient.
- Milestone M2 — Record linking
- Health records generated in the platform linked to the patient's ABHA and discoverable through the national exchange, subject to consent.
- Milestone M3 — Exchange
- Full consent-based exchange in both directions — the platform as Health Information Provider and as Health Information User.
M1–M3 are committed, not achieved. Certification is earned through a defined external process, and the conformance register states the position for each milestone. See CMP-08.
Terminology and standards
Interoperability fails quietly when two systems exchange perfectly-formed messages containing incompatible codes. The platform binds its clinical domains to the standards the national ecosystem uses: SNOMED CT for conditions, LOINC for investigations, ICD-11 for diagnosis, and ATC for medications, with NRCeS as the India profile and SNOMED authority.
| Domain | Standard | Authority |
|---|---|---|
| Conditions and findings | SNOMED CT | NRCeS affiliate registration |
| Investigations and observations | LOINC | Regenstrief / NRCeS profile |
| Diagnosis | ICD-11 | WHO |
| Medications | ATC | WHO Collaborating Centre |
| Exchange format | FHIR R4 | NRCeS India profiles |
| Units | UCUM | Regenstrief |