This section contains test cases performed with the LBL Simulator.
Tool: http://gazelle.ihe.net/LBLSimulator
Tool information page: http://gazelle.ihe.net/content/lbl-simulator
This test concerns the LB (Label Broker) actor. You will use the Order Manager tool to send a request to your system under test.
Access the LBL Simulator tool at this location : Order Manager
If it is your first time with this tool, please read the user manual : Order Manager 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 received the labeling instructions from the LBL Simulator.
As the SUT implements the LB (LB acts as a responder in this test) :
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 the 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 Gazelle as the result of 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)?
This test concerns only the LIP (Label Information Provider) actor. Your system under test will request the Order Manager tool (acting as Label Broker) to deliver the labels (LAB-61 transaction).
Access the LBL Simulator tool at this location : Order Manager
If it is your first time with this tool, please read the user manual : Order Manager 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 your system under test implements the LIP (LIP acts as an initiator in this test) :
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)?
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-62 transaction of the LBL Profile.
Access the LBL Simulator tool at this location : Order Manager
If it is your first time with this tool, please read the user manual : Order Manager User Manual
Please be remind that if you are logged in your configurations will be private. Requirements :
As your system implements the LIP (LIP acts as a responder in this test) :
In this test, you must use the LBL Simulator to query the SUT. Send severals messages using different parameters. All (Required) possibilities are defined in the steps below :
Take an example, for the step 1 :
Do this for all steps and don't forget to copy/paste the "test result link". Link the step number to the "test result link".
This test concerns the LB (Label Broker) actor. You will need to communicate with the LBL Simulator, in order to simulate
the LAB-62 transaction of the LBL Profile.
Access the LBL Simulator tool at this location : Order Manager
If it is your first time with this tool, please read the user manual : Order Manager User Manual
Please be remind that if you are logged in your configurations will be private. Requirements :
As your system implements the LB (LB acts as an initiator in this test) :
In this test, the SUT must query the LBL Simulator. Send severals messages using different parameters. All (Required) possibilities are defined in the steps below :
Take an example, for the step 1 :
Do this for all steps and don't forget to copy/paste the "test result link". Link the step number to the "test result link".
The point below must be verified for each steps :
This test concerns the LIP (Label Information Provider) actor. Your SUT will receive the label delivered notification from the Order Manager tool acting as Label Broker.
In this test, the Label Broker notifies the effective labeled containers production to the Label Information Provider.
So, the LBL Simulator, needs to know the labeling instruction, before to send a notification message to the LIP for the effective labels printing and labeled containers production.
Two steps are necessary in this test :
Access the LBL Simulator tool at this location : Order Manager
If it is your first time with this tool, please read the user manual : Order Manager User Manual
Please be remind that if you are logged in your configurations will be private.
This test concerns the LB (Label Broker) actor. You will use the Order Manager tool to simulate the Label Information Provider actor.
In this test, the Label Broker notify the effective labeled containers production to the Label Information Provider.
So, the SUT (System Under Test), needs to know the labeling instruction, before to label the tubes and to send a notification message to the LIP for the effective labels printing and labeled containers production.
Two steps are necessary in this test :
Access the LBL Simulator tool at this location : Order Manager
If it is your first time with this tool, please read the user manual : Order Manager User Manual
Please be remind that if you are logged in your configurations will be private.
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.