Platform, configuration and devices
Infrastructure, downtime, administration and support
See file 07.
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
C0857Does AuroraMed run on the single-cabinet on-site server with local operation independent of the internet?
Not built. What the pilot has is a stand-in, not the feature. Pilot detail: Cloud-only (D1 + Durable Object); the on-site port is required by spec. REQ-2301 says the system must run on the single-cabinet on-site server with local operation independent of the internet. Its acceptance check: pulling the WAN cable does not stop clinical work.
C0858Does AuroraMed provide downtime mode with read-only emergency data set and paper downtime forms?
REQ-2302 is a top-priority requirement for all three tiers: the system must provide downtime mode with read-only emergency data set and paper downtime forms. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says downtime set opens using cached credentials.
C0859Does AuroraMed provide backup, restore and DR per file 07 tiers?
The infrastructure, downtime, administration and support part of the specification (REQ-2303) says the system must provide backup, restore and DR per file 07 tiers. Designed, not built: there is no code for this in the pilot. Acceptance check: restore drill meets RTO/RPO.
C0860Does AuroraMed provide interface monitoring, application performance monitoring and audit dashboards?
How would it be tested? The specification says dashboards show queue depth. That is the check for REQ-2304: the system must provide interface monitoring, application performance monitoring and audit dashboards. This is on the design side of the line. Nothing in v0.2.0 does it.
C0861Does AuroraMed support scheduled maintenance with signed updates and rollback?
No. The specification describes it, but the pilot does not include it. For reference, REQ-2305 (a top-priority requirement, all three tiers) says the system must support scheduled maintenance with signed updates and rollback. Check: failed update auto-rolls back.
C0862Does AuroraMed provide data migration tooling: MPI cleanup, C-CDA/HL7 replay, chart abstraction, archive viewer?
The system must provide data migration tooling: MPI cleanup, C-CDA/HL7 replay, chart abstraction, archive viewer. That is REQ-2306, a high-priority requirement for all three tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: migration dry run report.
C0863Does AuroraMed provide training environments, proficiency tracking and support portals?
Designed, not built: there is no code for this in the pilot. REQ-2307 says the system must provide training environments, proficiency tracking and support portals. Its acceptance check: training data is synthetic.
C0864Does AuroraMed support printing and label infrastructure (Zebra ZPL, PDF, direct-attached printers)?
REQ-2308 is a top-priority requirement for all three tiers: the system must support printing and label infrastructure (Zebra ZPL, PDF, direct-attached printers). This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says label prints.
C0865Does AuroraMed support peripherals: barcode scanners, badge readers, signature pads, card readers, cameras where allowed?
The infrastructure, downtime, administration and support part of the specification (REQ-2309) says the system must support peripherals: barcode scanners, badge readers, signature pads, card readers, cameras where allowed. No. The specification describes it, but the pilot does not include it. Acceptance check: only allow-listed VID/PID devices enumerate.