Key takeaways
- NHSmail can encrypt messages to patients' ordinary email addresses; private clinics need an equivalent encrypted route from their own email provider.
- Agree email with the patient first: confirm the address, explain the risks and record their preference.
- Some information should not go by email at all, however it is protected; a call or a secure portal is better.
- Most email risk comes from the practice's own account being compromised, so multi-factor authentication matters as much as encryption.
Why email needs a policy, not just a habit
Many patients would rather receive a letter, a form or a result by email than wait for the post, and many practices now use email routinely. The convenience comes with risks: messages sent to the wrong address, read by someone else in a shared account, intercepted, or sent from a practice account that has been taken over by a scammer. Health information is special category data under UK GDPR[1], so the bar for protecting it is high.
Patients notice. In the government's public attitudes tracker, 57% of UK adults identified data not being held securely, or being hacked or stolen, as a risk of data use[2]. A clear, consistent approach to email is one of the most visible ways a practice can show it takes that risk seriously.
The secure routes available
| Route | Who can use it | When it fits |
|---|---|---|
| NHSmail to another secure NHS or care address | GP practices, NHS dental practices, pharmacies, many care providers | Sharing with other professionals involved in care |
| NHSmail encryption to a patient's personal address | Practices with NHSmail accounts | Sending a document or message containing health information to a patient |
| Encrypted email from a commercial provider | Private clinics and practices without NHSmail | Equivalent of the above, if properly configured |
| Secure patient portal or app messaging | Practices with a portal or messaging tool | Ongoing conversations and results, where the patient logs in |
| Ordinary unencrypted email | Anyone | Only non-sensitive admin, or at the informed request of the patient |
NHSmail is the NHS's secure email service. Messages between NHSmail and other accredited secure addresses are protected in transit. To send to a patient's personal address, NHSmail users can encrypt the message, typically by adding the word 'secure' in square brackets to the start of the subject line. The patient receives a notification and opens the message through the encryption service, where they can also reply securely.
Private clinics and practices without NHSmail
Private clinics usually run their own email, often on a business platform with an encryption option. Check three things with your provider: that messages can be encrypted end to end or through a secure portal for recipients outside your organisation, that staff can apply encryption easily, and that transport encryption between mail servers is enforced. If encryption is hard to use, staff will not use it, so test it with a real colleague's personal address before rolling it out.
A secure patient portal or messaging tool may be a better route for clinics that send many documents, because it keeps the information inside a system where the patient signs in, rather than in inboxes on both sides.
Agreeing email with the patient
Confirm the address
Ask the patient to give or confirm the address in person, by phone or through a verified form, and repeat it back. Do not rely on an address in an old referral.
Check who else can see it
Ask whether the account is personal. Family or work addresses can be read by others.
Explain the method
Tell them they will receive an encrypted message and how to open it, or that you will use the portal.
Record the preference
Note the address, the date it was confirmed and what the patient agreed to receive by email.
Send a test
For the first message, send something non-sensitive and ask the patient to confirm they received and opened it.
Some patients will say they do not want the bother of encryption and are happy with ordinary email. If you agree, explain the risks first, record the request and still keep the most sensitive information on secure routes. The patient's preference does not remove the practice's duty to protect the data.
What not to send by email
- Results or diagnoses that need explanation or might cause alarm, such as a new cancer, HIV or genetic result. Speak to the patient first.
- Safeguarding information, or anything about a third party who has not agreed to its disclosure.
- Full medical records, unless through a secure route agreed for a specific request.
- Passwords, login codes or payment card details.
- Anything to an address you have not confirmed with the patient.
- Information about a child to a parent's address where the young person is entitled to confidentiality.
A simple test before sending: if this email reached the wrong person, would the patient be harmed or distressed? If yes, use a secure route or a phone call, and double-check the recipient.
Wording that helps
Small pieces of standard wording reduce mistakes and set expectations. Agree them once and build them into templates.
- Subject lines: neutral and specific, such as 'Your appointment letter' rather than naming a condition or clinic.
- First line: who the email is for, so a wrong recipient knows immediately it is not meant for them.
- Footer: a short note that the email is confidential, what to do if it arrived by mistake and that the inbox is not monitored for urgent medical problems.
- Urgent help: a line pointing to NHS 111 or 999, so nobody waits for a reply to an emergency.
- Replies: how long the practice normally takes to respond, and which channel to use instead for clinical questions.
Review templates whenever a service changes. An out-of-date footer promising a same-day reply, for example, creates complaints the practice could easily have avoided.
Securing the practice's own accounts
Encryption protects messages in transit. It does nothing if someone has the password to the practice mailbox. Phishing was reported by 85% of businesses that identified a breach or attack in the Cyber Security Breaches Survey 2025[3], and a compromised mailbox exposes every message in it. Yet only 40% of businesses overall required two-factor authentication for access to their networks or applications, rising to 74% of medium and 92% of large businesses[3].
- Turn on multi-factor authentication for every mailbox, including shared ones.
- Give each person their own login; avoid passwords shared around reception.
- Limit who can access shared inboxes and review the list when staff leave.
- Set rules so mail cannot be forwarded automatically to personal accounts.
- Train staff to recognise phishing and to report it quickly without fear of blame.
Encryption and breaches
Encryption also changes the consequences of a mistake. If a breach is likely to result in a high risk to people, you must tell them, unless the data was protected so that it is unintelligible to anyone not authorised to access it, such as by encryption[4]. An encrypted message sent to the wrong address is still a breach to record and assess, but it is far less likely to harm the patient than an unencrypted one.
Shared inboxes and incoming email
Most practices receive far more email than they send, often into a shared reception inbox. Patients send photos, letters from other services and long descriptions of symptoms. Decide who monitors the inbox, how often, how messages are filed to the clinical record and how quickly they are deleted from the inbox once filed. Anything clinical should be moved into the record and triaged in the same way as other requests, rather than left in an inbox that only one person checks.
Newsletters and marketing are different
Care emails and marketing emails follow different rules. Marketing emails to individuals need prior consent unless the soft opt-in applies, which covers people whose details were collected during a sale, for similar products and services, with an opt-out each time[5]. Keep marketing lists separate from clinical contact details, and never use a patient's health information to target promotions without explicit consent.
Example: a clinic standardises its email
Example (fictional): a private physiotherapy clinic found its staff emailing treatment plans from a mix of personal-looking addresses with no encryption. The manager moved everyone onto named accounts with multi-factor authentication, switched on the email provider's encryption feature and wrote a one-page guide with the 'would this harm the patient' test. Treatment plans moved to the clinic's booking portal, where patients sign in to view them.
New patients now confirm their email address at the first appointment and receive a short test message. Six months later the clinic's breach log showed no misdirected emails, compared with several near misses the year before.
For the bigger picture on mistakes and attacks, see the most common data breaches in practices and reporting a breach within 72 hours. Text messaging raises related questions, covered in our guide to texting patients under GDPR.
Frequently asked questions
Can GP practices email patients using NHSmail?
Yes. NHSmail can send encrypted messages to patients' personal addresses, which the patient opens through the encryption service. Confirm the address and the patient's agreement first.
Is it a breach to email a patient without encryption?
Not automatically, but it increases risk. Use encryption or a secure portal for health information, and if a patient asks for ordinary email, explain the risks and record their request.
What should never be emailed to patients?
Results that need explanation, safeguarding information, third-party information, full records outside an agreed secure route, and anything to an unconfirmed address.
Does encryption matter if we send to the wrong person?
Yes. If data was unintelligible to the recipient, for example because it was encrypted, you may not need to notify the patients affected[4], though you must still record the breach.
References
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑
GOV.UK (Department for Science, Innovation and Technology) (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑
GOV.UK (Department for Science, Innovation and Technology) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 34: Communication of a personal data breach to the data subject (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). Privacy and Electronic Communications Regulations 2003, regulation 22 (opens in a new tab) ↑