Page Comparison

The HL7 Transport (New in Carbon 4.0) is available as an installable feature in WSO2 products. The user can simply plug it in if necessity, through the installation of the relevant allows you to handle Health Level 7 International (HL7) messages. It is available when you install the Axis2 Transport HL7 feature. For instructions to install on installing the HL7 transport and adding a proxy service , refer to that enables connection with an HL7 server, see the following topics:

The HL7 transport configuration is as follows:

<transportConfig>
    <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 improvements from version 4.0.0 onwards.

HL7

...

conformance profile support

The service-level parameter "transport.hl7.ConformanceProfilePath" points to a URL where the conformance profile XML can be found.

HL7

...

message pre-

...

processing

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 specify the implementation class is "transport.hl7.MessagePreprocessorClass".

Capability to

...

enable/

...

disable automatic ACK/NACK

...

You can enable or disable automatic message acknowledgement and validation. When automatic message acknowledgement is enabled, an ACK is immediately sent back to the client after receiving a message.

...

When

...

it is disabled, the user is given control to send back an ACK/NACK message from an ESB sequence after any message validations or related tasks. Different types of message validations done at the message builder are removed for behavioral consistency of the message builder with the transport.

Some Following are some example usage scenarios are given below:

1. When using a transport such as HTTP, to create an ACK/NACK message from an HL7 message in the flow, specify an axis2 scope message context property "HL7_GENERATE_ACK", and set its value to true. It This ensures that an ACK/NACK message is created automatically when a message is sent out (using the HL7 formatter). By default, an ACK message is created. If a NACK message is required to be generatedinstead, use the message context properties "HL7_RESULT_MODE" and "HL7_NACK_MESSAGE" have to be used.

2. Adding two new service-level parameters to be used by a proxy service.

...

4. When the result mode is ‘NACK’, you can use the following property can be used to give provide a custom description of the error message.

Code Block
language html/xml
<property name="HL7_NACK_MESSAGE" value="<ERROR MESSAGE>" scope="axis2" />

5. The You can use 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 The user doesn't have to again convert from XML to EDI again, so this usage may be particularly helpful inside a custom mediator.

6. Set the Java system property "ca.uhn.hl7v2.llp.charset" to control the encoding type of incoming messages.

Excerpt
hidden true
Instructions on how to install Information about the HL7 Transport in the WSO2 ESB.