Interoperability and transport requirements
Interoperability and exchange
Standards-based exchange (details in file 04).
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
C0784Does AuroraMed provide an interface engine supporting MLLP/TCP, HTTPS, SFTP, SOAP and message queues with transformation, routing, retry and dead-letter queues?
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.
C0785Does AuroraMed implement the HL7 v2 message families and segments in file 04 with configurable profiles?
The system must implement the HL7 v2 message families and segments in file 04 with configurable profiles. That is REQ-2102, a top-priority requirement for all three tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: conformance test suite passes for each family.
C0786Does 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, not built: there is no code for this in the pilot. REQ-2103 says the system must implement FHIR R4 (4.0.1) REST server, search, operations, US Core 6.1.0 profiles and SMART App Launch 2.0.0. Its acceptance check: inferno test kit results (to be verified).
C0787Does AuroraMed implement FHIR Bulk Data export subject to quorum approval and limiter rules?
REQ-2104 is a high-priority requirement for the medium and large tiers: the system must implement FHIR Bulk Data export subject to quorum approval and limiter rules. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says export cannot start without approved bulk workflow.
C0788Does AuroraMed create, receive and reconcile C-CDA R2.1 documents and support EHI export?
The interoperability and exchange part of the specification (REQ-2105) says the system must create, receive and reconcile C-CDA R2.1 documents and support EHI export. No. The specification describes it, but the pilot does not include it. Acceptance check: c-CDA scorecard results stored.
C0789Does AuroraMed support IHE XDS.b, XCA, XCPD, PIX/PDQ, ATNA, MHD profiles?
How would it be tested? The specification says iHE test tool results. That is the check for REQ-2106: the system must support IHE XDS.b, XCA, XCPD, PIX/PDQ, ATNA, MHD profiles. Not yet. It is designed in the specification and not built in the pilot.
C0790Does AuroraMed support TEFCA (QHIN participant/subparticipant) using document query and Facilitated FHIR with UDAP security and Exchange Purpose codes?
Designed, not built: there is no code for this in the pilot. For reference, REQ-2107 (a medium-priority requirement, the medium and large tiers) says the system must support TEFCA (QHIN participant/subparticipant) using document query and Facilitated FHIR with UDAP security and Exchange Purpose codes. Check: sandbox exchange with a QHIN test environment.
C0791Does AuroraMed support Carequality and CommonWell connectivity through a partner or direct implementation?
The system must support Carequality and CommonWell connectivity through a partner or direct implementation. That is REQ-2108, a medium-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: patient discovery test passes.
C0792Does AuroraMed support Direct Secure Messaging?
No. The specification describes it, but the pilot does not include it. REQ-2109 says the system must support Direct Secure Messaging. Its acceptance check: direct message sent between test addresses.
C0793Does AuroraMed support X12 and NCPDP transactions in file 04?
REQ-2110 is a top-priority requirement for the medium and large tiers: the system must support X12 and NCPDP transactions in file 04. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says conformance test.
C0794Does AuroraMed support DICOM, IEEE 11073, POCT1, ASTM device interfaces?
The interoperability and exchange part of the specification (REQ-2111) says the system must support DICOM, IEEE 11073, POCT1, ASTM device interfaces. Designed, not built: there is no code for this in the pilot. Acceptance check: device certification lab results.
C0795Does AuroraMed provide LatAm interfaces: RNDS (BR), IHCE/RDA (CO), NOM-024 (MX), RENIPRESS/SIS (PE), FONASA (CL), Receta electrónica (AR) as adapters?
How would it be tested? The specification says adapter pass-through test. That is the check for REQ-2112: the system must provide LatAm interfaces: RNDS (BR), IHCE/RDA (CO), NOM-024 (MX), RENIPRESS/SIS (PE), FONASA (CL), Receta electrónica (AR) as adapters. This is on the design side of the line. Nothing in v0.2.0 does it.
C0796Does AuroraMed provide conformance-tooling hooks (validators, ONC/Inferno, HL7 validator) in CI?
No. The specification describes it, but the pilot does not include it. For reference, REQ-2113 (a high-priority requirement, the medium and large tiers) says the system must provide conformance-tooling hooks (validators, ONC/Inferno, HL7 validator) in CI. Check: build fails on conformance regressions.