31002 : LBL Request Mode For Labeling Instruction (for Label Information Provider)

This test concerns only the LIP (Label Information Provider) actor. You will need to communicate with the LBL Simulator, in order to simulate
the LAB-61 transaction of the LBL Profile.

Instructions

Access the LBL Simulator tool at this location : LBL Simulator
If it is your first time with this tool, please read the user manual : LBL Simulator User Manual
Please be remind that if you are logged in your configurations will be private.

In this test, the SUT (System Under Test) must send the labeling instructions to the LBL Simulator.

As the implements the LIP (LIP acts as an initiator in this test) :

  1. Don't need to create a SUT configuration for your system. Just go to the "Simulators" menu entry and choose "LB" page to begin your test.
  2. Select the "LAB-61 Transaction" tab.
  3. In the charset drop-down list, select the desired charset.
  4. Use the Ip Address and the Port linked to this charset to send your message with the labeling instructions to the LBL Simulator.
  5. Don't forget to hit the "Refresh List" button after to have send your message.
  6. Check the simulator has properly received and acknowledged your message.

The messages exchanged between the simulator and the SUT can be found in the message table on the very same page or from the HL7 Message menu entry.
Hit the link on the left side of the raw (first column of the table), to display the Permanent Link to test report for the corresponding HL7 message. (You can access to the hl7v2 report tutorial for more details.)
If the validation report status is passed for the message and the response, copy the "test result link" and paste it in the comment section of the pre-connectathon log return page as the result for this test.
For further details, see this tutorial : How enter your pre-connectathon test result in Gazelle (only for the LAW, LCSD and LBL Profiles of the Laboratory Domain which send HL7v2 messages)?

Evaluation

  • The validation status must be passed for the two messages of the transaction. The message type must be the right message type, according to IHE.
  • The Acknowledgment code must be "AA" (MSA-1) in the acknowledgment message.