Key takeaways
- Notify the regulator without undue delay and within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to people.
- Health data raises the severity of almost any breach, so assess carefully and do not wait for full information before starting the clock.
- Tell affected patients directly when the risk to them is high, unless the data was unintelligible or the risk has been removed.
- Record every breach, including those you decide not to report, with the facts, effects and actions taken.
The rule in brief
When a practice becomes aware of a personal data breach, it must notify the regulator without undue delay and, where feasible, not later than 72 hours after becoming aware of it[1]. No notification is needed if the breach is unlikely to result in a risk to people's rights and freedoms[1]. If the notification is made after 72 hours, it must explain the reasons for the delay[1].
Since 30 September 2026, the regulator receiving these notifications has been the Information Commission rather than the Information Commissioner[1]. Most people still call it the ICO, and the process for practices is the same. The clock runs in hours, including weekends and bank holidays, so practices need a way to deal with a breach discovered on a Friday afternoon.
What counts as a breach
A personal data breach is any security incident that leads to the accidental or unlawful loss, destruction, alteration, disclosure of, or access to personal data. It is not limited to hacking. In practices, most breaches are ordinary mistakes.
- Confidentiality: a letter sent to the wrong address, an email to the wrong recipient, a receptionist reading a neighbour's record.
- Integrity: information added to the wrong patient's record, or results altered by a system fault.
- Availability: ransomware or a system failure that leaves the practice unable to access records, even temporarily.
- Loss: a laptop, phone, paper list or smartcard left on a train.
Awareness starts when the practice has a reasonable degree of certainty that a breach has happened, not when the investigation is complete. Start the log as soon as anyone suspects a breach.
The first hour
Contain
Recall the email if possible, ask the wrong recipient to delete or return the information, disable a compromised account, isolate an infected computer.
Tell the right people
Inform the practice manager or information governance lead immediately, and the data protection officer the same day.
Start the log
Record the time of discovery, who found it, what happened, which data and how many people are involved, and what has been done so far.
Preserve evidence
Keep the email, envelope, screenshots or system logs. Do not wipe an infected machine before advice is taken.
Set the deadline
Calculate 72 hours from when the practice became aware and put it in the log.
Assessing the risk
The reporting decision depends on the likely consequences for the people affected. Health information is special category data under UK GDPR[2], and disclosure can cause distress, discrimination, damage to relationships or risk to safety. Weigh these factors:
- Type of data: diagnoses, mental or sexual health, safeguarding information and test results are more sensitive than appointment times.
- Volume: how many patients and how much information about each.
- Recipient: another NHS organisation bound by confidentiality is less risky than a member of the public or a social media post.
- Recovery: whether the information was returned or deleted, and whether you can confirm it.
- Vulnerability: children, people at risk of domestic abuse and patients with mental health conditions face greater harm.
- Ease of identification: whether the data clearly identifies individuals.
| Scenario | Report to the regulator? | Tell the patients? |
|---|---|---|
| Discharge letter emailed to another GP practice, deleted on request | Usually not | Usually not, but record it |
| Sexual health result posted to a patient's former partner | Yes | Yes |
| Unencrypted laptop with patient lists stolen | Yes | Likely, depending on content |
| Encrypted laptop stolen, key not compromised | Usually not | No |
| Ransomware prevents record access for a day, no data taken | Often yes, because of availability risk | Depends on impact on care |
| Staff member looked at a relative's record without reason | Depends on content and outcome | Often yes |
What the notification must include
The report must at least describe the nature of the breach, including the categories and approximate numbers of people and records concerned; give the name and contact details of the data protection officer or another contact; describe the likely consequences; and set out the measures taken or proposed, including steps to reduce the harm[1]. If you do not yet have everything, report what you know and follow up.
Practices that complete the Data Security and Protection Toolkit normally report health and care data incidents through the toolkit's incident reporting tool, which assesses the incident and passes reportable cases on to the regulator. Check the current route with your integrated care board or DPO so you are not searching for it at the deadline.
Telling patients
Where a breach is likely to result in a high risk to people, the practice must tell them without undue delay[3]. That duty does not apply if the data was protected so that it was unintelligible to anyone not authorised to see it, such as by encryption; if later action means the high risk is no longer likely; or if contacting each person would involve disproportionate effort, in which case a public communication is needed instead[3].
Example call script: 'I am calling from the surgery about a mistake we made. On Tuesday a letter about your appointment was sent to the wrong address. We have spoken to the person who received it, who has returned it. I am sorry this happened. I would like to explain what we have done and answer any questions you have.'
Speak to patients before they hear from anyone else, use plain language, say what happened, what the risks are, what you have done and what they can do. Follow up in writing and give a named contact.
Breaches are common, so prepare
In the government's Cyber Security Breaches Survey 2025, 43% of businesses and 30% of charities identified a cyber security breach or attack in the previous 12 months[4]. Add misdirected letters and emails, which are not cyber attacks at all, and it is clear that every practice will face breaches. Preparation matters more than luck.
Source: GOV.UK (Department for Science, Innovation and Technology), 2025[4]
Show the data
| Item | Value |
|---|---|
| Businesses | 43% |
| Charities | 30% |
- Keep a one-page breach procedure at reception and in the staff handbook.
- Name an out-of-hours contact for breaches discovered at weekends.
- Store the DPO's contact details where everyone can find them.
- Rehearse once a year with a short tabletop exercise.
Record every breach
Whether or not you report it, UK GDPR requires you to document every personal data breach, including the facts, its effects and the remedial action, in a way that allows the regulator to verify compliance[1]. A good log also records the reasoning behind each decision not to report. Failing to notify or document breaches is a breach of controller obligations carrying fines of up to £8.7 million or 2% of worldwide turnover[5].
After the report: learning from it
The regulator may ask follow-up questions, close the case with advice or, for serious incidents, investigate further. Respond promptly and keep copies of everything you send. Meanwhile the more valuable work happens inside the practice: understanding why the breach happened and stopping it recurring.
- Ask why at least three times. 'The letter went to the wrong address' becomes 'the address was out of date' becomes 'address changes at the desk are not always entered in the clinical system'.
- Fix the system before retraining the person; most breaches come from processes that make mistakes easy.
- Share a short, anonymised summary at the next team meeting so everyone learns from it.
- Review the breach log every quarter to spot repeats, such as several misdirected emails from the same shared inbox.
A practice that treats breaches as learning, not blame, gets more reports of near misses, and near misses are the cheapest way to find weaknesses before patients are harmed.
Example: a 72-hour timeline
Example (fictional): at 4.30pm on a Thursday a patient rang to say they had received another patient's blood test letter. Reception logged it at 4.35pm and told the deputy manager, who called the recipient and arranged collection of the letter that evening. At 9am on Friday the DPO assessed the risk: the letter showed a diagnosis of a long-term condition, the recipient was a neighbour and the letter had been recovered.
Because of the sensitivity and the neighbour relationship, the DPO advised reporting. The practice submitted the report by Friday afternoon, well inside 72 hours, and the GP phoned the affected patient the same day. The root cause, two patients with similar names in the same street, led to a check on address-matching in the letter template.
For prevention, see the most common breaches in practices and emailing patients safely; for new systems, see DPIAs for new practice technology.
Frequently asked questions
Do we have to report every data breach?
No. You must report breaches unless they are unlikely to result in a risk to people's rights and freedoms[1]. You must record every breach, reported or not.
When does the 72-hour clock start?
When the practice becomes aware of the breach, meaning it has a reasonable degree of certainty that one has occurred[1]. Weekends count.
Must we tell the patients affected?
Yes, without undue delay, if the breach is likely to result in a high risk to them, unless an exception applies, such as the data being encrypted[3].
What if we report late?
Report anyway and explain the reasons for the delay, as the law requires[1].
References
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 33: Notification of a personal data breach (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (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) ↑
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 83: General conditions for imposing administrative fines (opens in a new tab) ↑