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 Enterprise Integrator(WSO2 EI) uses the HAPI parser to provide HL7 support, which currently does not support HL7v3.
Enabling the transport
You can create an HL7 proxy service using this transport after enabling it. You enable the HL7 transport in the
<EI_HOME>/conf/axis2/axis2.xml file as follows:
Configuring the transport
When creating an HL7 proxy service, 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 "transport.hl7.MessagePreprocessorClass" parameter 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 acknowledgment. When automatic message acknowledgment 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 integration 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 integration 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 in 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
transport.hl7. PassThroughInvalidMessages: when
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.
Creating an HL7 Proxy Service
If you want to try the example configurations on this page, you must have an HL7 client and HL7 back-end application set up and running. To see a sample that illustrates how to create an HL7 client and back-end application, see:
To create the HL7 proxy service:
- In the Management Console, create a custom proxy service (see Adding a Proxy Service).
In the transports list, specify
- Create an Address Endpoint with the URL of the HL7 server host and port, such as:
Add the following parameter to the proxy service (required to enable the transport):
For information on additional configuration you can set on the HL7 transport, see HL7 Transport.
If user doesn't want to wait for the back-end service to process the message and only needs acknowledgment from the system that the message was received, you can configure the proxy service to send an ACK/NACK message after the message is received. For example:
If you want to wait for the application's response before sending the acknowledgment message (see Configuring application acknowledgement), you add the HL7_APPLICATION_ACK property to the inSequence and any additional HL7 properties and transport parameters as needed. For example:
Exchanging HL7 messages with the File System
For more information on creating an HL7 proxy service, see Creating an HL7 Proxy Service.
Transferring messages from file system to file system
WSO2 Enterprise Integrator(WSO2 EI) allows messages to be transferred between HL7 and the file system using the HL7 and VFS transports. To begin, ensure that you have the VFS and HL7 transports enabled by uncommenting the relevant transportReceiver and transportSender elements inside the
<EI_HOME>/conf/axis2/axis2.xml file. You must also uncomment the relevant builder/formatter pair to enable WSO2 EI to work with the HL7 message format. For more information, see HL7 Transport and VFS Transport.
Once you have enabled the transports and started the WSO2 EI server, use the following proxy service configuration to run the sample.
This sample uses the UNIX temporary directory /tmp/ in several VFS parameters; be sure to change them to match a location in your file system.
Now, copy the following HL7 message into a text editor and save it as an
.hl7 file inside the directory you specified with the
transport.vfs.FileURI parameter (
/tmp/in in the above example).
The proxy service is configured to detect
.hl7 files in the
transport.vfs.FileURI directory. We have also configured the VFS content type as the
application/edi-hl7 MIME type with an optional charset encoding. When you save the
.hl7 file to that directory, the proxy service invokes the HL7 builders/formatters and builds the HL7 message into its equivalent XML format. It then prints the XML representation of the message on the management console and forwards the message to the VFS endpoint ‘/tmp/out’.
For more information on configuring these transports and general properties you can set, see the following topics:
Transferring messages between HL7 and the file system
Now, let's look at how we can send and receive files between an HL7 service and the file system. For this scenario, we will use the HAPI Test Panel to send messages to WSO2 EI. As with the previous example, ensure that you have the VFS and HL7 transports and their builders/formatters enabled, and replace the temporary directories shown in the sample with actual directories on your file system.
To invoke this proxy, use the HAPI Test Panel to connect to the HL7 service at the specified port and send a test message. When this proxy service runs, an HL7 service will start listening on the port defined in the
transport.hl7.Port parameter. When the HL7 message arrives, the proxy will send an ACK back to the client as specified in the HL7_RESULT_MODE property. The HL7 message is then processed through WSO2 EI and sent to the VFS endpoint, which will save the HL7 message in ‘/tmp/out’.
Transferring messages between HL7 and FTP
The following configuration is similar to the previous example, but it illustrates how to process files between an HL7 endpoint and files accessed through FTP. To run this sample, first set up an endpoint by starting a new receiver connection in the HAPI Test Panel on port 9988. You then configure this endpoint in the Send mediator as shown in the following proxy service example. The proxy service will detect
.hl7 files in the
transport.vfs.FileURI directory and send them to the HL7 endpoint.
Once you start the endpoint of the WSO2 EI server, if you place an HL7 message in the
transport.vfs.FileURI directory, you will be able to see the message passed to the HL7 endpoint in the HAPI Test Panel.