Order Manager tests

This section contains test cases performed with the the Order Manager tool.

Tool: http://gazelle.ihe.net/OrderManager

Tool user manual: https://gazelle.ihe.net/gazelle-documentation/Order-Manager/user.html

30001: LTW Order Placer sends notifications

This test will be performed against the Order Filler part of the OrderManager Gazelle simulator. Here, we are only checking the initiator part of the Order Placer; that means that, in this test, your system is only asked to send messages to the simulator to create and cancel orders. The receiver part of the Order Placer (used to receive notifications from the Order Filler) is tested in the test #30002.

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 -European instance- credentials)
  3. Select the Laboratory domain (bottom-right drop-down menu)
  4. Go to Order 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 Placer.

Pre-requisites

The LAB-1 (Lab Placer Order Management) transaction defines three structures of messages (OML^O21^OML_O21, OML^O33^OML_O33, OML^O35^OML_O35). As an initiator in this test, you are free to use the structure  your system under test supports. Please, add a comment into the pre-connectathon test instance you have started to tell us which structures your system uses.

Your Order Placer is assumed to be coupled with a PAM actor, that means that you should be able either to enter a new patient/encounter into your system or to receive a new patient/encounter from a PAM/PDS or PAM/PES actor. If you need to populate your system with a patient and encounter using an external system, you are free to use the PAMSimulator tool to do so.

Order creation

  1. Enter a new order within your system under test
  2. Send a message to the Order Filler part of the simulator. ORC-1 must be valued with "NW".
  3. 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.
  4. Copy and Paste the "permanent link to the test report" into Gazelle
  5. Go to Browse Data/All orders and retrieve the order you have sent. Copy and paste its permanent link into Gazelle

Order cancellation

  1. Within your system, cancel the previous order and send the notification to the simulator. ORC-1 must be valued with "CA".
  2. 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.
  3. Copy and Paste the "permanent link to the test report" into Gazelle

30002: LTW Order Placer receives notifications

The purpose of this test is checking that the Order Placer is able to integrate messages received from the Order Filler in the context of the LAB-2 (creation of new orders) and LAB-1 (cancellation and status updates) transactions. We will also check that the acknowledgements are properly built.

Pre-requisites

Before beginning this test, do not forgot to check that the configuration (IP address, port, application/facility names) of your system under test is enter within the simulator. 

Your Order Placer is assumed to be coupled with a PAM actor, that means that you should be able either to enter a new patient/encounter into your system or to receive a new patient/encounter from a PAM/PDS or PAM/PES actor. If you need to populate your system with a patient and encounter using an external system, you are free to use the PAMSimulator tool to do so. The Order Manager must also know this patient/encounter, to share the patient between the PAMSimulator and the Order Manager tools, read the tutorial available here. If you have already performed the test #30001, you can use the same patient.

We strongly recommend to read the tutorial available here.

1. Assign a number to an order created by the Order Filler (LAB-2)

In this step, you show the ability of your Order Placer to accept the creation of orders by the laboratory (ORC-1 = "SN") and to assign placer order numbers to these orders. The acknowledgement message (ORL of the corresponding message structure, with ORC-1="NA") must carry the placer order number (ORC-2).

As a receiver in this test, your Order Placer shall be able to integrate all of the three message structures defined in the technical framework. As a consequence, you are asked to perform this step three times.

  1. Go to Order management --> Order Filler --> Notify order placer of orders
  2. Select your system under test in the drop-down list
  3. Select "Create a new order" as action to perform
  4. Select one of the three message structures
  5. Select the patient for whom you want to create a new laboratory order
  6. Fill the order and click on the "send message" button
  7. Retrieve the permanent link to the test report and paste it in Gazelle.
  8. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.
  9. Play this step again with another message structure

2. Integrate the cancellation of an order on the laboratory initiative (LAB-1)

In this step, you show the ability of your Order Placer to intefration te cancellation of orders by the laboratory (ORC-1="OC") and to acknowledge it (ORL of the corresponding message structure, with ORC-1 = "OK")

  1. Go to Order management --> Order Filler --> Notify order placer of orders
  2. Select your system under test in the drop-down list
  3. Select "Cancel an existing order" as action to perform
  4. Select the message structure to use
  5. Select the laboratory order to cancel and when the pop-up raises, click on the "Yes" button.
  6. Retrieve the permanent link to the test report and paste it in Gazelle
  7. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

3. Integration an order status change notified by the Order Filler (LAB-1)

In this step, you show the ability of your Order Placer to integrate a change of status of an order (OBR-25 must change of calue, this must be visible in your application screenshot), notified by the Order Filler (ORC-1="SC") and to acknowledge it (ORL of the corresponding message structure, witch ORC-1 = "OK")

  1. Go to Order management --> Order Filler --> Notify order filler of orders
  2. Select your system under test in the drop-down list
  3. Select "Update order status" as action to perform
  4. Select the message structure to use
  5. Select the laboratory order to update and when the pop-up raises, select the new status and click on the "Send update notification" button.
  6. Retrieve the permanent link to the test report  and paste it in Gazelle
  7. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle

30003: LTW Order Filler receives notifications

This test is dedicated to the LAB-1 transaction from the point of view of the Order Filler. In this test, we will check that the Order Filler is able to integrate the notifications of creation and cancellation of orders received from the Order Placer. In this test, you are asked to use the Order Manager tool as an Order Placer to send messages to your system under test.

Pre-requisite

Before beginning this test, do not forget to check that the configuration (IP address, port, application/facility names) of your system under test is enter within the simulator. 

Your Order Filler is assumed to be coupled with a PAM actor, that means that you should be able either to enter a new patient/encounter into your system or to receive a new patient/encounter from a PAM/PDS or PAM/PES actor. If you need to populate your system with a patient and encounter using an external system, you are free to use the PAMSimulator tool to do so. The Order Manager must also know this patient/encounter, to share the patient between the PAMSimulator and the Order Manager tools, read the tutorial available here. If you have already performed the test #30004, you can use the same patient.

We strongly recommend to read the tutorial available here.

1. Laboratory Order creation

As a receiver in this test, your Order Filler shall be able to integrate all of the three message structures defined in the technical framework. As a consequence, you are asked to perform this step three times.

  1. Go to Order management --> Order Placer --> Notify order filler of orders
  2. Select your system under test in the drop-down list
  3. Select "Create a new order" as action to perform
  4. Select one of the three message structures
  5. Select the patient for whom you want to create a new laboratory order
  6. Fill the order and click on the "send message" button
  7. Retrieve the permanent link to the test report and paste it in Gazelle.
  8. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.
  9. Play this step again with another message structure

2. Cancellation of a laboratory order

In this step, your Order Filler shall prove its ability to accept and integrate an order cancellation sent by the Order Placer (ORC-1="CA") and to acknowledge it (ORC-1="CR").

  1. Go to Order management --> Order Placer --> Notify order filler of orders
  2. Select your system under test in the drop-down list
  3. Select "Cancel an existing order" as action to perform
  4. Select the message structure to use
  5. Select the laboratory order to cancel and when the pop-up raises, click on the "Yes" button.
  6. Retrieve the permanent link to the test report and paste it in Gazelle
  7. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

30004: LTW Order Filler sends notifications

 

This test will be performed against the OrderPlacer part of the OrderManager Gazelle simulator. Here, we are only checking the initiator part of the Order Filler; that means that, in this test, your system is only asked to send messages to the simulator to create and cancel orders and to update the status of orders. The receiver part of the Order Filler (used to receive notifications from the Order Placer) is tested in the test #30003.

First step to perform: retrieve the configuration of the Order Placer to which send messages: 

  1. Go to the OrderManager simulator
  2. Log onto the application using the CAS login (it uses your Gazelle -European instance- credentials)
  3. Select the Laboratory domain (bottom-right drop-down menu)
  4. Go to OrderManagement--> Order Placer --> Order Placer 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.

Pre-requisites

The LAB-1 (Lab Placer Order Management) and LAB-2 (Lab Filler Order Management) transactions define three structures of messages (OML^O21^OML_O21, OML^O33^OML_O33, OML^O35^OML_O35). As an initiator in this test, you are free to use the structure  your system under test supports. Please, add a comment into the pre-connectathon test instance you have started to tell us which structures your system uses.

As described in the Technical Framework  (TF-LAB volume 1), your system under test is assumed to implement actors from the PAM or PDQ profile in addition of the Order Filler actor from the LTW integration profile. That means that your system is able either to create a new patient and encounter or to receive those information from an external system. If your system under test implements PEC and/or PDC actors from the PAM profile, feel free to use the PAMSimulator tool to receive new patient and encounter for initializing this test.

Order creation

As a first step for this test, you will have to create two new orders (the status of the first one will be updated in step 2 and the second one will be cancelled in step 3).

  1. Enter a new order within your system under test
  2. Send a message to the Order Placer part of the simulator. ORC-1 must be valued with "SN".
  3. Check the acknowledgment received by your system. (ORC-1="NA") with a placer order number provided in ORB-2.
  4. Go to the "HL7messages" part of the simulator and retrieve the message you have sent. Click on the messageid(left-hand column) to get its permanent link and thevalidationresult.
  5. Copy and Paste the "permanent link to the test report" into Gazelle
  6. Go to Browse Data/All orders and retrieve the order you have sent. Copy and paste its permanent link into Gazelle.
  7. Perform steps 1 to 6 a second time in order to create a second order (could be for the same patient).

Update order status

In this second step, the status of the fist placed order will be updated to "A" (Some but not all results available).

  1. Update the status of the previous order to "A".
  2. Send a notification to the Order Placer part of the simulator. ORC-1 must be valued with "SC", ORC-5="A", OBR-25="P".
  3. Refresh the permanent page of the order and check its new status.
  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
  6. Do not drop your database after this test; you may want to use this order to send results to the Order Result Tracker (test #30006)

Order cancellation on Order Filler's initiative

This third test is dedicated to the cancellation of the second order you have sent.

  1. Within your system, cancel the order and send a notification (ORC-1="SC", ORC-5="CA", OBR-23="X") to the Order Placer part of the simulator.
  2. Refresh the permanent page of the order and check it has been cancelled.
  3. 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.
  4. Copy and Paste the "permanent link to the test report" into Gazelle

30005: LTW Work order management

This test is used to test the capability of the Order Filler and Automation Manager actors to manage work orders. For both actors, the test will be performed against the Order Manager Gazelle tool.

 

Order Filler

First step to perform: retrieve the configuration of the Automation Manager 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 Order Management --> Automation Manager --> Automation Manager 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.

Pre-requisites

The LAB-4 (Work Order Management) transaction defines three structures of messages (OML^O21^OML_O21, OML^O33^OML_O33, OML^O35^OML_O35). As an initiator in this test, you are free to use the structure  your system under test supports. Please, add a comment into the pre-connectathon test instance you have started to tell us which structures your system uses.

Your Order Filler is assumed to be coupled with a PAM actor, that means that you should be able either to enter a new patient/encounter into your system or to receive a new patient/encounter from a PAM/PDS or PAM/PES actor. If you need to populate your system with a patient and encounter using an external system, you are free to use the PAMSimulator tool to do so.

1. Order creation

  1. Enter a new work order within your system under test
  2. Send a message to the Automation Manager part of the simulator. ORC-1 must be valued with "NW".
  3. 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.
  4. Copy and Paste the permanent link to the test report into Gazelle
  5. Go to Browse Data/All work orders and retrieve the order you have sent. Copy and paste its permanent link into Gazelle

2. Order cancellation

  1. Within your system, cancel the previous work order and send the notification to the simulator. ORC-1 must be valued with "CA".
  2. 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.
  3. Copy and Paste the permanent link to the test report into Gazelle

Automation Manager

In this test, you will use the Order Manager tool to create a work order to send to your system under test. Before starting this test, make sure you have properly registered your system in the "SUT Configurations" section of the tool and that your system under test is reachable from the Internet (no firewall prevents it from receiving messages from our tools).

Pre-requisites

We strongly recommend to read the tutorial available here.

1. Work Order creation

As a receiver in this test, your Automation Manager shall be able to integrate all of the three message structures defined in the technical framework. As a consequence, you are asked to perform this step three times (if your system does not support all of the three messages, please leave a comment in Gazelle to explain which one it supports, and why it does not support all of them).

  1. Go to Order management --> Order Filler --> Notify Automation Manager of work orders
  2. Select your system under test in the drop-down list
  3. Select "Create a new order" as action to perform
  4. Select one of the three message structures
  5. Select the patient for whom you want to create a new work order
  6. Fill the order and click on the "send message" button
  7. Retrieve the permanent link to the test report and paste it in Gazelle.
  8. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.
  9. Play this step again with another message structure

2. Cancellation of a work order

In this step, you will cancel the first work order received by your Automation Manager.

  1. Go to Order management --> Order Placer --> Notify order filler of orders
  2. Select your system under test in the drop-down list
  3. Select "Cancel an existing order" as action to perform
  4. Select the message structure to use
  5. Select the work order to cancel and when the pop-up raises, click on the "Yes" button.
  6. Retrieve the permanent link to the test report and paste it in Gazelle
  7. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

30006: LTW Test result management

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.

30601 : LAW Normal Process (for Analyzer Manager)

This test concerns the Analyzer Manager actor. You will need to validate with EVSClient tool the IHE conformance of your HL7 messages.

Instructions

As your system implements the Analyzer Manager actor, you will need to test the HL7 messages used in the LAB-27, LAB-28 and LAB-29 transactions.
Your system must be able to send HL7 messages (to the Analyzer actor) of types :

  • RSP^K11^RSP_K11, for the LAB-27 transaction (Query for AWOS)
  • OML^O33^OML_O33, for the LAB-28 transaction (Analytical Work Order Step Broadcast)
  • ACK^R22^ACK_R22, for the LAB-29 transaction (AWOS Status Change)   

To test the IHE conformance of your HL7 messages, go to the EVSCLient tool at this location : EVSClient
If it is your first time with this tool, please read the user manual : EVSClient User Manual
    
In the EVSClient tool, go to the HL7 menu entry and choose "HL7v2" then click on "Message Validation".
Paste your message to validate in the box. (You can hit the "Guess" button to preset the Message Profile OID.)
    
For example, for the RSP^K11^RSP_K11 message :

  1. Copy the RSP^K11^RSP_K11 HL7 message from your system. Paste it in the box in the EVSClient page. 
  2. Select the Message profile OID according to your message. In this example : 
    • Affinity Domain : IHE
    • Domain : Laboratory
    • Actor : Analyzer Manager
    • Transaction : LAB-27
    • Message Type : RSP^K11^RSP_K11
    • HL7 Version : HL7v2.5.1  
  3. Once you have selected the Profile OID, press the "Validate" button. If the Validation Result is not "PASSED", it means your HL7 message is not according to the LAW Profile of the Laboratory  Technical Framework. If the Validation Result is "PASSED", copy the "Permanent 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) ?


Do this for all messages and don't forget to copy/paste the "Permanent link" of the validation result to Gazelle.

Evaluation

  • The validation status shall be "PASSED" for all messages.
  • The message type shall be the right message type, according to IHE.
  • The Acknowledgment code of the RSP^K11^RSP_K11 and the ACK^R22^ACK_R22 messages shall be "AA" (MSA-1).
  • Each of the three messages must be validated at least one time and the permanent link must be paste to Gazelle.

30602 : LAW Normal Process (for bi-directional Analyzer)

This test concerns the bi-directional Analyzer actor. You will need to validate with EVSClient tool the IHE conformance of your HL7 messages.

Instructions



As your system implements the Analyzer actor and supports the bi-directional communication option, you will need to test the HL7 messages used in the LAB-27, LAB-28 and LAB-29 transactions.
Your system must be able to send HL7 messages (to the Analyzer Manager actor) of types :

  • QBP^Q11^QBP_Q11, for the LAB-27 transaction (Query for AWOS)
  • ORL^O34^ORL_O34, for the LAB-28 transaction (Analytical Work Order Step Broadcast)
  • OUL^R22^OUL_R22, for the LAB-29 transaction (AWOS Status Change)

To test the IHE conformance of your HL7 messages, go to the EVSCLient tool at this location : EVSClient
If it is your first time with this tool, please read the user manual : EVSClient User Manual
   
In the EVSClient tool, go to the HL7 menu entry and choose "HL7v2" then click on "Message Validation".
Paste your message to validate in the box, and hit the "Guess" button to preset the Profile OID.
   
For example, for the QBP^Q11^QBP_Q11 message :

  1. Copy the QBP^Q11^QBP_Q11 HL7 message from your system. Paste it in the box in the EVSClient page.
  2. Select the Message profile OID according to your message. In this example : 
    • Affinity Domain : IHE
    • Domain : Laboratory
    • Actor : Analyzer
    • Transaction : LAB-27
    • Message Type : QBP^Q11^QBP_Q11
    • HL7 Version : HL7v2.5.1
  3. Once you have selected the Profile OID, press the "Validate" button. If the Validation Result is not "PASSED", it means your HL7 message is not according to the LAW Profile of the Laboratory Technical Framework. If the Validation Result is "PASSED", copy the "Permanent 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) ?

Do this for all messages and don't forget to copy/paste the "Permanent link" of the validation result to Gazelle.

Evaluation

  • The validation status shall be "PASSED" for all messages.
  • The message type shall be the right message type, according to IHE.
  • The Acknowledgment code of the ORL^O34^ORL_O34 message shall be "AA" (MSA-1).
  • Each of the three messages must be validated at least one time and the permanent link must be paste to Gazelle.

30603 : LAW Normal Process (for Analyzer)

This test concerns the Analyzer actor. You will need to validate with EVSClient tool the IHE conformance of your HL7 messages.

Instructions

As your system implements the Analyzer actor and supports the bi-directional communication option, you will need to test the HL7 message used in the LAB-29 transaction.
Your system must be able to send HL7 messages (to the Analyzer Manager actor) of type :    
OUL^R22^OUL_R22, for the LAB-29 transaction (AWOS Status Change)
   
To test the IHE conformance of your HL7 messages, go to the EVSCLient tool at this location : EVSClient
If it is your first time with this tool, please read the user manual : EVSClient User Manual
   
In the EVSClient tool, go to the HL7 menu entry and choose "HL7v2" then click on "Message Validation".
Paste your message to validate in the box, and hit the "Guess" button to preset the Profile OID.
   
For example :

  1. Copy the OUL^R22^OUL_R22 HL7 message from your system. Paste it in the box in the EVSClient page.
  2. Select the Message profile OID according to your message. In this example :
    • Affinity Domain : IHE
    • Domain : Laboratory
    • Actor : Analyzer
    • Transaction : LAB-29
    • Message Type : OUL^R22^OUL_R22
    • HL7 Version : HL7v2.5.1
  3. Once you have selected the Profile OID, press the "Validate" button. If the Validation Result is not "PASSED", it means your HL7 message is not according to the LAW Profile of the Laboratory Technical Framework. If the Validation Result is "PASSED", copy the "Permanent 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) ?

Evaluation

  • The validation status shall be "PASSED" for all messages.
  • The message type shall be the right message type, according to IHE.

30604 : LAW : Query for AWOS (for Analyzer Manager)

This test concerns only the Analyzer Manager actor. You will need to communicate with the LAW Simulator (which is included in the Order Manager Simulator), in order to simulate the LAB-27 transaction of the LAW Profile.

Instructions

Access the LAW 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 reminded that if you are logged in your configurations will be private, otherwise it will be public. 

In this test, the LAW Simulator plays the role of the "Analyzer". It is used to query the SUT (System Under Test) for an AWOS related to the specimen. 

 

The SUT implements the Analyzer Manager (Analyzer Manager acts as a responder in this test) :

  1. First at all, check that the selected "Domain for testing" (at the bottom right of the page) is "Laboratory".
  2. Create or update the configuration corresponding to the SUT.
  3. Then, go to the "Order Management" menu entry, choose "Analyzer", and click on the "Query Analyzer Manager for AWOS" page to begin the test.
  4. In the "SUT Configurations" drop-down list, select the configuration matching the SUT.
  5. Select the "Query Mode" and fill the required parameters values (See the description of the LAB-27 transaction in the LAW Technical Framework Supplement for further details about the usage of the parameters). 
  6. Then, hit the "Send Query" button. The LAW Simulator will send the query to the SUT.
  7. 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.
  • The QPD segment of the RSP^K11^RSP_K11 message must contain the same information that the QPD segment of the QBP^Q11^QBP_Q11 message

30605 : LAW Query for AWOS (for Analyzer)

 

This test concerns only the Analyzer actor. You will need to communicate with the LAW Simulator (which is included in the Order Manager Simulator), in order to simulate the LAB-27 transaction of the LAW Profile.

Instructions

Access the LAW 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

In this test, the LAW Simulator will be used to respond to the SUT (System Under Test) query.

 

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

  1. First at all, check that the selected "Domain for testing" (at the bottom right of the page) is "Laboratory".
  2. You must be log in to be able to continue this test.
  3. Go to the "Order Management" menu entry and choose "Analyzer Manager", then "Analyzer Manager Configuration" page to begin the test.
  4. In the charset drop-down list, select the desired charset. 
  5. Use the Ip Address and the Port linked to this charset to send your message to the LAW Simulator. 
  6. Don't forget to hit the "Refresh List" button after to have send your message. In this test, the Analyzer SUT queries the Analyzer Manager simulator for a WOS related to a specimen.
  7. 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.

30606 : LAW Analytical Work Order Step Broadcast (for Analyzer Manager)

This test concerns only the Analyzer Manager actor. You will need to communicate with the LAW Simulator (which is included in the Order Manager Simulator), in order to simulate the LAB-28 transaction of the LAW Profile.

Instructions

Access the LAW 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

In this test, the LAW Simulator will receive the AWOS from the SUT, saves all information and responds with an acknowledgment.

 

As the SUT implements the Analyzer Manager (Analyzer Manager acts as an initiator in this test) :

  1. First at all, check that the selected "Domain for testing" (at the bottom right of the page) is "Laboratory".
  2. You must be log in to be able to achieve this test.
  3. Then, go to the "Order Management" menu entry and choose "Analyzer", then "Analyzer Configuration" page to begin the test.
  4. In the "SUT Configurations" drop-down list, select the configuration matching the SUT.
  5. Use the Ip Address and the Port linked to this charset to send your message to the LAW Simulator.
  6. There are two different steps in this test.
    1.  
      1. Send a "new AWOS" message to the Analyzer. This message is used to broadcast the AWOS from your SUT to the Analyzer simulator.
      2. Don't forget to hit the "Refresh List" button after to have send your message.
      3. Check the simulator has properly received and acknowledged your message.
    1.  
      1. Send a "cancel AWOS" message to the Analyzer to cancel the AWOS sent in the first step.
      2. Don't forget to hit the "Refresh List" button after to have send your message.
      3. Check the simulator has properly received, and acknowledged your message.
    • First Step : Send "new AWOS" to the Analyzer simulator.
    • Second Step : Cancel the AWOS sent in the first step.

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

 

  • For all 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.
  • For the First Step :
    • In the OML^O33^OML_O33 message, the ORC-1 must be filled with "NW".
    • In the ORL^O34^ORL_O34 message, the ORC-1 must be filled with "OK" and ORC-5 with "SC" or "IP".
  • For the Second Step :
    • In the OML^O33^OML_O33 message, the ORC-1 must be filled with "CA".
    • In the ORL^O34^ORL_O34 message, the ORC-1 must be filled with "CR" and ORC-5 with "CA".

30607 : LAW Analytical Work Order Step Broadcast (for Analyzer)

This test concerns only the Analyzer actor. You will need to communicate with the LAW Simulator (wich is included in the Order Manager Simulator), in order to simulate the LAB-28 transaction of the LAW Profile.

Instructions

Access the LAW 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 reminded that if you are logged in your configurations will be private, otherwise it will be public. 

In this test, the LAW Simulator will be used to send to the SUT (System Under Test) an AWOS related to a specimen.

 

As the SUT implements the Analyzer (Analyzer acts as a responder in this test) :

  1. First at all, check that the selected "Domain for testing" (at the bottom right of the page) is "Laboratory".
  2. Create or update the configuration corresponding to the SUT.
  3. Then, go to the "Order Management" menu entry, choose "Analyzer Manager", and click on the "Analytical Work Order Step Broadcast" page to begin the test.
  4. In the SUT Configurations drop-down list, select the SUT configuration.
    1.  
      1. For the "Action to perform", select "Create a new order". 
      2. Select the patient to begin the test. Of course, you can create a new patient and a new encounter.(See the Order Manager user manual to have more information). 
      3. Once the patient and the encounter have been selected, go to the "Create specimen" panel and fill all required fields. It is possible to fill some fields randomly in hitting the "Fill with random values" button. 
      4. Hit the "create an order for specimen" button to save the specimen.
      5. Then, in the "Create order for current specimen" panel, fill all required fields. Once again, it is possible to fill some fields randomly in hitting the "Fill with random values" button.
      6. For the Result status, choose the value : "Final results: results stored and verified. Can only be changed with a corrected result.".
      7. At least, hit the "Add to current specimen and send message" button to send the order to the selected SUT.
      8. Check the simulator has properly received your acknowledgement message.
    1.  
      1. If you always are in the "Test Report" panel, hit the "Perform another test" button, otherwise return to the "Order Management" menu entry, choose "Analyzer Manager", and click on the "Analytical Work Order Step Broadcast" page.
      2. For the "Action to perform", select "Cancel an existing order".
      3. In the "Order Selection" panel, select the Order sent in the first step. You can use the filter option to search a specific Order.(See the Order Manager user manual to have more information). 
      4. A modal panel will ask you to confirm the order cancellation. Say "Yes". The LAW Simulator will send the cancellation order to the SUT.
      5. Check the simulator has properly received your acknowledgement message.
    • First Step : Create and send a new order.
    • Second Step : Cancel the AWOS sent in the first step.

The messages exchanged between the simulator and the SUT can be found in the message table on the very same page (see the "Test report" panel) 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

  • For all 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.
  • For the First Step :
    • In the ORL^O34^ORL_O34 message, the ORC-1 must be filled with "OK" and ORC-5 with "SC" or "IP".
  • For the Second Step :
    • In the ORL^O34^ORL_O34 message, the ORC-1 must be filled with "CR" and ORC-5 with "CA".

30608 : LAW AWOS Status Change (for Analyzer Manager)

 

This test concerns only the Analyzer Manager actor. You will need to communicate with the LAW Simulator (which is included in the Order Manager Simulator), in order to simulate the LAB-29 transaction of the LAW Profile.

Instructions

Access the LAW 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 reminded that if you are logged in your configurations will be private, otherwise it will be public.

In this test, the LAW Simulator will be used to send to the SUT (System Under Test) the test results.

 

As the SUT implements the Analyzer Manager (Analyzer Manager acts as a responder in this test) :

  1. Create or update the configuration corresponding to your system under test; go to SUT Configurations > HL7 Responders
  2. Then, go to Laboratory > Analyzer > [LAB-29] AWOS Status Change
  3. In the "SUT Configurations" drop-down list, select the configuration matching the SUT.
  4. Select a specimen to work on it. You can use the filter option to search a specific Specimen. (See the Order Manager user manual to have more information).
  5. In the "Specimen details" panel, you can Add an observation to this specimen (this is optional in this test). You will need to fill all required fields. For the "Observation result status" choose : "Final results". Then, hit the "Add observation to specimen" button.
  6. Now, in the "Related orders" panel, add an observation for each order. Hit the "related observations" link, then hit the "Add an observation to this order" button. You will need to fill all required fields. For the "Observation result status" choose : "Final results". Then, hit the "Add observation to order" button.
  7. Always in the "Related orders" panel, for each order, in the Status and Result Status columns : Update the "Status" to "Order is completed" and the "Result status" to "Final results" using the "Update" button.  
  8. Finally, hit the "Send Message" button. The LAW Simulator will send the message to the SUT.
  9. 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.

 

30609 : LAW AWOS Status Change (for Analyzer)

This test concerns only the Analyzer actor. You will need to communicate with the LAW Simulator (which is included in the Order Manager Simulator), in order to simulate the LAB-29 transaction of the LAW Profile.

Instructions

Access the LAW 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

In this test, the LAW Simulator will be used to respond to the SUT (System Under Test) query.

 

As the SUT implements the Analyzer Manager (Analyzer Manager acts as an initiator in this test) :

  1. First at all, check that the selected "Domain for testing" (at the bottom right of the page) is "Laboratory".
  2. You must be log in to be able to continue this test.
  3. Go to the "Result Management" menu entry and choose the "Analyzer Manager Configuration" page to begin the test.
  4. In the charset drop-down list, select the desired charset. 
  5. Use the Ip Address and the Port linked to this charset to send your message to the LAW Simulator.
  6. In this test, the Analyzer SUT needs to send test results related to a specimen.
  7. Don't forget to hit the "Refresh List" button after to have send your message.
  8. 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.

OM_MWL

In this test, the OrderManager tool is a DICOM Modality Worklist SCP, and your application (most commonly an Acquisition Modality actor) is the MWL SCU.

The test is a sanity check of your worklist query capabilities for pre-Connectathon testing.   In some cases, the Order Manager is used as a MWL SCP during a Connectathon, and this test helps prepare you for that.

Prerequisite

Refer to the OrderManager User Manual for instructions on creating a DICOM worklist.

Test Steps

As a MWL SCU in this test, your application will query the OrderManager (MWL SCP) for a worklist.

  1. First create a worklist entry in the Order Manager tool:
    1. TO CREATE A WORKLIST ENTRY FROM AN ORDER ALREADY IN THE TOOL: In the OrderManager, select menu Radiology-->Order Filler-->Create a DICOM worklist (or Eye care-->Order Filler-->Create a DICOM worklist).  Then select one order from the table of existing order entries
    2. TO CREATE NEW ORDER FOR A WORKLIST ENTRY: In the OrderManager, start by selecting  Radiology-->Order Filler-->[RAD-3] Create...orders (or Eye-->Order Filler-->[RAD-3] Create...orders).  Then proceed through the steps to create the order, schedule it, then create the worklist for your new order.
  2. You will be prompted to provide your application's "Station AE Title" prior to selecting the "Generate worklist" button
  3. Capture the "Permanent link" to your worklist details (ie the URL)
  4. Use your application to query the OrderManager for modality worklist 
  5. Create a screen capture from your application showing the worklist received.
  6. For your pre-Connectathon test results in gazelle, upload the screen capture file and copy the permanent link into the comment box as the results for this
    test.

Evaluation

The link to the worklist entry & the screen shot demonstrate that you have successfully received worklist.

 

OM_RAD-2-Receive

This tests the RAD-2 transaction from the point of view of the Order Filler as system under test.

In this test, we will check that your Order Filler is able to integrate the creation and cancellation of orders received from the OrderManager tool playing the role of the Order Placer actor. 

Prerequisite

  1. CONFIGURATION: Before beginning this test, do not forget to check that the configuration (IP address, port, application/facility names) of your system under test is entered within the OrderManager tool.  Use the "SUT Configurations" menu. 
  2. TEST PATIENT: Your Order Filler is assumed to be coupled with a ADT actor; that means that you should be able either to receive a new patient from an ADT or Patient Demographics Supplier actor.  To populate your system with a patient, use the PatientManager tool create a patient and an send ADT message to your system.  In the steps below, you will use that patient to create an order in the OrderManager.  Follow these  instructions for using PatientManager to create a patient that is then used by the OrderManager.

Refer to the OrderManager user manual and these details about sending RAD-2.

Test Steps

As a receiver in this test, your Order Filler shall be able to integrate all of the three message structures defined in the technical framework. As a consequence, you are asked to perform three steps.

1. Create a new order

In this step, your Order Filler proves its ability to accept and integrate an order creation sent by the Order Placer (ORC-1="NW") 

  1. Go to menu 'Radiology' or 'Eye care', then --> Order Placer --> [RAD-2] Create/Cancel orders
  2. Select your system under test in the drop-down list
  3. Select "Create a new order" as action to perform.  By default, you will get an HL7 v2.3.1 ORM.  If you want a HL7 v2.5.1 OMG messages, click that box.
  4. Select the patient for whom you want to create a order
  5. Fill the order and click on the "Send message" button
  6. Retrieve the permanent link to the test report and paste it into Gazelle Test Management as the results for this test.
  7. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

2. Cancel an existing order

In this step, your Order Filler proves its ability to accept and integrate an order cancellation sent by the Order Placer (ORC-1="CA") and to acknowledge it (with an ACK message).

  1. Go to Radiology --> Order Placer --> [RAD-2] Create/Cancel orders
  2. Select your system under test in the drop-down list
  3. Select "Cancel an existing order" as action to perform
  4. Select the  order to cancel and when the pop-up raises, click on the "Yes" button.
  5. Retrieve the permanent link to the test report and paste it in Gazelle.
  6. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

3. Stop the fulfillment of an order (DC)

In this step, your Order Filler proves its ability to accept the discontinue of an ongoing order sent by the Order Placer (ORC-1="DC") and to acknowledge it (with an ACK message).

  1. Repeat step 1. Create a new order
  2. On your Order Filler, starts processing the order. The Order Placer shall be notified that the order is "in progress": send a "Update Order Status" (RAD-3) message to the Order Placer actor of the tool (you will find its connection information under Radiology > Order Placer > Configuration). 
  3. Go to Radiology --> Order Placer --> [RAD-2] Create/Cancel orders
  4. Select your system under test in the drop-down list
  5. Select "Stop the fulfillment of an order (DC)" as action to perform
  6. Select the  order to discontinue and when the pop-up raises, click on the "Yes" button.
  7. Retrieve the permanent link to the test report and paste it in Gazelle.
  8. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

Evaluation

The permanent links to the test report & the screen shots demonstrate that you have successfully handled the received order messages.

OM_RAD-3-Receive

This tests the RAD-3 transaction from the point of view of the Order Placer as system under test.

In this test, we will check that your Order Placer is able to integrate the creation and cancellation of orders received from the Order Manager tool playing the role of the Order Filler actor. 

Prerequisite

  1. CONFIGURATION: Before beginning this test, do not forget to check that the configuration (IP address, port, application/facility names) of your system under test is entered within the Order Manager tool.  Use the "SUT Configurations" menu. 
  2. TEST PATIENT: Your Order Filler is assumed to be coupled with a ADT actor; that means that you should be able either to receive a new patient from an ADT or Patient Demographics Supplier actor.  To populate your system with a patient, use the Patient Manager tool create a patient and an send ADT message to your system.  In the steps below, you will use that patient to create an order in the Order Manager.  Follow these  instructions for using Patient Manager to create a patient that is then used by the Order Manager.

Refer to the Order Manager user manual.

Test Steps

As a receiver in this test, your Order Placer shall be able to integrate all of the three message structures defined in the technical framework. As a consequence, you are asked to perform three steps.

1. Create a new order

In this test, your Order Placer receives an ORM (v2.3.1) or OMG (v2.5.1) from the Order Manager acting as Order Filler.  You respond with an ORR (v2.3.1) or ORG (v2.5.1)

  1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-3] Create/Update/Cancel orders
  2. Select your system under test in the drop-down list
  3. Select "Create a new order" as action to perform.  By default, you will get an HL7 v2.3.1 ORM.  If you want a HL7 v2.5.1 OMG messages, click that box.
  4. Select the patient for whom you want to create a order
  5. Fill the order and click on the "Send message" button
  6. Retrieve the permanent link to the test report and paste it into Gazelle Test Management as the results for this test.
  7. Take a screenshot of your application as a proof of the good integration of the message (a new order). Upload it in Gazelle.

2. Cancel an existing order

In this test, your Order Placer receives an ORM-Cancel (v2.3.1) or OMG-Cancel (v2.5.1) from the Order Manager acting as Order Filler.  You respond with an ACK.

  1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-3] Create/Update/Cancel orders
  2. Select your system under test in the drop-down list
  3. Select "Cancel an existing order" as action to perform
  4. Select the  order to cancel and when the pop-up raises, click on the "Yes" button.
  5. Retrieve the permanent link to the test report and paste it in Gazelle.
  6. Take a screenshot of your application as a proof of the good integration of the message (a cancelled order). Upload it in Gazelle.

3. Update order status

In this test, your Order Placer receives an ORM-Status update (v2.3.1) or OMG-Status update (v2.5.1) from the Order Manager acting as Order Filler.  You respond with an ACK.

  1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-3] Create/Update/Cancel orders
  2. Repeat step 1. Create a new order to place a new order in your Order Placer
  3. Select your system under test in the drop-down list
  4. Select "Update order status" as action to perform
  5. Select the  order to updpate and when the pop-up raises, click on the "Yes" button.
  6. Retrieve the permanent link to the test report and paste it in Gazelle.
  7. Take a screenshot of your application as a proof of the good integration of the message (an updated order). Upload it in Gazelle.

 Evaluation

The permanent links to the test report & the screen shots demonstrate that you have successfully handled the received order messages.

 

OM_RAD-4_Rad-13-Receive

This tests the RAD-4 (Procedure Scheduled) and RAD-13 (Procedure Updated) transactions from the point of view of the Image Manager as system under test.

In this test, we will check that your Image Manager is able to integrate the scheduling and cancelllation of procedures received from the Order Manager tool playing the role of the Order Filler actor. 

You may use the Order Manager to send

  • RAD-4 and RAD-13:  HL7 v2.3.1 orders (SWF), or
  • RAD-4 and RAD-13:  HL7 v2.5.1 orders (SWF.b)

Prerequisite

  1. CONFIGURATION: Before beginning this test, do not forget to check that the configuration (IP address, port, application/facility names) of your system under test is entered within the Order Manager tool.  Use the "SUT Configurations" menu. 
  2. TEST PATIENT:   In the steps below, you will use a test patient to create and schedule an order in the Order Manager.  Follow these  instructions for using Patient Manager to create a patient that is then used by the Order Manager.

Refer to the Order Manager user manual.

Test Steps

As a receiver in this test, your Image Manager shall be able to integrate all of the message structures defined in the technical framework. As a consequence, you are asked to perform these four steps.

1. Procedure Scheduled [RAD-4]

In this step, your Image Manager proves its ability to accept and integrate a new scheduled procedure sent by the Order Filler.

  1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-4/13] Schedule/update procedures
  2. Select your system under test in the drop-down list
  3. Select "Procedure Scheduled" as action to perform.  
  • By default, you will get an HL7 v2.3.1 ORM.  If you want an HL7 v2.5.1 OMG messages, click that box.
  • Select an existing order in the tool, or create an order from scratch
  • Complete the "Scheduled Procedure Step" information and then select the "Send message" button
  • Retrieve the permanent link to the test report and paste it into Gazelle Test Management as the results for this test.
  • Take a screenshot of your application as a proof of the good integration of the message (eg. this may be evidence of a database entry). Upload it in Gazelle.
  • 2. Procedure update:  cancel order request (CA) [RAD-13]

    In this step, your Order Image Manager proves its ability to accept and integrate an order cancellation sent by the Order Filler (ORC-1="CA") and to acknowledge it.

    1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-4/13] Schedule/update procedures
    2. Select your system under test in the drop-down list
    3. Select "Procedure update: cancel order request" as action to perform.  
      1. By default, you will get an HL7 v2.3.1 ORM.  If you want an HL7 v2.5.1 OMI message, click that box. 
    4. Select the procedure to cancel and when the pop-up raises, click on the "Yes" button.
    5. Retrieve the permanent link to the test report and paste it in Gazelle.
    6. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

    3. Procedure update: discontinue order request (DC) [RAD-13]

    In this step, your Image Manager proves its ability to accept the discontinue of an ongoing order sent by the Order Filler (ORC-1="DC") and to acknowledge it.

    1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-4/13] Schedule/update procedures
    2. Select your system under test in the drop-down list
    3. Select "Procedure update: discontinue order request" as action to perform.  
      1. By default, you will get an HL7 v2.3.1 ORM.  If you want an HL7 v2.5.1 OMI message, click that box. 
    4. Select the procedure to cancel and when the pop-up raises, click on the "Yes" button.
    5. Retrieve the permanent link to the test report and paste it in Gazelle.
    6. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

    4. Procedure update: change order request (XO) [RAD-13]

    In this step, your Image Manager proves its ability to accept the procedure update/change order request (order still scheduled or in progress) sent by the Order Filler (ORC-1="XO") and to acknowledge it.

    1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-4/13] Schedule/update procedures
    2. Select your system under test in the drop-down list
    3. Select "Procedure update: change order request" as action to perform.  
      1. By default, you will get an HL7 v2.3.1 ORM.  If you want an HL7 v2.5.1 OMI message, click that box. 
    4. Select the procedure to cancel and when the pop-up raises, click on the "Yes" button.
    5. Retrieve the permanent link to the test report and paste it in Gazelle.
    6. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

    5. Procedure update: order has been completed (XO) [RAD-13]

    In this step, your Image Manager proves its ability to accept the procedure update/order completed sent by the Order Filler (ORC-1="XO") and to acknowledge it.

    1. Go to menu 'Radiology' or 'Eye care', then --> Order Filler --> [RAD-4/13] Schedule/update procedures
    2. Select your system under test in the drop-down list
    3. Select "Procedure update: order has been completed" as action to perform.  
      1. By default, you will get an HL7 v2.3.1 ORM.  If you want an HL7 v2.5.1 OMI message, click that box. 
    4. Select the procedure to cancel and when the pop-up raises, click on the "Yes" button.
    5. Retrieve the permanent link to the test report and paste it in Gazelle.
    6. Take a screenshot of your application as a proof of the good integration of the message. Upload it in Gazelle.

    Evaluation

    The permanent links to the test report & the screen shots demonstrate that you have successfully handled the received order messages.

    Preload_Codes_for_HL7_and_DICOM

    Introduction

    To prepare for testing workflow profiles in RAD, CARD, LAB, and EYECARE domains, and also for the ITI PAM Profile, it is helpful for systems that send HL7 messages (eg patient registration and orders) and/or DICOM messages (modality worklist, storage) to work with a common set of codes. 

    We ask ADT, Order Placer, Order Filler and Acquisistion Modality actors and PAM Patient Demographic & Encounter Supplier actors to load codes relevant to their system in advance of the Connectathon

    These codes include, for example:

    • Administrative sex codes in PID-8
    • Dcotors sent in PV1
    • Facility codes sent in HL7 PV1-3
    • Universal Service ID (order codes) sent in OBR-4
    • Priority codes sent in OBR-27 or TQ1-9
    • Acquisition Modality code sent in OBR-24 and (0008,0060)
    • ...and more

    Instructions

    The codes that you need depend on the profile/actors you support.  HL7 and DICOM codes used for Connectathon testing are the same set that is used in the Gazelle OrderManager tool. OrderManager contains simulators for some actors in workflow profiles.

    ** HL7 codes ** - are documented here:

    Some of these codes are also mapped into DICOM messages.  Use the spy-glass icon in the right column to view the value set for each code.  (Note that the format of these files is compliant with the IHE SVS Sharing Value Sets profile.)

    • ADT, Order Placer, and Order Filler plus PAM Supplier systems should review the link above and load codes relevant to the HL7 messages it supports

    ** DICOM codes ** - Order Filler and Acquisition Modality actors need a mapping between Requested Procedure codes, Scheduled Procedure codes, and Protocol Codes. 

    For RAD and CARD, that hierarchy is here: https://gazelle.ihe.net/common/order-manager/orderHierarchy4Radiology.xml   
    For EYECARE, that hierarchy is here: https://gazelle.ihe.net/common/order-manager/orderHierarchy4Eyecare.xml. (Note that this is documented in excel form here.)

    • An Order Filler system should load codes relevant to the domain(s) it is testing. 
    • An Acquisition Modality system should load codes relevant to the acquisitions it can perform. 

    Evaluation

    There is no evaluation for this 'test'.   If you do not load the codes you need on your test system prior to the Connectathon, you may find yourself wasting valuable time on the first day of Connectathon syncing your codes with those of your test partners.

    Preload_Codes_for_PLT

    Introduction

    To prepare for testing the ITI Patient Location Tracking (PLT) Profile, the PLT Supplier, Consumer and Supplier actors must use a common set of HL7 codes. 

    We ask these actors to load codes relevant to their system in advance of the Connectathon.

     

    Instructions

    The codes you need are identified in the peer-to-peer test that you will perform at the Connectathon.

    1.  In Gazelle Test Management for Europe or North America, find the test "PLT_TRACKING_WORKFLOW" on your main Connectathon page.

    2.  Read the entire test to understand the test scenario.

    3.  Load the codes for PV1-11 Temporary Patient Location.  These are in a table at the bottom of the Test Description section.

     

    Note:  These codes are are a subset of the HL7 codes used during Connectathon.  If you already performed pre-Connectathon test "PRELOAD_Codes_for_HL7_and_DICOM", then you already have these codes.

     

    Evaluation

    There is no evaluation for this 'test'.   If you do not load the codes you need on your test system prior to the Connectathon, you may find yourself wasting valuable time on the first day of Connectathon syncing your codes with those of your test partners.