Introduction
The Ayushman Bharat Digital Mission (ABDM) is India's national health data network, run by the National Health Authority (NHA). It is three gateways, not one, and this section documents the second of them.
UHI is the Unified Health Interface, ABDM's open network for finding and booking a health service. After this page you will know which role to build, how far each service goes, and where the protocol is written down.
HIE-CM moves records that already exist. UHI finds a doctor, an ambulance or a unit of blood before any record exists.
The gate before anything else
Your application must have completed ABDM M2 with HIE-CM before it can be onboarded to any UHI service. This applies to every service on the network. UHI sits on top of HIE-CM, it is not an alternative to it.
Two roles
| Role | Full name | What it does |
|---|---|---|
| EUA | End User Application | The patient facing app. Searches, shows results, books, displays status. |
| HSPA | Health Service Provider Application | The provider platform. Holds availability, answers searches, drives the booking lifecycle. |
The HSP is the hospital, clinic, doctor, ambulance operator or blood bank, and the HSPA is its digital interface. The gateway is the network's routing layer. Each service page says which roles it accepts.
Services
A service is identified by fixed values inside the call, not by a different endpoint. All three documents behind this page use core_version 0.7.1.
| Service | Domain code | Discovery | Order and quote | Booking and lifecycle |
|---|---|---|---|---|
| Physical consultation | nic2004:85111 | search, on_search | init, on_init | confirm, on_confirm, status, on_status, on_update, cancel, on_cancel, on_message |
| Ambulance booking | nic2008:86909 | search, on_search | init, on_init | Not open for onboarding yet |
| Blood bank | nic2008:86906 | search, on_search | Not in this service | Not in this service |
Four more services have their own onboarding documents and their own pages: Jan Aushadhi Kendra, Jan Aushadhi medicine search, AMRIT pharmacy and PMJAY HEM.
Two transports in one flow
Discovery goes through the gateway, which broadcasts your one search to every registered HSPA in that domain, so several on_search calls come back. Everything after discovery is point to point between your EUA and the HSPA the patient chose. There is no central UHI API for those stages.
Every call is asynchronous and signed.
Next
- Network and protocol, for the message pairs, the
contextblock, Ed25519 signing and the network registry lookup - Onboarding, for the route from M2 to sandbox credentials to production
- Physical consultation, the service with the full booking lifecycle
- Support