What often plays out
-
Two or three audiences at once: patients, family, care providers, and the staff you are trying to hire.
-
Privacy-sensitive content, so anything that touches patient data has to be right the first time.
-
High visitor numbers on a site that has to stay readable, accessible and fast on a five-year-old phone.
-
Practical questions that decide whether someone comes in at all: who is welcome, what does it cost, where is the nearest location.
A patient and a care provider on the same site, with a different question
We split the site by the question people arrive with instead of by the organisation chart. A route for patients and family, a route for care providers, one shared knowledge base underneath, so both read the same source without reading the same page. See websites and web design.
Then we make the practical part actually work. Location finders with a radius, opening times per location, request forms with rules in them that stop a request when it cannot be honoured yet, and accessibility built in from the start rather than patched in after the audit. See web applications and automation & AI.
The result should feel calm. For the care provider, because the tool is where they look for it. For the patient, because the answer is in plain language.
Client example
Like at PoZoB. Or see LEEFH, the national expertise centre for inherited high cholesterol, where families and care providers take separate routes through one site with a shared knowledge section behind both. The test kit request is a form with rules in it: it asks whether a doctor has been spoken to and whether the family has already had DNA testing, and it stops the request with an explanation when the answer means the kit cannot be sent yet.
Cases in Healthcare
-
LEEFH: inherited high cholesterol, explained to two audiences at once
-
Straatzorg Rotterdam: a site that says where the street doctor is today 
Straatzorg Rotterdam: a site that says where the street doctor is today
View case
