
The Laboratories Reopened Before the Reckoning Was Complete
The ransomware attack on Synnovis delayed thousands of appointments and contributed to a patient’s death, the British government says. Service was restored in 2024, but examining the stolen data took more than a year, and notifications passed through different institutions.
In a parliamentary answer in July 2026, the British government confirmed that the cyberattack on Synnovis had contributed to a patient’s death. It described a contribution to the death, rather than finding that the attack was its sole cause. More than two years after the incident began, the harm extended beyond the number of postponed appointments or the length of a laboratory shutdown.
The attack began on June 3, 2024, affecting a laboratory-testing provider serving London health care institutions. According to NHS England, more than 11,000 appointments and procedures were postponed. Those were delayed services, not a count of 11,000 people who suffered medical harm. Establishing what happened to an individual patient requires a different examination from counting delays across a system.
Laboratory services were operating again by the end of 2024. For clinical teams, that was an operational milestone: a functioning testing process could once again be relied upon. But at least two other inquiries continued alongside the return of service—the effects of delays on treatment and the scope of the stolen information.
Regional records from September 2024 described panels reviewing immediate and longer-term harm. They were intended to examine broader effects alongside investigations by individual institutions. Their existence did not mean that every individual case had already been resolved. In its 2026 answer, the government said a patient-safety investigation had been conducted, lessons had been learned and processes for identifying harm had been improved.
The difficulty of assessing harm was not captured by appointment totals alone. Minutes from October 2024 described a lack of access to demographic data needed to examine equality considerations. The same record also reported reduced concerns following harm reviews. It depicts a system attempting to examine its own performance while recovering, rather than a study already establishing that one group had been harmed more than another.
The Slower Clock of Stolen Data
The privacy review followed a different timetable. According to the NHS and SYNLAB, examining the stolen files took more than a year because the information was fragmented and unstructured. Giving a medical institution a useful notification required identifying which of its information appeared in the files, rather than simply confirming that an attacker had copied a large dataset.
SYNLAB’s statement describes service restoration by late fall 2024. Synnovis’s March 2026 update confirms that notifications to institutions were completed by the end of November 2025. Each institution was responsible for assessing whether patients needed notification. Completion of notices to organizations did not mean every affected person received an individual notice that day.
The experience of North Cumbria shows what that stage looked like in practice. The organization said it learned only in November 2025 that its information had been included in the theft. It listed types of identifiers and testing-related data, but said no test results had been found in its particular affected information. Patients at that institution were therefore told that identifiers had been exposed, while test results were not included in the information identified.
North Cumbria also explained that it chose a website announcement rather than individual contact with everyone, partly because of the difficulty of verifying contact details and the time required. That explanation records the institution’s choice of notification method. The material reviewed contains no regulatory determination that the method violated the law.
The lengthy review does not mean laboratory services remained shut down throughout that period. Conversely, restoring routine testing does not resolve the experience of someone whose information was copied or whose treatment was postponed. Service, health and privacy advance on different timelines, even when they originate in the same incident.
Dependence on an outside provider has direct consequences here. A hospital needs a test result on time. It also needs sufficient information from its supplier to investigate harm and notify a patient. When the supplier is attacked, the institution depends on it both to restore work and to explain what happened behind its systems.
By the end of 2024, it was possible to announce that testing had returned. A year later, information about the data theft was still being communicated, and in 2026 the government confirmed a contribution to a death. Those dates do not contradict one another. They show why the day a computer returns to service is not necessarily the day a medical crisis ends.
Compiled November 16, 2026. Records and findings keep the dates stated in their sources; each link in the text opens the document it relies on.