Scheduling interfaces provide the necessary data to create patient appointments within external systems. One use for this type of channel is PACS systems. When doing diagnostic imaging in the office there are often times when a scheduled appointment in iSalus needs to be available in the worklist for the imaging software. This may also be helpful for non-integrated appointment reminders.
Definition & Diagram
SIU | Scheduling Information Unsolicited
These message types are used to transfer scheduling data to external systems. We do not accepts SIU messages.
Claims interfaces are established to assist in transferring financial data from one software to another. The common use case for these types of interfaces is when a facility/device creates claims on your behalf. These are instances such as PACS systems, Clinitek devices, etc. In these scenarios, claims are being created within iSalus programmatically. The outbound DFT channels can be established for practice's working with partners who require these files to create claims externally or do financial reporting.
Definitions & Diagrams
DFT | Detail Financial Transaction
Using the international standard of HL7. DFT message types are sent and/or received to create electronic claims. If using an Outbound DFT interface you may need the assistance of a Demographics (ADT) interface. This channel would be used to create a patient within the external system by providing new patient demographics data and updates to existing records.
This article describes the flow of information for a bidirectional orders and results interface. This is the most common interface iSalus supports. Establishing an interface such as this substantially increases a practice's clinical efficiency. This removes the need to allocate ancillary staff time to index received results and transcribe the values. Another added value of interfaced results is the ability to set up the Data Trends for encounter notes.
Definitions & Diagrams
ORM | Order Entry Message
Order entry messages are created in the application by placing orders in the Order Entry chart tab. These messages are not sent until a user prints the requisition. This message is then sent to the interface engine to be translated and sent to the external system using the established connection method.
ORU | Observation Result
Result messages are initially received by the interface engine via the established connection method. Once the message is sent to the practice the message will be displayed in the My Task - Results section of the EMR. 
NOTE: Result messages are processed by the database every other even minute (8:02, 8:04, etc.).
During the discovery phase of a new interface, there will need to be a decision made regarding the network connectivity of the two parties. All HL7 interfaces will use one of the following methods. This article describes the different methods as well as the information required from the vendor to complete the corresponding connection.
VPN | Virtual Private Network
A VPN to our communication servers can be established with the third party to transfer various HL7 files. This is the preferred connection method for us. The benefit of a VPN is the ability to receive an ACK, or Acknowledgement Message. This lets us know if the file successfully transfers to their server.
Requirements
- Third-Party Provides VPN Worksheet
- Uses TCP/IP protocols
- Private Key exchange
SFTP | Secure File Transfer Protocol
The SFTP connection method is useful due to its simplicity. The downfall, however, is the inability to receive confirmation that the HL7 file has been received. Establishing connectivity to an SFTP server does not require involvement from the data center, Expedient, unlike the VPN method.
Requirements
- Third-Party Hosts SFTP Server
- Affiliate provides:
- Destination (Domain/IP)
- User Name
- Password
- Directory Location (if other than root)
- Port (if other than 22)
