Requirements explained (from the specification)
Interoperability and transport requirements
Standards-based exchange and the optional transport-order interface.
Interoperability and exchange (13)
Standards-based exchange (details in file 04).
- Does AuroraMed provide an interface engine supporting MLLP/TCP, HTTPS, SFTP, SOAP and message queues with transformation, routing, retry and… Designed
- Does AuroraMed implement the HL7 v2 message families and segments in file 04 with configurable profiles? Designed
- Does AuroraMed implement FHIR R4 (4.0.1) REST server, search, operations, US Core 6.1.0 profiles and SMART App Launch 2.0.0? Designed
- Does AuroraMed implement FHIR Bulk Data export subject to quorum approval and limiter rules? Designed
- Does AuroraMed create, receive and reconcile C-CDA R2.1 documents and support EHI export? Designed
- Does AuroraMed support IHE XDS.b, XCA, XCPD, PIX/PDQ, ATNA, MHD profiles? Designed
All 13 answers in this section →
Transport orders (Elyria integration) (5)
Only integration with Elyria Drone Shipping.
- Can a clinic send a transport order to Elyria Drone Shipping from a terminal? Designed
- What patient information would a transport order to Elyria carry? Designed
- Would pickup, handoff, delivery and incident events for a transport order be audited? Designed
- When could specimens or blood be sent through the Elyria integration? Designed
- How would results from transported specimens get back to the clinic? Designed