Most health-data breaches that make the news involve ransomware crews or stolen databases. The problem the UK's data protection regulator is now taking on comes from inside: staff who are already allowed into the system and open patient records they have no reason to see.
On November 12, 2026, the UK Information Commissioner's Office (ICO) said its Chief Executive, Paul Arnold, had written to more than 200 senior leaders across the health sector. The letter asks each of them to personally assure the regulator that their organisation can stop, spot and deal with unauthorised access to medical records. They have until November 27, 2026 to reply.
The trigger was volume. The ICO says that between January 1 and mid-October 2026 it received more than 300 reports of unauthorised access from health-sector organisations. That figure leaves out reports still waiting to be assessed.
What counts as "snooping"?
According to the ICO, the reports fall into three broad patterns:
- Staff viewing records with no legitimate need to do so.
- Staff looking up the records of people they know.
- Staff sharing information from those records.
As The Register put it in its coverage, the problem is often people with legitimate access misusing it, not outsiders hacking in. That makes it a hard class of incident to fight with perimeter tools. The person opening the record is typically signed in normally, with an account that is meant to reach patient data. Nothing looks wrong at the network layer. What makes it a breach is why the record was opened.
One caveat on the numbers. The Register notes that the 300-plus figure covers reports submitted by healthcare organisations, not confirmed breaches. Some of those reports may not turn out to be unlawful access. The count still shows how often organisations themselves are raising the alarm.
The cases behind the warning
Infosecurity Magazine pointed to several recent incidents that show what this looks like in practice:
- In May, 11 staff were sacked and 14 given written warnings after accessing the records of victims of the 2023 Nottingham knife attacks.
- A Cambridgeshire hospital investigated around 40 staff who accessed the records of a seriously injured child.
- In June, the ICO cautioned a former healthcare worker who tried to access and sell the Princess of Wales's medical records.
The same pattern runs through all three. A high-profile or emotionally charged case brings in curious insiders, and in the worst cases someone tries to make money from it. The ICO said it had already set out practical advice and good practice recommendations to the sector in June. This week's letter goes further: it asks named leaders to put their own assurance on record.
What the ICO is actually asking for
The letter, titled "Protecting patients from unauthorised access to health records," asks chief executives for assurance in four areas:
- Effective access controls: controlling who can see which records in the first place.
- Effective monitoring: spotting suspicious access through monitoring and audit.
- Regular and effective training: making sure staff know what is expected of them and what happens if they break the rules.
- Consistent action when things go wrong: including notifying affected individuals and, where required, the ICO.
There is also a time element. Leaders are asked to confirm that they have reviewed these measures within the past six months. If they have not, they must complete a review within three months. Responses go to the ICO through a link supplied in the letter.
The ICO says the letter will be published and that the responses will shape its next steps. It is working with the National Data Guardian in England on the issue.
Who can be punished: the staff member or the organisation?
Potentially both.
For individuals, the ICO can prosecute under section 170 of the Data Protection Act 2018. The regulator says it has prosecuted 16 healthcare staff in the last decade. That works out to fewer than two a year, which suggests prosecution is saved for the worst cases. Most incidents end in internal discipline, like the dismissals and warnings in Nottingham.
For organisations, The Register reports that Arnold warned the ICO could also take enforcement action against bodies whose protections are not adequate. That shifts the focus. A trust that shows it had sensible controls, caught the snooping and acted on it is in a very different position from one that only learned what happened when a patient complained.
Asking for personal assurance from senior leaders matters too. Once a chief executive has told the regulator in writing that monitoring works, a later incident showing nobody was reviewing the audit logs becomes much harder to explain.
What It Means for Defenders
This is not a software flaw, so there is no patch. The fix is a set of controls and processes. The ICO's four areas work as a checklist for any organisation that holds sensitive personal records, inside or outside the UK.
Who is directly affected: the 200-plus senior health-sector leaders who got the letter, who have until November 27, 2026 to respond. Anyone running identity, access or security operations for those organisations, or for suppliers that host or support their clinical systems, may well be asked what evidence exists.
What to check now, mapped to the ICO's four areas:
- Access controls. Can you show who can open which records, and why? Role-based access exists to limit what each job can reach. Review whether roles are set as narrowly as clinical work allows, and whether accounts for leavers and people who changed jobs have been removed or adjusted.
- Monitoring and audit. Having audit logs is not the same as watching them. The patterns the ICO describes (looking up people you know, piling into a high-profile patient's record) are exactly what proactive audit is meant to catch. The Nottingham and Cambridgeshire cases show the value of being able to list everyone who touched a particular record after the fact. Confirm you can do that quickly, and confirm someone is actually reviewing the alerts.
- Training. The ICO wants staff to know both the expectations and the consequences. Training that says, in plain terms, that snooping has led to dismissals and prosecutions is more likely to stick than a generic data protection module.
- Response. Have a written, consistently applied process for investigating suspected misuse, disciplining staff, telling affected patients and, where required, reporting to the ICO.
- Review cadence. If these controls have not been reviewed in the past six months, the ICO expects that done within three months. Record the review date and its findings so the assurance you give is backed by evidence.
For organisations outside the UK: the ICO's rules do not bind US hospitals or the contractors that support them. Still, the four-part model (control, monitor, train, act) is a clear way to deal with insider access to any high-value dataset, from medical records to case files to customer data. Any team whose biggest data risk is authorised users going where they should not can use the letter as a ready-made self-assessment. The question to ask is not whether an outsider could get in, but whether you would notice if a legitimate user started reading records out of curiosity.
Sources
- UK health sector warned to tackle medical record snooping (ICO, Nov 12, 2026)
- Protecting patients from unauthorised access to health records (ICO letter to chief executives, Nov 12, 2026)
- Crackdown on UK medical record snooping after staff reported sneaking 300+ times this year (The Register, Nov 13, 2026)
- ICO Receives 300+ Reports of Medical Snooping (Infosecurity Magazine, Nov 16, 2026)