Telehealth booking pages: what CQC expects

If you run any kind of remote consultation service, from online GP appointments to video physiotherapy sessions, you need a CQC compliant booking page before you take a single payment. Not a booking page with a privacy policy bolted on afterwards. One built with the regulator's expectations in mind from the start.

The confusing part is that CQC does not publish a checklist for website design. It regulates the care, not the CSS. But the standards it inspects against (safe care, good governance, information that lets patients make an informed choice) all show up on the booking page whether you planned for it or not. Here is what actually needs to be there.

🩺 Registration status has to be visible, not buried

If your service delivers a regulated activity online (prescribing, diagnosis, treatment following a remote consultation), you must be CQC registered, and that registration needs to be findable from the booking page itself. Not three clicks away in a footer link to an "About us" page nobody reads.

In practice this means:

• Your CQC registration number and the legal entity name, stated near the booking form itself, not just on a separate compliance page.
• A link through to your actual CQC profile page, so patients can check your rating and any inspection reports themselves.
• The name of the registered manager, if your service structure requires one.

Patients comparing online GP services are increasingly used to seeing this. If a competitor shows it clearly and you don't, that is a trust gap that costs you bookings before anyone has even spoken to a clinician.

📋 What has to happen before the booking is confirmed

CQC expects remote consultations to meet the same standard of care as in-person ones, which means the booking page cannot treat a telehealth appointment like a restaurant table. A few things need to happen before confirmation, not after:

• A clear statement of what the appointment includes and what it does not (is a prescription included in the fee, or billed separately, is this a video call or phone call, how long does it run).
• Basic suitability screening. Some services use a short pre-booking questionnaire to flag conditions that genuinely need an in-person assessment rather than a video call, and to make sure patients aren't booking a remote service for something it isn't built to handle.
• A visible route to urgent care. If someone lands on your booking page with something that needs 999 or A&E, that needs to be obvious before they waste time filling in a form.

None of this needs to slow the booking down much. A well-built form can handle screening questions as a short step before the calendar, not a separate PDF nobody completes.

🔒 Consent, data handling and where the small print actually belongs

Telehealth involves transmitting health information electronically, which brings UK GDPR and data protection obligations directly into how the booking page is built, not just into a policy document sitting in a folder.

Practically, the booking page needs:

• Clear consent language at the point of booking, not a vague "by booking you agree to our terms" link that nobody opens.
• A plain explanation of how video consultation data, consultation notes and any prescribing records are stored and for how long.
• A named way to contact the practice about data requests, separate from the general enquiry form.

This is also where a lot of DIY website builders fall down. A booking widget bolted onto a template site often has no proper field for consent capture, no audit trail of what was agreed and when, and no sensible way to store that record against the patient's booking. That is a governance gap an inspector will ask about directly.

🧭 Make the booking journey itself inspectable

CQC inspections increasingly look at the whole patient journey, including how someone found the service, what they were told before paying, and what happened if something went wrong. A booking page that keeps a clear record of what was shown to the patient at each step (fees, cancellation terms, clinician details, consent wording) gives you something concrete to point to if that journey is ever questioned.

This is less about adding more legal text and more about structure: dated version control on your terms, a booking confirmation email that restates what was agreed, and a system that logs rather than overwrites previous versions of your pricing and policy pages.

The Practical takeaway

A CQC compliant booking page is really just a booking page that treats registration status, consent and clear pre-appointment information as part of the build, not as an afterthought bolted onto a generic template. For most small telehealth or hybrid practices, that means a proper booking flow with screening questions, visible registration details and a documented consent step, rather than a standard clinic site with a calendar embed. It is a day's work to design properly and far cheaper than fixing it after an inspection flags a gap.