XDS - IHE

IHE Radiology Technical Framework Supplement - XDS-I.b______________________________________________________________________________# Issue/ (Answer)7 At some point there will likely be a need/desire to address Web services-based transferprotocols for images in coordination with DICOM WG10 and ITI. Are there benefits ofupgrading XDS-I to use current XDS.b transport mechanisms without replacing theDICOM object retrievals with their to-be-developed web services counterparts?Answer: T he current version of the supplement includes an approach for a web servicesbased DICOM image retrieval. This new transaction is required to be supportedby the Imaging Document Source Actor.8 Are the added profile dependency on ATNA/ Radiology Option and the correspondingupdate made to RAD TF-1: 18.6 adequate specifications for the security requirements(beyond what is already listed in and RAD TF-1: Appendix H)?Answer: The current specification is believed to be adequate9 What is the most effective way to reference ITI‟s XDS (XDS.a/ XDS.b) profiles,especially considering that XDS.b has not yet been folded in the ITI TF (e.g., §4.54.4.1)?Answer: The current Final Text ITI TF makes appropriate references to the XDS.b TISupplement, thus referring to XDS (or XDS.b) via the main ITI TF and its correspondingsections is appropriate and adequate.10 Should the „Referenced Standards‟ section of the Provide and Register ImagingDocument Set transaction (4.54.3) include actual references, or instead just refer to ITITF-2:3.41.3 - the References section for the ITI-41 transaction. That way if ITI makeschanges, the RAD transaction just inherits them.Answer: A reference is made to the XDS.b Referenced Standards section and only theradiology-specific standards are explicitly listed.11 The Provide and Register Imaging Document Set transaction (RAD-54) includes copiesof the metadata tables included in the ITI Framework with updates / overrides to a subsetof the attributes (mostly in the source/ value of the attribute). In some cases, it is theDocument Repository‟s responsibility to fill/ populate the attribute, but the DocumentRepository is not strictly part of the XDS-I profile. In addition, the expected actionsdescribe some required behaviors of the Document Repository. Is there a better way todocument this information without losing too much contextual information?Answer: The RAD-54 transaction is being retired and replaced by a new RAD-68transaction based on XDS.b’s Provide and Register Document Set-b. The new RAD-68transaction is written to specify only “delta requirements” and makes liberal use ofreferences to the baseline ITI transaction. The new transaction (RAD-68) is named:“Provide and Register Imaging Document Set – b”.__________________________________________________________________________Rev. 1.1 - 2009-06-215Copyright © 2009: IHE International