Keeping Care Running Through Disruption

Most continuity planning starts by asking what the business can tolerate losing and for how long. In healthcare that question has a different weight, because the answer is measured in care delivered rather than revenue deferred.

Cyber incidents have made this concrete. A hospital that loses its clinical systems does not pause and resume. It falls back to paper, diverts patients, reschedules procedures, and absorbs the consequences for weeks after the systems return. The recovery clock and the clinical risk run together.

The plan has to be reachable when the network is not

This is the detail that catches organisations out. Continuity procedures are frequently stored in the environment they exist to recover — a file share, an intranet, a system behind the same authentication as everything else. An incident that takes out access takes out the instructions for responding to it.

Procedures have to be held somewhere separately reachable, in a form people can act on under pressure. Not a 90-page binder; the specific sequence for the specific unit, available to the person standing in it.

Dependencies are where the surprises live

Clinical services depend on far more than clinical systems. Diagnostics, pharmacy, sterilisation, patient transport, third-party labs, supply — each has its own systems, its own vendors and its own failure modes, and most are invisible from the top of an organisation chart.

Dependency mapping is unglamorous work that pays off exactly once, catastrophically. It is how you find out before an incident that a single supplier sits underneath four services you had assumed were independent, and that a third-party outage reaches further into your operation than anyone had drawn.

Accreditation is the floor, not the goal

Healthcare organisations carry a heavy compliance load, and it is tempting to let the accreditation cycle define the programme. It is a floor. Meeting the standard proves the documentation exists; it does not prove the organisation can execute under stress.

The distinction shows up in exercising. A programme built for accreditation exercises to produce a record. A programme built for resilience exercises to find out what it has got wrong — and treats each finding as the point of the exercise rather than an exception to be closed.

Learning from every incident

The organisations that get steadily better at this treat every disruption, including the small ones, as information. A two-hour outage in one department tells you something about dependencies, response times and whether people could find the procedure. That is worth capturing while it is fresh, because the next incident will not be considerate enough to be identical.