This document captures the list of steps needed to execute an ITB test using the Patient Manager (simulator) application.
For ITB Test Execution, we will be using two PatientManager instances, each deployed on a different server. These systems will be configured as GATEWAY_OR1 and GATEWAY_OR2 in Gazelle TM.
GATEWAY_OR1 (deployed on Server A)
This will be the initiating SUT that will submit the PIX Feed. This instance of PatientManager cannot be deployed on same server as Gazelle Proxy.
GATEWAY_OR2 (deployed on Server B)
The responding SUT will be the PIX Manager. This instance of PatientManager can be deployed alongside Gazelle TM and Gazelle Proxy (but does not have to be).
PatientManager configuration on Server B
1.1 On the responding PatientManager instance deployed on Server B, click on “Administration / HL7 Responders’ configuration” menu link.
1.2 Verify that PDQ and PIX Manager actor IP addresses and ports are configured as highlighted below. These are the default ports in Patient Manager for these actors. The IP address of 127.0.0.1 means that these actors are running locally which is correct. If these values are different for you, you’ll need to edit these rows to match these values. On this screen, it’s ok to use the loopback address (127.0.0.1).
Gazelle TM configuration on Server B
2.1 On Server B, log into Gazelle TM using the admin credentials.
2.2 Click on the “Configurations / All Configurations” menu item.
2.3 Filter for “GATEWAY_OR2” in the system dropdown. GATEWAY_OR2 will be the responding PatientManager on Server B.
2.4 Verify that the IP address and ports in black font match the values from this step 1.2 Note that it’s best to use the actual IP address of the machine where the responding Patient Manager is installed (Server B) and not the loopback address (127.0.0.1). You can focus on the rows highlighted in red. Ignore the other rows. If the ports or IP addresses are incorrect then edit the row. Note that after editing the row, the proxy ports (in red font) will likely change dynamically. Take a snapshot of your screen after you’ve made your edits as you’ll need the IP address and Proxy port (red) for later steps.
To change the IP address of the “host” that Server B (GATEWAY_OR2) represents, you would need to follow the steps below:
2.4.1 As admin user, click on “Administration / Manage / Configurations / Manage hosts’ configurations” menu item.
2.4.2 Click on the Edit button for OR2:
2.4.3 Change the IP address to the actual IP address of Server B. Do not use loopback address (127.0.0.1). Click on Save.
Follow steps 2.4.1 – 2.4.3 for OR1 system. This time you would be changing the IP address to IP address of Server A.
Create test instance
3.1 Log out of Gazelle and log back in as tuser1/tuser1. This is the user representing the organization in control of GATEWAY_OR1.
3.2. Click on the “Interoperability Dashboard” menu link:
3.3. Filter for GATEWAY_OR1 in the system dropdown:
3.4. Filter for PAT_IDENTITY_SRC in the Actor dropdown:
3.5. Click on the plus sign next to ITB_PIX_FEED to start the “New Test Instance” wizard:
3.6. Click the plus sign, then move “GATEWAY_OR2” to the right, and then click on “Add Selected Partners” button:
3.7. Click the play button highlighted in red to create the test instance:
3.8. Leave your current browser window and open a new browser window for the rest of the steps.
4.1 On the initiating Patient Manager instance installed on Server A, click on “SUT Configurations” menu link. Verify that the IP address and ports match the values from step 2.4 i.e. the IP address of the Server B (where the Proxy is installed) and the Proxy ports waiting for messages to be intercepted and forwarded to responding Patient Manager. The ports on this step need to match the Proxy ports (in red) in step 2.4 and NOT the ports in black font. If they don’t match, then click on Edit button and correct them.
4.2. On the same initiating Patient Manager UI, click on the ITI-8 menu link
4.3. Select “Patient Manager” in the SUT dropdown:
4.4. Verify that the IP address and port matches the IP address and Proxy Port (red) values from step 2.4 for PIX Manager. Then click on “generate patient” radio button. Then click on “Generate patient” button.
4.5. Click on “Fill in the encounter with random data” on the same screen:
4.6. Click on the “Send” button.
4.7. The execution might take a minute or so. You should see the “Execution status” progress from Waiting Initiated Completed on your first browser window:
10. Validation Context
Notice in the Test Instance screen above that the Configuration column cells for Sending and Receiving Actors are empty. No Validation Context files have been configured yet. Validation Context files allow for more content validation using NIST Validation services. You can upload Validation Context files as a Test Editor user on the Test Definition screen and recreate/re-execute a new test instance: