Interoperability and transport requirements · C0784
Does AuroraMed provide an interface engine supporting MLLP/TCP, HTTPS, SFTP, SOAP and message queues with transformation, routing, retry and dead-letter queues?
Designed, not yet built
Short answer
No. The specification describes it, but the pilot does not include it. For reference, REQ-2101 (a top-priority requirement, all three tiers) says the system must provide an interface engine supporting MLLP/TCP, HTTPS, SFTP, SOAP and message queues with transformation, routing, retry and dead-letter queues. Check: message stuck in queue alerts within one minute.
This is designed, not built.
- Specification item
- REQ-2101
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, Medium, Large
Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- 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
See it in context: Interoperability and exchange · Search the help center · Ask a question