| RAD68 | RAD68-001 | reviewed | Testable |
2
|
1
| | The Imaging Document Source Actor is instructed to submit a set of one or more new imaging documents for sharing... which triggers a Provide and Register Imaging Document Set – MTOM/XOP Request message | 172 | Section 4.68.4.1.1 | 2/13/17 11:47:10 AM by aberge |
|
| RAD68 | RAD68-002 | reviewed | 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... which triggers a Provide and Register Imaging Document Set – MTOM/XOP Request message | 172 | Section 4.68.4.1.1 | 1/18/17 4:14:24 PM by jdramou |
|
| RAD68 | RAD68-003 | reviewed | Testable |
2
|
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. | 173 | Section 4.68.4.1.2.1 | 2/13/17 11:47:13 AM by aberge |
|
| RAD68 | RAD68-004 | reviewed | Testable |
2
|
1
| | the structure of the Request message between the Document Source and the Document Repository is an MTOM/ XOP formatted message. | 173 | Section 4.68.4.1.2.1 | 2/13/17 11:47:15 AM by aberge |
|
| RAD68 | RAD68-005 | reviewed | Testable |
2
|
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”. | 173 | Section 4.68.4.1.2.1 | 2/13/17 11:47:17 AM by aberge |
|
| RAD68 | RAD68-006 | reviewed | Testable |
0
|
1
| | The Imaging Document Source shall ensure that the DICOM SOP Instances referenced from within the manifest are available to be retrieved. If the 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 Document Repository and 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. | 173 | Section 4.68.4.1.2.1 | 1/18/17 4:17:13 PM by jdramou |
|
| RAD68 | RAD68-007 | reviewed | Testable |
0
|
1
| | If the Imaging Document Source makes all referenced DICOM SOP Instances unavailable in a published manifest, then it shall deprecate the published manifest without any replacement (IHE ITI XDS Metadata Update Supplement). | 174 | Section 4.68.4.1.2.1 | 1/18/17 4:17:13 PM by jdramou |
|
| RAD68 | RAD68-008 | reviewed | Testable |
2
|
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. | 174 | Section 4.68.4.1.2.1.1 | 2/13/17 11:47:20 AM by aberge |
|
| RAD68 | RAD68-009 | reviewed | Testable |
2
|
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) | 174 | Section 4.68.4.1.2.1.1 | 2/13/17 11:47:22 AM by aberge |
|
| RAD68 | RAD68-010 | reviewed | Testable |
2
|
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) | 174 | Section 4.68.4.1.2.1.1 | 2/13/17 11:47:24 AM by aberge |
|
| RAD68 | RAD68-011 | reviewed | Testable |
2
|
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) | 174 | Section 4.68.4.1.2.1.1 | 2/13/17 11:47:28 AM by aberge |
|
| RAD68 | RAD68-012 | reviewed | Testable |
0
|
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 HeadingsCDA Wrapped Text ReportPDF Report | 174 | Section 4.68.4.1.2.2 | 1/18/17 3:47:24 PM by jdramou |
|
| RAD68 | RAD68-013 | reviewed | Testable |
0
|
1
| | The CDA R2 Header and Body shall conform to the HL7 Clinical Document Architecture Release 2.0. The report content shall be encoded in the StructuredBody element and shall use Section elements identified with a code and there shall be no nonXMLBody element. | 175 | Section 4.68.4.1.2.2 | 1/18/17 4:17:07 PM by jdramou |
|
| RAD68 | RAD68-014 | reviewed | Testable |
0
|
1
| | The CDA R2 Header shall conform to the HL7 Clinical Document Architecture Release 2.0. The CDA Body shall be text encoded with UTF-8 UNICODE format. | 175 | Section 4.68.4.1.2.2 | 1/18/17 4:14:31 PM by jdramou |
|
| 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. | 175 | Section 4.68.4.1.2.2 | 1/18/17 4:06:01 PM by jdramou |
|
| RAD68 | RAD68-016 | reviewed | Testable |
0
|
1
| Imaging Document Source set to NONE | Hyperlinks that reference images from reports shall be valid links. | 175 | Section 4.68.4.1.2.2 | 1/18/17 4:06:24 PM by jdramou |
|
| RAD68 | RAD68-017 | reviewed | Testable |
2
|
1
| | The Provide and Register Imaging Document Set – MTOM/XOP Request message shall include the metadata attributes that will be forwarded by the XDS Document Repository Actor to the XDS Registry Actor using the Register Document Set-b transaction (ITI-42). | 176 | Section 4.68.4.1.2.3 | 2/13/17 11:47:31 AM by aberge |
|
| RAD68 | RAD68-018 | reviewed | Testable |
2
|
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. | 177 | Section 4.68.4.1.2.3.2 | 2/13/17 11:47:33 AM by aberge |
|
| RAD68 | RAD68-019 | reviewed | Testable |
2
|
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. | 177 | Section 4.68.4.1.2.3.2 | 2/13/17 11:47:36 AM by aberge |
|
| RAD68 | RAD68-020 | reviewed | Testable |
2
|
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. | 177 | Section 4.68.4.1.2.3.2 | 2/13/17 11:47:38 AM by aberge |
|