Worked example: Health & clinics
An inspectable clinic booking prototype
Our own worked example: a clinic information and booking prototype with sample treatments, explicit booking states and a defined health-data boundary.
A demonstration build on one of our own live demos, not a client project. It shows exactly how we’d approach yours.
Willow is our own demonstration, not a client project. Every clinic name, treatment, fee, appointment, address and review placement is illustrative. The prototype shows an interface and a release method; it does not claim a patient result, practitioner credential, regulatory status or working connection to a clinical system. Open the Willow demonstration →
What can be inspected
The demonstration makes four parts of a clinic build visible:
- Sample treatment rows show where an approved name, duration, fee and location note would appear.
- The booking prototype distinguishes availability, selection and confirmation states.
- Credential and testimonial areas are labelled as placements for verified source material.
- The build notes define which information belongs on the public site and which belongs in the clinic's selected booking or clinical system.
The content and source contract
For a client build, each public element needs a clinic owner and release record.
| Public element | Supplied or approved by | Release evidence |
|---|---|---|
| Treatment or service description | Clinic's appointed clinical owner | Approved wording, source, approval date and next review date |
| Practitioner name and credentials | Clinic and relevant public register | Registration check, approved profile and review owner |
| Fee, range or pricing factors | Clinic's commercial and regulatory owners | Approved amount, inclusions, exclusions and applicable rule check |
| CQC or professional-body display | Clinic's regulatory owner | Current source, approved placement and next review date |
| Review or treatment result | Clinic, attributable source and permission owner | Source link or consent record; demonstrations remain labelled |
| Booking action | Clinic and booking-system owner | State contract, destination, notification and recovery tests |
Booking states, rather than a decorative calendar
The visible times in Willow are samples. A production booking route starts with the clinic's booking provider and makes each state explicit:
- The booking system supplies current availability, or the page clearly presents an administrative request instead.
- A selected time remains pending until the provider accepts it.
- The page shows a confirmed state only after the provider returns a confirmation identifier.
- An unavailable or stale slot returns the user to current options without creating a duplicate.
- A provider outage leads to the clinic-approved fallback, with the action labelled as a request rather than a booking.
- Cancellation and rescheduling use the provider route selected by the clinic.
The delivery record retains tests for valid, unavailable, duplicate, stale, cancelled and provider-unavailable scenarios.
The health-data boundary
Appointment details can reveal health information. Before a client form is built, the clinic decides whether each field is needed, where it goes, who can access it, how long the selected system keeps it and who owns the lawful-basis decision.
The public website can carry administrative details and attribution fields agreed by the clinic. Treatment selections, symptoms and free text stay out of marketing-event values. Clinical records remain in the clinic's chosen specialist system.
The detailed acceptance sheet and current CQC, GDC, ASA, ICO and WCAG starting points are on our private clinic website design page.
What this demonstration does not establish
- It has no live availability feed or clinical-system connection.
- Its sample practitioners, treatments, fees and address are not public claims about a clinic.
- It has no CQC rating, professional registration or patient testimonial.
- It does not establish legal, regulatory, clinical or accessibility conformance for a client.
- It contains no measured booking or marketing result.
Those are client inputs and release decisions. A production build receives them only through the clinic's named owners and source records.
What a build starts from
Website projects are fixed and itemised from £2,000, using the current floors on our web design pricing page. Booking integration, clinical-system boundaries, content volume and regulatory review inputs are confirmed during scope. The quote names what is included, the accounts involved and the evidence handed over.
Use the prototype as a review tool
Open Willow, change the palette and inspect the treatment, credential, booking and review placements. Then bring the booking system, priority services and approval owners to a scoping conversation. We will confirm the supported route and itemise the build before work starts.