What Building a Healthcare Booking System Taught Us About UX
Scheduling software for clinics sounds simple until you are dealing with practitioner availability, recurring sessions, cancellation policies, and anxious patients. Here is what we got wrong first.
When we started building the appointment booking platform for a psychology clinic, we thought the hard part was going to be the technical implementation. Availability windows, calendar logic, time zones, notifications. There is complexity there, but it is manageable complexity.
The harder part turned out to be something we did not fully anticipate: the emotional context of the user.
The User Is Not in a Neutral State
Someone booking an appointment with a psychologist is not in the same headspace as someone booking a restaurant table. They may be anxious. They may have taken effort just to get to the point of booking. Any friction in the flow, a confusing step, an unclear error message, an unexpected redirect, hits harder than it would in a lower-stakes product.
This changed how we thought about every decision in the interface. Forms got simpler. Error messages got clearer and more human. The confirmation screen became more reassuring. None of this required extra engineering time. It required stepping back and thinking about who is sitting on the other side of the screen.
Availability Logic Is Deceptively Complex
A practitioner's availability sounds simple: they work Monday to Friday, 9am to 5pm. In reality:
- They have lunch breaks, admin slots, and supervision time blocked out
- They may see some clients weekly and others fortnightly
- They may work part-time on certain days
- They occasionally need to cancel and reschedule a recurring slot
Building a system that handles all of this without exposing the complexity to the patient took several iterations. The first version we built required the admin team to manage too much manually. The second version overcorrected and tried to automate too much, introducing edge cases. The third version was the right one.
Get ready to build it three times.
Recurring Appointments Are Their Own Problem
A one-off booking is straightforward. A recurring weekly appointment for 12 weeks is not, especially when one of those weeks falls on a bank holiday, or the practitioner takes leave, or the patient needs to reschedule a single session without disrupting the rest of the series.
We ended up treating each appointment in a recurring series as an individual entity linked to a series record, rather than trying to derive them from a recurrence rule at display time. This made individual edits clean and the data model predictable.
Automated Reminders Need Opt-Out, Not Opt-In
Every patient gets reminders by default. Some patients actively do not want a reminder 48 hours before their appointment, perhaps for privacy reasons or because the reminder itself causes anxiety. The system needs to respect that cleanly.
We also learned that the timing of reminders matters more than we expected. 48 hours out is standard. But adding a 24-hour reminder for first-time patients improved attendance rates noticeably. Small detail, real impact.
What We Would Do Differently
We spent too long early on optimising the practitioner-facing dashboard before the patient booking flow was solid. The admin experience matters, but the patient flow is the product. Get that right first.
If we were starting again, we would have put two or three real admin staff in front of the system in the first two weeks and watched them use it. The feedback would have saved us a sprint of rework.
Want to work with us?
Let us talk through your project.