The HL7 transport allows you to handle Health Level 7 International (HL7) messages. The following sections describe how to install, enable, and configure the HL7 transport:
WSO2 ESB uses the HAPI parser to provide HL7 support, which currently does not support HL7v3.
Installing the HL7 feature
The HL7 transport is available as a feature in WSO2 Enterprise Service Bus (WSO2 ESB). For instructions on installing the HL7 feature, see Installing the Axis2 Transport HL7 Feature.
Enabling the transport
You enable the HL7 transport in
<ESB_HOME>/repository/conf/axis2/axis2.xml as follows:
Creating an HL7 proxy service
For information on creating a proxy service that uses the HL7 transport, see Creating an HL7 Proxy Service.
Configuring the transport
You can optionally configure the following behavior of the HL7 transport.
Add the parameter "transport.hl7.ConformanceProfilePath" in the proxy service to point to a URL where the HL7 conformance profile (XML file) can be found.
Add the parameter "transport.hl7.MessagePreprocessorClass" in the proxy service to point to an implementation class of the interface "org.wso2.carbon.business.messaging.hl7.common.HL7MessagePreprocessor", which is used to process raw HL7 messages before parsing them so that potential errors in the messages can be rectified using the transport.
You can enable or disable automatic message acknowledgement. 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.
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. This ensures that an ACK/NACK message is created automatically when a message is sent (using the HL7 formatter). By default, an ACK message is created. If a NACK message is required instead, use the message context properties "HL7_RESULT_MODE" and "HL7_NACK_MESSAGE" as described below.
In the proxy service, add the following parameters to enable or disable auto-acknowledgement and validation:
When ‘AutoAck’ is false, you can set the following properties inside an ESB sequence.
When the result mode is ‘NACK’, you can use the following property to provide a custom description of the error message.
You can use the property "HL7_RAW_MESSAGE" in the axis2 scope to retrieve the original raw EDI format HL7 message in an ESB sequence. The user doesn't have to convert from XML to EDI again, so this usage may be particularly helpful inside a custom mediator.
To control the encoding type of incoming messages, set the Java system property "ca.uhn.hl7v2.llp.charset".
Configuring application acknowledgement
In general, we don't wait for the back-end application's response before sending an "accept-acknowledgement" message to the client. If you do want to wait for the application's response before sending the message, define the following property in the InSequence:
<property name="HL7_APPLICATION_ACK" value="true" scope="axis2"/>
In this case, the request thread will wait until the back-end application returns the response before sending the "accept-acknowledgement" message to the client. You can configure how long request threads wait for the application's response by configuring the time-out in milliseconds at the transport level:
<transportReceiver name="hl7" class="org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener">
By default, the HL7 transport validates messages before building their XML representation. You configure validation with the following parameter in the proxy service:
transport.hl7.ValidateMessage is set to false, you can set the following parameters to handle invalid messages:
transport.hl7.BuildInvalidMessages: when set to
true, builds a SOAP envelope with the contents of the raw HL7 message inside the
BuildInvalidMessagesis set to
true, you use this parameter to specify whether to pass this message through (true) or to throw a fault (false).
The following diagram illustrates these flows.
Configuring the thread pool
The HL7 transport uses a thread pool to manage connections. A larger thread pool provides greater performance, because the transport can process more messages simultaneously, but it also uses more memory. You can add the following properties to the proxy service to configure the thread pool to suit your environment:
transport.hl7.corePoolSize: the core number of threads in the pool. Default is 10.
transport.hl7.maxPoolSize: the maximum number of threads that can be in the pool. Default is 20.
transport.hl7.idleThreadKeepAlive: the time in milliseconds to keep idle threads alive before releasing them. Default is 10000 (10 seconds).
You can use the HL7 message store to automatically store HL7 messages, allowing you to audit and replay messages as needed. The HL7 store is a custom message store implementation on top of Open JPA. To use the message store, you take the following steps:
- Create an empty database in your RDBMS, and then create a message store configuration that points to that database.
- Create a sequence that points to that message store configuration.
In this configuration, when the HL7 proxy service runs, an HL7 service will start listening on the port defined in the
transport.hl7.Port service parameter. When an HL7 message arrives, the proxy will send an ACK back to the client as specified in the HL7_RESULT_MODE property. The Clone mediator is used inside the proxy to replicate the message into the Send and Store sequences, where the message is sent to the specified endpoint and is also stored in the message store HL7StoreJPA.
The HL7StoreJPA message store is a custom message store implemented in
org.wso2.carbon.business.messaging.hl7.store.jpa.JPAStore. It takes OpenJPA properties as parameters. In this example, the
openjpa.ConnectionDriverName properties are used to create an Apache DBCP pooled connection set to a MySQL database. You will need to create the database specified in the connection properties and provide the database authentication details matching your database. You may also need to place the JDBC drivers for your database into
You can view the messages in this message store using the HL7 Console UI. You can search for messages on the unique message UUID or HL7 specific Control ID. The search field supports the wildcard ‘%’ to allow LIKE queries. The table can also be filtered to search for content within messages.
Selected messages can be edited and injected into a proxy service. Reinjecting a message to the same service will result in a new message being stored with a different message UUID.