AuroraMed v0.5.0 is a synthetic-data pilot. See exactly what's built →

Ledger, sync, offline and hardware requirements

Downtime and business continuity

Safe-mode ladder L0-L5.

How to read status labels: In the pilot (v0.5.0, synthetic data) Simulated in the pilot (no real external system) 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?

The pilot covers part of this. The rest is designed, not built. Pilot detail: Safe-mode ladder L0 to L5 with entry conditions. 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.

In the pilot (v0.5.0, synthetic data)Permalink

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. The pilot covers part of this. The rest is designed, not built. Where the code stands: Downtime reports (census, meds, allergies, orders..), sealed and logged; no MAR downtime sheet. Test in the specification: report generated with WAN disconnected.

In the pilot (v0.5.0, synthetic data)Permalink

C0976Does AuroraMed provide back-entry of downtime paper records with reconciliation and audit flag?

The pilot covers part of this. The rest is designed, not built. In the pilot: Back-entry with reconciliation and audit flag. 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.

In the pilot (v0.5.0, synthetic data)Permalink
See the synthetic-data demo first.Request a demo