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

Platform, configuration and devices

Mobile, bedside and point-of-care

Tablets and handhelds.

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

C0866Does AuroraMed provide sealed tablet terminals as thin clients displaying a server-rendered live feed with no persistent data?

The mobile, bedside and point-of-care part of the specification (REQ-2351) says the system must provide sealed tablet terminals as thin clients displaying a server-rendered live feed with no persistent data. The pilot covers part of this. The rest is designed, not built. In the pilot: Electron client and web build exist; not a sealed thin client; no mobile push. Acceptance check: power-cycled terminal contains no PHI.

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

C0867Does AuroraMed provide bedside barcode scanning and mobile documentation on approved devices with server-rendered display?

How would it be tested? The specification says scan resolves the patient. That is the check for REQ-2352: the system must provide bedside barcode scanning and mobile documentation on approved devices with server-rendered display. This is on the design side of the line. Nothing in v0.2.0 does it.

Designed, not yet builtPermalink

C0868Does AuroraMed support offline-first capture only through the on-site server and local wired/wireless LAN; no PHI is stored on mobile devices?

No. The specification describes it, but the pilot does not include it. For reference, REQ-2353 (a top-priority requirement, all three tiers) says the system must support offline-first capture only through the on-site server and local wired/wireless LAN; no PHI is stored on mobile devices. Check: device loss exposes no PHI.

Designed, not yet builtPermalink

C0869Does AuroraMed support mobile secure messaging and push notifications through the system-wide messaging service?

The system must support mobile secure messaging and push notifications through the system-wide messaging service. That is REQ-2354, a top-priority requirement for all three tiers. The pilot covers part of this. The rest is designed, not built. Where the code stands: Electron client and web build exist; not a sealed thin client; no mobile push. Test in the specification: push contains no PHI beyond policy.

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