Use the HL7 nodes to develop message flows that connect to clinical applications.
You can connect your clinical applications by using the HL7DFDLInput and HL7DFDLOutput nodes (if you are using the DFDL message model) or the GenericHL7Input and GenericHL7Output nodes (if you are using the HL7v25P message set). Use these nodes with the built-in nodes provided in WebSphere® Message Broker to develop message flow applications that meet your requirements. For more information about developing message flow applications from scratch, see Developing message flow applications from scratch in the WebSphere Message Broker documentation.
Use the HL7DFDLInput node to receive HL7 messages from a clinical application into a message flow. You can then use the existing features of WebSphere Message Broker to process these messages to meet your requirements.
The HL7DFDLInput node receives HL7 messages that use the MLLP protocol over TCP/IP and makes those messages available in a message flow. The messages are parsed by using the HL7 message format in the DFDL message model. There are three versions of the DFDL message model, one for HL7 v2.7, one for HL7 v2.6, and one for HL7 v2.5.1 and earlier. You select the DFDL message model that is appropriate for the version of HL7 that you are using.
Messages from the HL7DFDLInput node are processed under transactional control. When the message flow in which the node is used ends successfully, all messages in the transaction are committed. If the message terminates with an exception that is not caught, all messages that are written under the transaction are rolled back.
For more information about the HL7DFDLInput node, see HL7DFDLInput node.
Use the HL7DFDLOutput node to send HL7 messages from a message flow to a clinical application.
The HL7DFDLOutput node receives HL7 messages, which are parsed by using the HL7 message format in the DFDL message model, and sends them to a destination application. After a message is successfully sent, the HL7DFDLOutput node waits for an acknowledgment from the destination application.
For more information about the HL7DFDLOutput node, see HL7DFDLOutput node.
Use the GenericHL7Input node to receive HL7 messages from a clinical application into a message flow. You can then use the existing features of WebSphere Message Broker to process these messages to meet your requirements.
The GenericHL7Input node receives HL7 messages that use the MLLP protocol over TCP/IP and makes those messages available in a message flow. The messages are defined in the MRM domain and are parsed by using the HL7 message format in the HL7v25P message set. You can configure the node to check for duplicates.
Messages from the GenericHL7Input node are processed under transactional control. When the message flow in which the node is used ends successfully, all messages in the transaction are committed. If the message terminates with an exception that is not caught, all messages that are written under the transaction are rolled back.
For more information about the GenericHL7Input node, see GenericHL7Input node.
Use the GenericHL7Output node to send HL7 messages from a message flow to a clinical application.
The GenericHL7Output node receives HL7 messages, which are parsed by using the HL7 message format in the HL7v25P message set in the MRM domain, and sends them to a destination application. After a message is successfully sent, the GenericHL7Output node waits for an acknowledgment from the destination application.
For more information about the GenericHL7Output node, see GenericHL7Output node.