Page Comparison

The HL7 Transport transport (New new in Carbon version 4.0) allows you to handle Health Level 7 International (HL7) messages. The following sections describe how to install, enable, and configure the HL7 transport:

Installing the HL7 feature

The HL7 transport is available as an installable feature in WSO2 products. The user can simply plug it in if necessity, through the installation of the relevant feature. For instructions to install HL7 transport and adding a proxy service, refer to

The HL7 transport configuration is as follows

...

Enabling the HL7 transport 

You enable the HL7 transport in the <ESB_HOME>/repository/conf/axis2/axis2.xml file as follows:

<transportReceiver name="hl7" class="org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener">

       <parameter name="port">9292</parameter>
   
</transportReceiver>
   
<transportSender name="hl7" class="org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender">
  
     <!--parameter name="non-blocking">true</parameter-->
   
</transportSender>
</transportConfig>

...

The Axis2 Transport HL7 feature supports the following in "Axis2 Transport HL7" feature improvements from version 4.0.0 onwards.

Creating an HL7 proxy service

You can add a proxy service with HL7 transport after enabling it. 

HL7 Conformance Profile Support

...

An implementation of the interface "org.wso2.carbon.business.messaging.hl7.common.HL7MessagePreprocessor" can be used to process raw HL7 messages before parsing them, so that potential errors in the messages can be rectified using it. The service-level parameter used to mention the implementation class is "transport.hl7.MessagePreprocessorClass".

Capability to Enable/Disable Automatic ACK/NACK

...

at Suitable Times

Supports disabling or enabling automatic message acknowledgement and validation.

...

5. The property "HL7_RAW_MESSAGE" in the axis2 scope can be used to retrieve the original raw EDI format HL7 message in an ESB sequence. As the user doesn't have to again convert from XML to EDI, this usage may be particularly helpful inside a custom mediator.

Synchronization with Builder/Formatter

The transport listener/sender, message builder/formatter uses a common implementation of parsing/validation logic of HL7 messages6. Set the Java system property "ca.uhn.hl7v2.llp.charset" to control the encoding type of incoming messages. More information about this configuration will be coming up soon.