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

Clinical care requirements

Emergency department

Triage, tracking, ED workflows, time metrics.

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

C0718Does AuroraMed provide ED triage using ESI, CTAS or Manchester with site-selected scale?

The emergency department part of the specification (REQ-1001) says the system must provide ED triage using ESI, CTAS or Manchester with site-selected scale. No. The specification describes it, but the pilot does not include it. Acceptance check: triage level required before provider assignment.

Designed, not yet builtPermalink

C0719Does AuroraMed provide an ED tracking board with configurable statuses and time clocks?

How would it be tested? The specification says board hides sensitive data. That is the check for REQ-1002: the system must provide an ED tracking board with configurable statuses and time clocks. Not yet. It is designed in the specification and not built in the pilot.

Designed, not yet builtPermalink

C0720Does AuroraMed support provider-in-triage, fast-track and quick registration?

Designed, not built: there is no code for this in the pilot. For reference, REQ-1003 (a high-priority requirement, the medium and large tiers) says the system must support provider-in-triage, fast-track and quick registration. Check: quick registration flow works.

Designed, not yet builtPermalink

C0721Does AuroraMed provide ED order sets for chest pain, stroke, sepsis, trauma?

The system must provide ED order sets for chest pain, stroke, sepsis, trauma. That is REQ-1004, a high-priority requirement for the medium and large tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: sets are versioned.

Designed, not yet builtPermalink

C0722Does AuroraMed track stroke and STEMI time metrics?

No. The specification describes it, but the pilot does not include it. REQ-1005 says the system must track stroke and STEMI time metrics. Its acceptance check: door-to-needle and door-to-balloon computed.

Designed, not yet builtPermalink

C0723Does AuroraMed ingest EMS prehospital data (NEMSIS/ePCR)?

REQ-1006 is a medium-priority requirement for the medium and large tiers: the system must ingest EMS prehospital data (NEMSIS/ePCR). Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says ePCR data displays as external.

Designed, not yet builtPermalink

C0724Does AuroraMed document EMTALA screening and transfer?

The emergency department part of the specification (REQ-1007) says the system must document EMTALA screening and transfer. Designed, not built: there is no code for this in the pilot. Acceptance check: mSE record required before discharge.

Designed, not yet builtPermalink

C0725Does AuroraMed provide ED throughput analytics?

How would it be tested? The specification says metrics match test data. That is the check for REQ-1008: the system must provide ED throughput analytics. This is on the design side of the line. Nothing in v0.2.0 does it.

Designed, not yet builtPermalink

C0726Does AuroraMed support Brazilian Pronto Atendimento risk classification?

No. The specification describes it, but the pilot does not include it. For reference, REQ-1009 (a lower-priority requirement, all three tiers) says the system must support Brazilian Pronto Atendimento risk classification. Check: manchester-based classification available.

Designed, not yet builtPermalink
See the synthetic-data demo first.Request a demo