Booking & Patient Records

Booking against the real diary, reminders that go out without anyone remembering, and one screen reception can work from.

Concept build

Meridian Clinic is an invented company. We built this to show how the thing works, not for a customer, so there are no business figures anywhere on this page.

The situation

What this kind of business is dealing with

Common in the trade, not a description of anybody in particular. If two or three of these sound like your week, the build below is the shape of the answer.

  • Reception is on the phone all morning while the waiting room queues behind it.
  • Booking is only possible during the hours patients are at work.
  • Every no-show is an empty chair somebody else was waiting for.
  • New patients fill in a paper form that someone then types up.
  • Finding a patient's history means having three things open at once.

What we built

The pieces of it

Each of these exists and runs. Ask for a walkthrough of any one of them.

Booking that respects the real diary
Patients book the right length of slot with a clinician who does that treatment. The availability shown is the diary, so it cannot drift out of step with it.
Reminders that do not depend on anyone remembering
A reminder before every appointment with a link to confirm or move it. Reminders are the most reliable thing a clinic can do about no-shows, so they run on a schedule rather than when there is a spare ten minutes.
Intake forms filled in at home
History, consent and insurance details completed on a phone before the visit, arriving in the record instead of on a clipboard someone has to type up.
A records view built for reception
Today's list, the patient in front of you, their history and their balance on one screen. Built for a busy Monday morning, not a demo.
Payments and invoices
Card taken at booking or after the visit, receipts sent automatically, and an invoice history per patient the front desk can pull up.
Access by role, and a log of who looked
Reception, clinicians and the practice manager each see a different amount, and every record opened is written to an audit log.

How it works

What actually happens, in order

  1. 01

    A patient picks a service, and the site offers only slots of the right length with a clinician who does it.

  2. 02

    They book, pay or leave a card, and get a confirmation.

  3. 03

    The intake form arrives by message and they fill it in on their phone before the visit.

  4. 04

    A reminder goes out ahead of the appointment with a link to confirm or rebook.

  5. 05

    On the day, reception works from one screen: the list, the notes and the balance for each patient.

  6. 06

    The clinician writes the visit up against the same record.

  7. 07

    Anything clinical stays with the clinician. The automatic parts handle times, forms and money, and nothing else.

The build

Facts about the thing itself

Size, scope and how long it took. These describe the build. They are not customer figures, because there is no customer and a number we did not measure would be worth nothing to you.

Screens
16
Build time
4 weeks

Built with

  • Next.js
  • PostgreSQL
  • Stripe
  • Twilio
  • Audit logging

Next step

Could this work for you?

Tell us what your version of this looks like. We will say what would carry across, what would have to be built differently, and roughly what that takes.