By Hitesh Ganjoo, Founder
An “ABDM” or “UHI” claim on a proposal doesn't explain your phone bookings. Ayushman Bharat Digital Mission (ABDM) is India's national programme of digital health registries and gateways; Unified Health Interface (UHI) is its open network for finding and booking healthcare services. The UHI documents reviewed here do not describe a patient phone channel.
When a vendor drops “ABDM” or “UHI” into a sales call, I would ask them to finish the sentence. What does their software actually do? A national programme's name doesn't tell a clinic owner where tomorrow's appointment will land.
I read the official documents with that booking question in mind. The National Health Authority (NHA) guidebook compares UHI with Unified Payments Interface (UPI). The developer pages explain the steps. Here is what I would take into a vendor review.
What is ABDM, in plain words?
ABDM gives different healthcare systems common ways to identify people and facilities, exchange records with consent, and handle services and claims. It was launched nationally on 27 September 2021.
Start with the identities. The guidebook names three foundational registries:
- Ayushman Bharat Health Account (ABHA): a unique 14-digit digital health identifier for a person, used to connect health records across providers with informed patient consent.
- Healthcare Professionals Registry (HPR): a national repository of verified healthcare professionals across systems of medicine.
- Health Facility Registry (HFR): a national database covering public and private health facilities, including clinics and hospitals.
Then come three gateways. Health Information Exchange–Consent Manager (HIE-CM) supports sharing health records with consent. UHI covers finding and using healthcare services. National Health Claims Exchange (NHCX) covers health insurance claims. Different jobs, under one programme.
On 15 November 2026, ABDM's own home page showed “98,93,49,721” ABHA numbers, marked “as on 15/11/2026 03:07”. That is the figure on that page at that time. I would not use an identity count to judge whether a particular clinic's booking workflow works.
What is UHI, and how does a booking travel?
UHI connects patient apps to provider systems through a shared network. The developer introduction says an app joins once and can reach providers on that network, without a separate arrangement with each one.
There are three participants. The patient or caregiver uses an End User Application (EUA); the documentation gives Aarogya Setu and the ABHA app as examples. The provider's system is a Health Service Provider Application (HSPA). NHA runs the UHI Gateway.
The Gateway introduces them.
A patient's search for a doctor goes through the Gateway to provider systems, and their answers come back through it. Once the patient chooses a provider, the app talks directly to that provider's system. For Physical Consultation, even the second search, for the chosen doctor's slots, goes directly. Booking, tracking and cancellation follow that direct route. The provider system also sends the Gateway audit copies of specified order callbacks, so “direct” does not mean no audit record (UHI routes).
The documents call the four stages Discovery, Order, Fulfilment and Post-fulfilment (DOFP). In Physical Consultation, that means finding a doctor, choosing and booking a slot, checking in and completing the visit, with cancellation and messaging also covered.
The provider system holds the selected slot for 15 minutes while booking proceeds. The patient accepts the terms; confirmation brings a four-digit personal identification number (PIN) for check-in at the clinic. A hold is not the confirmation.
Physical Consultation is described as the one end-to-end UHI service in the reviewed documentation. Ambulance Booking reaches discovery and a quote in Phase 1, with fulfilment and post-fulfilment assigned to Phase 2. The other listed services, including blood-bank and Jan Aushadhi discovery, stop at discovery.
Payment has a boundary too. Physical Consultation uses pay on visit. Online payment before booking and refunds through the UHI flow are outside its current scope. The UPI comparison describes the open-network idea; it should not be read as a promise that UHI handles the bill.
There is also an onboarding dependency: the UHI introduction says an EUA must complete Milestone 2 on HIE-CM before joining any UHI service.
What does this change for patient booking by phone?
In my view, phone and app bookings need one dependable account of availability. The clinic should be able to point to the system that owns the slot calendar.
Take a hypothetical dermatology clinic in Pune. A daughter calls to move her father's Friday consult to Saturday morning. At the same time, another patient selects that Saturday slot in an app. I would want the clinic's team to see the app's hold before promising the slot on the phone.
In this example, I would not promise the same slot to two patients.
UHI's documented 15-minute hold makes this a concrete test. Ask the vendor to hold a slot through the app, then try to book it by phone. Let the hold expire and try again. Confirm it, then cancel it. Watch what the clinic's calendar shows at each step.
These are my suggested tests, not claims about a particular deployment. I would also check what the caller hears when the calendar does not answer. “I couldn't confirm that appointment” is a useful answer. A confident “booked” without a confirmation is not.
Where do voice agents fit, honestly?
The reviewed UHI documents describe app-to-provider application programming interface (API) roles: EUA and HSPA. They do not describe a patient phone channel. I would keep the call workflow and the network workflow distinct when reviewing a proposal.
There is a voice initiative in the ABDM material, but it does a different job. NHA's Expression of Interest (EoI), published on 2 September 2026, seeks ambient voice-to-text solutions that turn doctor-patient conversations into structured clinical records for clinician review and approval. The records follow Fast Healthcare Interoperability Resources (FHIR), a standard for structuring health information. Preparing a consultation record is different work from answering a patient's booking call.
Consent needs its own demonstration.
In the documented record-sharing flow, a Health Information User (HIU) requests access. The patient approves or denies it through the PHR app. A Health Information Provider (HIP), which holds the records, supplies the authorised information after the relevant checks. The Milestone 2 example explicitly shows approval in the ABHA app.
A voice call is not part of that documented consent flow. If a vendor claims it can access those records during a call, I would ask it to show where approval is captured and how access stays within that approval. I would not treat a spoken “yes” as evidence that these documented steps occurred.
Registration and software integration also need separate evidence. HFR identifies facilities; HPR identifies professionals. The HIE-CM sandbox page gives six stages for software: request access, receive approval, integrate the applicable APIs, complete functional testing and a security audit, demonstrate the solution to the Health Tech Committee for production approval, then go live. A clinic's registry entry does not demonstrate that a vendor completed those stages.
What would I ask a vendor who says “ABDM” or “UHI”?
I would ask for a demonstration tied to the proposed software. Seven questions, with evidence beside each answer.
- A role should have a name. Are you acting as a HIP, HIU, EUA or HSPA? Which milestones and service are covered? Please show the role in the workflow you are selling us.
- Sandbox access is a stage. What evidence shows the move from testing to approved production use? Which product and version does it cover? I would ask for the approval evidence, not only a screenshot of a working test.
- Scope belongs in writing. Does this integration create an identity, link records, request records, discover providers or complete bookings? Which steps remain with our staff or another system?
- The calendar needs an owner. Which system owns availability? Show what happens when an app holds a slot and someone tries to book it by phone. Who resolves a disagreement?
- A number is not a consent demonstration. How do you handle ABHA details on a call, and where does the patient approve record access? Show what happens after denial or withdrawal. For further reading on the broader questions, see our DPDP and hospital voice AI post.
- A caller must be able to reach a person. What happens when someone asks for the clinic team, or asks a clinical question? What context reaches the person taking over, and what happens outside their working hours?
- The outcome needs a record. Can we review the request, booking result and handover? Who can access those logs, and for how long? Ask what is excluded too: the Physical Consultation documentation says its check-in PIN must never be written to a database or log.
I would keep these answers with the proposal. They are easier to check before a rollout than to reconstruct after a disputed appointment.
Krisper for patient enquiries
Krisper, our healthcare voice agent, has already supported over 100,000 patients. For patient enquiries, Krisper works through enquiries already in a customer relationship management (CRM) system. It calls those people and answers questions on cost, process and timeline using the team's approved information.
The outcome goes back to the CRM. When the person wants a consult, Krisper can book, reschedule or confirm it using the provider's availability and rules. It connects to existing phone numbers, CRM and calendar.
It says it is an AI. Education here means explaining the approved information, not giving medical advice. When someone needs a person or clinical judgement, Krisper hands over with the context of the call.
This post describes the national programme. It does not say that Krisper connects to ABDM or UHI.
FAQ
What is the difference between ABDM and UHI?
Ayushman Bharat Digital Mission (ABDM) is the national digital health programme, with registries and gateways for identities, health records, claims and services. Unified Health Interface (UHI) is the open network within it for finding and using healthcare services.
What is an ABHA number?
An Ayushman Bharat Health Account (ABHA) number is a unique 14-digit digital health identifier. It helps identify a person across healthcare providers and connect their health records; the ABDM components page specifies informed patient consent for linking records across systems.
What does UHI Physical Consultation cover today?
In the documentation reviewed on 15 November 2026, it covers finding a doctor, selecting and booking a slot, receiving a four-digit check-in PIN, visiting the clinic, status tracking and cancellation. It also includes messaging. The provider system holds the selected slot for 15 minutes during booking.
Does UHI handle payments?
The reviewed Physical Consultation flow uses pay on visit. Online payment before booking and refunds through UHI are outside its current scope. Its payment terms say that UHI and the patient app do not collect, hold, settle or refund the fee.
Which application roles do the reviewed UHI documents describe?
They describe End User Applications (EUAs), used by patients or caregivers, and Health Service Provider Applications (HSPAs), which represent providers.
Who runs the UHI Gateway?
The National Health Authority (NHA) runs the UHI Gateway. It routes discovery searches and responses. Booking proceeds directly between the patient app and provider system, with specified Physical Consultation audit copies sent to the Gateway.
Source notes
Reviewed 15 November 2026 (Asia/Calcutta). Based on the official documents and page snapshots reviewed on that date. Service scope refers to those documents; it is not evidence of any particular vendor's deployment. The booking tests and vendor questions are my recommendations. This is an operational guide, not legal advice.
- NHA, ABDM State Adoption Index: A Reference Guidebook, April 2026, p. 1: launch date, registries, gateways and UPI comparison: https://abdm.gov.in/strapicms/uploads/ABDM_A_Reference_Guidebook_97b46e09ce.pdf
- ABDM components: ABHA, professional and facility registries: https://abdm.gov.in/abdm-components
- ABDM home page: the ABHA figure in the supplied snapshot, marked as on 15/11/2026 03:07: https://abdm.gov.in/
- UHI developer introduction: participants, service coverage, DOFP and EUA onboarding: https://docs.abdm.gov.in/docs/uhi/v1
- UHI network routes: discovery, direct booking and audit copies: https://docs.abdm.gov.in/docs/uhi/v1/concepts/routes
- UHI Physical Consultation: booking hold, check-in PIN, payment scope and terms: https://docs.abdm.gov.in/docs/uhi/v1/services/consultation
- Scan and Share counter flow: profile-sharing consent and 60-minute token: https://docs.abdm.gov.in/skills/abdm-m1/references/functionalities/scan-and-share.md
- OPD token generation: patient profile sharing with the scanned facility: https://docs.abdm.gov.in/docs/hiecm/v3/api/p2/endpoints/p2-abdm-hiecm-patient-share-phr/01-p2-post-patient-share-v3-share
- HIE-CM Milestone 2: provider role, FHIR records and ABHA-app consent example: https://docs.abdm.gov.in/docs/hiecm/v3/milestones/m2
- HIE-CM Milestone 3: user role and consent-based record access: https://docs.abdm.gov.in/docs/hiecm/v3/milestones/m3
- HIE-CM sandbox: six stages from access request to production: https://docs.abdm.gov.in/docs/hiecm/v3/getting-started/sandbox
- NHA, Open-Source Ambient AI enabled Voice-to-Text Solutions for Digital Health Record Creation under ABDM, EoI published 2 September 2026, pp. 1 and 4–5; official notice page: https://abdm.gov.in/partner-offers
