View scope

keyword
XDS-I.b
Description
All assertions which applies to the XDS-I.b actors
Back

81 Assertions in Scope

Search Criteria

Id scheme
Assertion id
Predicate
RAD68RAD68-001The Imaging Document Source is instructed to submit a set of one or more new imaging documents for sharing.
RAD68RAD68-002A previously submitted document or the contents of a previously submitted manifest changes, requiring the Imaging Document Source to submit an update.
RAD68RAD68-003The Imaging Document Source creates a manifest that describes and collects references to DICOM SOP instances that are intended for sharing. The manifest, a Key Object Selection (KOS) Document Instance, is the actual document provided to the Document Repository and registered at the Document Registry.
RAD68RAD68-004The structure of the Request message between the XDS Document Source and the XDS Document Repository is an MTOM/ XOP formatted message.
RAD68RAD68-005The KOS Document Instance is encoded in the Request message as a DICOM Part 10 File format having a MIME type of “application/dicom”.
RAD68RAD68-006The Imaging Document Source shall ensure that the DICOM SOP Instances referenced from within the manifest are available to be retrieved.If the XDS-I 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 XDS Document Repository and XDS 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.
RAD68RAD68-007If 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).
RAD68RAD68-008The references to the DICOM SOP Instances shall be included in the Current Requested Procedure Evidence Sequence (0040,A375) attribute of the KOS Manifest Document.
RAD68RAD68-009The Imaging Document Source shall support these attributes in Current Requested Procedure Evidence Sequence (0040,A375), which are represented in the Hierarchical SOP Instance Reference Macro: Study Instance UID (0020,000D) & Referenced Series Sequence (0008,1115) & Series Instance UID (0020,000E) & Referenced SOP Sequence (0008,1199) & Referenced SOP Class UID (0008,1150) & Referenced SOP Instance UID (0008,1155)
RAD68RAD68-010The Imaging Document Source shall support these attributes in Current Requested Procedure Evidence Sequence (0040,A375), which are represented in the Hierarchical SOP Instance Reference Macro, using its own identification:Retrieve AE Title (0008,0054) & Retrieve Location UID (0040,E011)
RAD68RAD68-011The Imaging Document Source may support these attributes in Current Requested Procedure Evidence Sequence (0040,A375), which are represented in the Hierarchical SOP Instance Reference Macro:Storage Media File-Set ID (0088,0130) & Storage Media File-Set UID (0088,0140)
RAD68RAD68-012The Imaging Document Source shall support shared reports in at least one of the following formats: CDA Imaging Report with Structured Headings, CDA Wrapped Text Report or PDF Report.
RAD68RAD68-013The 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.
RAD68RAD68-014The 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.
RAD68RAD68-015Hyperlinks that reference images from reports shall be formatted as a DICOM WADO URI, using https.
RAD68RAD68-016The Imaging Document Source is required to ensure that image references are valid links.
RAD68RAD68-017The Provide and Register Imaging Document Set MTOM/XOP Request message shall include the metadata attributes that will be forwarded by the Document Repository to the XDS Document Registry using the Register Document Set-b [ITI-42] transaction.
RAD68RAD68-018XDSDocumentEntry 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.
RAD68RAD68-019XDSDocumentEntry 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.
RAD68RAD68-020XDSDocumentEntry Attribute: eventCodeList - Anatomic Region (required if known) shall contain code(s) from the DICOM Content Mapping Resource (DICOM PS3.16) Context Group CID 4. Each anatomic region codes displayName shall be populated with the corresponding Code Meaning text from Context Group CID 4.