Testing the Healthcare: HL7 to reports pattern

Use the following information to help you to test the Healthcare: HL7 to reports pattern.

This topic contains the following sections:

Basic pattern instance setup
Flow of information through the pattern instance

Basic pattern instance setup

The main message flows of the pattern instance are:

You must ensure that you have all the queues set up for the pattern instance, see the "Queues" section in Managing a Healthcare: HL7 to reports pattern instance.

Flow of information through the pattern instance

When you send a message with the test application, the information flows through a pattern instance in the following sequence:

  1. The Healthcare Pattern Test application adds MLLP bytes to your message and then sends it over TCP/IP to the pattern instance.
  2. The message arrives in the Receiver message flow where the MLLP bytes are trimmed.
  3. The MSH segment in the message is parsed.
  4. If the duplicate message option is turned on in the pattern instance, duplicate messages are checked.
  5. An acknowledgment reply (ACK) message is sent back to the Healthcare Pattern Test application.
  6. The message is sent to the RXF queue. The message is picked up from the RXF queue by the Processor message flow.
  7. In the Processor flow a PHP script is run to generate the text based report. The name of the PHP script is determined from the HL7 message event and code. For example, the script ADT_A01.php is invoked for an ADT^A01 HL7 message.
  8. The output from running the PHP script is appended to the report file. You provide the name of the report file as a pattern parameter.
  9. Periodically the report file is copied to the destination directory. Once the copy has completed, the report file is deleted and a new report file is started.

All flows also have an exception handling subflow that handles any problems that are caught by the flow.

Back to the Healthcare: HL7 to HL7 pattern specification