Hundreds of maternity files 'methodically deleted' at NHS trust
Summarised from 2 outlets · Updated 7 Nov, 13:32 · Archive
Hundreds of files relating to maternity cases at Nottingham University Hospitals NHS Trust were found to have been 'methodically and selectively deleted', an independent barrister's investigation concluded. The deletion occurred in July 2024 and followed a police inquiry. Nottinghamshire Police concluded in June 2025 that the loss was 'most likely' intentional or malicious and the action of an individual, but found no evidence of systemic corruption within the trust.
Despite the investigation determining that files were deliberately deleted, it proved impossible to identify who was responsible. The barrister found that the absence of auditing information prevented investigators from establishing the individual's identity. The deleted material was eventually restored and would have been relevant to both the senior coroner and the independent review of maternity failings led by senior midwife Donna Ockenden, which identified significant care failures at the trust.
Families affected by the maternity scandal have expressed concern about both the 2024 deletion and a separate data incident in August 2024 in which maternity data was unintentionally overwritten during IT work. The trust has apologised for the distress caused by both breaches.

How it is being reported
- NUH does not know who 'methodically' deleted Nottingham baby death recordsHundreds of files relating to child deaths at Nottingham's hospitals were deletedNottinghamshire Live · 7 Nov, 12:49
- Maternity data deleted 'methodically and selectively'Investigations were carried out into two data breaches at Nottingham University Hospitals NHS Trust.BBC Nottingham · 6 Nov, 18:45
In this story: Nottingham University Hospitals NHS Trust · Donna Ockenden · Nottinghamshire Police · Nottingham
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)