XDS - IHE

IHE Radiology Technical Framework Supplement - XDS-I.b______________________________________________________________________________XDSDocumentEntryAttributesourcePatientInfotypeCodetypeCodeDisplayNameuniqueIdXDS-I.b-specific RequirementsAs an example, the Imaging Document Source could take the value of Study Date(0008,0020) and Study Time (0008,0030) from the associated DICOM studyThis attribute shall represent the Patient demographics information used in the ImagingDocument Source actor system to identify the patient.This attribute allows multiple values for different pieces of patient demographics, seemetadata specification of the IHE ITI XDS Integration Profile (Table 4.1-5 in ITI TF-2:4.1.7).As an example, this information can be transformed from DICOM Patient‟s Name(0010,0010), Patient‟s Birth Date (0010,0030), and Patient‟s Sex (0010,0040).This attribute shall be populated by the source actor from a coding system of the RequestedProcedure Code of the Requested Procedure, to which the document is associated. In certainspecial cases previously defined in other IHE Profiles some sort of user intervention will benecessary 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 selecta single, pre-coordinated procedure code that represents the multiple Requested Proceduresthat were acquired as a single study.The coding system of the Radiology Imaging Requested Procedure Code will be designatedby the XDS Affinity Domain and shared by all Imaging Document Sources in the XDSAffinity Domain.This attribute shall be filled by the source actor using the code meaning text of thecorresponding Requested Procedure Code valued in typeCode.This attribute shall contain the Document unique ID generated by the source actor. It shallbe an ISO OID.For a DICOM Manifest document, this attribute value shall be the same as the SOPInstance UID of the corresponding DICOM KOS object. In the event that any informationin the manifest changes and it needs to be resubmitted from the Imaging Document Sourceto the Document Repository, the Imaging Document Source shall generate a new SOPInstance UID for the DICOM KOS object to ensure that its submission to the Repositorywill succeed.For a CDA wrapped text report, this value shall be formulated from the HL7 CDA R2header as follows:ClinicalDocument/id@root.ClinicalDocument/id@extension4854.68.4.1.2.3.3 Transformation of DICOM VR to XDS Document Metadata DataTypesA number of XDS document metadata attributes use HL7 data types for value representation.Some of the metadata attributes may be transformed from data elements of the correspondingDICOM SOP Instance. In this section, transformations of DICOM VR (Value Representation) tothe HL7 data types used in XDS metadata are described.__________________________________________________________________________Rev. 1.1 - 2009-06-2125Copyright © 2009: IHE International