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

Interoperability and transport requirements

Transport orders (Elyria integration)

Only integration with Elyria Drone Shipping.

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

C0797Can a clinic send a transport order to Elyria Drone Shipping from a terminal?

The transport orders (elyria integration) part of the specification (REQ-3701) says clinics must be able to create transport orders from a terminal for Elyria Drone Shipping, a separate company, through a defined external interface. No. The specification describes it, but the pilot does not include it. Acceptance check: order created, sent, acknowledged; Elyria has no access to the clinic chart.

Designed, not yet builtPermalink

C0798What patient information would a transport order to Elyria carry?

How would it be tested? The specification says payload schema linter blocks PHI fields not on allow-list. That is the check for REQ-3702: the order must carry cargo class, origin, destination, requested time and handling requirements only; no PHI beyond the minimum needed (for example a specimen accession number) unless a BAA and profile allow. Not yet. It is designed in the specification and not built in the pilot.

Designed, not yet builtPermalink

C0799Would pickup, handoff, delivery and incident events for a transport order be audited?

Designed, not built: there is no code for this in the pilot. For reference, REQ-3703 (a high-priority requirement, all three tiers) says chain-of-custody events (pickup, handoff, delivery, temperature excursion, incident) must be audit events and shown on the order. Check: every custody event has a signature and audit record.

Designed, not yet builtPermalink

C0800When could specimens or blood be sent through the Elyria integration?

Specimens and blood must be enabled only when Elyria certified cold-chain capability is configured. That is REQ-3704, a high-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: cargo class disabled by default.

Designed, not yet builtPermalink

C0801How would results from transported specimens get back to the clinic?

No. The specification describes it, but the pilot does not include it. REQ-3705 says results must return to the clinic through the normal results interface. Its acceptance check: result attaches to the original order.

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