Transport Method Options

• S3 - preferred (this is the preferred option in most situations)

• STFP

While the AIMS ETOR Intermediary can support other transport methods, S3 and STFP are strongly preferred given functionality, resiliency, and versatility.

Network/Firewall Requirements

• For those using S3 as a transport method, the firewall needs to allows for HTTPS in/out

• For those using SFTP as a transport method, the firewall/network needs to allow for SFTP in/out

Network/firewall components are directly linked to PHL transport methods.

File Format Options

• HL7 v2.x - most preferred (this is the preferred option in most situations)

• FHIR

• XML

• CSV - least preferred

Any of the outlined file formats are compatible with the ETOR intermediary solution as long as the LIMS 1) is capable of importing sufficient order information and 2) contains a field for the data elements necessary to create a result.

Data FieldsMust have the necessary data fields of the test in scope (or the ability to create those data fields).Field Requirements and Recommendations

The necessary and recommended data fields for the in-scope test(s) are defined here: Insert Link

This allows for the creation of orders and results in the LIMS.

LIMS CapabilitiesCapability Requirements

• Able to import sufficient information to create an order within the system.

• Able to link order and results using a unique ID/token.

• Able to export sufficient information to create a result within the system.

• Has a protocol for handling (e.g., consuming, reviewing) of error messages.

Integration EngineNone

No integration engine required.

APHL recommends the LIMS not use and/or not have relevant data flow through.

Note: No integration engine should be needed if the LIMS can import/export data. If the LIMS cannot import/export data, APHL will work with the LIMS representative to communicate updates needed.

Out of Scope Related Components

APHL developing the code to allow data to be imported/exported from the LIMS. (can write some script but not everything)

APHL is able to assist in conversations with PHL LIMS representatives to make these changes.

Transport Method Options

1. RESTful - preferred (this is the preferred option in most situations)

2. FHIR

3. MLLP / VPN - least preferred

While the AIMS ETOR Intermediary can support other transport methods, RESTful, FHIR and MLLP / VPN are preferred given functionality, resiliency, and versatility.

Network/Firewall Requirements

• For those using RESTful or FHIR as a transport method:

  • Able to enable AIMS RESTful service for orders receival.

  • Able to enable HCO RESTful service for result delivery.

  • Able to authenticate RESTful connection

• For those using MLLP/VPN, the network/firewall must be able to establish VPN from AWS to VPN/server to VPN/firewall.

Network/firewall components are directly linked to PHL transport methods.

File Format Options

• HL7 v2.x - most preferred (this is the preferred option in most situations)

• FHIR

• XML

• CSV - least preferred

Any of the outlined file formats are compatible with the ETOR intermediary solution as long as the EHR 1) is capable of importing sufficient order information and 2) contains a field for the data elements necessary to create a result.

Data FieldsMust have the necessary data fields of the test in scope (or the ability to create those data fields).Field Requirements and Recommendations

The necessary and recommended data fields for the in-scope test(s) are defined here: Insert Link

This allows for the creation of orders and results in the EHR.

EHR CapabilitiesCapability Requirements

• Able to export sufficient information to create an order.

• Able to link order and results using a unique ID/token.

• Able to import results.

• Has established processes for test data collection and data entry into the EHR with which staff comply, ensuring data of high quality.

• Able to identify (i.e., include in the order) the appropriate PHL to receive the test order (should be included in the ordeorder

• Has ability to require specific data fields be populated (for data elements required by the test in scope) - preferred

Integration EngineNone

No integration engine required.

APHL recommends the LIMS not use and/or not have relevant data flow through.

Note: No integration engine should be needed if the LIMS can import/export data. If the LIMS cannot import/export data, APHL will work with the LIMS representative to communicate updates needed.

Out of Scope Related Components

APHL developing the code to make changes to the EHR.

APHL is able to assist in conversations with HCO EHR representatives to make these changes.