Pretend you are the LTACH ops lead and force the long-term acute package to survive questions about who can freeze a ventilator wean protocol, how staffing ratio cuts are timed across units, and which override classes still lack a named owner when the live sample disagrees with the slide.
This seat sits between LTACH tools and the length-of-stay narrative leadership will quote. It asks which wean trees invent completeness the page export never measured, which staffing windows look crisp on a slide and soft in the live sample, and what happens when an ICU stepdown hand-off lands because ownership is incomplete. A green LTACH board does not answer those questions. The review needs the wean map, staffing calendar, override packet, and the named person who can freeze an LTACH path.
Bring exhibits, not slogans
Hand over the LTACH tools in use, ventilator wean protocol draft, staffing ratio cut plan, override packet, last payer-visible length gaps, and one recent case where a delayed freeze hurt an LTACH narrative. Include which LTACH promises still bypass the same review. State the decision: clear the LTACH change, revise specific controls, or hold until a wean owner is named.
Boundaries matter. The LTACH ops lead can challenge untested wean protocols, staffing windows that ignore measured lead time, exceptions without a kill switch, and override paths without logging. Clinical outcome ownership stays with treating clinicians. Spend ceilings belong in the same packet so a quiet dashboard does not hide a brittle LTACH path.
Authority questions worth answering in writing
- Which critical wean class still lacks a tested freeze path with a measured age-out, and who owns the gap?
- What must hold before a staffing ratio cut can promote into a lasting policy, and who can waive it without a written reason?
- How does a declined wean exception become visible to the requester within the claimed window?
- What is the measured time from a failed stepdown finding to a human with freeze authority?
- Which shared override can ship many LTACH changes without failing a single wound care health check?
- Who has authority to pause exceptions or force an LTACH 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 LTACH authority, force one named decision before the next tool change starts.
Leave an LTACH ledger
Run the role in Pingpong with the same exhibits the LTACH team will use. Have the home team answer each objection in writing. The useful output is a short LTACH ledger: approved wean classes, blocked classes, freeze windows, and the person who can call a freeze.
For adjacent LTACH work, pair this seat with a ventilator wean protocol, a staffing ratio cut stress test, an ICU stepdown hand-off, and a wound care backlog stress test. The war-game decisions hub has more seats. Before approving the package, make the LTACH ops lead write the exact freeze and wean check that will decide whether the change continues.