Website & Development
GDPR Compliant Forms for Appointments and Contact on a Healthcare Website
Copy for AI
A healthcare website may offer appointment and contact forms, if it asks carefully.
The verdict: GDPR compliant forms on a healthcare site ask only for contact details, keep medical details out, rest on a valid legal ground and say plainly what happens next.
Health data falls under the special categories of the GDPR (the European data protection law). It’s subject to a processing ban in principle.
The practical fix is almost always the same:
- ask for as little sensitive information as possible
- base your processing on a valid legal ground
- be transparent about what happens to the data
Below: how to build GDPR compliant forms without watching your submissions dry up.
What makes a healthcare website different from a regular B2B site?
The type of data. Contact details are ordinary personal data, but anything about a complaint or treatment is health data.
Ordinary data versus health data
A name, email address and phone number are regular personal data.
As soon as a visitor reveals something about a complaint, a condition, a treatment or medication, you’re dealing with health data. The GDPR treats that as sensitive.
The Article 9 ban and its exceptions
For those special categories, Article 9 of the GDPR sets out a general ban on processing.
So you can’t simply collect them. Not even through an innocent-looking free text field on an appointment form.
The ban has exceptions. Two matter most for a healthcare site:
- Explicit consent of the data subject “for one or more specified purposes” (Article 9(2)(a))
- Care purposes: processing necessary for preventive medicine, medical diagnosis or the provision of health care or treatment (Article 9(2)(h)), under the professional secrecy conditions of Article 9(3)
Which exception applies depends on who you are and what you use the data for.
For example, a hospital or practice is in a different position than a supplier serving healthcare organisations.
Who supervises this in Belgium
The supervisory authority in Belgium is the Data Protection Authority (DPA). It has overseen the correct application of the GDPR since 2018.
Watch out: unsure about your legal ground? Have it reviewed by a lawyer or your data protection officer.
This article covers the web side: how to build your forms so you keep the risk small.
Which data should you ask for, and which should you avoid?
Only what you need to call someone back or schedule an appointment. That’s the core rule of data minimisation.
Start from the purpose of the form
On most healthcare websites that purpose isn’t “building a medical record”. It’s simply “calling someone back” or “scheduling an appointment”.
You don’t need a diagnosis for that.
Here’s the split in one picture:
What to ask for
Do ask for: name, phone number or email address, and optionally a preferred time slot or the department or service the person is calling about.
That’s enough to get in touch.
What to keep off the form
Better not to ask for: specific complaints, symptoms, diagnoses, medication or other medical details.
Even an open field saying “describe your question” invites exactly that kind of information.
If you keep a free text field
Add a short line asking visitors not to share medical details. Ask them to save those for a personal conversation.
That steers behaviour and lowers the chance of receiving health data you never wanted.
The substantive conversation then happens through a secure channel, by phone or at the practice, not through an open web form.
For example, a physiotherapy practice could ask only for name, phone and preferred day. The receptionist then asks about the complaint during the call.
Here’s what such a minimal form could look like:
Shorter forms convert better too
This approach isn’t only cleaner legally. It’s also better for your conversion.
Every extra field costs you completions.
The principles behind form conversion optimisation and those behind privacy point the same way: shorter is almost always better.
Our guide to lead form optimization goes field by field.
How do you handle consent without scaring the visitor off?
Make it specific, freely given and unambiguous, in one readable line. In practice: no pre-ticked boxes.
The visitor ticks a box or takes a deliberate action. You explain in one sentence what you use the data for, with a link to your privacy statement.
Three practical points follow.
Separate your purposes
Consent to be contacted about a request isn’t the same as consent for a newsletter. Don’t lump the two into one checkbox.
The Belgian Data Protection Authority’s consent rules also say a pre-ticked box is never valid consent. Withdrawing must be as easy as giving it.
Keep the text readable
One line next to the submit button, with a link to the full explanation.
A wall of legal text under every form damages both trust and conversion. The details belong in your website privacy policy.
Keep cookie consent and form data apart
The cookie consent for analytics or marketing on your site is separate from the ground on which you process form data.
Don’t confuse the two in your copy. Our overview of cookie banner rules in Belgium covers the cookie side.
Consent isn’t always the right basis
If you base your processing on another legal ground, for example because the data is necessary for providing care, a consent checkbox isn’t always the correct or required basis.
Have that decided case by case.
What always applies: be transparent about who you are, what you do with the data and how long you keep it.
How do you keep GDPR compliant forms technically secure?
With an encrypted connection, restricted access, a retention period and proper processor agreements.
Transparency and data minimisation are half the work. The technical side is the other half.
Encrypt the connection
The entire site, and certainly the form pages, run over HTTPS. Submitted data is then encrypted in transit.
Handle submissions securely
Don’t send form submissions in plain text to an unsecured mailbox half your team can read.
Limit who has access, and store the data somewhere with appropriate security. Our guide to website security covers the basics.
Set a retention period
Agree on how long you keep submissions, and delete them once you no longer need them.
Rule of thumb: less stored data means less risk.
Watch your processors
A form tool, CRM or email platform that processes data on your behalf is a processor.
The EDPB puts it simply: a processor “acts under the instructions of the controller only, by processing personal data on behalf of the controller” (EDPB guide for SMEs).
That calls for a data processing agreement. Article 28(3) GDPR requires a contract setting out the subject-matter, duration, nature and purpose of the processing.
According to the EDPB, that contract must also cover a few points, including:
- processing only on your instructions
- confidentiality for everyone with access
- deleting or returning the data when the service ends
Also check where the data is stored. Our piece on EU hosting and GDPR data residency explains why location matters.
Choose tools that support all this properly.
The same rules on every platform
Whether you build in Webflow, WordPress or a headless setup, these requirements apply regardless of platform.
We’re platform independent. We look case by case at which mix of form tool, hosting and processors best fits your security and growth needs.
You can read more about that approach on our page about web design and in the website development guide.
How do you stop privacy from costing you conversions?
By making the form short and clear about what happens next. Good privacy and good conversion reinforce each other.
A form that’s short, and makes clear what will happen and why it’s safe, feels more trustworthy.
On a healthcare website, where the threshold for sharing data is higher, that trust is decisive.
Four things help both privacy and conversion.
Say what happens after submitting
“We will call you back within one working day” creates clarity and takes the tension away.
Show trust signals around the form
A real phone number, an address and a face do more than a long disclaimer.
See also building trust on a B2B website, and our tips to optimize a contact page.
Offer an alternative
Not everyone wants to fill in a form. A visible phone number or email address gives people the choice.
Make it accessible
Clear labels, enough contrast and keyboard operation help everyone. They also prevent common web accessibility mistakes.
Be honest about what a form can do
A form captures the request safely and in a conversion-friendly way.
The medical substance and the real trust emerge in the contact that follows.
Frequently asked questions
Can a healthcare website use a contact form under the GDPR?
Yes. Ask only for contact details, keep medical details off the form, base your processing on a valid legal ground and explain what happens to the data.
Is a consent checkbox required on a healthcare contact form?
Not always. It depends on your legal ground. If you do use consent, the box must be unticked by default and separate from newsletter consent.
Do I need a data processing agreement with my form tool?
Yes, if the tool processes personal data on your behalf. Article 28(3) GDPR requires a contract that sets out the subject-matter, duration, nature and purpose of the processing.
The short summary
A healthcare website can offer appointment and contact forms, as long as you treat health data as a special category.
Ask only for contact details. Keep medical details off the form, rest on a valid legal ground, and state the purpose and retention period.
On the technical side, use HTTPS, restricted access and proper processor agreements.
Do that well, and you gain both trust and completed requests.
Want your healthcare website to be both GDPR compliant and conversion focused? We’ll review your current forms field by field.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.