| RAD68 | RAD68-001 | to delete | Testable |
1
|
1
| | The Imaging Document Source is instructed to submit a set of one or more new imaging documents for sharing. | 472 | Section 4.68.4.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| RAD68 | RAD68-002 | to delete | Testable |
0
|
1
| | A previously submitted document or the contents of a previously submitted manifest changes, requiring the Imaging Document Source to submit an update. | 472 | Section 4.68.4.1.1 | 3/15/24 2:33:35 PM by vhofman |
|
| RAD68 | RAD68-012 | reviewed | Testable |
1
|
1
| Imaging Document Source set to NONE | The Imaging Document Source shall support shared reports in at least one of the following formats: CDA Imaging Report with Structured Headings, CDA Wrapped Text Report or PDF Report. | 474 | Section 4.68.4.1.2.2 | 11/22/23 2:50:41 PM by vhofman |
|
| RAD68 | RAD68-015 | reviewed | Testable |
0
|
1
| Imaging Document Source set to NONE | Hyperlinks that reference images from reports shall be formatted as a DICOM WADO URI, using https. | 475 | Section 4.68.4.1.2.2 | 3/15/24 2:33:35 PM by vhofman |
|
| RAD68 | RAD68-016 | reviewed | Testable |
1
|
1
| Imaging Document Source set to NONE | The Imaging Document Source is required to ensure that image references are valid links. | 475 | Section 4.68.4.1.2.2 | 11/22/23 4:36:49 PM by vhofman |
|
| RAD68 | RAD68-017 | reviewed | Testable |
1
|
1
| | The Provide and Register Imaging Document Set MTOM/XOP Request message shall include the metadata attributes that will be forwarded by the Document Repository to the XDS Document Registry using the Register Document Set-b [ITI-42] transaction. | 475 | Section 4.68.4.1.2.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-018 | reviewed | Testable |
1
|
1
| | XDSDocumentEntry Attribute: creationTimeshall record the date and time at which the clinical content conveyed in the shared document is created. If the published document is a DICOM object or is transformed from a DICOM information object, this attribute value should be taken from the tags Instance Creation Date (0008,0012) and Instance Creation Time (0008,0013) of the DICOM object. | 476 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-019 | reviewed | Testable |
0
|
1
| | XDSDocumentEntry Attribute: eventCodeList - Acquisition Modality (required if known)shall contain a code from the DICOM Content Mapping Resource (DICOM PS3.16) Context Group CID 29 for each distinct acquisition modality with which images were acquired in the study. | 476 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-020 | reviewed | Testable |
0
|
1
| | XDSDocumentEntry Attribute: eventCodeList - Anatomic Region (required if known) shall contain code(s) from the DICOM Content Mapping Resource (DICOM PS3.16) Context Group CID 4. Each anatomic region codes displayName shall be populated with the corresponding Code Meaning text from Context Group CID 4. | 477 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-021 | to delete | Testable |
0
|
1
| | XDSDocumentEntry Attribute: eventCodeDisplayNameList (required if eventCodeList is present) contains the Code Meaning text(s) of the code(s) for Acquisition Modality and for Anatomic Region valued in eventCodeList, from DCMR Context Group CID 29 and from DCMR Context Group CID 4, respectively. See DICOM PS 3.16 for DICOM Context Group definitions. The ordering of the Code Meaning texts populated in this attribute shall be sorted in the same order of the corresponding codes in eventCodeList. | 477 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-030 | reviewed | Testable |
0
|
1
| | XDSDocumentEntry Attribute: practiceSettingCode shall be populated by the XDS-I Imaging Document Source describe the high-level imaging speciality. It is strongly recommended to use the values from the DICOM Content Mapping Resource (DICOM PS3.16) Context Group CID 7030. | 477 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-031 | reviewed | Testable |
0
|
1
| | XDSDocumentEntry Attribute: referenceIdList can describe both the Accession Number and Study Instance UID. The Accession Number value may be found in the Originating HL7 Imaging Order Message (OMI) Imaging Procedure Control (IPC) Segment, Sequence 1 for Accession Identifier, or in the DICOM attribute Accession Number (0008,0050). The referendIdList may be populated with the Accession Number and assigning authority. Only the CXi.1, CXi.4 and CXi.5 components shall be valued. The referencedIdList may contain multiple entries for Accession Number. The Study Instance UID uniquely identifies an imaging study. Only the CXi.1 and CXi.5 components shall be valued: CXi.1 - shall be the Study Instance UID CXi.5 shall be urn:ihe:iti:xds:2016:studyInstanceUID. | 477 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-032 | reviewed | Testable |
1
|
1
| | XDSDocumentEntry Attribute: serviceStartTime shall be populated by the Imaging Document Source for a date and time that indicates the imaging service start time. | 478 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-033 | reviewed | Testable |
1
|
1
| | XDSDocumentEntry Attribute: sourcePatientInfo, This attribute allows multiple values for different pieces of patient demographics. | 478 | Section 4.68.4.1.2.3.2 | 11/22/23 4:49:51 PM by vhofman |
|
| RAD68 | RAD68-034 | reviewed | Testable |
0
|
1
| | XDSDocumentEntry Attribute: typeCode 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. | 478 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-035 | reviewed | Testable |
0
|
1
| | XDSDocumentEntry Attribute: typeCodeDisplayName shall be filled by the source actor using the code meaning text of the corresponding performed Procedure Code Sequence (0008,1032) valued in typeCode. | 478 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-036 | reviewed | Testable |
1
|
1
| | XDSDocumentEntry Attribute: uniqueId shall contain the Document unique ID generated by the XDS-I Imaging Document Source. It shall be an ISO OID. | 479 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| XDSI | XDSI-004 | reviewed | Not testable |
0
|
5
| | XDS and XDS-I.b do not address transactions for the management or configuration of an XDS Affinity Domain. For example, the configuration of network addresses or the definition of what type of clinical information is to be shared is specifically left up to the policies established by the XDS Affinity Domain. | 177 | Section 18 | 2/1/24 9:55:02 AM by alegrand |
|
| XDSI | XDSI-005 | reviewed | Not testable |
0
|
5
| | XDS and XDS-I.b do not specifically address the patient information reconciliation process necessary between the XDS Affinity Domain and any other local patient identity domains that Document Sources and Document Consumers may be members of. For a discussion of some of these issues see RAD TF-1: Appendix G. | 177 | Section 18 | 2/1/24 9:55:02 AM by alegrand |
|
| XDSI | XDSI-006 | reviewed | Not testable |
0
|
5
| | XDS and XDS-I.b do not directly address the rendering and display of the documents retrieved by the Document and Imaging Document Consumers. Users wishing to achieve a well-defined level of display/ rendering capability simply need to request systems that combine the XDS-I.b Imaging Document Consumer Actor with an Image Display Actor from the appropriate Profile (e.g., Mammography Image, NM Image, Basic Image Review, etc.). | 177 | Section 18 | 2/1/24 9:55:02 AM by alegrand |
|