The aim of this test is to prove the capability of the Order Filler, Automation Manager and Order Result Tracker to manage laboratory test results. In other words, we check that your system is able to send, receive and/or integrate the messages defined in Order Result Management (LAB-3) and Test Result Management (LAB-5). 

Those tests have to be performed against the Order Manager Gazelle tool, which will play the role of Order Result Tracker, Order Filler or Automation Manager according to the cases.

Order Filler

The Order Filler actor is involved in both LAB-3 (as initiator) and LAB-5 (as receiver) transactions. In this test, we check that your system is able to integrate the test results sent by the Automation Manager (role played by the Order Manager Gazelle tool) and to send order results to the Order Result Tracker (role played by the Order Manager tool).

Order Result Management (LAB-3)

This part of the test will use the Order Manager as an Order Result Tracker. First step to perform: retrieve the configuration of the Order Result Tracker to which send messages: 

1. Go to the OrderManagersimulator
2. Log onto the application using the CAS login, it uses your Gazelle (EU-CAT) credentials
3. Select theLaboratorydomain (bottom-right drop-down menu)
4. Go to Results Management --> Order Result Tracker
5. Select the character set encoding you will use to send messages to the simulator and enter the given configuration within your Order Filler.

Pre-requisites

The LAB-3 (Order Result Management) transaction defines two structures of messages (OUL^R22^OUL_R22 and ORU^R01^ORU_R01). As an initiator in this transaction, you are free to use the structure  your system under test supports.

You are assumed to perform this test after working on test #30004 so that you can reuse the order previously placed in the Order Placer. If you have followed the instruction of the test #30004 you shall have the values: ORC-5="A" and OBR-25="P". 

1. The Order Filler notifies the Order Result Tracker of the clinical validation of the results

1. Retrieve the laboratory order to use (or create a new one with the previously given characteristics) and add two observations relative to the order (OBX-11 = "P" or OBX="F")
2. Send a notification to the Order Result Tracker 
3. Follow menu Browse data --> Order Result Tracker's data and retrieve the order you have just sent to the tool
4. Copy and paste the permanent link to this order in the pre-connectathon instance started in Test Management
5. Go to the "HL7 messages" part of the simulator and retrieve the message you have sent. Click on the message id (left-hand column) to get its permanent link and the validation result.
6. Copy and Paste the "permanent link to the test report" into Gazelle

2. The Order Filler notifies the Order Result Tracker of the deletion of the test

1. Cancel the previous order from your Order Filler.
2. Send a notification to the Order Result Tracker. OBR-25 must be valued with "X", OBX-11 with "X" and ORC-5 with "CA"
3. Check that the tool has received the message and properly integrated it.
4. Go to the "HL7 messages" part of the simulator and retrieve the message you have sent. Click on the message id (left-hand column) to get its permanent link and the validation result.
5. Copy and Paste the "permanent link to the test report" into Gazelle

Test Results Management (LAB-5)

This part of the test will use the Order Manager part as an Automation Manager. If you have already performed tests #30003 and #30004, your system under test is already registered within the tool. 

Pre-requisites

The LAB-5 (Test Results Management) transaction defines two structures of messages (OUL^R22^OUL_R22 and OUL^R23^OUL_R23). As a responder in this transaction, your system under test must be able to integrate both. Go to Results management --> Automation Manager.

1. The Automation Manager transmits multiple results related to a specimen to the Order Filler

1. Select your system under test in the drop-down list located at the top of the page
2. Select "Specimen centered result reporting" as Message structure to use
3. Click on "Create a new result from scratch". The list of available patients is displayed, pick one known by your Order Filler (You may have already used patients for previous tests)
4. Fill the specimen, put the specimen available (tick the "specimen available?" checkbox) and ask for created only one container. Then click on "Create an order for specimen".
5. Fill the new work order. Result status must be equal to "Results stored; not yet verified" and the order status to "Some but not all results available".
6. Click on "Add to current specimen". Then, click on "Add observations".
7. Add an observation relative to the work order. Observation result status must be equal to "Results entered - not verified".
8. Finally, send the message and check that it is properly received and integrated by your system under test.
9. Go to the "HL7 messages" part of the simulator and retrieve the message you have sent. Click on the message id (left-hand column) to get its permanent link and the validation result.
10. Copy and Paste the "permanent link to the test report" into Gazelle
11. As a proof of the correct integration of the message within your system, take a screenshot of your application (showing the order and observation) and upload it in Test Management.

2. The Automation Manager transmits multiple results related to one or more specific containers with one specimen to the Order Filler

1. Click on "Perform another test"
2. Select "Reporting results related to one or more containers for a specific specimen" as Message structure to use
3. Select the same patient as for the previous test
4. Fill the specimen; it must be available (tick "specimen available ?"). Then click on "create a container for specimen"
5. For the created container, click on "Add an order for this container"
6. Fill the new order. Result status must be equal to "Results stored; not yet verified" and the order status to "Some but not all results available".
7. Click on "Add to current specimen" and then click on "Add observations"
8. Add an observation relative to the work order. Observation result status must be equal to "Results entered - not verified".
9. Finally, send the message and check that it is properly received and integrated by your system under test.
10. Go to the "HL7 messages" part of the simulator and retrieve the message you have sent. Click on the message id (left-hand column) to get its permanent link and the validation result.
11. Copy and Paste the "permanent link to the test report" into Gazelle
12. As a proof of the correct integration of the message within your system, take a screenshot of your application (showing the order and observation) and upload it in Test Management.

Automation Manager

The Automation Manager is involved in LAB-5 transaction as an initiator. In this test, we check the capability of your system to send messages to the Order Filler part of the Order Manager Gazelle tool. LAB-5 transaction defines two message structures (OUL^R22^OUL_R22 and OUL^R23^OUL_R23); as an initiator for this transaction, your system under test must support one out of these two structures. If your system supports both, please repeat this test twice so that we can check the conformance of the messages produced by your system.

Pre-requisites

This part of the test will use the Order Manager as an Order Filler. First step to perform: retrieve the configuration of the Order Filler to which send messages: 

1. Go to the OrderManager simulator
2. Log onto the application using the CAS login, it uses your Gazelle (EU-CAT) credentials
3. Select the Laboratory domain (bottom-right drop-down menu)
4. Go to Results Management --> Order Filler --> Order Filler configuration
5. Select the character set encoding you will use to send messages to the simulator and enter the given configuration within your Order Filler.

The Automation Manager transmits multiple results to the Order Filler

1. Within your application, create a new work order with the following information OBR-25 = "R" and ORC-5="A"
2. Add an observation to this order with OBX-11 = "R"
3. Send the appropriate message to the Order Filler part of the Order Manager
4. Follow menu Browse data --> Order Filler's data and retrieve the work order you have just sent to the tool
5. Copy and paste the permanent link to this order in the pre-connectathon instance started in Test Management
6. Go to the "HL7 messages" part of the simulator and retrieve the message you have sent. Click on the message id (left-hand column) to get its permanent link and the validation result.
7. Copy and Paste the "permanent link to the test report" into Gazelle

Order Result Tracker

The Order Result Tracker is involved in LAB-3 transaction as a responder. In this test, we check the capability of your system to integrate the messages received from an Order Filler (role played by the Order Manager Gazelle tool). This transaction defines two message structures (OUL^R22^OUL_R22 and ORU^R01^ORU_R01); as a responder your system must support both of them.

Pre-requisites

This test used the Order Manager tool as an Order Filler. In order to tell the simulator to which system send messages, your first action will be to create a new configuration for your system under test within the Order Manager. Go to the "SUT configurations" section to do so.

Then, go to Results management --> Order Filler --> Send test results to your SUT to start the test.

1. The Order Filler transmits specimen centered results to the ORT

1. Select your system under test in the drop-down list located at the top of the page
2. Select "Specimen centered result reporting" as Message structure to use
3. Click on "Create a new result from scratch". The list of available patients is displayed, select an existing one or create a new one.
4. Fill the specimen, put the specimen available (tick the "specimen available?" checkbox) and ask for created only one container. Then click on "Create an order for specimen".
5. Fill the new order. Result status must be equal to "Results stored; not yet verified" and the order status to "Some but not all results available".
6. Click on "Add to current specimen". Then, click on "Add observations".
7. Add an observation relative to the order. Observation result status must be equal to "Results entered - not verified".
8. Finally, send the message and check that it is properly received and integrated by your system under test.
9. Go to the "HL7 messages" part of the simulator and retrieve the message you have sent. Click on the message id (left-hand column) to get its permanent link and the validation result.
10. Copy and Paste the "permanent link to the test report" into Gazelle
11. As a proof of the correct integration of the message within your system, take a screenshot of your application (showing the order and observation) and upload it in Test Management.

2. The Order Filler transmits order centered results to the ORT

1. Click on "Perform another test"
2. Select "Order centered result reporting" as Message structure to use
3. Select the same patient as for the previous test
4. Fill the new order. Result status must be equal to "Results stored; not yet verified" and the order status to "Some but not all results available". Then click on "Create a specimen for order".
5. Fill the specimen; it must be available (tick "specimen available ?") and ask for created only one container. Then click on "Add to current order"
6. Finally click on "Add observations"
7. Add an observation relative to the order. Observation result status must be equal to "Results entered - not verified".
8. Finally, send the message and check that it is properly received and integrated by your system under test.
9. Go to the "HL7 messages" part of the simulator and retrieve the message you have sent. Click on the message id (left-hand column) to get its permanent link and the validation result.
10. Copy and Paste the "permanent link to the test report" into Gazelle
11. As a proof of the correct integration of the message within your system, take a screenshot of your application (showing the order and observation) and upload it in Test Management.