Ledger, sync, offline and hardware requirements
Downtime and business continuity
Safe-mode ladder L0-L5.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0974Does AuroraMed provide the safe-mode ladder L0 normal through L5 paper/downtime, with defined entry conditions and UI banners?
No. The specification describes it, but the pilot does not include it. For reference, REQ-4801 (a top-priority requirement, all three tiers) says the system must provide the safe-mode ladder L0 normal through L5 paper/downtime, with defined entry conditions and UI banners. Check: each level transition produces an alert and audit.
C0975Does AuroraMed generate downtime reports (census, MAR, orders, allergies, medications, problem list, code status, contact list) at schedule and on demand, to the directly attached printer?
The system must generate downtime reports (census, MAR, orders, allergies, medications, problem list, code status, contact list) at schedule and on demand, to the directly attached printer. That is REQ-4802, a top-priority requirement for all three tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: report generated with WAN disconnected.
C0976Does AuroraMed provide back-entry of downtime paper records with reconciliation and audit flag?
Designed, not built: there is no code for this in the pilot. REQ-4803 says the system must provide back-entry of downtime paper records with reconciliation and audit flag. Its acceptance check: back-entered entries carry original time and entry time.