Imaging Document Source (2018): Read This First

The System Under Test (SUT) is an Imaging Document Source.

The tests assume a standard testing procedure:

  1. The Imaging Document Source imports the test images and does not change patient identifiers, accession numbers or unique identifiers. The tests will fail if the Imaging Document Source modifies those elements within the images.
  2. The Imaging Document Source maps the departmental identifiers to the identifiers identified by the Affinity Domain (see individual tests for values). The test tools do not provide a mapping service.
  3. The Imaging Document Source generates a KOS object for each imaging study and submits that KOS object via a Provide and Register Imaging Document Set (RAD-69) transaction to a Repository/Registry simulator that is dedicated to the Imaging Document Source.
  4. The test software retrieves each imaging study using these mechanisms defined by the XDS-I profile:
  5. The DICOM C-Move retrieve mechanism is not tested.

You need to configure your Imaging Document Source to communicate with the simulators listed in the conformance testing tool. If you are reading this document as a standalone document, that configuration is not available to you.

The tests for an Imaging Document Source use a fixed set of images as input data. Each imaging study is identified by a department identifier (DICOM Patient ID (0010,0020)) and possibly by an Accession Number (0008, 0050). It is the responsibility of the Imaging Document Source to map the departmental identifier to the Affinity Domain identifier specified in the test cases.

You will find the image data set here:

Do not use your own images. The tests are designed to use specific images and values from the image headers.

The XDS-I.b profile makes no comment on changing the headers on the original image sets. This test software assumes an environment where the customer requires that the Imaging Document Source does not change the values for Patient Identifier, Patient's Birth Date, Patient Sex and Accession Number.

Configuration Requirements

Key
Comment
Repository Unique ID
Test software requires that you configure to use this value:
1.3.6.1.4.1.21367.13.80.110
See below for implications on KOS object.

DICOM Fields of Interest in KOS Object

Attribute Name Tag Comment
Patient Name 0010,0010 Should not change, but would not be surprised by format differences (e.g., extra ^ symbols)
Patient ID 0010,0020 Shall not change.
Patient's Birth Date 0010,0030 Shall not change.
Patient's Sex 0010,0040 Shall not change.
Accession Number 0008,0050 Shall not change.
Study Instance UID 0020,000D Shall not change.
Series Instance UID 0020,000E Shall not change in images.
KOS object shall be in a new series with a new Series Instance UID.
Retrieve AE Title 0008,0054 Shall be present in KOS Referenced Series Sequence.
No specified value required.
Retrieve Location UID 0040,E011 Shall be present in KOS Referenced Series Sequence.
Test configuration specifies this value: 1.3.6.1.4.1.21367.13.80.110

XDS Metadata Values

The tables below list metadata values evaluated by the testing procedure. Some metadata values are defined by the Affinity Domain. In these tests, we have defined what we think are reasonable values and ask you to use those values. We will point out the metadata values that are defined by the XDS-I.b profile and those that are specific to the test environment. Metadata values required by XDS-I or XDS that are not listed in the table below shall be present and encoded properly. If they are not explicitly listed, you are at liberty to use your own values.

Document Entry Metadata Requirements

The table below contains Document Entry requirements based on RAD TF 3:4.68.1.2.3.2.

Attribute Requirement Reference
creationTime Not tested
eventCodeList
  • System under test includes all eventCode items required by RAD-68 transaction. See Acquisition Modality and Anatomic Region.
  • System under test does not include other eventCode items not found in the image set.
RAD TF 3:4.68.1.2.3.2
formatCode code: 1.2.840.10008.5.1.4.1.1.88.59
codingScheme: 1.2.840.10008.2.6.1
string: Key Object Selection Document
RAD TF 3:4.68.1.2.3.2
mimeType application/dicom RAD TF 3:4.68.1.2.3.2
referenceIdList
  • Contains at least one value with DICOM Accession Number (0008, 0050).
  • Format of the value is defined in RAD-68 transaction (see Reference).
  • Test configuration specifies this OID for Assigning Authority: 1.3.6.1.4.1.21367.13.202.2000
  • Other referenceIdList values are ignored.
RAD TF 3:4.68.1.2.3.2
serviceStartTime
  • Value for serviceStartTime is tested but only reported as a warning.
  • RAD-68 transaction provides a suggested method, but this is not a requirement.
  • If the value supplied by system under test does not use this value, we will report a warning
  • Software has one test for date (YYYYMMDD) and a separate test for date/time (YYYYMMDDhhmm)
  • Any precision beyond minutes is ignored
RAD TF 3:4.68.1.2.3.2
sourcePatientInfo Not tested
typeCode Specific to the test case. See notes below on typeCode. Selected by test authors from a set of LOINC codes
uniqueId Shall equal KOS SOP Instance UID RAD TF 3:4.68.1.2.3.2

The table below contains Document Entry requirements based on ITI TF 3:4.3.1

Attribute Requirement Reference
classCode code: IMAGES
codingScheme: 1.3.6.1.4.1.19376.1.2.6.1
string: Images
Selected by test authors.
confidentialityCode code: R
codingScheme: 2.16.840.1.113883.5.25
string: restricted
Selected by test authors from HL7 value set.
creationTime No specific value
entryUUID No specific value
formatCode See RAD-68 requirements
healthcareFacilityTypeCode code: 35971002
codingScheme: 2.16.840.1.113883.6.96
string: Ambulatory care site
Selected by test authors.
languageCode No specific value
mimeType See RAD-68 requirements
objectType
  • objectType shall be Stable
  • UUID for objectType shall be urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1

patientId Specific to the test case. See notes below on format. Selected by test authors.
practiceSettingCode code: Practice-A
codingScheme: 1.3.6.1.4.1.21367.2017.3
string: Radiology
Selected by test authors from a value set defined by test authors
sourcePatientInfo See RAD-68 requirements
typeCode See RAD-68 requirements
uniqueId See RAD-68 requirements

Notes on Document Entry Metadata

DocumentEntry.PatientId
Use the following value for the Assigning Authority for the patient identifiers in the XDS Affinity Domain:

1.3.6.1.4.1.21367.2005.13.20.1000
Patient identifiers will be of the following form (ignoring escaping for XML)
ABCXYZ^^^&1.3.6.1.4.1.21367.2005.13.20.1000&ISO
Please follow test instructions to use the proper patient identifier as well as format.

DocumentEntry.typeCode
This quote is taken from Rad TF 3:68.4.1.2.3.2

This attribute shall be populated by the XDS-I Imaging Document Source from a code in the Procedure Code Sequence (0008,1032) of the performed procedure with which the document is associated. In certain special cases previously defined in other IHE Profiles some sort of user intervention will be necessary to select the single Procedure Code used to populate this attribute. For example, handling the Group Case as defined in Scheduled Workflow will require the user to select a single, pre-coordinated procedure code that represents the multiple Requested Procedures that were acquired as a single study.

If you parse the paragraph above very closely, you could interpret the intent as the Imaging Document Source will map codes from Procedure Code Sequence (0008,1032) to a value that is placed in DocumentEntry.typeCode. These tests make a simplifying assumption that you can copy the (single) Procedure Code to the DocumentEntry.typeCode. Future test versions may require you to actually perform such mapping. We need to consult with the IHE Radiology Technical Committee.

Configure Your System to Use These OIDs

These are described above and are repeated for completeness.

Usage Value
Assigning authority for Accession Number 1.3.6.1.4.1.21367.13.202.2000
Assigning authority for Patient Id 1.3.6.1.4.1.21367.2005.13.20.1000
Repository Unique ID
1.3.6.1.4.1.21367.13.80.110