Platform, configuration and devices
System-wide platform services
Common services.
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
C0849Does AuroraMed provide a common event bus, job scheduler, notification service, document renderer (PDF/A) and search index, all running on-site?
The pilot covers part of this. The rest is designed, not built. Pilot detail: Event fan-out and alarm-driven timers exist (per-clinic DO); no job scheduler/doc service/generic event store. REQ-3801 says the system must provide a common event bus, job scheduler, notification service, document renderer (PDF/A) and search index, all running on-site. Its acceptance check: each service starts without internet.
C0850Does the global search respect access limits and leave an audit trail?
REQ-3802 is a top-priority requirement for all three tiers: global search must respect the read limiter, minimum necessary, and audit each query with criteria hashed. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says enumeration pattern is detected.
C0851Does AuroraMed provide a generic clinical timeline/event store from which patient-visible access history and audit reports are derived?
The system-wide platform services part of the specification (REQ-3803) says the system must provide a generic clinical timeline/event store from which patient-visible access history and audit reports are derived. Designed, not built: there is no code for this in the pilot. Acceptance check: derived views reconcile with audit.
C0852Does AuroraMed provide time synchronization (NTS/PPS) with skew alarms?
How would it be tested? The specification says clock skew above threshold alerts. That is the check for REQ-3804: the system must provide time synchronization (NTS/PPS) with skew alarms. This is on the design side of the line. Nothing in v0.2.0 does it.