AssertionManagerGui

Id scheme	Assertion id	Status	Testable?	#Coverage	#Applies to	Predicate	Page	Tags	Last changed

RAD69	RAD69-006	reviewed	Testable	0	2	If the Imaging Document Consumer or Responding Imaging Gateway specifies a transfer syntax field 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.	195	Section 4.69.4.2.3	1/20/17 5:16:40 PM by jdramou
RAD69	RAD69-007	reviewed	Testable	0	1	Shall respond to IDC requests using Async using async.	196	Section 4.69.4.3	1/20/17 5:16:54 PM by jdramou
RAD69	RAD69-008	reviewed	Testable	0	1	Shall use Async if IDS supports it.	196	Section 4.69.4.3	1/20/17 5:17:05 PM by jdramou
RAD69	RAD69-009	reviewed	Testable	0	1	Shall use Async if IDC supports it.	196	Section 4.69.4.3	1/20/17 5:17:17 PM by jdramou
RAD69	RAD69-010	reviewed	Testable	0	2	shall use the non-anonymous response EPR in the WS-Addressing replyTo header	196	Section 4.69.4.3	2/14/17 9:36:03 AM by
RAD69	RAD69-011	reviewed	Testable	0	4	Shall use the Asynchronous Web Services Exchange method in the ITI TF-2x: Appendix V.5: Web Services for IHE Transactions,	196	Section 4.69.4.3	2/14/17 9:36:03 AM by

reviewed

Testable

If the Imaging Document Consumer or Responding Imaging Gateway specifies a transfer syntax field 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.

195

Section 4.69.4.2.3

1/20/17 5:16:40 PM by jdramou

RAD69

RAD69-007

reviewed

Testable

0

1

Shall respond to IDC requests using Async using async.

196

Section 4.69.4.3