Stress-test an outbreak terminal clean by proving that each hold window and restore rule can place terminal-clean rooms inside the planned isolation lane, survive override pressure, and avoid trapping EVS and bed teams inside a green outbreak slide that hides long-lived soft holds.
Outbreak terminal cleans often list a room checklist while leaving restore behavior, override authority, and abort ownership implicit. Those edges decide whether a late isolation room stays inside the outbreak packet or leaves a broken bed path live under peak volume. The exercise should follow actual isolation inventories, unit maps, and escalation paths rather than a clean infection board.
Map the terminal-clean holds
List every outbreak terminal-clean class with its response window, waive rule, override behavior, owners, and notification channels. Mark paths that cannot reverse without a manual amendment. Attach the last three outbreak terminal-clean incidents with raw timelines and any waivers. Include the source of truth for open isolation counts during the observation window.
- A minority isolation class keeps a side-channel while the aggregate outbreak dashboard stays green.
- A restore has already left an EVS desk without a trusted terminal-clean state.
- The primary outbreak export lags beyond the planned observation window.
- An operator skips a terminal-clean gate because a bed cutoff is near.
- Automated and human divert messages collide under the new clean rule.
- Infection control and EVS claim different freeze owners for the same isolation class.
For each drill, identify detection time, unit impact, containment, and the authority to force an outbreak terminal-clean rollback. Require commands and dashboard links in the runbook.
Name detect and restore owners
Name detect, hold, divert, abort, and restore owners with exit conditions. Write the point after which a stuck terminal clean would require a different bed plan, then review whether that action is still permitted. Capture maximum acceptable dwell in measurable units, including which room classes are excluded from the terminal-clean path and why.
Run the package in Pingpong with infection control, EVS, bed management, and nursing seats. Ask infection control which patient decision becomes unsafe first if terminal cleans still stick after the claimed window. Ask EVS whether macros can absorb a forced override. Ask owners to show the exact outbreak version or export used as the exit condition.
Related reviews include an outbreak response ladder, the infection control lead seat, the EVS ops lead seat, and a room-turn SLA. Browse the war-game decisions hub for adjacent controls.
Authorize the published terminal-clean path only after a timed drill restores usable hold hygiene inside the documented budget without an undocumented manual step.