| RAD68 | RAD68-003 | reviewed | Testable |
1
|
1
| | The Imaging Document Source creates a manifest that describes and collects references to DICOM SOP instances that are intended for sharing. The manifest, a Key Object Selection (KOS) Document Instance, is the actual document provided to the Document Repository and registered at the Document Registry. | 472 | Section 4.68.4.1.2.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-004 | reviewed | Testable |
1
|
1
| | The structure of the Request message between the XDS Document Source and the XDS Document Repository is an MTOM/ XOP formatted message. | 473 | Section 4.68.4.1.2.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-005 | reviewed | Testable |
1
|
1
| | The KOS Document Instance is encoded in the Request message as a DICOM Part 10 File format having a MIME type of “application/dicom”. | 473 | Section 4.68.4.1.2.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-006 | reviewed | Testable |
1
|
1
| | The Imaging Document Source shall ensure that the DICOM SOP Instances referenced from within the manifest are available to be retrieved.If the XDS-I Imaging Document Source makes one or more SOP Instances unavailable that are referenced in a published manifest, then it shall submit a new manifest as a replacement for the published manifest already in the XDS Document Repository and XDS Document Registry (see IHE ITI TF-3:4.2.2.2 Document Relationships).The new manifest shall have the updated list of DICOM SOP Instances with the unavailable instances removed. | 473 | Section 4.68.4.1.2.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-007 | reviewed | Testable |
0
|
1
| | If the XDS-I Imaging Document Source makes all referenced DICOM SOP Instances unavailable in a published manifest, then it may consider implementing the Remove Imaging Document Option (see RAD TF-1: 18.2.5). | 473 | Section 4.68.4.1.2.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-008 | reviewed | Testable |
1
|
1
| | The references to the DICOM SOP Instances shall be included in the Current Requested Procedure Evidence Sequence (0040,A375) attribute of the KOS Manifest Document. | 473 | Section 4.68.4.1.2.1.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-009 | reviewed | Testable |
1
|
1
| | The Imaging Document Source shall support these attributes in Current Requested Procedure Evidence Sequence (0040,A375), which are represented in the Hierarchical SOP Instance Reference Macro: Study Instance UID (0020,000D) & Referenced Series Sequence (0008,1115) & Series Instance UID (0020,000E) & Referenced SOP Sequence (0008,1199) & Referenced SOP Class UID (0008,1150) & Referenced SOP Instance UID (0008,1155) | 473 | Section 4.68.4.1.2.1.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-010 | reviewed | Testable |
1
|
1
| | The Imaging Document Source shall support these attributes in Current Requested Procedure Evidence Sequence (0040,A375), which are represented in the Hierarchical SOP Instance Reference Macro, using its own identification:Retrieve AE Title (0008,0054) & Retrieve Location UID (0040,E011) | 473 | Section 4.68.4.1.2.1.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-011 | reviewed | Testable |
0
|
1
| | The Imaging Document Source may support these attributes in Current Requested Procedure Evidence Sequence (0040,A375), which are represented in the Hierarchical SOP Instance Reference Macro:Storage Media File-Set ID (0088,0130) & Storage Media File-Set UID (0088,0140) | 473 | Section 4.68.4.1.2.1.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-022 | reviewed | Testable |
0
|
1
| | XDSDocumentEntry Attribute: formatCodeShall use 1.2.840.10008.5.1.4.1.1.88.59 (DICOM KOS SOP Class UID) as the Format Code Value and 1.2.840.10008.2.6.1 (DICOM UID Registry UID) as the Format Coding Scheme OID for a DICOM Manifest document. | 477 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-026 | reviewed | Testable |
1
|
1
| | XDSDocumentEntry Attribute: mimeType shall be application/dicom for a DICOM Manifest document | 477 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-037 | reviewed | Testable |
1
|
1
| | XDSDocumentEntry Attribute: uniqueIdShall. For a DICOM Manifest document, this attribute value shall be the same as the SOP Instance UID of the corresponding DICOM KOS object. In the event that any information in the manifest changes and it needs to be resubmitted from the XDS-I Imaging Document Source to the XDS Document Repository, the XDS-I Imaging Document Source shall generate a new SOP Instance UID for the DICOM KOS object to ensure that its submission to the XDS Document Repository will succeed. | 479 | Section 4.68.4.1.2.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-039 | reviewed | Testable |
0
|
1
| | The Extended Composite ID shall be mapped from DICOM elements to the HL7 CX data type as described in ITI TF-3: 4.2.3.1.7 and table 4.68.4.1.2.3-2 CX Data Type Mapping. | 480 | Section 4.68.4.1.2.3.3.1 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-040 | reviewed | Testable |
0
|
1
| | HL7 DTM Data Type can be represented as YYYY[MM[DD[HH[MM[SS]]]]], transformed from DICOM elements of VR DA (format: YYYYMMDD) and TM (format: HHMMSS.fraction). | 480 | Section 4.68.4.1.2.3.3.2 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-041 | reviewed | Testable |
0
|
1
| | HL7 XCN data types for person ID and name shall be representing using data from the DICOM elements, transcoded as described in RAD TF-2 4.68.4.1.2.3.3.3 and Table 4.68.4.1.2.3-3. | 480 | Section 4.68.4.1.2.3.3.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-042 | reviewed | Testable |
0
|
1
| | HL7 XON data types for organization ID and name shall be represented using data from the DICOM elements as described in RAD TF-2 4.68.4.1.2.3.3.4 and table 4.68.4.1.2.3-4. | 481 | Section 4.68.4.1.2.3.3.4 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD68 | RAD68-043 | reviewed | Testable |
0
|
1
| | HL7 CXi data types for accession numbers shall be represented using data from the DICOM elements as described in RAD TF-2 4.68.4.1.2.3.3.5 and table 4.68.4.1.2.3-5 | 482 | Section 4.68.4.1.2.3.3.5 | 2/1/24 9:55:02 AM by alegrand |
|
| XDSI | XDSI-010 | reviewed | Testable |
0
|
1
| | If the Imaging Document Source supports the Set of DICOM Instances option, it shall support all of the following transactions:+ [RAD-16] Retrieve Images+ [RAD-17] Retrieve Presentation States+ [RAD-27] Retrieve Reports+ [RAD-31] Retrieve Key Image Note+ [RAD-45] Retrieve Evidence Documents+ [RAD-55] WADO Retrieve+ [RAD-69] Retrieve Imaging Document Set | 178 | Section 18.1 | 2/1/24 9:55:02 AM by alegrand |
|
| XDSI | XDSI-011 | reviewed | Testable |
1
|
1
| | This option requires the Imaging Document Source to create a DICOM manifest that references DICOM instances, and to provide and register this document to the Document Repository. The Imaging Document Source is required to ensure that the referenced images from within a published manifest are available to be retrieved. For details of the transaction affected by this option, refer to RAD TF-3: 4.68.4.1.2.1. | 180 | Section 18.2.1 | 2/1/24 9:55:02 AM by alegrand |
|