Pretend you are the infection control lead and force the infection package to survive questions about who can freeze an outbreak response ladder, how isolation delays are timed across units, and which surveillance classes still lack a named owner when the live sample disagrees with the slide.
This seat sits between infection tools and the safety narrative leadership will quote. It asks which outbreak trees invent completeness the page export never measured, which isolation windows look crisp on a slide and soft in the live sample, and what happens when a surveillance exception lands because ownership is incomplete. A green infection board does not answer those questions. The review needs the outbreak map, isolation calendar, surveillance packet, and the named person who can freeze an infection path.
Load the seat with evidence
Hand over the infection tools in use, outbreak ladder draft, isolation plan, surveillance packet, last regulator-visible infection gaps, and one recent case where a delayed isolation hurt an infection narrative. Include which infection promises still bypass the same review. State the decision: clear the infection change, revise specific controls, or hold until an outbreak owner is named.
Boundaries matter. The infection control lead can challenge untested outbreak ladders, isolation windows that ignore measured lead time, exceptions without a kill switch, and override paths without logging. Clinical outcome ownership stays with attending clinicians. Spend ceilings belong in the same packet so a quiet dashboard does not hide a brittle infection path.
Force answers that name owners
- Which critical isolation class still lacks a tested response path with a measured age-out, and who owns the gap?
- What must hold before an outbreak response ladder can promote into a lasting rule, and who can waive it without a written reason?
- How does a declined isolation exception become visible to the requester within the claimed window?
- What is the measured time from a failed surveillance finding to a human with freeze authority?
- Which shared override can ship many infection changes without failing a single infection health check?
- Who has authority to pause exceptions or force an infection rollback at week end without waiting for the system owner?
Require observed, inferred, or unknown labels. Observed claims need a source. Unknowns become owners and due dates. When two teams claim the same infection authority, force one named decision before the next tool change starts.
Convert objections into an infection ledger
Run the role in Pingpong with the same exhibits the infection team will use. Have the home team answer each objection in writing. The useful output is a short infection ledger: approved isolation classes, blocked classes, outbreak windows, and the person who can call a freeze.
For adjacent infection work, pair this seat with an outbreak response ladder, the care management lead seat, the quality ops lead seat, and a discharge planning backlog stress test. The war-game decisions hub has more seats. Before approving the package, make the infection control lead write the exact freeze and outbreak check that will decide whether the change continues.