Skip to main content

​
In short

  • The app searches UHI for doctors, fetches a doctor’s open slots and books one for the patient.
  • The patient accepts the quote and the provider’s terms before the app confirms.
  • The provider returns a PIN that the patient shows at the clinic.
  • The app keeps the booking’s reference to check status, reschedule or cancel later.

​
Who and when

A consumer health app, such as a Personal Health Record (PHR) app, used by a patient who wants to see a doctor in person. The patient opens the app and asks for a doctor by speciality, name, facility or location. The app searches doctors across the Unified Health Interface (UHI), not only one hospital’s own list, and books the visit on the patient’s behalf. Already in place: your app acts as a UHI consumer app on Eka. The patient has an ABHA and is logged in on your app. That means you hold Eka’s id for the patient (Log in to an existing ABHA). Your server can receive Eka webhooks.

​
What they want

“Find a doctor near me who can see me this week, book a slot, and tell me what to show at the clinic.”

​
The steps

  1. The patient describes who they want to see. That can be a speciality, a doctor’s name, a hospital, a district or pincode, or their current location with a radius. They choose the days they are free.
  2. The app searches UHI for doctors who match and shows the list: name, qualifications, languages, years of experience, facility and address. → workflow: Book a physical consultation over UHI
  3. The patient picks a doctor. The app fetches that doctor’s open slots for the chosen window, with the price of each. → same workflow
  4. The patient picks a slot and gives billing details. The app starts the booking and shows the quote, the price breakup and the provider’s terms. → same workflow
  5. The patient accepts the terms. The app confirms the booking. The provider returns a PIN that the patient shows to the doctor before the consultation. → same workflow
  6. Before the visit, the app checks the booking’s status and shows it to the patient. → same workflow
  7. The patient goes to the clinic, shows the PIN, and sees the doctor. This is a human step.

​
What they have at the end

The patient has a confirmed in-person appointment with a named doctor at a named facility, at a known start and end time. They hold the PIN to show at the clinic. Your app holds the booking’s reference, the provider’s identifier and the transaction’s identifier, so it can check status, reschedule or cancel later.

​
Branches

  • No doctor matches the search. The patient widens the search: a larger radius, another speciality, or a wider time window. → same workflow, search step
  • The doctor has no open slot in the window. The patient picks another window or another doctor. → same workflow, slot search step
  • The patient wants another time. The app moves the booking to a new slot. → same workflow, update step
  • The patient cannot go. The app cancels the booking and confirms the cancellation. → same workflow, cancel step
  • The patient changes their mind before confirming. They leave after seeing the quote and terms.
  • The patient also needs blood. Separately from booking, the same app can offer a related UHI search. It finds blood banks that hold a blood group and component. This is not a step of the booking. → workflow: Search blood banks over UHI