XDS - IHE

IHE Radiology Technical Framework Supplement - XDS-I.b______________________________________________________________________________Modify RAD TF-1:18 as follows18 Cross-eEnterprise Document Sharing for Imaging (XDS-I.b)Integration Profile200205210215220225230IMPORTANT: The Cross-Enterprise Document Sharing for Imaging (XDS-I) IntegrationProfile (originally found here) has been deprecated and is replaced by a functionallyequivalent profile called Cross-Enterprise Document Sharing for Imaging (XDS-I.b), whichis described in the remainder of this section.The Cross-Enterprise Document Sharing (XDS) Profiles in the IHE IT Infrastructure Domainprovides a solution for sharing (publishing, finding and retrieving) documents across a group ofaffiliated enterprises. The XDS for Imaging (XDS-I.b) Profile, defined here, extends andspecializes the mechanisms defined by XDS.b to support imaging “documents”, specificallyincluding the following:Imaging studies that include images acquired on a broad range of different modalities,as well as evidence documents (e.g. post-processing measurements/analysisoutcome), and presentation states.Diagnostic reports resulting from the interpretation of one or more related imagingstudies provided in a ready-for-display formA selection of diagnostically significant images associated with the report content.These document types along with the actor capabilities required to share them are defined by thisprofile.Since the XDS for Imaging (XDS-I.b) Profile depends on and extends the IT InfrastructureXDS.b Profile including the use of terms defined in XDS (e.g., XDS aAffinity dDomain,submission set, etc.) the reader of XDS-I.b is expected to have read and understandsunderstood the XDS Profiles (See ITI TF-1: 10). The XDS-I.b specification does not repeatrequirements and text for the XDS-defined Actors Document Repository, Document Registry,and Document Consumer, and does not place any new requirements on these actors.Both the XDS.b and XDS for Imaging (XDS-I.b) Profiles are not intended to address all crossenterpriseEHR communication needs. Many scenarios may require the use of other IHEIntegration profiles, such as Patient Identifier Cross-Referencing (PIX), Audit Trail and NodeAuthentication (ATNA), Enterprise User Authentication (EUA), Cross-eEnterprise UserAuthentication (XUA) and Retrieve Information for Display (RID). Other scenarios may be onlypartially supported, while still others may require future IHE Integration profiles, which will bedefined by IHE as soon as the necessary base standards are available. Specifically:1. The operation of any XDS-I Clinical XDS Affinity Domain will require that a propersecurity model be put in place. It is expected that a range of security models should be__________________________________________________________________________Rev. 1.1 - 2009-06-2112Copyright © 2009: IHE International