Baton

A private clinic's work is a relay: booking, payment, registration, ID check, questionnaires, allocation, the consultation, the report, prescribing, titration, the GP letter, discharge. Most clinics stitch that together from a booking tool, a spreadsheet, an email inbox and a separate records system — so things get retyped, and things get dropped between them.

And it's a regulated setting: sensitive health data, controlled-drug prescribing, and inspection evidence that has to exist as a matter of course, not be assembled the week before.

We built the whole pathway as one system on a proper clinical backbone (FHIR), multi-tenant so each clinic is isolated with its own records and access rules. Each stage knows what the last one did and prepares the next — booking that takes card payment and holds the slot, a patient portal, a clinician console that shows what's waiting in the order it went late, prescribing on numbered controlled-drug forms, and discharge that actually closes the case.

Governance is built in, not bolted on: access by role enforced on the server (a consultant sees their own patients; an administrator sees no clinical notes), staff two-factor, a full audit trail of who did what to which record, and AI that drafts assessment reports only from the clinic's own evidence and never signs anything off. It's hosted in the UK.

Baton is in daily clinical use, running a live UK clinic end to end — and because it's a platform, the next clinic onboards onto the same system rather than starting from scratch.