Conformance XCAI Responding Imaging Gateway
This page describes IHE conformance tests for the Responding Imaging Gateway actor in the XCA-I Integration Profile.
There are several classes of tests, and these are described below.
These are tests where the Responding Imaging Gateway is retrieving images from a single Imaging Document Source.
In these tests with a single Imaging Document Source, the retrieve parameters are varied to make sure that the Responding Imaging Gateway processes those parameters correctly. Some tests are success cases. Other tests exercise error cases.
There are tests where the Responding Imaging Gateway needs to distribute a single request to multiple Imaging Document Sources, consolidate the results, and return those results to the requesting simulator. These tests include both success and error cases.
Your Responding Imaging Gateway will retrieve data from three Imaging Document Source simulators: E, F and G. Your system will also be sent requests for a fourth Imaging Document Source as an error condition. Do configure your Responding Imaging Gateway to recognize simulators E, F and G per the table below.
| Community | Entity | Identifier Type | Identifier Value |
|---|---|---|---|
| D | Community | homeCommunityID | urn:oid:1.3.6.1.4.1.21367.13.70.201 |
| D | Imaging Doc Source (E) | Repository Unique ID | 1.3.6.1.4.1.21367.13.71.201.1 |
| D | Imaging Doc Source (F) | Repository Unique ID | 1.3.6.1.4.1.21367.13.71.201.2 |
| D | Imaging Doc Source (G) | Repository Unique ID | 1.3.6.1.4.1.21367.13.71.201.3 |
The endpoints of the simulator actors are tied to the session name you defined. When you create the test environment in the Conformance Test pane, it will tell you the URLs of the simulated actors.
Notes on Simulator Endpoints
- March, 2021: All traffic to the simulators is routed through a proxy. The URL of all simulator endpoints should begin with http://tools.iheusa.org/xds-imaging.
- March, 2021: No TLS configuration is available.
-
Access the XDSToolkit server that is designated for testing imaging actors.
-
For Connectathons, use http://tools.iheusa.org/xds-imaging
-
For other testing, contact the testing manager for the proper URL
-
-
Define a test session for your system. Follow the naming convention: organization-rig where organization is a short name. Do not use any spaces in the test session.
-
Define your Responding Imaging Gateway as a system in the test software.
xxxx!
Follow the naming convention: organization-sut__rig where organization is a short name.
Do not use any spaces in the test session. -
Select the Conformance Tests link in the toolkit.
-
In the selection widget at the top right part of the Conformance Test pane, make sure you select the proper test session and your system as the system under test.
-
Select the Responding Imaging Gateway tab in the Conformance Test pane.
-
If not already done, activate the button to create the simulator environment for your system. Simulator names and URLs are tied to your session name (hence, the naming convention above).
-
Configure your Responding Imaging Gateway to use the simulators that are defined.
-
Configure your system to use the homeCommunityId that is listed in the Responding Imaging Gateway tab of the Conformance Test pane. You cannot define your own value.
You are now ready to run the test cases.
We recommend that you run the Single Image, Single IDS test as the first step. That will ensure that you are using the proper endpoint and that the test system is operating properly.
Once you have successfully completed the Single Image, Single IDS test, you can run the remaining tests individually or you can run all of the tests as a batch.
Each time you run a test, the test software does remove the prior result and sends a new request to your Responding Imaging Gateway. Running test A should not disturb the results from test B.
The Responding Imaging Gateway tools use the standard results page introduced in the XDSTools4 version of software. The screen capture below shows an example of a set of tests where all tests are completed successfully. All individual tests need to succeed.
The arrows in the screen capture highlight the button to run all tests as well as the Test Context frame.
