Blog
Compliance & Privacy

How to Set Up Patient Communication That Complies With GDPR in UK

April 6, 2026 · Jordan Ellis

How to Set Up Patient Communication That Complies With GDPR in UK
Formisoft

From the team at Formisoft, the HIPAA-ready platform for patient intake, scheduling, and payments. Learn more →

Your front desk sends appointment reminders, payment requests, lab result notifications, and follow-up messages every single day. Under GDPR, every single one of those messages has to meet specific rules about consent, data minimization, and patient rights. Get it wrong and you're looking at fines up to £17.5 million or 4% of annual turnover, whichever is higher.

The good news: you don't need a law degree to run compliant patient communication workflows. You need clear processes, the right tools, and an understanding of what GDPR actually requires when you text or email health information.

What GDPR Says About Patient Communication

GDPR (the UK General Data Protection Regulation, retained after Brexit and enforced by the ICO) treats patient communication as processing of personal data. When you send an SMS reminder, you're processing name, contact details, appointment date, and sometimes health information. All of that falls under GDPR.

Here's what the regulation requires:

Lawful basis for processing. You need one of six legal grounds to send messages. For NHS practices, that's usually "public task" (providing healthcare). For private practices, it's often "legitimate interests" (appointment management) or "contract" (fulfilling an agreement with the patient). Marketing messages require explicit consent.

Data minimization. Only send what's necessary. An appointment reminder doesn't need the patient's full medical history in the message body.

Security. Messages containing personal data must be sent securely. That means encrypted channels, not plain-text SMS with diagnosis details.

Patient rights. Patients can request access to their communication history, ask you to stop messaging them, or demand deletion of their contact data.

I've worked with London clinics that thought GDPR meant they couldn't text patients at all. That's not true. You just have to do it right.

Consent vs. Legitimate Interests: Which One Do You Need?

Most practices get confused about whether they need explicit consent to send appointment reminders. The answer is usually no.

Most practices rely on legitimate interests as their lawful basis for appointment-related communication. The ICO accepts that clinics have a legitimate need to confirm appointments and reduce no-shows, and this interest isn't overridden by patient privacy concerns, especially if you're minimizing data in the messages.

You do need explicit consent for:

  • Marketing messages (special offers, new service announcements)
  • Communication methods the patient didn't provide (like emailing someone who only gave a phone number)
  • Sharing data with third parties for non-clinical purposes

When you collect patient contact information during new patient intake, include a clear statement: "We'll use this number to send appointment reminders and practice updates. You can opt out anytime." That documents your legitimate interest and gives patients control.

For marketing, use an opt-in checkbox. "I'd like to receive promotional offers and health tips via SMS/email." No pre-ticked boxes.

SMS Reminders: The GDPR Checklist

Text message reminders are the most common patient communication channel practices use. They're also the easiest to get wrong.

Here's what GDPR-compliant SMS reminders look like:

1. Don't include diagnosis or treatment details in the message body. "Reminder: Dr. Patel appt tomorrow at 2pm" is fine. "Reminder: diabetes follow-up tomorrow at 2pm" is not. SMS is inherently insecure. Anyone with the phone can read it.

2. Include an opt-out mechanism. "Reply STOP to unsubscribe" at the end of reminders. When someone opts out, remove them from automated messaging immediately.

3. Document your lawful basis. In your privacy notice, explain that you send reminders as part of appointment management (legitimate interests) and patients can opt out.

4. Keep it minimal. Name, date, time, location. Nothing else.

5. Use a GDPR-ready platform. Your SMS provider needs to be GDPR-compliant too. Check for data processing agreements and UK-based or adequately protected data storage.

I worked with a Manchester dental practice that was sending reminders with procedure names in the SMS. A patient's partner saw "root canal reminder" on the lock screen and complained. The practice switched to generic reminders and documented consent for detailed messages. No more issues.

Email Communication: Encryption and Access Controls

Email is more secure than SMS, but only if you set it up right. GDPR requires that emails containing health information be sent through encrypted channels.

Use TLS encryption for all patient emails. This encrypts the message in transit. Most modern email providers (Gmail, Outlook, etc.) use TLS by default, but verify with your IT team.

Avoid sending detailed clinical information via regular email. Lab results, treatment plans, and diagnosis details should go through a secure patient portal, not a standard email. If you must email clinical info, use encrypted email services that require recipient authentication.

Include unsubscribe links. Even for transactional emails (appointment confirmations, payment receipts), patients should be able to opt out of future messages.

Train your staff on email security. No BCCing patient lists, no forwarding patient emails to personal accounts, no discussing cases via unencrypted channels.

A Birmingham clinic I worked with switched to patient notifications through a secure platform instead of regular email. They still send appointment confirmations via email, but anything clinical goes through the portal. Patients log in with two-factor authentication, and the practice has full audit trails for GDPR compliance.

WhatsApp, Messenger, and Other Messaging Apps

Here's the reality: patients ask to communicate via WhatsApp. Clinicians want the convenience. But GDPR and the ICO are clear that consumer messaging apps aren't appropriate for most clinical communication.

Why WhatsApp is risky:

  • Meta (WhatsApp's parent) processes metadata and contact information
  • End-to-end encryption doesn't cover metadata or backups
  • No clear data processing agreement for healthcare use
  • Difficult to maintain audit trails and patient access rights

If you must use messaging apps:

  • Get explicit written consent from each patient
  • Document that the patient understands the risks
  • Only use for non-clinical coordination (appointment scheduling, general questions)
  • Never send diagnosis, test results, or treatment details
  • Use WhatsApp Business with privacy settings locked down

A better option: use a healthcare-specific messaging platform that's built for GDPR. These tools give you messaging convenience with proper encryption, audit trails, and data processing agreements.

Payment Reminders and Collection Messages

Sending payment reminders introduces another layer of GDPR considerations. You're now processing financial data alongside personal data.

Keep payment messages separate from clinical messages. "You have an outstanding balance of £150" is fine. "Your outstanding balance for the colonoscopy is £150" is mixing clinical and financial data unnecessarily.

Use secure payment links. Don't include card details in messages. Send a link to a secure payment page where the patient can pay through an encrypted form.

Document your lawful basis. Payment collection is usually covered under "contract" (fulfilling the terms of service) or "legitimate interests" (collecting payment owed).

I've seen practices in Leeds automate payment reminders through online payment systems that generate unique, time-limited payment links. The SMS just says "Outstanding balance: click here to pay securely." No clinical details, no stored card numbers, full GDPR compliance.

Building a GDPR-Compliant Communication Workflow

Here's how to structure your patient communication to meet GDPR requirements from intake to follow-up:

At intake: Collect contact preferences. "How would you like to receive appointment reminders: SMS, email, phone call?" Document consent for each channel. Explain what types of messages you'll send.

For appointment reminders: Use automated systems that send minimal-data messages with opt-out options. Track who's opted out and respect those preferences across all channels.

For clinical communication: Use secure patient portals for anything sensitive. Email and SMS should only handle scheduling and general practice updates.

For payment collection: Send reminders with secure payment links, never detailed billing information via unsecured channels.

For marketing: Require explicit opt-in consent. Separate marketing lists from operational communication lists. Make unsubscribe obvious and immediate.

For record-keeping: Keep logs of consent, opt-outs, and communication channels for each patient. This is your proof of GDPR compliance if the ICO ever asks.

The Tools That Make This Easier

Running GDPR-compliant communication manually is possible but tedious. The practices I work with use platform features that handle the heavy lifting:

  • Automated consent capture during patient registration
  • Opt-out tracking that prevents messages to unsubscribed numbers
  • Message templates that enforce data minimization
  • Audit logs that show every message sent and when
  • Secure patient portals for clinical communication
  • Data processing agreements with your vendors

Look for patient communication platforms that can show you their GDPR compliance documentation, not just promise they're compliant.

Common Mistakes That Get Practices Fined

I've seen these slip through even at practices trying to comply:

Storing patient phone numbers in unsecured spreadsheets. If a staff member's laptop gets stolen, you've got a data breach. Use encrypted systems.

Sending clinical details via SMS. Just because the message is brief doesn't mean it's secure.

Not documenting consent. "We thought they agreed" isn't proof under GDPR. You need written records.

Ignoring opt-outs. If a patient says stop, you stop. Continuing to message them is a violation.

Using non-GDPR compliant third-party tools. Your SMS provider, email service, and messaging app all need to have data processing agreements in place.

The ICO regularly publishes enforcement actions. Most fines come from lack of documentation and ignoring patient rights requests, not from the communication itself.

Moving Forward

GDPR compliance for patient communication isn't about stopping communication. It's about doing it transparently and securely. Your patients want reminders. They want to know test results. They just want to know their data is handled properly.

Start with your current workflows. Which messages are you sending? What's your lawful basis? Are patients opting out? Are you storing data securely? Fix the biggest gaps first, then work through the checklist above.

If you're uncertain, contact the ICO directly. They publish guidance specifically for healthcare providers, and you can ask for clarification on your specific situation.

Your front desk can keep sending reminders. Just make sure every message follows the rules.

Ready to digitize your intake?

Start building HIPAA-ready patient intake forms in minutes.

Get Started