Patient Diversion

Expanded Definition

Patient diversion describes a controlled shift of patients to another site, service line, or care pathway when the original facility cannot safely absorb demand. It is not the same as routine transfer, elective referral, or bed management. The defining feature is urgency tied to capacity, capability, or systems failure, where the clinical team must protect patient safety by moving demand elsewhere.

In healthcare operations, diversion can be triggered by emergency department saturation, staffing shortages, ICU capacity constraints, power loss, or the unavailability of supporting technology such as triage, laboratory, medication, imaging, or communications systems. The security-relevant boundary is important: diversion is a consequence-management action, not a security control by itself. When cyber or resilience events disrupt core workflows, diversion may become the safest available operational response.

There is broad consensus that diversion should be governed as an operational safety decision with clear escalation criteria, local authority, and coordination with regional partners. The practical misunderstanding is treating diversion as only an ambulance-routing issue. In reality, it often reflects a wider inability to provide safe clinical handling at that point in time. NIST SP 800-53 Rev 5 Security and Privacy Controls helps frame the underlying availability and continuity expectations that failures can affect, even though diversion itself is a clinical response.

Examples and Use Cases

Patient diversion appears in several operational settings where demand outstrips safe local handling or where essential services are degraded. In each case, the goal is to prevent unsafe intake rather than simply reduce workload.

• Emergency department diversion during a surge, where incoming ambulances are directed to another hospital because local triage and treatment capacity are exhausted.
• Redirecting trauma, stroke, or cardiac cases to a specialist centre when the original site lacks the required service capability or an enabling system is down.
• Diverting patients away from a facility during a major cyber incident that prevents reliable access to records, medication orders, or diagnostic systems.
• Moving callers or referrals to neighbouring sites when scheduling, call centre, or transfer coordination systems are unavailable.
• Using regional diversion protocols to preserve critical care capacity when staffing, bed availability, or transport coordination cannot support safe intake.

A common tradeoff is that diversion protects safety at one site but increases pressure on another, so the decision has network-wide consequences. It can also delay diagnosis or treatment if downstream capacity is already tight. That is why diversion planning is usually coordinated across facilities rather than treated as a local emergency-only workaround.

Security Implications

When diversion is driven by a cyber incident, the security problem is not just system unavailability. The deeper issue is loss of safe operating visibility: if staff cannot trust records, medication status, imaging results, or communications channels, then accepting new patients can create immediate clinical risk. This is especially serious where the facility depends on integrated systems for identity verification, medication administration, or handoff continuity.

Failure mechanisms are usually indirect but well understood. A ransomware event, network outage, or identity platform disruption can impair access to core services, forcing manual fallback or closing intake altogether. If diversion is delayed, patients may arrive at a site that cannot safely triage them. If it is overused, legitimate demand can be displaced unnecessarily, creating congestion elsewhere and lengthening response times across the care network.

What practitioners often miss: diversion is a resilience signal as much as an operational response. Repeated or prolonged diversion can indicate that backup workflows, manual intake procedures, or interfacility coordination are not robust enough to preserve safe service under degraded conditions. The most visible symptom is often not the cyber event itself, but the inability to make trustworthy accept-or-divert decisions quickly.

Domain and Governance Relevance

Patient diversion matters in healthcare governance because it sits at the point where clinical safety, operational continuity, and external coordination meet. It is not a purely IT concept, but cyber resilience strongly influences whether diversion is needed and how safely it can be executed. When supporting systems fail, the organisation must decide whether it can continue to accept patients with confidence or whether safe handling requires rerouting demand.

For identity and access governance, the relevance is indirect but real: clinicians, dispatchers, transfer coordinators, and partner sites need dependable access to the right systems and the right information at the right time. If access controls, authentication services, or workflow systems fail, the organisation may lose the ability to support intake decisions or confirm patient status. For NHIMG readers, this makes diversion a useful example of how operational resilience failures can cascade into safety decisions even when the original failure is technical.

Governance implication: diversion planning should be owned as a cross-functional resilience responsibility, not left to frontline staff improvisation. The decision rules, coordination paths, and recovery thresholds need to be clear before an incident occurs, because during disruption the organisation is managing uncertainty, not just capacity.

Risk and Threat Considerations

Patient diversion creates material risk when it becomes prolonged, poorly coordinated, or necessary because core clinical and support systems are unavailable. The exposure is not only operational overload, but also delayed care, unsafe intake, and loss of trust in the facility’s ability to receive patients safely.

Failure mechanism: cyber incidents, outages, or identity and communications failures can prevent reliable triage, records access, medication verification, or handoff coordination. When staff cannot confirm patient status or service capability, the facility may need to divert patients to avoid unsafe treatment, but delayed or fragmented diversion decisions can push patients into avoidable queues or misrouted transfers.

Impact: the consequence can be degraded emergency response, extended treatment delays, overburdened partner facilities, and reduced regional surge capacity. In severe cases, diversion can become a symptom of wider service unavailability rather than a temporary traffic-control measure.

Related resources from NHI Mgmt Group

• How should healthcare organisations govern non-human identities that handle patient data?
• Who is accountable when a shared clinical device exposes patient data?
• What breaks when staff use consumer AI with patient data?
• Why do autonomous agents complicate patient privacy governance?