When Healthcare Systems Fail, Look at the Decisions, Not the Hardware

An anonymous clinician's hands holding a tablet showing an alert screen in a dim hospital corridor at night, illustrating a human response to a system that has already failed.

Healthcare IT governance failures rarely look like governance failures until they are reconstructed afterward. On 3 June 2024, a ransomware group encrypted the systems of Synnovis, a pathology services provider contracted by NHS trusts across London. Within days, more than 1,700 elective operations had been cancelled, over 10,000 outpatient appointments were disrupted, and blood testing services failed across multiple hospitals, depleting O-negative stocks across the country. Synnovis\u2019s own accounts, filed in January 2025, put the direct financial loss at £32.7 million for the year.

The technical cause was a ransomware attack. The decisions behind it were made long before June 2024.

 

The Pre-Incident Decisions That Matter

Healthcare IT failures accumulate rather than arrive without warning. They come from governance decisions that treated third-party dependencies as acceptable risk, from budgets where maintenance lost out to transformation spend, and from cultures where uptime was assumed to be someone else’s problem until it became everyone’s.

Synnovis is illustrative rather than exceptional. The breach at Change Healthcare, the US health-payment processing company, in February 2024, eventually confirmed to have affected close to 193 million individuals, remains the largest healthcare data breach in US history. Its root cause traced back to inadequate third-party oversight and a disengaged board. The pattern repeats across geography.

Healthcare IT downtime costs hospitals between $5,300 and $9,000 per minute depending on facility size, according to industry survey data. The CrowdStrike outage in July 2024 alone produced an estimated $1.94 billion in healthcare losses globally. These figures price predictable governance failures, more than any single unpredictable technical event.

 

Single Points of Failure Get Accepted

A consistent feature of major healthcare IT incidents: the single point of failure was known before it became a crisis.

Third-party pathology services were deeply integrated with operational workflows at the trusts Synnovis served. The dependency was structural, not hidden. Governance should have asked, repeatedly: what happens when this fails, what is the fallback, and has recovery been tested?

In most cases those questions were asked at procurement and never revisited as the system’s footprint grew into critical infrastructure.

 

The Maintenance Conversation Nobody Wants to Have

Healthcare organisations face a structural pressure that favours underinvestment in resilience in the short term. Clinical priorities are immediate and visible. System maintenance is invisible until it fails. Capital allocation conversations reward new platforms and new integrations, and depress investment in keeping existing systems dependable.

The result surfaces only during an incident: deferred patching, undocumented legacy dependencies, recovery processes untested for eighteen months, disaster recovery plans describing an environment that no longer exists.

NHS England and five of its largest hospital trusts, Manchester University, Guy’s and St Thomas’, Newcastle Hospitals, Mid and South Essex, and Barts Health, reported 274,620 IT incidents across 2025, according to an analysis of Freedom of Information responses reported by SecurityBrief UK. Several trusts could not provide complete incident counts or link incidents to patient care, so the reported figure understates the true number. It is a governance statistic as much as a technology one: it describes systems maintained below the level their operational dependency required.

 

Who Owns Uptime?

The most important resilience question in any healthcare organisation is simple: who, at executive level, is accountable for treating resilience as a strategic priority, and who will be asked to explain themselves when it fails?

Where that question has a clear answer, resilience investment is sustained and third-party dependencies are reviewed systematically. Where uptime is an unassigned default left to the IT function, the accountability gap opens and risk accumulates.

That requires leaders who can translate infrastructure risk into patient safety language, and keep making the case without headlines to justify it.

 

What Strong Healthcare IT Governance Looks Like

Organisations with strong healthcare IT resilience share four habits. They treat third-party dependencies as their own risk rather than the vendor’s. They test recovery under conditions that approximate a real incident. They assign executive accountability for resilience beyond the CISO or the IT director. They fund maintenance on the same cycle as innovation.

None of it requires exceptional technology. It requires leadership willing to ask hard questions before an incident forces them.

 

The Lesson the Data Keeps Offering

Every major healthcare IT failure of the past three years has offered the same lesson: the root cause was a governance gap accumulated over years rather than created in a single technical moment.

The organisations that avoid the next incident will not be the ones with the newest systems. They will be the ones where someone senior enough asked, long before the crisis, what happens when this fails, and made sure the answer was unacceptable.

Resilience is a decision. It is made before the incident, or not at all.

Get new articles by email. One short digest a week, no spam, unsubscribe any time.

Lighting Up The Tunnel, in your inbox

Pre-Mortems, cheat sheets and practical ideas on PMO, governance, AI and cyber for leaders. Short, useful and free.

No spam. Unsubscribe any time. Read our privacy policy for more info.

Scroll to Top