Reforma Consultancy was invited to CCR at ExCeL London alongside Mediva Pharmacy and OxygenRX. Between the three of us, we cover most of what happens to a patient after they find an aesthetic clinic online. Mediva Pharmacy provides the dispensing. OxygenRX provides an all-in-one platform for clinics to manage medical data, write prescriptions and fulfil orders from its web app. Reforma's part was to explain how we build clinic websites, and how we integrate them into OxygenRX's system, so the journey from booking through to treatment feels like one thing to the patient, even though several systems are doing the work.
The patient sees one journey. The clinic runs several systems.
A patient booking a consultation at an aesthetic clinic doesn't know, or care, which system they're in. They find the clinic, choose a treatment, book a time, answer some questions, see a clinician and, where a treatment needs it, receive a prescription that's dispensed and delivered. Behind that, the website, the booking engine, the prescribing platform and the pharmacy are all separate.
Most of the problems we see in clinic websites happen at the joins between those systems: details typed into a booking form and then retyped into a medical record, a consultation booked for a treatment the patient isn't yet eligible for, or a patient who pays and then hears nothing until someone remembers to email them. None of those are design problems. They're integration problems, and they're what Reforma spent most of its time at CCR talking about.
"A clinic website isn't finished when it looks right. It's finished when nothing has to be retyped."
Start with the treatments, not the template
Aesthetic clinics rarely book every treatment the same way. Some treatments can be booked straight away. Some need a consultation first. Some involve prescription-only medicines, so a consultation and a prescriber's decision have to come before anything else. A template site with a booking widget treats all of those as "pick a service, pick a time".
So the first thing we do on a clinic build is map each treatment's real journey: what the patient has to do, what the clinic has to decide, and in what order. The website's structure, the booking rules and the integration all come from that map. It's the same approach described on our website development page, applied to the way clinics actually work.
Booking that follows the clinic's rules
Once the journeys are clear, the booking engine can enforce them. On the Armstrong Clinic platform, a slot is held the instant a patient submits, released automatically after thirty minutes if they abandon payment, and a booking only exists once its consultation fee has cleared. Treatments that depend on a clinical decision can't be booked until that decision has been made. The clinician decides, and the system follows.
If you'd like the detail on why booking widgets struggle with clinics, we've written about it separately in custom booking systems for private clinics.
Integrating the website with OxygenRX
This was the part of the conversation people asked most about. For prescribed treatments, the clinical side lives in OxygenRX: the patient's medical data, the prescription and the order. The website's job is to get the patient into that system with the right information, first time.
On the Armstrong Clinic build, the assessment form is fetched live from OxygenRX, so the questions on the website are always the ones the prescribing platform expects. When a patient submits it, the platform finds or creates them as an OxygenRX patient and writes their answers straight onto their clinical record. Nothing is typed twice, and nobody copies details from an inbox into a medical record.
Every submission also arrives with a suggested verdict and the reasons behind it, worded as a prompt rather than a decision, because the prescribing decision belongs to the prescriber. From there, the prescription and order are handled in OxygenRX, and dispensing by the pharmacy.
Why the whole chain matters
Being at CCR with a pharmacy and a prescribing platform made one point very clearly: a clinic's website is the front of a chain, not a standalone brochure. If the website collects the wrong information, or collects it in a way the next system can't use, the delay shows up later, at the prescriber, at the pharmacy, or in the patient's inbox. If the website hands over cleanly, every step after it is easier.
That's why we build clinic websites as part of the clinic's operations. The public pages still need to look the part and rank for the treatments you offer, but the measure of a good build is what happens after the patient clicks "book".
Lara Young, who has worked with us across a range of client projects, put it well in her Google review: "He takes time to understand the business first, then builds exactly what's needed."
"He delivers fast and builds things that actually work, from polished websites to custom platforms and integrations." Lara Young, Google review
Questions to ask before you commission a clinic website
Whoever you work with, these are worth asking early. Can each treatment have its own booking journey? Can bookings be held until payment clears, and released if it doesn't? Can treatments that need a clinical decision be gated until that decision is made? Will patient answers go straight into your prescribing or records system, or will someone retype them? And who looks after the integration when one of those systems changes?
If the answers are vague, the gaps will be filled by your team, by hand. Our Armstrong Clinic case study shows what one connected platform looks like, from the public website to the OxygenRX integration.
Thank you to Mediva Pharmacy and OxygenRX for the invitation, and to everyone who stopped to talk at CCR.
If you run an aesthetic clinic and your website stops at the booking form, tell us how your patient journey actually works. Discovery costs nothing, and we'll give you an honest view of what your website should be doing. See our clinic booking systems and website development service.
Start the conversation →