net.ihe.gazelle.assets.SearchCriteria : 32 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
RAD55RAD55-022reviewedTestable 0 1 Shall parse the request and if there are no errors, shall construct an HTTP Get Response with the requested DICOM instance content and return the response as specified by the DICOM WADO standard, with HTTP response code 200 (OK)126Section 4.55.4.1.38/26/19 5:25:26 PM by xfrancois
RAD55RAD55-023reviewedTestable 0 1 Shall return HTTP response code 406 (Not Acceptable), if it cannot serve the requested response MIME type(s) in parameter contentType and/or Accept Field.126Section 4.55.4.1.38/26/19 5:25:26 PM by xfrancois
RAD55RAD55-024reviewedTestable 0 1 Shall return HTTP response code 404 (Not Found) if it cannot locate the requested DICOM SOP Instance or cannot recognize the UID values specified in the received HTTP Request-URI. 126Section 4.55.4.1.38/26/19 5:25:26 PM by xfrancois
RAD55RAD55-025reviewedTestable 0 1 The Imaging Document Source shall return HTTP response code 400 (Bad Request) if any required HTTP field or required WADO HTTP parameters are missing in the received HTTP Request-URI, or any other syntactic error is detected in the HTTP Request-URI (e.g., media type in contentType parameter conflicts with media types in Accept field).126Section 4.55.4.1.38/26/19 5:25:26 PM by xfrancois
RAD55RAD55-026reviewedTestable 0 1 Shall return HTTP response code 404 (Not Found) if the Imaging Document Consumer requested retrieval of rejected DICOM SOP Instance(s) referenced in that KOS. Rejected SOP Instances are marked with Document Title valued (113001, DCM, “Rejected for Quality Reasons”), (113037, 2855 DCM, “Rejected for Patient Safety Reasons”), (113038, DCM, “Incorrect Modality Worklist Entry) or (113039, DCM, “Data Retention Policy Expired")126Section 4.55.4.1.31/18/17 5:57:11 PM by jdramou
RAD68RAD68-001reviewedTestable 1 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 message166Section 4.68.4.1.28/26/19 5:26:29 PM by aeschlimann
RAD68RAD68-002reviewedTestable 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 message166Section 4.68.4.1.15/10/19 9:41:46 AM by wbars
RAD68RAD68-012reviewedTestable 0 1 Imaging Document Source set to NONEthe 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 168Section 4.68.4.1.2.25/10/19 9:41:46 AM by wbars
RAD68RAD68-015reviewedTestable 0 1 Imaging Document Source set to NONEHyperlinks that reference images from reports shall be formatted as a DICOM WADO URI, using https.168Section 4.68.4.1.2.25/10/19 9:41:46 AM by wbars
RAD68RAD68-016reviewedTestable 0 1 Imaging Document Source set to NONEHyperlinks that reference images from reports shall be valid links.168Section 4.68.4.1.2.25/10/19 9:41:46 AM by wbars
RAD68RAD68-017reviewedTestable 1 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). 169Section 4.68.4.1.2.38/26/19 5:30:18 PM by aeschlimann
RAD68RAD68-018reviewedTestable 1 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. 170Section 4.68.4.1.2.3.28/26/19 5:30:21 PM by aeschlimann
RAD68RAD68-019reviewedTestable 0 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.170Section 4.68.4.1.2.3.25/10/19 9:41:46 AM by wbars
RAD68RAD68-020reviewedTestable 0 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. 170Section 4.68.4.1.2.3.25/10/19 9:41:46 AM by wbars
RAD68RAD68-021reviewedTestable 0 1 XDSDocumentEntry Attribute: eventCodeDisplayNameList (required if eventCodeList is present) contains the Code Meaning text(s) of the code(s) for Acquisition Modality and for Anatomic Region valued in eventCodeList, from DCMR Context Group CID 29 and from DCMR Context Group CID 4, respectively. See DICOM PS 3.16 for DICOM Context Group definitions. The ordering of the Code Meaning texts populated in this attribute shall be sorted in the same order of the corresponding codes in eventCodeList. 170Section 4.68.4.1.2.3.25/10/19 9:41:46 AM by wbars
RAD68RAD68-030reviewedTestable 0 1 XDSDocumentEntry Attribute: practiceSettingCodeShall be populated by the Imaging Document Source describe the high-level imaging specialty. It is strongly recommended to use the values from the DICOM Content Mapping Resource (DICOM PS3.16) Context Group CID 7030. 170Section 4.68.4.1.2.3.25/10/19 9:41:46 AM by wbars
RAD68RAD68-031reviewedTestable 0 1 XDSDocumentEntry Attribute: referenceIdListShall be populated by the Imaging Document Source with the Accession Number and assigning authority of the Order Filler for each Order associated with the Imaging Document, if the Accession Number is known.The format shall conform to the Data Type CXi where CXi.5 (Identifier Type Code) is urn:ihe:iti:xds:2013:accession. The Data Types are specified in ITI TF-3: Table 4.2.3.1.7-2.An Imaging Document may be referenced by multiple Accession Numbers, so this attribute may contain multiple values.170Section 4.68.4.1.2.3.25/10/19 9:41:46 AM by wbars
RAD68RAD68-032reviewedTestable 1 1 XDSDocumentEntry Attribute: serviceStartTimeshall be populated by the Imaging Document Source for a date and time that indicates the imaging service start time. 170Section 4.68.4.1.2.3.28/26/19 5:31:11 PM by aeschlimann
RAD68RAD68-033reviewedTestable 0 1 XDSDocumentEntry Attribute: sourcePatientInfo NOT SURE IF THIS IS TESTABLEThis attribute allows multiple values for different pieces of patient demographics, see metadata specification of the IHE ITI XDS Integration Profile (ITI TF-3:Table 4.2.3.2-1).As an example, this information can be transformed from DICOM Patient’s Name (0010,0010), Patient’s Birth Date (0010,0030), and Patient’s Sex (0010,0040). 170Section 4.68.4.1.2.3.25/10/19 9:41:46 AM by wbars
RAD68RAD68-034reviewedTestable 0 1 XDSDocumentEntry Attribute: typeCodeshall be populated by the source actor from a code in the Procedure Code Sequence (0008,1032) of the performed procedure with which the document is associated.170Section 4.68.4.1.2.3.25/10/19 9:41:46 AM by wbars