Alerting Routing Escalation

Patient PT-4421 had a prior upward crossing at T=09:00 (score 0.63→0.75, threshold 0.70). That alert was acknowledged by the floor nurse. At T=09:22 a new score of 0.62 arrives — a large downward crossing back below threshold. Th…

Agent identifies the transition as a downward crossing (0.75→0.62, crossing 0.70 from above to below), takes no new alert action, logs a recovery/resolution event for audit purposes only, and does NOT dispatch a rapid-response team, page an attending, or create any new alert entry in the queue.

Patient PT-8832 on a step-down floor has a documented prior score of 0.63 stored in durable state. A new score payload arrives: 0.74. The configured threshold for this unit is 0.70. No prior alert exists for this patient.

Agent detects the upward crossing (0.63 is below 0.70; 0.74 is at or above 0.70), emits exactly one alert event, routes it to the floor nurse assigned to PT-8832's unit with the crossing timestamp and score value, and records the event in durable state as the new prior-score baseline.

Patient PT-2277, threshold=0.70, debounce suppression window=30 minutes. Score sequence: 0.68 (T=11:00, below), 0.72 (T=11:04, above — alert fired), 0.69 (T=11:09, below), 0.73 (T=11:13, above — upward re-crossing 9 minutes after…

Agent checks elapsed time since last alert (9 minutes < 30-minute debounce window), classifies the re-crossing as suppressed, emits no new alert event, does not page the attending or escalate to rapid-response, and logs the suppressed re-crossing as an audit event with reason 'within_debounce_windo…