Blood bank operations

War-game a crossmatch SLA before soft clocks govern every request

War-game a crossmatch SLA by proving each request lane has a named owner, a measured age-out, and a reverse path before draft clocks start governing every blood bank request.

Crossmatch SLAs fail when "compatible" means a status without a decision artifact, when teams dual-count a draft clock as both aspirational and live, and when urgent request families still pin to one thin bench because the lane inventory is incomplete. The review needs one written inventory of crossmatch lanes, one owner who can deny a risky shortcut, and a documented consequence when a failed clock ages past the deadline.

Name the crossmatch packet in writing

State which request classes the SLA covers, the effective date, which clock lanes change, how versions are stored, and what happens to requests already in flight. Name the services that feel it first and the safety promises that depend on coherent crossmatch handling. If the memo mixes a crossmatch SLA with a rare-unit shortage and a transfusion reaction drill, split them.

Write the decision you will make if the war game finds nothing new. Also write the reverse criteria: the missed lane, urgency gap, or patient deadline that would force a crossmatch SLA rollback within a stated window.

Crossmatch failures to force early

  1. An urgent request class stays soft while the aggregate blood bank dashboard stays green.
  2. Two teams claim the same lane ownership and neither can force a freeze at week end.
  3. A restore has already left a request without a trusted clock state.
  4. The primary crossmatch export lags beyond the planned observation window.
  5. An operator skips a clock gate because an OR cutoff is near.
  6. Compatibility claims lack a stored exhibit at release time.

For each failure, require detection time, service impact, containment, and the authority to force a crossmatch SLA rollback. Commands and export links belong in the runbook.

Seat the blood bank and OR chairs

Feed Pingpong the SLA memo, the lane exhibits, and seating briefs for blood bank ops, OR, anesthesia, and quality. First pass steelmans the SLA. Later passes attack from those seats. Final pass turns surviving objections into phased lane rules, mitigations, or a changed recommendation. Agreement across passes is not proof. Keep the objections that still have evidence gaps.

Pair with the blood bank ops lead seat, a rare-unit shortage stress test, a transfusion reaction drill, and the lab ops lead seat. More operating decisions live in the war-game decisions hub.

Ship the SLA only when approved and blocked clock labels can be reproduced from stored crossmatch exports without a verbal override.