Hospital wards must respond quickly to patient safety incidents, yet accumulated alerts often fail to lead to resolution. This study defines this breakdown as alert leakage, focusing on disconnections after an alert is issued—acknowledgement, assignment of responsibility, action execution, and closure. We propose five leakage types and structure ward situation awareness–based information system interaction as a stepwise pipeline from patient monitoring setup and patient–sensor linkage to event capture, state interpretation, priority ordering, responsibility designation, acknowledgement and confirmation, action execution, closure or unresolved-state retention, and switching under delay. For each stage, we map likely leakage points and propose minimal interaction design mechanisms, including standardized state levels with concise rationale and check items, top-incident emphasis with bundled summaries, explicit primary/backup/escalation paths, persistent unresolved-state visibility, a minimal action sequence (verify–contact–intervene–document), and clear closure conditions. The system is illustrated through infusion anomaly and fall scenarios and refined via expert group discussion with nurses, developers, and UX specialists. The contribution is a design-oriented information system interaction framework that secures end-to-end continuity from alert to closure within ward workflows.