LBL Simulator tests

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

31001 : LBL Request Mode For Labeling Instruction (for Label Broker)

This test concerns the LB (Label Broker) actor. You will use the Order Manager tool to send a request to your system under test.

Instructions

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) :

  1. Create or update the configuration corresponding to the SUT.
  2. Then, go to the "Laboratory" menu entry and choose Label Information Provider > [LAB-61] page to begin the test. 
  3. In the SUT Configurations drop-down list, select the SUT configuration.
  4. Once you have selected the patient, hit the "Send" button. The simulator will send the message to the SUT with the labeling instructions.
  5. Check the simulator has properly received your acknowledgement 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 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)?

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.

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

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).

Instructions

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) :

  1. You do not need to create a SUT configuration for your system. Just go to the "Laboratory" menu entry and choose Label Broker > Configuration page to begin your test.
  2. Configure your system under test to send the messages to IP address and port displayed on screen.
  3. Don't forget to hit the "Refresh List" button after to have send your message.
  4. 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.

31003 : LBL Query 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-62 transaction of the LBL Profile.

Instructions


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) :

  1. Create or update the configuration corresponding to the SUT (System Under Test).
  2. Then, go to the "Laboratory" menu entry and choose Label Broker > [LAB-62] page to begin your test.
  3. In the SUT Configurations drop-down list, select your LB system.
  4. In order to construct your request, you will need to fill the request parameters table. You will find all information in the SUT system.

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 :

  • Step 1 : Label Broker (Simulator) queries the Label Information Provider (SUT) using the patient ID.
  • Step 2 : Label Broker (Simulator) queries the Label Information Provider (SUT) using the Placer Visit Number.
  • Step 3 : Label Broker (Simulator) queries the Label Information Provider (SUT) using the Placer Group Number.
  • Step 4 : Label Broker (Simulator) queries the Label Information Provider (SUT) using the Placer Order Number.
  • Step 5 : Label Broker (Simulator) queries the Label Information Provider (SUT) using the Filler Order Number.
  • Step 6 : Label Broker (Simulator) queries the Label Information Provider (SUT) using the search period and patient id.
  • Step 7 : Label Broker (Simulator) queries the Label Information Provider (SUT) using the search period and patient visit number.
  • Step 8 : Label Broker (Simulator) queries the Label Information Provider (SUT) using a patient ID which is unknown by the LIP. (This is an error case, to test the answer of your LIP in this situation.)

Take an example, for the step 1 :

  1. In the request parameters table, fill the Patient ID field with a patient ID from you SUT.
  2. Then hit the "Send" button. 3.The LBL Simulator will send the message to your system and will get a response (if the SUT answers).
  3. Check the simulator has properly received your acknowledgement message.
  4. 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) ?

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".

Evaluation

  • The point below must be verified for each steps :
  • 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.
  • All steps must have been done.

31004 : LBL Query Mode For Labeling Instruction (for Label Broker)

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.

Instructions

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) :

  1. You do not need to register your SUT (System Under Test) configuration in the simulator. Just go to the "Laboratory" menu entry and choose Label Information Provider > Configuration page to begin your test.
  2. Configure your SUT to send messages to IP Address and Port of the simulator.
  3. Go to the Messages > HL7v2 messages

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 :

  • Step 1 : Label Broker (SUT) queries the Label Information Provider (Simulator) using the patient ID.
  • Step 2 : Label Broker (SUT) queries the Label Information Provider (Simulator) using the Placer Visit Number.
  • Step 3 : Label Broker (SUT) queries the Label Information Provider (Simulator) using the Placer Group Number.
  • Step 4 : Label Broker (SUT) queries the Label Information Provider (Simulator) using the Placer Order Number.
  • Step 5 : Label Broker (SUT) queries the Label Information Provider (Simulator) using the Filler Order Number.

Take an example, for the step 1 :

  1. The SUT queries the LBL Simulator using a patient ID (the SUT send a message to the LBL Simulator). See the "Patient Information available for your Request to the simulator" panel to get the patient Identifier. This panel give information about the patients of the LBL simulator.
  2. 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.
  3. Check the simulator has properly received and acknowledged your message.
  4. 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) ?

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".

Evaluation

The point below must be verified for each steps :

  • 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.
  • All steps must have been done.

31005 : LBL Labels And Containers Delivered (for Label Information Provider)

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 :

  • First, the SUT (System Under Test) will send the labeling instruction to the LBL Simulator (see test LBL Request Mode For Labeling Instruction).
  • Second, the LBL Simulator will notify the SUT for the effective labels printing and labeled containers production (this test).

Instructions


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.

 

  1. Create or update the configuration corresponding to your SUT from the SUT Configurations > HL7v2 responders page.
  2. Go to the "Laboratory" menu entry and choose Label Broker > [LAB-63] page to begin your test.
  3. In the SUT Configurations drop-down list, select your LIP system.
  4. Then, select in the "Table on the tubes label by the LB simulator" table, the tube according to your labeling instruction send to the LBL Simulator in the first step of this test. You can use the filter option to find it easy.
  5. Once you have selected the right tube to confirm, hit the "Send the confirmation of the selected labeled tubes" button. The LBL Simulator will send the message to your system.
  6. Check the simulator has properly received your acknowledgement message.
  7. 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.

31006 : LBL Labels And Containers Delivered (for Label Broker)

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 :

  • First, the LBL Simulator will send the labeling instruction to the SUT (see test "LBL Request Mode For Labeling Instruction")
  • Second, the SUT will notify the LBL Simulator for the effective labels printing and labeled containers production.

Instructions


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.

 

  1. Go to the "Laboratory" menu entry and choose Label Information Provider > Configuration page to begin your test.
  2. Configure your SUT to send messages to the IP Address and Port displayed on screen.
  3. Send a message to the LBL Simulator for the effective labels printing and labeled containers production.
  4. Access the messages exchanged between your SUT and the simulator under Messages > HL7v2 messages.
  5. Check the simulator has properly received your acknowledgement message.
  6. 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 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) ?

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.