This document describes testing requirements for the Imaging
Document Source actor in the IHE XDS-I.b integration profile. The
Imaging Document Source will perform tests using the XDS Toolkit
software from NIST and also ATNA security tests using the Gazelle
software. The test procedure includes:
Certain toolkit management functions are password protected and must be performed by the test administrator. Please follow these general instructions.
|User||Test Data||The Imaging Document Source tests use a specific set of
DICOM images. You will need to import these into your system
and use the correct images specified for each test. These
images specified in ids/ids_2018-4800.html.
|All||Configuration||The test cases require that the Imaging Document Source under test use specific values for patient identifiers, patient identifier assigning authority and repositoryUniqueID. These values is documented in ids/ids_2018-4800.html and also within the toolkit when you run the tests.|
|User||Configuration||Your Imaging Document Source will need to communicate with a Document Repository simulator. The detailed instructions below will tell you how to obtain the configuration information for the simulator.|
|User||Configuration||Provide test administrator with configuration parameters for your Imaging Document Source.|
|Admin||Configuration||Create a testing SESSION for this Imaging Document Source. The system under test should use only this SESSION and no others.|
|User||Instruction||Use only the testing ENVIRONMENT and testing SESSION assigned by the administrator when testing your Imaging Document Source. Do not test other actors using this testing SESSION.|
|User||Instruction||It is expected that the user will execute the tests and the administrator will review results when the tests are complete. The user may execute individual or all tests multiple times. Each time you execute a test, the toolkit will overwrite the previous results in the test SESSION for that test.|
Instructions for individual tests are stored in the toolkit. The links below provide static copies of the documentation that do not rely on toolkit access.