net.ihe.gazelle.assets.SearchCriteria : 16 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
RAD69RAD69-001reviewedTestable 2 2 extracts the XDSDocumentEntry.uniqueId and a repositoryUniqueId associated with the Imaging Document Source from the manifest (KOS) object retrieved previously via the Retrieve Document Set transaction187Section 4.69.4.1.28/26/19 5:33:50 PM by aeschlimann
RAD69RAD69-002reviewedTestable 1 3 The Request shall contain:+ repositoryUniqueId that identifies the Imaging Document Source from which the DICOM instance is to be retrieved.+ one or more documentUniqueIds that identify the documents within the Imaging Document Source.+ one or more DICOM transfer syntax UIDs that the Imaging Document Consumer is capable of processing. + Study Instance UID value that identifies the study containing the DICOM images/ objects to be retrieved. + Series Instance UID value that identifies the series containing the DICOM images/ objects to be retrieved. homeCommunityID, if the Retrieve Imaging Document Set request is to an Initiating Imaging Gateway.187Section 4.69.4.1.28/26/19 5:33:54 PM by aeschlimann
RAD69RAD69-003reviewedTestable 1 2 The semantics of the Retrieve Imaging Document Set Response Message are identical to those inherited from the ITI-43 transaction and are specified in ITI TF-2b: 3.43.4.2.2.188Section 4.69.4.2.28/26/19 5:34:07 PM by aeschlimann
RAD69RAD69-004reviewedTestable 1 2 response: shall return the imaging document(s) or an error code in case the document could not be returned188Section 4.69.4.2.38/26/19 5:35:05 PM by aeschlimann
RAD69RAD69-005reviewedTestable 1 2 response: The pixel data shall be encoded using one of the DICOM transfer syntaxes included in the request or an error status shall be returned188Section 4.69.4.2.38/26/19 5:35:09 PM by aeschlimann
RAD69RAD69-006reviewedTestable 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. 188Section 4.69.4.2.35/10/19 9:48:41 AM by wbars
RAD69RAD69-007reviewedTestable 0 1 Shall respond to IDC requests using Async using async.189Section 4.69.4.35/10/19 9:48:41 AM by wbars
RAD69RAD69-008reviewedTestable 0 1 Shall use Async if IDS supports it. 189Section 4.69.4.35/10/19 9:48:41 AM by wbars
RAD69RAD69-009reviewedTestable 0 1 Shall use Async if IDC supports it.189Section 4.69.4.35/10/19 9:48:41 AM by wbars
RAD69RAD69-010reviewedTestable 1 2 shall use the non-anonymous response EPR in the WS-Addressing replyTo header189Section 4.69.4.38/26/19 5:35:43 PM by aeschlimann
RAD69RAD69-011reviewedTestable 0 4 Shall use the Asynchronous Web Services Exchange method in the ITI TF-2x: Appendix V.5: Web Services for IHE Transactions,189Section 4.69.4.35/10/19 9:48:41 AM by wbars
RAD69RAD69-012reviewedTestable 2 2 The <iherad:RetrieveImagingDocumentSetRequest/> element for use with the Retrieve Imaging Document Set Request Message is defined as:•One or more <iherad:StudyRequest/> elements each of which includes a “studyInstanceUID” attribute identifying the study associated with the DICOM images/ objects being retrieved. Each <iherad:StudyRequest/> element shall contain: •One or more <iherad:SeriesRequest/> elements each of which includes a “seriesInstanceUID” attribute identifying the series associated with the DICOM images/ objects being retrieved. Each <iherad:SeriesRequest/> element shall contain:•One or more <ihe:DocumentRequest/> elements, each one representing an individual document that the Imaging Document Consumer or Responding Imaging Gateway wants to retrieve from the Imaging Document Source. Each <ihe:DocumentRequest/> element contains:•A required <ihe:RepositoryUniqueId/> element that identifies the Imaging Document Source from which the document is to be retrieved. This value corresponds to XDSDocumentEntry.repositoryUniqueId.•A required <ihe:DocumentUniqueId/> element that identifies the document within the Imaging Document Source. This value corresponds to the SOP Instance UID referenced within the DICOM manifest.•A conditionally required <ihe:HomeCommunityId/> element that corresponds to the home attribute of the Identifiable class in ebRIM. The element shall be populated if the request is to an Initiating Imaging Gateway. Otherwise, it may be absent.190Section 4.69.58/26/19 5:36:22 PM by aeschlimann
RAD69RAD69-013reviewedTestable 2 2 A required <iherad:TransferSyntaxUIDList/> element which contains a list of one or more <ihe:TransferSyntaxUID> elements. Each element represents one of the transfer syntax encodings that the Imaging Document Consumer is capable of processing190Section 4.69.58/26/19 5:36:25 PM by aeschlimann
RAD69RAD69-014reviewedTestable 1 2 The <ihe:RetrieveDocumentResponse/> element for use with the Retrieve Imaging Document Set Response Message is defined as:•A required /ihe:RetrieveDocumentSetResponse/rs:RegistryResponse element •A conditionally required sequence, if a matching document exists with <ihe:DocumentResponse/> elements containing•A conditionally required <ihe:HomeCommunityId/> element. The value of this element shall be the same as the value of the /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest/HomeCommunityId element in the Retrieve Document Set Request Message. If the <ihe:HomeCommunityId/> element is not present in the Retrieve Document Set Request Message, this value shall not be present.•A required <ihe:RepositoryUniqueId/> that identifies the Imaging Document Source from which the document is to be retrieved. The value of this element shall be the same as the value of the /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest/RepositoryUniqueId element in the original Retrieve Imaging Document Set Request Message. This value corresponds to RetrieveLocation UID in the DICOM manifest.•A required <ihe:DocumentUniqueId/> that identifies the document within the Imaging Document Source. The value of this element shall be the same as the value of the /RetrieveImagingDocumentSetRequest/StudyRequest/SeriesRequest/DocumentRequest/DocumentUniqueId element in the original Retrieve Imaging Document Set Request Message. This value corresponds to the SOP Instance UID referenced within the DICOM manifest.•A required <ihe:Document/> element that contains the retrieved document as an XOP Infoset.•A required <ihe:mimeType/> element that indicates the MIME type of the retrieved document190Section 4.69.58/26/19 5:36:10 PM by aeschlimann
RAD69RAD69-015reviewedTestable 1 2 The /RetrieveDocumentSetResponse/rs:RegistryResponse/@status attributes provides the overall status of the request: It shall contain one of the following values:urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success urn:ihe:iti:2007:ResponseStatusType:PartialSuccess urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure190Section 4.69.58/26/19 5:36:59 PM by aeschlimann
RAD69RAD69-016reviewedTestable 1 2 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:•@severity is urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Warning•@errorCode is specified•@codeContext contains the warning message•@location contains the DocumentUniqueId of the document requested •The document shall be returned in an instance of /RetrieveDocumentSetResponse/DocumentResponse/Document as an XOP Infoset. The returned document and warning are correlated via the DocumentUniqueId. •If an error is reported when retrieving a document, then a /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be returned with:•@severity is urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error•@errorCode is specified•@codeContext contains the error message•@location contains the DocumentUniqueId of the document requested•No corresponding RetrieveDocument SetResponse/DocumentResponse element shall be returned •If the document is successfully retrieved (without warning) then no /RetrieveDocumentSetResponse/rs:RegistryResponse/rs:RegistryErrorList/ rs:RegistryError element shall be present and a /RetrieveDocumentSetResponse/DocumentResponse/Document element shall be returned containing the document as an XOP Infoset.190Section 4.69.58/26/19 5:36:55 PM by aeschlimann