Search Criteria : 19 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
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 message172Section 4.68.4.1.11/18/17 4:14:24 PM by jdramou
RAD68RAD68-006reviewedTestable 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. 173Section 4.68.4.1.2.11/18/17 4:17:13 PM by jdramou
RAD68RAD68-007reviewedTestable 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). 174Section 4.68.4.1.2.11/18/17 4:17:13 PM by jdramou
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 174Section 4.68.4.1.2.2 1/18/17 3:47:24 PM by jdramou
RAD68RAD68-013reviewedTestable 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. 175Section 4.68.4.1.2.2 1/18/17 4:17:07 PM by jdramou
RAD68RAD68-014reviewedTestable 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. 175Section 4.68.4.1.2.2 1/18/17 4:14:31 PM by jdramou
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.175Section 4.68.4.1.2.2 1/18/17 4:06:01 PM by jdramou
RAD68RAD68-016reviewedTestable 0 1 Imaging Document Source set to NONEHyperlinks that reference images from reports shall be valid links.175Section 4.68.4.1.2.2 1/18/17 4:06:24 PM by jdramou
RAD68RAD68-023reviewedTestable 0 1 XDSDocumentEntry Attribute: formatCodeShall use “urn:ihe:rad:TEXT” 178Section 4.68.4.1.2.3.21/18/17 4:16:58 PM by jdramou
RAD68RAD68-024reviewedTestable 0 1 XDSDocumentEntry Attribute: formatCodeShall use “urn:ihe:rad:PDF”178Section 4.68.4.1.2.3.21/18/17 4:16:57 PM by jdramou
RAD68RAD68-025reviewedTestable 0 1 XDSDocumentEntry Attribute: formatCodeShall use “urn:ihe:rad:CDA:ImagingReportStructuredHeadings:2013” unless overridden by a requirement in a Content Profile178Section 4.68.4.1.2.3.21/18/17 4:16:56 PM by jdramou
RAD68RAD68-027reviewedTestable 0 1 XDSDocumentEntry Attribute: mimeTypeShall be “text/xml”178Section 4.68.4.1.2.3.21/18/17 4:16:54 PM by jdramou
RAD68RAD68-028reviewedTestable 0 1 XDSDocumentEntry Attribute: mimeTypeShall be “application/pdf”178Section 4.68.4.1.2.3.21/18/17 4:16:53 PM by jdramou
RAD68RAD68-029reviewedTestable 0 1 XDSDocumentEntry Attribute: mimeTypeShall be “text/xml”178Section 4.68.4.1.2.3.21/18/17 4:16:52 PM by jdramou
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). 179Section 4.68.4.1.2.3.21/18/17 4:16:48 PM by jdramou
RAD68RAD68-038reviewedTestable 0 2 XDSDocumentEntry Attribute: uniqueIdShall be ClinicalDocument/id@root.ClinicalDocument/id@extension179Section 4.68.4.1.2.3.21/18/17 4:14:35 PM by jdramou
RAD68RAD68-044reviewedTestable 0 2 XDS and XDS-I.b Metadata values shall be mapped from CDA elements and values as described in RAD TF-3 table 4.68.4.1.2.3-60Section 4.68.4.1.2.3.41/18/17 4:15:59 PM by jdramou
RAD68RAD68-045reviewedTestable 0 1 The CDA metadata wrapper for plain text reports is the same as defined in the ITI XDS-SD Profile (see the metadata specification Table in ITI TF-3: 5.2.3) except for notations in RAD TF-3 4.68.4.1.2.3.5.1 and subsections.185Section 4.68.4.1.2.3.51/18/17 4:16:03 PM by jdramou
RAD68RAD68-046reviewedTestable 0 1 ClinicalDocument Child-less elements for CDA-wrapped plain text reports shall have:ClinicalDocument/templateId element 1.3.6.1.4.1.19376.1.2.21ClinicalDocument/code element with the following attribute values: • code=“11528-7” • codeSystem=“2.16.840.1.113883.6.1” • codeSystemName=“LOINC” • displayName=“Radiology Report”186Section 4.68.4.1.2.3.5.1.11/18/17 4:16:21 PM by jdramou