Code and clinical alert notifications

C0990Does AuroraMed support alert classes CODE, CLINICAL-CRITICAL (lab, imaging, blood), PING-EMERGENCY, PING-URGENT and PING-STANDARD with defined priority levels, ack rules and escalation?

It is one of the few requirements the pilot meets at MVP scope; nothing has touched real data. Pilot detail: Classes, default 22-template code library, alert audit events present. For reference, REQ-4201 (a top-priority requirement, all three tiers) says the system must support alert classes CODE, CLINICAL-CRITICAL (lab, imaging, blood), PING-EMERGENCY, PING-URGENT and PING-STANDARD with defined priority levels, ack rules and escalation. Check: each class has a policy record with timers.

C0991Can a facility define what its own codes mean?

Code alerts must be configurable per facility: name, color, meaning, script, audience, sound, lockdown and integration actions. No code meaning must be hard-coded as universal. That is REQ-4202, a top-priority requirement for all three tiers. The pilot covers part of this. The rest is designed, not built. Where the code stands: Editable templates with propose/approve; no per-facility scripts/integration actions. Test in the specification: two facilities can define Code Silver differently and both work.

C0992Does AuroraMed ship a default code library (Code Blue, Red, Pink, Purple, Silver, Active Shooter/Imminent Threat, Gray, Black, Orange, Yellow, Green, White, Triage, Amber, Rapid Response, Stroke, STEMI, Trauma, Sepsis, Massive Transfusion) as editable templates with no asserted universal meaning?

It is one of the few requirements the pilot meets at MVP scope; nothing has touched real data. In the pilot: Classes, default 22-template code library, alert audit events present. REQ-4203 says the system must ship a default code library (Code Blue, Red, Pink, Purple, Silver, Active Shooter/Imminent Threat, Gray, Black, Orange, Yellow, Green, White, Triage, Amber, Rapid Response, Stroke, STEMI, Trauma, Sepsis, Massive Transfusion) as editable templates with no asserted universal meaning. Its acceptance check: templates can be edited and cloned; UI shows a "confirm local meaning" notice and first activation of a template in a facility requires review and sign-off by two authorized roles.

C0993How does a two-person cancel of an imminent-threat alert work in the spec?

REQ-4204 is a top-priority requirement for all three tiers: Imminent Threat / Active Shooter alerts must have the highest priority, override all DND and screen locks, support silent (non-audible) mode, and be cancellable only by two authorized roles. The pilot covers part of this. The rest is designed, not built. What v0.2.0 does today: P0 full-screen presentation exists; no overhead/door/fire integration. To verify it, the specification says cancel with one role fails.

C0994Do code alerts work when the internet or cloud is down?

The code and clinical alert notifications part of the specification (REQ-4205) says Code alerts must work with the WAN and cloud unavailable, using only the on-site server and local network. Not built. What the pilot has is a stand-in, not the feature. Pilot detail: Runs on Cloudflare Durable Object, not on-site; fails the WAN-down requirement. Acceptance check: cut WAN: Code Blue delivered to all terminals.

C0995What happens if a critical result is not acknowledged?

How would it be tested? The specification says simulated no-ack escalates. That is the check for REQ-4206: Critical lab/imaging/blood alerts must reach the responsible clinician with acknowledgment tracking and escalation to an alternate if not acknowledged within the configured time (still an open decision). The pilot covers part of this. The rest is designed, not built. Where the code stands: Critical result alert with ack + escalation works; 422 no_recipients if patient has no care assignment. Parts of it are explicitly marked as open in the specification.

C0996Does alert delivery survive failures, and which channels does it fall back to?

The pilot covers part of this. The rest is designed, not built. In the pilot: Store-and-forward with late flag, dedup; ordering/at-least-once under failure not load-tested. For reference, REQ-4207 (a top-priority requirement, the medium and large tiers) says Alert delivery must be at-least-once with de-duplication, ordered per alert, with delivery receipts, and must fall back across channels (terminal, tablet, pager/radio/phone gateway where installed). Check: kill one channel; alert arrives via next.

C0997Do pager and SMS alerts contain patient information?

Alert payloads to non-terminal channels (pager, SMS) must contain no PHI by default. That is REQ-4208, a top-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: payload linter passes.

C0998Is every alert action audited?

It is one of the few requirements the pilot meets at MVP scope; nothing has touched real data. Pilot detail: Classes, default 22-template code library, alert audit events present. REQ-4209 says Alert actions must be audit events: send, delivered, read, ack, escalate, cancel, all-clear. Its acceptance check: timeline reconstructs a drill.

C0999Does AuroraMed support code drills that reuse the alert path with a DRILL flag and record timings?

REQ-4210 is a high-priority requirement for all three tiers: the system must support code drills that reuse the alert path with a DRILL flag and record timings. The pilot covers part of this. The rest is designed, not built. Where the code stands: Drill flag and silent mode exist; no drill session records/schedule. To verify it, the specification says drill does not trigger lockdown integrations unless selected.

C1000Can alerts be acknowledged with one touch on a tablet?

The code and clinical alert notifications part of the specification (REQ-4211) says Alert acknowledgment on sealed tablets must be one-touch with accessibility support (large targets, audible, vibration where the device has it). The pilot covers part of this. The rest is designed, not built. In the pilot: One-touch ack exists in UI; not tested on sealed tablets; 36 px targets. Acceptance check: usability test with gloved hands.