This topic contains the following sections:
This Receiver flow uses the GenericHL7Input node to read incoming HL7 messages completely; no restrictions exist on the segments that you can include in a message, provided that the segments are present in the HL7v25P message set that is used by the pattern. The pattern uses the HL7v25P message set that is included with IBM WebSphere Message Broker Connectivity Pack for Healthcare. The HL7v25P message set includes definitions of all segments that are valid and standard at HL7 version 2.5. You can add additional Z-segments to this HL7v25P message set. Z-segments are used by applications to send or receive data that is defined outside the HL7 specification.
Duplicate checking and HL7 acknowledgment are carried out once, by the Receiver flow, on the source message. This pattern does not provide any sequencing options nor does the pattern provide any remainder processing for extra fields.
The Processor flow ensures that a report is generated for each HL7 message. You design PHP scripts to generate the reports. You must deploy the PHP scripts to the broker along with the message flows which implement the pattern. The HL7v25P message set must also be deployed to the broker before any messages are sent.
In addition to the reports generated from the HL7 messages, this pattern provides a number of other outputs. These outputs are either written to a queue or sent to a Publication node. The destination is determined by the pattern parameter Publish . If the Publish option is selected, all information is published by using a topic hierarchy that begins with the pattern instance name.
If the Write to Queue option is selected, output is sent to queues with names that are generated from the pattern parameter Queue prefix and a fixed set of suffixes, as shown in the following table.
Note: The pattern instance name prefix for the queue and topic names is not shown.
Output | Queue | Topic | Notes |
---|---|---|---|
Source feed | .SRC | /Source | A copy of the source message, as received, is written. |
Journal | .JRNL | /Journal | This output provides a journal of
incoming messages in standard pattern format.
See Note 1. |
To Processor flow | .RXF | Not applicable | |
Messages in error | .ERR | Not applicable | Messages that cannot be correctly processed are written to the error queue with error information in an MQRFH2 header. |
Message IDs for duplicate checking | .DUPID | Not applicable | Message identifiers, and associated
ACK messages, are stored for comparison with later incoming messages to detect
duplicate messages.
See Note 2. |
Note 1: A journal message is produced from a source message by adding MQMD and MQRFH2 headers. The MQRFH2 header includes:
Note 2: Each message, as it arrives, is checked by the queue for message IDs for a previous message with the same ID. These messages are given a timeout, which is determined by a message parameter, after which the messages are removed from the queue. Therefore, duplicates are checked for a given time period only, the default is 24 hours.
Back to the Healthcare: HL7 to reports pattern specification