How to: |
The inbound channel creates an XML representation of a HL7 inbound message, and an acknowledgement message. The documents are routed to designated folders based on the success or failure results of the transformation and HL7 rule validation.
The New Integration Project dialog box opens, as shown in the following image.
A new Integration Project node called EDIHL7_usr_sample_proj is added to the Integration Explorer.
The Inbound/Outbound Protocols pane appears.
The Define emitter type pane appears.
Note: Passthrough does not emit data from the listener. Instead, it just passes the control here and does nothing.
The Channel Builder pane appears, as shown in the following image.
Note: Process flows should already be built and available in the iIT integration project. They can be found in the EDIHL7_usr_sample_proj directory inside the Flows folder.
For more information, see Process Flow Used for Inbound Processing: HL7 to XML.
Your screen should resemble the following image.
Your screen should resemble the following image.
This section provides an overview of the process flow used for inbound processing: HL7 to XML. This process flow (EDIHL7toXML_pflow_QS_AckAgent_ValidRpt) is already built and available in the iIT integration project. It is located under the EDIHL7_usr_sample_proj node inside the Flows subfolder.
The following image shows the entire inbound process flow, including all of the nodes that are used and their connections.
In this process flow, an HL7 formatted document is read from a validation report file. The XML tags are stripped and the document is written to a directory.
Note: Using a Catch service (com.ibi.agents.XDCatchAgent) in an EDI flow is not supported. The error handling does not work as a result.
After renaming or changing the channel components, your iIT Channel Builder should resemble the following image.
iWay Software |