Conformance XDSI Imaging Document Source DICOM Instances
This page describes IHE conformance tests for the Imaging Document Source actor in the XDS-I.b Integration Profile. The tests on this page only cover the DICOM Instances option. Further, the tests are limited to retrieval of images from the Imaging Document Source using the RAD-55 (WADO) and RAD-69 (SOAP) transactions. Traditional DICOM Retrieve transactions are not included.
There are two classes of tests. Both submission tests and retrieval tests are described below.
The Imaging Document Source is given multiple imaging studies and asked to create and submit the DICOM KOS object for each imaging study. The tests require that one KOS object is submitted per imaging study. Once the KOS objects are submitted, the validation software reviews the submitted files and tests both the XDS.b metadata associated with each file as well as the content of the KOS objects themselves.
The retrieval tests rely on the same image sets used for the submission tests. As part of the submission process, the Imaging Document Source would naturally make those images available for retrieval through RAD-55 (WADO) or RAD-69 (SOAP). Tests for RAD-16 transactions (DICOM Retrieve) have been removed in the 2018 version.
There are tests in this category that send retrieve requests and expect the Imaging Document Source under test to return the images successfully. There are also tests in this category that exercise error conditions such as missing UIDs in the request.
The test image dataset consists of DICOM images with patient identifiers that are considered departmental identifiers. These are the identifiers stored in the DICOM element (0010,0020). There is no reason to modify the images in the DICOM objects unless your software coerces those values.
There are also patient identifiers for the Affinity Domain defined for the testing infrastructure. Each test will tell you the proper patient identifier to use. You must use the specified identifier (for the Affinity Domain). The patient identifier for the Affinity Domain is not the same as the departmental identifier inside the DICOM image.
The tests do not expect you to place the Affinity Domain patient identifier inside the DICOM images.
-
Retrieve the set of test images: ftp://ftp.ihe.net/Connectathon/test_data/RAD-profiles/XDS-I.b_test_data/ids_20180830.zip. You will not need to import all of them. The test instructions will tell you which imaging studies you will need to submit as part of testing.
-
Access the XDSToolkit server that is designated for testing imaging actors.
-
For Connectathons, use http://xds-imaging-tools
-
For other testing, contact the testing manager for the proper URL
-
-
Define your Imaging Document Source as a system in the test software. Use following naming convention: organization-sut__ids.
-
Define a test session for your system. Follow the naming convention: organization-ids 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 Imaging Document Source 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 Imaging Document Source to use the simulators that are defined.
-
Configure your system to use the Repository Unique Id that is listed in the Imaging Document Source tab of the Conformance Test pane. You cannot define your own value. Your KOS object will need to contain this value.
-
Import the images into your system using a mechanism you define.
You are now ready to run the test cases.
We recommend that you run the submission tests individually as the first step. That will ensure that you are using the proper endpoint and that the testing software finds your submitted KOS object.
Once you have successfully completed the submission tests, you can run the retrieval tests individually or you can run all of the tests as a batch.
When you activate the run button for a submission test, the testing system examines the repository simulator and searches for the KOS object that you have submitted. The testing system looks for the most recent version (by patient identifier) and does not delete any KOS objects that you have submitted. Therefore, you can submit a KOS object one time and run the submission validation test(s) multiple times.
Each time you run a retrieve test, the test software does remove the prior retrieve results and sends a new request to your Imaging Document Source. Retrieve tests do not disturb the KOS objects you submitted to the repository simulator.
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.
The Imaging Document Source 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 the first two tests fail but other 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.
