Clinic Appointment Booking Portal

Project overview

We built an online appointment portal for a group of outpatient clinics with doctors across several specialities, many of whom work at more than one location. Patients search by speciality, symptom, location or language, see real availability, book an in-person or video appointment and manage it themselves.

The engagement covered discovery with reception teams and doctors, UX, a React front end, a Node.js API on MongoDB, video consultation integration and dashboards for clinic staff. It is part of our healthcare software development work in the healthcare sector.

The client and the challenge

Appointments were booked by phone and written into each clinic's diary. Patients could not see availability, receptionists spent much of the day on calls, doctors who worked at two clinics were occasionally double-booked, and no-shows left gaps that could not be refilled.

The clinics wanted online booking that reflected each doctor's real schedule across locations, video appointments for follow-ups, automated reminders, and careful handling of patient information — booking reasons are health data and had to be treated that way.

Solution architecture & delivery

Doctors' schedules are defined as recurring templates per clinic: working days, session times, slot length by appointment type and breaks. The Node.js scheduling service expands templates into bookable slots and subtracts leave, blocked time and existing bookings. Because a doctor has one schedule across all clinics, a slot booked at one location removes overlapping time at the others, which ended cross-clinic double-booking.

Booking is protected against race conditions. When a patient picks a slot, the API performs an atomic conditional write in MongoDB that only succeeds if the slot is still free, then holds it briefly while the patient confirms details. Patients verify their mobile number with a one-time code rather than creating a password up front, and can book for family members under one account. Rescheduling releases the old slot and claims the new one in a single operation, so a patient never loses their original appointment if the new time is taken first. Clinics can set rules per appointment type, such as how far ahead new patients may book, minimum notice for cancellation and which slot types are reserved for follow-ups.

The React portal's doctor discovery combines speciality, symptom-to-speciality mapping maintained by the clinics, location, language, gender preference and next available slot. Doctor profiles show qualifications, clinic locations and appointment types. For video appointments, the patient receives a secure link that opens a browser-based consultation room at the booked time — no app download — and the doctor joins from the dashboard, where the patient's intake answers are visible.

Reception dashboards show the day's queue per clinic, check-in status, walk-ins and cancellations, and a waitlist that offers freed slots to waiting patients by SMS. Reminders go out ahead of each appointment with confirm and cancel links. Booking reasons and intake answers are only visible to the treating doctor and reception at that clinic, access is logged, and messages never include clinical details. Our clinic management desktop software case study shows the in-clinic records side of similar workflows.

Key features we built

• Doctor discovery by speciality, symptom, location, language and availability
• Real-time slot booking with conflict-safe holds
• One schedule per doctor across multiple clinic locations
• Browser-based video appointments with no app install
• Mobile number verification and family member bookings
• SMS and email reminders with confirm and cancel links
• Waitlist that offers cancelled slots to waiting patients
• Reception dashboard with queue, check-in and exportable reports

How we delivered it

1. Discovery. Shadowing receptionists at several clinics and interviewing doctors about slot lengths, overbooking rules and which appointments suit video.
2. UX and prototype. Prototypes of doctor search and booking tested with patients on mobile browsers, including older patients and people booking for relatives.
3. Build. Two-week sprints on scheduling, booking, dashboards and video, with automated tests around slot generation and double-booking, following our CI/CD and testing pipeline.
4. Clinic roll-out. Doctors' schedules and future phone bookings imported clinic by clinic, with reception teams running the dashboard alongside the diary for the first days.
5. Support. Ongoing maintenance, new specialities and clinic locations, and reminder wording updates under a support agreement.

Technology choices

• React — a fast, component-based patient portal and staff dashboards that share search, calendar and booking components.
• Node.js — scheduling, booking, reminder and video session services with many short concurrent requests and scheduled jobs.
• MongoDB — flexible documents for varied doctor profiles and schedule templates, with atomic conditional updates for safe slot booking.

Outcomes

• Patients book, reschedule and cancel online instead of phoning reception
• Doctors who work at several clinics are no longer double-booked
• Follow-up appointments can happen by video without the patient travelling
• Cancelled slots are offered to waitlisted patients rather than left empty
• Reception teams spend less of the day on routine booking calls and more on patients at the desk

FAQ