Solutions · Health & fitness

Doctor appointment app: what to decide, build and test.

Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.

Before you brief anyone: whose queue is this?

A clinic app looks like a booking form, but the real question is who the queue belongs to. Answer these first, because each one changes the screens, the data you hold and the rules that apply.

ForkChoiceWhat it means
One clinic or many doctorsYour own clinic or groupYou control the queue and the fee. One reception, one data owner. This is the simplest and safest start.
orA directory of other people's clinicsYou hold health data for clinics that are not yours, and need contracts, onboarding and support for each. Much heavier.
Slots or tokensFixed time slotsSuits dental, physio, dermatology and procedures with predictable length.
orTokens with a live queueSuits OPDs with walk-ins and long waits. Our concept build Cliniqo is built around this.
Fee collectionPay in advance by UPIFewer no-shows and an easier day for reception, but you need refund rules for doctor delays.
orPay at the counterLess friction for patients, and no-shows stay.
Video visitsInclude from the startAdds identity checks, prescription rules and video quality testing.
orAdd after the clinic flow worksCheaper, and nothing is wasted. Most single clinics should start here.

The clinic software guide covers the choices in more depth. Before the first meeting, have these ready:

  • How many doctors, chambers and branches at launch?
  • What share of patients are walk-ins today?
  • Who at the clinic will use the reception screen all day?
  • Which existing billing or records software must keep working?

What the first release of a clinic system includes

ModuleFirst versionAdd laterWhy
Patient bookingPick doctor, pick slot or token, phone OTP, confirmationFamily profiles, packages, follow-up remindersBooking is why patients open the app.
Reception boardCheck-in, walk-ins, reschedule, mark late or emergency, fee receiptMulti-branch roll-upsReception decides whether the system survives the first Monday.
Queue displayTV screen that shows the next token with a chimeVoice call-out in extra languagesIt cuts the shouting and the crowding at the door.
Doctor deskToday's list, history, notes, prescription with saved templatesOrder sets, referral lettersA doctor will not type more than they do on paper.
RemindersWhatsApp or SMS confirmation and a reminderReview requests, recall campaignsReminders reduce no-shows fastest.
PaymentsUPI link and counter receiptInsurance and package billingInsurance logic is a project of its own.
Records and consentRole-based access, consent capture, audit logABHA linking, lab report syncAccess control cannot be bolted on afterwards.
TeleconsultNot in version 1 for a first clinicVideo room, e-prescriptionAdd once the in-person flow is steady.

A 6 to 10 week build, and what the clinic provides

A single practice with booking and a doctor desk fits the short end; a multi-doctor OPD with reception and a queue screen is closer to 8 to 10 weeks.

  1. Weeks 1–2: map one real day in your clinic, from first call to the last token. You provide: a day of access, the current register or sheet, doctor schedules, fee list.
  2. Weeks 2–4: booking, reception board and doctor desk screens working on test data. You provide: sample patients (made up, never real ones), your prescription template, the logo and letterhead.
  3. Weeks 4–6: reminders, UPI payment, queue screen, role-based access. You provide: payment gateway and WhatsApp business accounts in the clinic's name, a TV or tablet for the waiting room.
  4. Weeks 6–8: a week of shadow use alongside the paper register. You provide: the receptionist and one doctor for daily feedback.
  5. Weeks 8–10 (multi-doctor): extra chambers, branch reports and polish, then switch-over in a quiet week. You provide: privacy notice and consent wording reviewed by your lawyer, staff training time.

How we work with you each week

The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.

  • Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
  • Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
  • Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
  • Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
  • One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.

The full version, including how the beta and user testing work across every kind of project, is on our process page.

The beta: one clinic, one OPD

The beta is the shadow week in weeks 6–8 of the plan, once booking, the reception board, the doctor desk and reminders all run on the same data. The paper register stays open beside it, so no patient is turned away if something breaks.

  • What's in it. Booking by slot or token, phone OTP, the reception board with walk-ins and late marks, the queue screen in the waiting room, the doctor's list and prescription templates, WhatsApp or SMS reminders and the UPI fee link.
  • What stays out. Teleconsult, family profiles, insurance billing, ABHA linking and branch reports. They come after the in-person day runs cleanly.
  • Who uses it. One clinic: the receptionist who runs the counter all day, one or two doctors, the owner, and 20–30 patients who already visit, such as parents booking for a child or older patients booking a follow-up. The clinic recruits them at the counter. Staff relatives booking fake visits tell you nothing.
  • How they get it. Patients install the app through TestFlight or Google Play testing, or use the booking link on their phone. Reception and the doctor desk run on the clinic's own computer and the waiting-room TV.
  • How long. One to two weeks, covering at least one Monday OPD, because that is the day that breaks a queue. Real data enters only after the consent screen and role-based access are switched on; until then everything runs on made-up patients.

A new personal Google Play developer account has to run a closed test with at least 12 testers for 14 days before it can publish. Count the beta patients towards that, or use an organisation account.

What we test with real people, and the tasks we set

Each session is one task, done on the person's own phone or at their own desk, in the language they speak at the clinic. We watch and stay quiet, even when they get stuck. Around five people per role is enough to show the main problems. We fix those and run the same task again. Sessions use made-up patient records, never a real person's history.

The reception test runs during a real OPD rush, with the doctor already behind.
WhoThe taskWhat we watch for
Patient"Book a token with Dr Mehta for Thursday evening and pay the consultation fee by UPI."Do they find the right doctor and day? Do they see the fee and refund rule before paying? Does the confirmation arrive on WhatsApp?
Family member"Book a follow-up for your mother, who doesn't have a smartphone."Can they book for someone else without making a second account? Does the reminder reach the right phone?
Receptionist"A walk-in arrives, token 14 is running late, and an emergency comes in. Sort the queue."How many taps against writing in the register? Does the queue screen update straight away? Is anything lost if they get it wrong?
Doctor"Finish this consult and write a prescription for a returning patient using your usual template."Is it as fast as paper? Do they find past visits without asking reception? Does the printout match the letterhead?
Clinic owner"Tell me how many booked patients didn't turn up last week, and who collected today's fees."Can they answer from the dashboard without calling the receptionist? Do the totals match the counter?

The numbers that say it's working

In week 1 the clinic chooses two or three of these. If the register or appointment diary already shows a figure, such as last month's no-shows, we write it down as the starting point. Tracking goes in before the beta. We report at switch-over and again 30 days after. We can't promise where the numbers land; our job is to put them where the clinic can see them.

GoalWhat we measureWhere it comes from
Patients book on their ownShare of bookings made without a phone call to receptionBooking records
Fewer empty slotsBooked patients who didn't arrive, with and without advance paymentReception board check-ins
Shorter crowd at the doorTime from check-in to being called inQueue timestamps
Reception keeps upTime to check in a walk-in, against the registerTesting sessions and reception board
The doctor stays on paper lessShare of visits closed with a digital prescriptionDoctor desk
Fees reconcileGap between fees recorded and fees received by UPI and cashPayment gateway and counter receipts

What a clinic app costs and why

A single-doctor booking site with a simple desk sits in the one-user-type tier of our app development cost guide: a ballpark of ₹3–10 lakh. A multi-doctor clinic with patient app, reception board and doctor desk moves into the two-user-types-plus-admin tier of ₹10–25 lakh. If records, lab flows and integrations dominate, it can fall under data-heavy business software, ₹12–35 lakh. These are small-studio ballparks, not a quote.

  • Pushes it up: integration with existing hospital or billing software, because we must match their data and test against it.
  • Pushes it up: teleconsult video and e-prescriptions, which add rules, identity checks and device testing.
  • Pushes it up: several branches, each with its own doctors, fees and screens.
  • Pushes it down: starting with one practice, slots only and no video, then adding modules as the clinic grows.

Health data, prescriptions and tax: what to design for

  • Teleconsults: the 2020 telemedicine guidelines are for registered medical practitioners and group medicines into lists with different rules, including a video-first rule for some. Our concept build Careloop shows the checks in the doctor tool at the point of writing a prescription. Have your doctor or lawyer confirm the current text.
  • Health data: records, prescriptions and reports are sensitive personal data. The DPDP Rules were notified in November 2025 and duties phase in over 18 months, so capture consent by purpose and keep an access log now. See the DPDP checklist.
  • ABDM: patients may ask to link an ABHA number, and doctors and facilities can register in national registries. Treat it as an optional integration to plan for, not a day-one requirement; confirm with your doctor or facility.
  • GST: healthcare services by a clinical establishment or authorised medical practitioner are exempt, but a software fee we or you charge is a separate supply. Ask your CA how receipts should read.
  • Registration: clinic registration rules differ by state. Confirm yours before you put the clinic's name on a public booking page.
  • Languages and habits: patients arrive late, book by phone for parents and read WhatsApp more than email. Keep reminders short and offer Hindi or the local language; see regional language apps.

This is general information, not legal or medical advice. Confirm current rules with a lawyer and your medical council or doctor before launch.

Clinic app mistakes and what to do instead

  • Designing for patients and forgetting reception. If check-in takes longer than the paper register it will be abandoned. Time the screen against the register.
  • Promising live wait times the doctor cannot keep. Show a range and update it when the doctor runs late.
  • Real patient data in demos and testing. Use made-up records until consent and access control are in place.
  • Starting with video. Most clinics earn from visits; get the in-person queue right first.
  • Using one login for the whole staff. Give reception, doctor and owner different access, with a log of who opened what.
  • Ignoring the doctor's template. If the prescription takes extra clicks, the doctor will go back to paper. Build their templates in.

Cost and timeline

6–10 weeks for a first version.

Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.

  • Number of doctors, chambers and branches
  • Teleconsult video and e-prescriptions
  • Lab or pharmacy workflows on top of appointments
  • Integration with your existing billing or hospital software
  • Languages for patients and the waiting-room screen

How app costs work in India →

Questions

About your doctor appointment app.

How much does a doctor appointment app cost in India?

It depends on the number of doctors and branches, and whether you need teleconsults, e-prescriptions or lab workflows. We give a fixed quote within 48 hours of your brief. Our clinic software guide explains what to include first. Teleconsults can be added later.

Can it handle walk-in patients, not just online bookings?

Yes. In our concept build Cliniqo, reception adds walk-ins to the same token queue as online bookings, and the waiting-room screen and patient app update together. Most Indian clinics need both. Reception can also mark emergencies and broadcast delays. Patients see the change at once.

How long does it take?

A single-practice booking site with a clinician desk can be ready in about six weeks. A multi-doctor OPD system with reception, doctor desk and waiting-room screen usually takes 8 to 10 weeks. You see working screens from the first fortnight, and we time the switch-over to a quieter clinic week.

Is patient data kept private?

We design for privacy from the start: consent screens, role-based access, and records that only the right staff can open. We also walk you through your obligations under India's data protection law; see our DPDP checklist. We are not lawyers, so we recommend a legal review before launch.

Who owns the system?

You do. Source code, designs and documentation are handed over in full, and you choose where it is hosted. Patient records stay in accounts that belong to the clinic, and your own team or any other developer can take the system forward without us.

Start a project

Tell us how your business runs. We'll build what it runs on.

Four taps, about a minute. Fixed quote within 48 hours.

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert