Blog/Digital health/Voice agents

UHI and ABDM for Indian Clinics: Where Voice Agents and Patient Booking Fit

What ABDM and UHI mean for Indian clinics: how app bookings travel, where phone calls fit, and what to ask a vendor about calendars, consent and scope.

Patient phone screens and clinic doorways linked through a navy hub, with one amber line connecting a phone directly to a clinic on a warm paper background.
Conceptual illustration: a shared hub introduces patient apps and clinics; an amber line represents the direct booking connection. This is a metaphor, not a technical diagram.
In brief
  • The programme has separate jobs. Patient identities, health records, insurance claims and finding healthcare services sit in different parts of it.
  • Discovery and booking take different routes. The Gateway routes the initial search; the patient app and provider system then book directly.
  • I would ask to see one whole booking. Check the calendar, the patient's consent and the handover to your team before accepting a broad vendor claim.

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.

The programme

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.

The booking path

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.

At the counter

How is this different from Scan and Share?

Scan and Share starts at the facility's QR code. In the documented counter flow, the patient scans it in a Personal Health Record (PHR) app, reviews their profile and agrees to share it with the facility. The patient then receives an outpatient department (OPD) token valid for 60 minutes.

That token is for the counter. The OPD token API describes sharing the patient's profile with the facility whose code was scanned. UHI Physical Consultation describes finding a doctor and reserving a slot. I would ask a vendor to demonstrate both separately if they put both on the proposal.

My view on operations

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.

The vendor review

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.

  1. 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.
  2. 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.
  3. 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?
  4. 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?
  5. 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.
  6. 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?
  7. 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.

Patient enquiries and education

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

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.

Hitesh Ganjoo, Founder

Hitesh Ganjoo is Founder of Iksha Labs. The team builds the safety and policy layer that healthcare agents run on, with Krisper as its flagship healthcare voice agent.

Next step

See the system behind the voice.

Explore how Iksha Labs approaches safety, policy and accountable execution, or bring these questions to a conversation with our team.