| CH-XDSI | CH-XDSI-005 | to be reviewed | Testable |
0
|
0
| | The purpose of use of the X-User Assertion SHALL be equal to DICOM_AUTO. The Document Repository SHALL accept KOS documents only if this requirement is fulfilled. | 9 | Section 1.3.a | 3/15/24 2:33:35 PM by vhofman |
|
| CH-XDSI | CH-XDSI-006 | to be reviewed | Testable |
0
|
0
| | The DocumentEntry.formatCode SHALL be equal to the coded value of DICOM Manifest (1.2.840.10008.5.1.4.1.1.88.59^^1.2.840.10008.2.6.1). The Document Repository SHALL accept KOS documents only if this requirement is fulfilled. | 9 | Section 1.3.b | 3/15/24 2:33:35 PM by vhofman |
|
| CH-XDSI | CH-XDSI-007 | to be reviewed | Testable |
0
|
0
| | The DocumentEntry.mimeType SHALL be equal to application/dicom. The Document Repository SHALL accept KOS documents only if this requirement is fulfilled. | 9 | Section 1.3.c | 3/15/24 2:33:35 PM by vhofman |
|
| 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-050 | to be reviewed | Testable |
0
|
0
| | The XDS-I Imaging Document Source shall handle all error messages detailed for the Provide and Register Document Set-b [ITI-41] transaction in ITI TF-3: Table 4.2.4.1-2 Error Codes. | 489 | Section 4.68.4.2 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-051 | to be reviewed | Testable |
0
|
0
| | A Provide and Register Imaging Document Set MTOM/XOP transaction carries Metadata describing zero or more new documents. | 470 | Section 4.68.1 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-052 | to be reviewed | Testable |
0
|
0
| | A Provide and Register Imaging Document Set MTOM/XOP transaction carries, within metadata, one DocumentEntry object per document. | 470 | Section 4.68.1 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-053 | to be reviewed | Testable |
0
|
0
| | A Provide and Register Imaging Document Set MTOM/XOP transaction carries one Submission Set definition along with the linkage to new documents and references to existing documents. | 470 | Section 4.68.1 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-054 | to be reviewed | Testable |
0
|
0
| | Provide and Register Imaging Document Set MTOM/XOP transaction carries zero or more Folder definitions along with linkage to new or existing documents. | 470 | Section 4.68.1 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-055 | to be reviewed | Testable |
0
|
0
| | A Provide and Register Imaging Document Set MTOM/XOP transaction carries zero or more documents. | 470 | Section 4.68.1 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-056 | to be reviewed | Testable |
0
|
0
| | For a PDF Report, a specific PDF version is not specified, but use of PDF/A (ISO 19005-1) is recommended. | 474 | Section 4.68.4.1.2.2 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-058 | to be reviewed | Testable |
0
|
0
| | Since the sharing environment is inherently cross-enterprise, the secured version of HTTP (i.e., HTTPS) shall be used when formatting the hyperlink. | 475 | Section 4.68.4.1.2.2 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-059 | to be reviewed | Testable |
0
|
0
| | The metadata of the Manifest document shall be related to the referenced source content or its creation process | 475 | Section 4.68.4.1.2.3.1 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD68 | RAD68-060 | to be reviewed | Testable |
0
|
0
| | If the Manifest references source data from multiple authors, then one primary author, source data creation time and document title shall be chosen. | 476 | Section 4.68.4.1.3.1 | 3/15/24 2:33:35 PM by alegrand |
|
| RAD69 | RAD69-006 | reviewed | Testable |
0
|
2
| | If the request contains a transfer syntax of 1.2.840.10008.1.2.4.94 (DICOM JPIP Referenced Transfer Syntax) or 1.2.840.10008.1.2.4.95 (DICOM JPIP Referenced Deflate Transfer Syntax), and the Imaging Document Source supports the requested transfer syntax, the following behavior is expected: If the DICOM Image Object(s) already have the same JPIP transfer syntax as the one indicated in the request, the Retrieve Imaging Document Set Response shall include the DICOM Image Objects unchanged. If the DICOM Image Object(s) have a transfer syntax that differs from that of the request, the Retrieve Imaging Document Set Response shall include the DICOM image with the transfer syntax changed to the requested transfer syntax. In addition, the pixel data Attribute (7Fe0,0010 tag) will have been removed and replaced with a Pixel Data Provider URL (0028,7FE0 tag). The URL represents the JPIP request and will include the specific target information.Upon receipt of this Retrieve Imaging Document Set Response, the Imaging Document Consumer may request the pixel data from the pixel data provider using the supplied URL. Additional parameters required by the application may be appended to the URL when accessing the pixel data provider. | 492 | Section 4.69.4.2.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-007 | reviewed | Testable |
0
|
1
| | An Image Document Consumer that supports the Asynchronous Web Services Option shall use the Asynchronous Web Services Exchange method if the Initiating Imaging Gateway also supports the Asynchronous Web Services Option.The Initiating Imaging Gateway that supports the Asynchronous Web Services Option, shall respond to an Image Document Consumer using the use the Asynchronous Web Services Exchange method. | 493 | Section 4.69.4.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-008 | reviewed | Testable |
0
|
1
| | A Responding Imaging Gateway shall use the Asynchronous Web Services Exchange method if the Image Document Source supports the Asynchronous Web Services Option. | 493 | Section 4.69.4.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-009 | reviewed | Testable |
0
|
1
| | The Image Document Source that supports the Asynchronous Web Services Option, shall respond to an Image Document Consumer using the Asynchronous Web Services Exchange method. | 493 | Section 4.69.4.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-011 | reviewed | Testable |
0
|
4
| | The Initiating Imaging Gateway, Responding Imaging Gateway, the Image Document Source and the Image Document Consumer shall support the Asynchronous Web Services Methods in the ITI TF-2: Appendix V. | 493 | Section 4.69.4.3 | 2/1/24 9:55:02 AM by alegrand |
|
| RAD69 | RAD69-017 | reviewed | Testable |
0
|
0
| | For each document requested in a /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest element, if a warning is reported when retrieving the document, then a /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be returned with the element @severity (urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Warning). | 496 | Section 4.69.5 | 3/15/24 2:33:35 PM by alegrand |
|