XDS-I.b_Prepare_Manifests

Introduction

This test is for Imaging Document Source actors in the XDS-I.b and XCA-I Profiles that support the "Set of DICOM Instances" option.  If your Imaging Document Source only supports PDF or Text Reports, then this test does not apply to you.

In Connectathons prior to 2019, Imaging Document Source actors created and submitted manifests for their own image set(s).   You will be able to do this for other XDS-I.b peer-to-peer tests during the Connectathon.  However, for this test, we ask you to create manifests for 3 studies that Connectathon Technical Managers provide.  This enables us to check both the metadata and manifest for expected values that match data in the images and in Connectathon affinity domain codes (i.e. codes.xml).

The manifests you create for these 3 studies will be used for some XDS-I/XCA-I tests during Connectathon week.

Location of the studies

There are three DICOM studies available.  The Imaging Document Source must load these three studies onto its system.  

Summary of the DICOM studies

For Connectathon testing purposes, we treat as individual imaging studies for one patient who has been imaged in three different affinity domains.  This helps facility cross-community testing in XCA-I.

The contents of the 3 studies are summarized in the "XDS-I,b XCA-I and WIA studies" google spreadsheet.  

Please review all 3 tabs:

  1. Identifies values in key attributes in the DICOM header for each study.  
  2. Identifies values in key attributes in the XDS-I Manifest (DICOM KOS) for each study
  3. Identifies values in the key XDS Metadata attributes when the Imaging Document Source submits the manifest to an XDS-I Repository (using RAD-68)

Patient IDs to use in the XDS Metadata for the Manifests

The Patient ID in the DICOM headers for the images is considered the 'local' or 'departmental' Patient ID, (ie sourcePatientId in the documentEntry metadata for the manifest). When the Imaging Document Source submits a Manifest for these studies to an XDS Repository/Registry, documentEntry.patientId must contain the affinity domain ID for the patient.

For XDS/XCA testing, we use Patient IDs that are included in the Connectathon Patient Demographics pre-loaded onto each Registry and Gateway at Connectathon, and onto the NIST XDS Tools Registry, as follows:

For the DX study with "local" Patient ID C3L-00277, the affinity domain Patient IDs is:

  • IHERED-2737^^^IHERED&1.3.6.1.4.1.21367.13.20.1000&ISO

For the CT study with "local" Patient ID C3N-00953, the affinity domain Patient IDs is:

  • IHEGREEN-2737^^^IHEGREEN&1.3.6.1.4.1.21367.13.20.2000&ISO

For the CT study with "local" Patient ID TCGA-G4-6304, the affinity domain Patient IDs is:

  • IHEBLUE-2737^^^IHEBLUE&1.3.6.1.4.1.21367.13.20.3000&ISO

 

Instructions

Prior to the Connectathon, the Imaging Document Source should:

  1. Load the 3 DICOM studies onto its test system. They are stored in a zip file here:  IHE Documents > Connectathon> test_data> RAD-profiles > XDS-I.b_test_data
  2. Construct 3 XDS-I Manifests, one for each of the studies identified above 
  3. In the Samples area of Gazelle Test Management, for one of the DICOM Manifests:
    • On the "Samples to share" tab, find the entry for "XDS-I_Manifest"
    • Upload the .dcm file for your manifest
    • Under "Actions", use the green triangle icon the validate your manifest using Gazelle EVSClient.  We expect a validation result with no errors.

 

Evaluation

Evaluation of the manifest will not be performed until Connectathon, but we encourage the Imaging Document Source to  read this evaluation now to ensure its manifest will pass verification during Connectathon.  There are two verifications that Connectathon Monitors will perform: (1) examine the DICOM Manifest for the study, and (2) examine the metadata for the submitted manifest

(1) MANIFEST CHECK:

The Connectathon Monitor will examine the XDS-I Manifest that the Imaging Document Source uploaded into Gazelle Test Management.    The evaluation of the manifest is based on the requirements in RAD TF-2: 4:68.4.1.1 "Manifest KOS Document"

Find the manifest:  Choose Gazelle Test Management menu Testing-->Sample Repository.  Then use the "Object Types" dropdown list to filter the entries for "XDS-I_Manifest".  Find an entry for the Imaging Document Source under test with an uploaded DICOM manifest. 

First:  Within the sample you can call the EVSClient (green triangle) and examine the attributes in the Manifest and perform validation.  We expect no errors.

Next:   Using the DICOM dump in EVSClient examine the attributes in the DICOM Manifest.  Verify the values in the attributes using Tab 2 of the "XDS-I.b XCA-I and WIA studies" sheet. 

  • Column 1 identifies the attributes for the monitor to examine. 
  • The remaining columns contain guidance on what is expected in each attribute.   Note that all 3 studies are in the spreadsheet, but the Monitor is only examining one Manifest created by the Imaging Document Source.


 

(2) METADATA CHECK:

TThe Connectathon Monitor will examine the XDS metadata for the DICOM Manifest submitted by the Imaging Document Source to the NIST XDS Tools (deployed at the Connectathon). Evaluation of the metadata is based on the requirements in RAD TF-2: 4:68.4.1.2.3.2 "DocumentEntry Metadata"

The monitor will examine the metadata using the NIST XDS Tools --> under "Connectathon Tools" and "XDS.b_Doc_Source_Stores_Document".  The SubmissionSet.uniqueId value (provided by the Imaging Document Source at Connectathon) will to help the monitor find the metadata in the tool.    

In this first version of the test, we manually examine attributes.  We anticipate a tool will do this in the future:

The monitor will examine the metadata in the NIST XDS Tool for both submitted manifests, using Tab 3 of the "XDS-I.b XCA-I and WIA studies" sheet to evaluate the metadata:

  • Column 1 identifies (a subset of of the) metadata attributes to evaluate.  We focus on attributes that have 'special' requirements for XDS-I in [RAD-68].
  • Column 2 documents where the values come from
  • Column 3 identifies values we expect in the metadata for the manifest for the DX study
  • Column 4 identifies values we expect in the metadata for the manifest for the CT study