MediBook
Doctor discovery, booking and consultation management for patients, doctors and clinics.
- Type
- Web application · Multi-role platform
- Platform
- Responsive web, patient mobile views
- Scope
- Product design, architecture, full-stack
- Status
- Concept Project
Doctor profile & booking. Doctor profile, services and availability calendar with a guided booking summary.
Overview
MediBook is a concept for a healthcare appointment platform that serves three audiences at once: patients looking for care, doctors managing their schedules, and clinic administrators running the practice.
The focus was on making booking dependable — no double bookings, clear availability and reminders that reduce no-shows — while treating sensitive health information with appropriate care.
Problem & solution
The business problem
Booking a doctor is still often done by phone, during office hours, with little visibility into availability. Clinics, in turn, juggle paper diaries, cancellations and no-shows.
- Patients cannot easily compare doctors, specialties, fees or availability.
- Phone-based booking ties up reception staff and leads to scheduling errors.
- Doctors lack a consolidated view of their day, patient history and follow-ups.
- Prescriptions and consultation notes are scattered across paper and separate systems.
- Clinics have little data on demand, cancellations or no-show rates.
Proposed solution
A booking platform built around a single source of truth for doctor availability, with dedicated experiences for patients, doctors and clinic staff.
- A searchable doctor directory with profiles, specialties, languages, fees and the next available slot.
- Availability calculated from working hours, breaks, leave and existing bookings.
- A guided booking flow with confirmation, reminders and simple rescheduling.
- A doctor workspace with the day's schedule, consultation records and e-prescriptions.
- Clinic administration for doctors, rooms, services and booking analytics.
Key features
- 01
Doctor discovery & profiles
Search and filter by specialty, location, language, fee and availability; profiles with qualifications and services.
- 02
Appointment booking
A short guided flow: choose a service, pick a slot, confirm details, receive confirmation.
- 03
Availability calendar
Weekly working patterns, breaks, holidays and one-off overrides, managed by the doctor or clinic.
- 04
Patient dashboard
Upcoming and past appointments, prescriptions, documents and reminders in one place.
- 05
Doctor dashboard
Day and week views, patient queue, consultation notes and follow-up scheduling.
- 06
Appointment management
Reschedule, cancel and no-show handling with configurable clinic policies.
- 07
Consultation records
Structured notes per visit, linked to the patient's history, with access restricted by role.
- 08
E-prescription interface
Medication, dosage and duration captured in a structured format and shared with the patient.
- 09
Video consultation (concept)
Integration concept for a third-party video provider using secure, time-limited session links.
- 10
Clinic administration
Manage doctors, services, rooms, opening hours and staff permissions.
- 11
Booking analytics
Bookings by specialty, utilisation, cancellations and no-show trends.
Interface design
User roles & workflows
Finds care and manages their own appointments and documents.
- 1
Search doctors by specialty
- 2
Compare profiles and availability
- 3
Book and confirm a slot
- 4
Attend and receive prescription
Architecture
- Patient web app
- Doctor workspace
- Clinic admin console
- REST API
- Auth, consent & RBAC
- Audit logging
- Availability engine
- Booking service
- Notifications
- Consultation records
- PostgreSQL
- Redis — slot holds & queues
- Encrypted document storage
- Email & SMS reminders
- Calendar (iCal) export
- Video provider (concept)
No double bookings
Slots are held briefly while a patient confirms, and the final booking is protected by a database exclusion constraint on the doctor's time range — two concurrent requests can never both succeed.
Time zones done properly
Times are stored in UTC alongside the clinic's time zone, and availability is computed in local time so daylight-saving changes behave correctly.
Privacy by design
Clinical data is separated from booking data, encrypted at rest, and every access to a consultation record is logged. The design takes regulations such as GDPR and POPIA into account.
Event-driven notifications
Booking events are published to a queue that handles confirmations, reminders and cancellations independently of the booking request.
Technology stack
- Frontend
- Next.js
- React
- TypeScript
- Tailwind CSS
- Backend
- Node.js
- NestJS
- REST API
- WebSockets
- Data
- PostgreSQL
- Prisma ORM
- Redis
- Integrations
- Email & SMS provider
- iCal
- Video API (concept)
Proposed stack for the concept; choices would be validated against a real client's constraints.
Engineering considerations
- 01
Availability is a computation, not a table
Availability combines recurring schedules, exceptions, leave, buffers and existing bookings. Computing it on demand — cached per doctor and day — keeps it accurate whenever anything changes.
- 02
Concurrency at peak times
Popular doctors' slots can be requested at the same moment. Short-lived holds plus database constraints guarantee exactly one booking wins, and the other patient is offered the next slot.
- 03
Role-appropriate access
Patients, doctors and administrators see different slices of the same information. Access rules are enforced in the API, not just hidden in the interface.
- 04
Designing against no-shows
Reminder timing, easy rescheduling and clear cancellation policies were designed together, because each affects the others.
Project status
MediBook is a self-initiated concept project, created to explore product design and engineering for healthcare scheduling. It has not been delivered to or deployed for a client. The interface designs and architecture are presented as a case study, and all names, businesses and figures shown in the mockups are illustrative.