SOAPwareXchangeHL7 Implementation Guide
Here is SOAPware's implementation process for all HL7 interface projects. Following this process will allow interface projects to be expedited most effectively.
Step 1 - Establish the Appropriate License
SOAPware offers 5 turnkey HL7 interface types; Labs, Radiology, Pathology, Transcription (textual), and Demographics. Each type has its own license and technical specs found in the SOAPware Interface Manual.
Once payment has been received, our Sales Team will issue the client the appropriate license for the SOAPwareXchangeHL7 module. An email is automatically generated to inform the client of its availability.
Step 2 Installation
After the order has been processed, a request is also sent to the SOAPware Support Team to contact the client and coordinate an appointment to install/configure the SOAPwareXchangeHL7.
If this is the client’s first HL7 interface, our Support Team will install and configure the SOAPwareXchangeHL7 and provide training on its use. If the client already owns a SOAPwareXchangeHL7 license with another facility, the application is already installed and configured.
In either event, the Support Tech will email the Lab Company’s primary contact as indicated in the quote request form. They will notify the lab contact that the installation has been completed and indicate the IP address and source where HL7 messages may be delivered.
Step 3 - Connectivity
The next step is to establish connectivity for message delivery. The majority of SOAPware clients are locally hosted on their own private networks. SOAPware, Inc. does not maintain a constant connection with their network. As such, the responsibility of establishing connectivity for message delivery is that of the client and sending facility. SOAPware, Inc. does offer connectivity services when none are available through the Lab company for an additional setup and subscription fee. Speak with the SOAPware Sales Team if these services are needed.
The SOAPwareXchangeHL7 can process messages via file-based delivery and/or TCP/IP connection. While it can scan messages from multiple sending facilities via file-based delivery, it can only scan a single port for TCP/IP and therefore may not be available to all sending facilities.
*Some SOAPware users are hosted by the SOAPware Cloud Services (SCS). In this case, the SCS Team will assist in establishing connectivity to the clients VPS.
Step 4 - Validation and Testing
Once connectivity has been established, testing and validation may begin. While this process may begin without direct SOAPware intervention, if preferable the SOAPware Support Team can assist in coordinating a conference call to involve all parties, that is; the client and/or their IT person, the sending facility, the LIS service provider (when applicable) and the SOAPware Support Team to assist in starting the validation process. To schedule a resource from the SOAPware Support Team, you may call directly to 800-455-7627 option 2 or email Support@soapware.com.
In order to expedite the validation process, it is required to have sample messages from the sending facility. The SOAPware tech will assist is processing up to 5 sample messages into the SOAPware EHR for validation by the sending facility. They will also instruct the client in how they can produce reports and/or screen shots out of SOAPware for continued validation by the sending facility.
It is the responsibility of the client and sending facility to conduct all future validation testing once the conference call has concluded. SOAPware, Inc. does not participate in ongoing validation testing; unless specific issues arise in which case the Support Team can be engaged following the method above.
Additional implementation considerations
The SOAPware Support Team is primarily responsible for all HL7 interface implementations. SOAPware, Inc. does not assign a specific resource to an interface project; instead the entire Support Team is able to assist throughout the implementation process.
Rather than attend kick-off calls for interface projects, we advocate a single conference call, if necessary, to be coordinated AFTER connectivity has been established.