The Elite Clinic booking desk

Built by Noorflows. This is the plain-text version of the working demo on the main page. It carries the same information without any of that page's design, because no major AI crawler runs JavaScript — this is the version a machine reads.

What it is

A booking desk for a clinic in England offering both dental and aesthetic treatment. It takes an enquiry, decides whether the appointment can be made at all, refuses where it must, and writes down what happened.

The public demo is loaded with invented patients so that anyone can try it. Run for the clinic itself, it would be a separate deployment with its own store and its own keys, holding their records and nobody else's. That is how it is built — a separate deployment, holding the clinic's records and not these. No real patient record has ever been copied into this demo.

Why the booking is the thing that matters

In England, a business that makes an appointment for anti-wrinkle injections or injected filler for someone under eighteen commits a criminal offence. The treatment never has to happen. The offence is the booking.

That changes where the control has to sit. Checking age when the patient arrives is too late, because by then the offence is already complete. So age is established before an appointment exists at all.

And the defence in law is not that the patient turned out to be old enough. It is showing what the business did to find out, at the time. That is why refusals are recorded rather than discarded: the record made at the moment of the enquiry is the evidence.

Under eighteen is not one rule

This is the part most booking systems get wrong by treating age as a single switch.

Both paths end with a person. They are not the same refusal, and calling them the same would be wrong in one direction or the other.

How a decision is reached

Every fact in a decision — the treatment asked for, the date of birth given, which side of the clinic it falls on — is read from the enquiry by ordinary code. In this demo the wording is fixed text as well: no language model is called at all, and the page is not permitted to reach anything beyond itself. Where a model is used it chooses the wording and nothing else — it cannot decide whether a booking is allowed, invent an age, or change what the record says.

Each answer displays what it was decided from, so a reader can check the decision against its source without asking anyone.

What it will not do on its own

Book an age-restricted treatment for someone under eighteen
There is no override, no "the parent said it was fine", and no path through the desk that reaches a booking. The refusal is recorded with what was asked and what was answered.
Decide whether a young dental patient is suitable
It refuses to make that call rather than refusing the patient, and sends it to a clinician. Those are different outcomes and the desk keeps them different.
Give clinical advice
No dose, no treatment recommendation, no opinion on whether something is right for someone. A question of that kind goes to a person at the clinic.
Quietly drop an awkward enquiry
Anything it will not decide is handed over, not discarded. A refusal that leaves no trace protects nobody — least of all the clinic relying on it as a defence.

What a person receives

Anything handed over arrives with the enquiry, the treatment asked for, which side of the clinic it falls on, the age position, a one-line explanation of why it stopped, and the enquirer's own words. The point is that the person can act without opening anything else, and the patient never has to start again.

Limits, stated plainly


Built by Noorflows. Back to the working demo. How this demo handles data.