Free Website Audit: Discover what's holding your digital presence back
What does a patient booking build include?
A booking build is a journey, not a form. The patient has to find the right appointment type, pick a time that is really free, confirm, and get a reminder. Each of those steps is a piece of scope.
| Part of the build | What it covers | What decides the effort |
|---|---|---|
| Appointment types | Services, durations, preparation notes, who can perform them | How many rules a clinic applies per type |
| Availability | Working hours, rooms, equipment, holidays, buffers | Whether availability lives in one calendar or several |
| The booking flow | Fields, validation, confirmation, cancellation, rescheduling | Guest booking or patient accounts |
| Messages | Confirmation, reminder, change and cancellation notices | Channel count: email, SMS, or both |
| Staff view | Who sees a booking, who may change it, what is logged | The number of roles and the audit rules |
| Records | What is written to the scheduling or record system, and when | Whether that system has a usable API |
The healthcare industry page covers the wider picture: patient-facing sites, accessibility and the digital estate around care. This page covers the booking and telehealth part of it.
Who decides what patient data the system may hold?
Your clinic decides, with your own data protection adviser. Konzept does not certify your compliance and does not write your legal opinion.
What we do is build the controls that your adviser will ask about, and show how they work:
- Encryption in transit and at rest.
- Role-based access, so a receptionist and a clinician do not see the same record.
- Audit logging, so you can show who opened or changed a record and when.
- Data minimisation in the form itself, so the booking asks only for what the appointment needs.
- A written retention rule for bookings, messages and logs.
Bring that list to your adviser before the build starts. The cheapest time to remove a field is in discovery. The most expensive time is after launch, when the field is already full of patient data.
How does booking connect to a scheduling or record system?
Through an API, when one exists. Confirm that first, because the answer changes the estimate more than any design decision.
Four questions settle the integration scope:
- Which system is the source of truth for availability, the website or the clinical system?
- Does the booking write in real time, or on a schedule?
- What does the system return when a slot is taken between the patient seeing it and confirming it?
- Who fixes a record that fails to sync, and how do they find it?
Enterprise solutions is the service behind this work: custom integrations that connect internal systems and keep data in sync. Where the build is mainly a patient-facing site with booking on top, it sits under web development.
What does WCAG 2.1 AA mean for a booking flow?
It means a patient who cannot use a mouse, or who uses a screen reader, can still book an appointment without calling you.
In a booking flow that comes down to a short list of concrete things:
- Every step works from the keyboard alone, in a sensible order.
- The date picker announces the date it has landed on, and accepts typed input as well.
- Error messages say what is wrong and how to fix it, in text, not colour alone.
- Text and controls meet the contrast ratio at the sizes the page actually uses.
- A session that times out warns the patient and lets them extend it.
We design to WCAG 2.1 AA and test during the build, on real devices. Accessibility is cheaper as a design constraint than as a repair.
What does a booking or telehealth build cost?
The published project tiers apply. A booking flow on a new clinic site usually sits in Growth. A build with record integration, several locations and two languages usually sits in Scale.
| Tier | Starting price | Timeline | What it usually covers here |
|---|---|---|---|
| Growth | EUR 14,500 | 4–8 weeks | Clinic site with a booking flow, one calendar, email confirmations, CMS and training |
| Scale | EUR 29,500 | 8–14 weeks | Record or scheduling integration, several locations, multi-language, performance work |
| Enterprise | EUR 44,000 | 14–20+ weeks | Custom software, API architecture, advanced authentication, multi-site structure |
The pricing page is the source for the current packages and the monthly plans. For the drivers that move any website estimate, read the website cost guide.
What should a clinic bring to discovery?
Six things, and none of them need a developer to prepare:
- A list of appointment types, with duration and any preparation the patient must do.
- How availability is set today, and who sets it.
- The name and version of your scheduling or record system, and whether it has an API.
- Who may see a booking, who may change it, and what has to be logged.
- The languages the flow must support, and who writes the second language.
- Your data protection adviser’s requirements, in writing.
Send those and the scope conversation takes one call instead of three.
Has Konzept built an online booking before?
Yes, though not yet in a published healthcare case study. The closest published build is Central Heritage Hotel: a website with commission-free direct booking. A hotel is not a clinic, and the data rules are not the same, but the booking mechanics are: real availability, a short flow, a confirmation the guest trusts.
We would rather say that plainly than dress a hotel up as a hospital. The rest of the published work is in our project archive.
What is the next step?
Send the six discovery items through the quote form and we will propose a scope and a fixed price. If you would rather talk the integration through first, book a call.
