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

Clinical care requirements

Orders and CPOE

Order entry, sets, communication, tracking, prior authorization.

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

C0647Does AuroraMed provide CPOE for medications, labs, imaging, procedures, referrals, nursing, diet, therapy, DME, blood and isolation?

Not built. What the pilot has is a stand-in, not the feature. Pilot detail: Order entries are text plus priority, T5 only; no catalog, order sets, status machine or CDS. REQ-0501 says the system must provide CPOE for medications, labs, imaging, procedures, referrals, nursing, diet, therapy, DME, blood and isolation. Its acceptance check: each order type has a registry definition and state machine.

Designed, not yet builtPermalink

C0648Can any clinician place any kind of order, or is ordering limited by role and licence?

REQ-0502 is a top-priority requirement for all three tiers: the system must require ordering authority by role and licensure and must restrict order types per role. The pilot covers part of this. The rest is designed, not built. Where the code stands: Basic MVP equivalent: patient banner/summary, vitals/note/I&O entries, stay/day/hour timeline, care assignment, results view; free-text, not coded or templated. To verify it, the specification says unauthorized order type is not offered.

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

C0649Does AuroraMed support order sets, panels, quick orders and preference lists with versioning?

The orders and cpoe part of the specification (REQ-0503) says the system must support order sets, panels, quick orders and preference lists with versioning. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. Acceptance check: order set edits create a new version.

Coming (Wave 2, rolling out)Permalink

C0650Does AuroraMed support ask-at-order-entry questions?

How would it be tested? The specification says required questions block signature until answered. That is the check for REQ-0504: the system must support ask-at-order-entry questions. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet.

Coming (Wave 2, rolling out)Permalink

C0651Does AuroraMed support verbal/telephone orders with read-back and cosign deadlines?

Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. For reference, REQ-0505 (a top-priority requirement, all three tiers) says the system must support verbal/telephone orders with read-back and cosign deadlines. Check: unsigned verbal order escalates after deadline (still an open decision). Parts of it are explicitly marked as open in the specification.

Coming (Wave 2, rolling out)Permalink

C0652Does AuroraMed support protocol/standing/pended/future/recurring orders?

The system must support protocol/standing/pended/future/recurring orders. That is REQ-0506, a high-priority requirement for all three tiers. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. Test in the specification: pended order cannot execute.

Coming (Wave 2, rolling out)Permalink

C0653Does AuroraMed track order status from ordered to final with a defined state machine?

Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. REQ-0507 says the system must track order status from ordered to final with a defined state machine. Its acceptance check: illegal transitions refused.

Coming (Wave 2, rolling out)Permalink

C0654Does AuroraMed emit and consume HL7 v2 orders/results and FHIR ServiceRequest/Task/DiagnosticReport?

REQ-0508 is a top-priority requirement for all three tiers: the system must emit and consume HL7 v2 orders/results and FHIR ServiceRequest/Task/DiagnosticReport. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. To verify it, the specification says interface tests pass.

Coming (Wave 2, rolling out)Permalink

C0655Does AuroraMed check duplicate orders, medical necessity and authorization requirements?

The orders and cpoe part of the specification (REQ-0509) says the system must check duplicate orders, medical necessity and authorization requirements. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. Acceptance check: duplicate warns with links to existing order.

Coming (Wave 2, rolling out)Permalink

C0656Does AuroraMed show appropriate-use criteria for advanced imaging where required?

How would it be tested? The specification says aUC consultation id stored with order. That is the check for REQ-0510: the system must show appropriate-use criteria for advanced imaging where required. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet.

Coming (Wave 2, rolling out)Permalink

C0657Does AuroraMed optionally display cost of care at order entry?

Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. For reference, REQ-0511 (a lower-priority requirement, the large tier only) says the system must optionally display cost of care at order entry. Check: displayed price matches charge master.

Coming (Wave 2, rolling out)Permalink

C0658Does AuroraMed reconcile orders at transfer, admission and discharge?

The system must reconcile orders at transfer, admission and discharge. That is REQ-0512, a top-priority requirement for the medium and large tiers. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. Test in the specification: discharge reconciliation blocks discharge orders if unresolved (per site policy).

Coming (Wave 2, rolling out)Permalink

C0659Does AuroraMed verify consent before blood product orders?

Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. REQ-0513 says the system must verify consent before blood product orders. Its acceptance check: missing transfusion consent blocks non-emergency order.

Coming (Wave 2, rolling out)Permalink

C0660Does AuroraMed support referral/consult orders with closed-loop tracking?

REQ-0514 is a high-priority requirement for all three tiers: the system must support referral/consult orders with closed-loop tracking. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. To verify it, the specification says unclosed referral appears on worklist.

Coming (Wave 2, rolling out)Permalink

C0661Does AuroraMed support DME/home-health/SNF orders with face-to-face documentation?

The orders and cpoe part of the specification (REQ-0515) says the system must support DME/home-health/SNF orders with face-to-face documentation. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. Acceptance check: f2F date required.

Coming (Wave 2, rolling out)Permalink

C0662Does AuroraMed support electronic lab ordering to external networks and bi-directional interfaces?

How would it be tested? The specification says order sent and result matched by accession. That is the check for REQ-0516: the system must support electronic lab ordering to external networks and bi-directional interfaces. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet.

Coming (Wave 2, rolling out)Permalink

C0663Does AuroraMed support electronic prior authorization (X12 278, Da Vinci PAS, NCPDP ePA) and real-time prescription benefit?

Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. For reference, REQ-0517 (a high-priority requirement, the medium and large tiers) says the system must support electronic prior authorization (X12 278, Da Vinci PAS, NCPDP ePA) and real-time prescription benefit. Check: pA request and response linked to order.

Coming (Wave 2, rolling out)Permalink

C0664Does AuroraMed provide order entry on approved mobile devices?

The system must provide order entry on approved mobile devices. That is REQ-0518, a medium-priority requirement for the medium and large tiers. Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. Test in the specification: mobile enforces same authorization.

Coming (Wave 2, rolling out)Permalink

C0665Does AuroraMed mark AI-generated order suggestions as drafts requiring explicit signature?

Coming, not available: Wave 2 is still being built, and this item has no test evidence yet. REQ-0519 says the system must mark AI-generated order suggestions as drafts requiring explicit signature. Its acceptance check: aI draft cannot be signed automatically.

Coming (Wave 2, rolling out)Permalink
See the synthetic-data demo first.Request a demo