Healthcare website design starts with the person trying to use it
Written by Derrick KityoA clinic visitor and a clinical-software buyer need different journeys. Start with the tasks, the content owner and the point where another service takes over.

Someone opening a clinic website may need a phone number, directions or a clear explanation of a service. A buyer looking at clinical software has a different job. Putting both through the same sales journey makes neither task easier.
For healthcare website design, I’d settle that distinction before discussing the homepage. Who is the site for, what can it genuinely help them do, and where does responsibility pass to another service?
A polished website can still leave those questions unanswered. The useful work is making the route clear enough that people don’t have to guess.
Give the public website a clear job
Write down the tasks the website owns. For a practice, that might include explaining services, showing where appointments take place and directing people to an existing booking system. For a healthtech company, it might mean explaining the product and arranging a conversation with its team.
Keep the boundaries visible. A general enquiry form shouldn’t look like a clinical advice service. A link to an appointment system should explain that the visitor is moving to another service. Response information should describe what the team can actually deliver.
Here’s a fictional planning example. A clinic wants people to understand a service before requesting an appointment. Its public page explains the service, location and booking route. The appointment provider manages availability and the information needed to book. The marketing CMS holds the public explanation.
That division gives the designer, clinic and booking provider something concrete to agree. It also stops a website redesign quietly becoming a patient-system replacement.
Organise pages around questions people bring
A service page should help someone work out whether they’ve reached the right place. Explain what the service covers, who delivers it, where it is available and how to ask about suitability. Have the clinical team approve wording that touches on care or treatment.
Avoid making people decode your internal departments. If the same service appears under several names, agree which wording helps the audience and explain the alternatives where useful. A search box can help, but the main navigation still needs to make sense.
Put practical details close to the action. If someone needs to call, show the relevant number beside the reason to call. If a location has access information, place it with the address and directions. A generic contact page shouldn’t carry every unanswered question.
I’d review the mobile version with those tasks in mind. Can someone find the right location without dismissing several panels? Does the booking link describe where it goes? Can the page be read without opening a PDF?
Make health content someone’s responsibility
Clinical content needs an owner who can judge its accuracy. The person laying out the page shouldn’t be asked to make that judgement from a folder of old brochures.
The NHS content policy describes clinical approval by suitably qualified staff and an evidence-based editorial process for NHS.uk. That’s the NHS’s process, rather than a certification offered to other websites. The useful lesson for a project is to agree who can approve the clinical wording.
Record the source, reviewer and review date with the content. Decide what should trigger another check: a changed service, a new product release or a correction to the underlying material. A visible review date only helps if someone maintains it.
For a resource centre, different material may need different templates. I designed and built WithPower’s Webflow content hub, with separate collections for guides, publications, podcasts and case studies. My scope was the publishing structure and CMS.

Want to apply this to your own website or app?
Tell me what you are working on and where it is getting stuck. I will help you turn the useful ideas into shipped work.
Include accessibility in the actual tasks
Test the pages and controls people will use, including anything supplied by a third party. Follow the booking route with a keyboard. Read the form labels, deliberately leave a required answer out and check whether the error explains how to recover.
The W3C forms tutorial explains labels, instructions and feedback. Those are useful foundations for reviewing an enquiry journey. They don’t turn a quick browser check into a complete accessibility audit.
Content structure matters too. W3C’s guidance on headings explains how heading levels communicate the organisation of a page. Use headings to describe the sections, rather than choosing a level because it happens to look right.
Include representative readers in research where the project allows it. A page that seems obvious to the team may still use unfamiliar terms or hide the detail someone needs before they feel comfortable making contact.
Check what happens after the click
A successful button press is only the beginning of an enquiry. Somebody must receive it, understand why it arrived and know what to do next.
Before launch, submit an agreed test enquiry using fictional information. Confirm the destination, acknowledgement and follow-up owner. Repeat the check when a connected service is unavailable. The website should give an honest explanation if it can’t accept a submission.
Keep health information out of a general marketing workflow unless the organisation has deliberately designed and approved that handling. The ICO’s explanation of health data shows why the content of a message can change its sensitivity. Choosing a familiar form tool doesn’t settle those questions.
Bring a journey to the first design conversation
Choose one important task and walk through it from the visitor’s first question to the staff member who takes over. List the unclear wording, missing information and handoffs along the way. That gives a redesign a useful starting point.
My healthcare and healthtech website work covers public websites and publishing systems, with the client’s product and clinical expertise involved where needed. The review sheet on that page helps you record owners and evidence before committing to a build.
If you’re still preparing the scope, the website brief template gives you somewhere to capture those decisions. Include the existing site, the booking or enquiry route and who will review the content.
Frequently asked questions
Should a healthcare website include patient accounts?
Only if the scope calls for them. A public website can explain a service and link to an existing patient or booking system. Accounts, health records and clinical workflows need their own requirements, responsibilities and data-handling review.
Who should approve clinical website content?
Agree a suitably qualified reviewer with the organisation. The website team can organise and present material, while the clinical reviewer checks its meaning and accuracy. Keep the approved version, source and review responsibility together.
Does an accessibility check guarantee the whole website is accessible?
No. A task review can reveal problems, but it only covers what was examined. Include representative templates, forms and third-party steps in the agreed assessment, then record findings and remaining work without claiming universal accessibility.

.jpg)






