Search Criteria : 24 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-002to deleteTestable 0 1 A previously submitted document or the contents of a previously submitted manifest changes, requiring the Imaging Document Source to submit an update.472Section 4.68.4.1.13/15/24 2:33:35 PM by vhofman
RAD68RAD68-007reviewedTestable 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).473Section 4.68.4.1.2.12/1/24 9:55:02 AM by alegrand
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. 474Section 4.68.4.1.2.23/15/24 2:33:35 PM by vhofman
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. 475Section 4.68.4.1.2.23/15/24 2:33:35 PM by vhofman
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.475Section 4.68.4.1.2.23/15/24 2:33:35 PM by vhofman
RAD68RAD68-023reviewedTestable 0 1 XDSDocumentEntry Attribute: formatCodeShall use urn:ihe:rad:TEXT for a CDA Wrapped Text Report.477Section 4.68.4.1.2.3.23/15/24 2:33:35 PM by vhofman
RAD68RAD68-025reviewedTestable 0 1 XDSDocumentEntry Attribute: formatCodeShall use urn:ihe:rad:CDA:ImagingReportStructuredHeadings:2013 unless overridden by a requirement in a Content Profile477Section 4.68.4.1.2.3.23/15/24 2:33:35 PM by vhofman
RAD68RAD68-027reviewedTestable 0 1 XDSDocumentEntry Attribute: mimeTypeShall be text/xml for a CDA Wrapped Text Report or for a CDA Imaging Report with Structured Headings477Section 4.68.4.1.2.3.23/15/24 2:33:35 PM by vhofman
RAD68RAD68-029to deleteTestable 0 1 XDSDocumentEntry Attribute: mimeTypeShall be text/xml477Section 4.68.4.1.2.3.23/15/24 2:33:35 PM by vhofman
RAD68RAD68-044reviewedTestable 0 2 XDS and XDS-I.b Metadata values shall be mapped from CDA elements and values as described in RAD TF-2 table 4.68.4.1.2.3-6482Section 4.68.4.1.2.3.43/15/24 2:33:35 PM by vhofman
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-2 4.68.4.1.2.3.5.1 and subsections.484Section 4.68.4.1.2.3.53/15/24 2:33:35 PM by vhofman
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.21 ClinicalDocument/code element with the following attribute values: code=11528-7 codeSystem=2.16.840.1.113883.6.1 codeSystemName=LOINC displayName=Radiology Report and tThe ClinicalDocument/effectiveTime shall denote the time at which the CDA text document was recorded.484Section 4.68.4.1.2.3.5.1.13/15/24 2:33:35 PM by vhofman
RAD68RAD68-047to be reviewedTestable 0 0 This ClinicalDocument/component/nonXMLBody element shall be present and used to wrap the text content. The requirements for the nonXMLBody are the same as defined in the ITI XDS-SD Profile (see ITI TF-3: 5.2.3.9), with the following exceptions/ clarifications in RAD-TF-2, section 4.68.4.1.2.3.5.1.8487Section 4.68.4.1.2.3.5.1.83/15/24 2:33:35 PM by vhofman
RAD68RAD68-050to be reviewedTestable 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.489Section 4.68.4.23/15/24 2:33:35 PM by alegrand
RAD68RAD68-051to be reviewedTestable 0 0 A Provide and Register Imaging Document Set MTOM/XOP transaction carries Metadata describing zero or more new documents.470Section 4.68.13/15/24 2:33:35 PM by alegrand
RAD68RAD68-052to be reviewedTestable 0 0 A Provide and Register Imaging Document Set MTOM/XOP transaction carries, within metadata, one DocumentEntry object per document.470Section 4.68.13/15/24 2:33:35 PM by alegrand
RAD68RAD68-053to be reviewedTestable 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.470Section 4.68.13/15/24 2:33:35 PM by alegrand
RAD68RAD68-054to be reviewedTestable 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.470Section 4.68.13/15/24 2:33:35 PM by alegrand
RAD68RAD68-055to be reviewedTestable 0 0 A Provide and Register Imaging Document Set MTOM/XOP transaction carries zero or more documents.470Section 4.68.13/15/24 2:33:35 PM by alegrand
RAD68RAD68-056to be reviewedTestable 0 0 For a PDF Report, a specific PDF version is not specified, but use of PDF/A (ISO 19005-1) is recommended.474Section 4.68.4.1.2.23/15/24 2:33:35 PM by alegrand