Search Criteria : 27 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-001reviewedTestable 2 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 message172Section 4.68.4.1.12/13/17 11:47:10 AM by aberge
RAD68RAD68-003reviewedTestable 2 1 The 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. 173Section 4.68.4.1.2.12/13/17 11:47:13 AM by aberge
RAD68RAD68-004reviewedTestable 2 1 the structure of the Request message between the Document Source and the Document Repository is an MTOM/ XOP formatted message.173Section 4.68.4.1.2.12/13/17 11:47:15 AM by aberge
RAD68RAD68-005reviewedTestable 2 1 The KOS Document Instance is encoded in the Request message as a DICOM Part 10 File format having a MIME type of “application/dicom”.173Section 4.68.4.1.2.12/13/17 11:47:17 AM by aberge
RAD68RAD68-008reviewedTestable 2 1 The references to the DICOM SOP Instances shall be included in the Current Requested Procedure Evidence Sequence (0040,A375) attribute of the KOS Manifest Document. 174Section 4.68.4.1.2.1.12/13/17 11:47:20 AM by aberge
RAD68RAD68-009reviewedTestable 2 1 The 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)174Section 4.68.4.1.2.1.12/13/17 11:47:22 AM by aberge
RAD68RAD68-010reviewedTestable 2 1 The 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)174Section 4.68.4.1.2.1.12/13/17 11:47:24 AM by aberge
RAD68RAD68-011reviewedTestable 2 1 The 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)174Section 4.68.4.1.2.1.12/13/17 11:47:28 AM by aberge
RAD68RAD68-017reviewedTestable 2 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). 176Section 4.68.4.1.2.3 2/13/17 11:47:31 AM by aberge
RAD68RAD68-018reviewedTestable 2 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. 177Section 4.68.4.1.2.3.22/13/17 11:47:33 AM by aberge
RAD68RAD68-019reviewedTestable 2 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.177Section 4.68.4.1.2.3.22/13/17 11:47:36 AM by aberge
RAD68RAD68-020reviewedTestable 2 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. 177Section 4.68.4.1.2.3.22/13/17 11:47:38 AM by aberge
RAD68RAD68-021reviewedTestable 2 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. 177Section 4.68.4.1.2.3.22/13/17 11:47:46 AM by aberge
RAD68RAD68-022reviewedTestable 2 1 XDSDocumentEntry Attribute: formatCodeShall use “1.2.840.10008.5.1.4.1.1.88.59” (DICOM KOS SOP Class UID) as the Format Code Value and “1.2.840.10008.2.6.1” (DICOM UID Registry UID) as the Format Coding Scheme OID 177Section 4.68.4.1.2.3.22/13/17 11:47:48 AM by aberge
RAD68RAD68-026reviewedTestable 2 1 XDSDocumentEntry Attribute: mimeTypeShall be “application/dicom”177Section 4.68.4.1.2.3.22/13/17 11:47:50 AM by aberge
RAD68RAD68-030reviewedTestable 2 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. 178Section 4.68.4.1.2.3.22/13/17 11:47:56 AM by aberge
RAD68RAD68-031reviewedTestable 2 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.178Section 4.68.4.1.2.3.22/13/17 11:47:59 AM by aberge
RAD68RAD68-032reviewedTestable 2 1 XDSDocumentEntry Attribute: serviceStartTimeshall be populated by the Imaging Document Source for a date and time that indicates the imaging service start time. 179Section 4.68.4.1.2.3.22/13/17 11:48:03 AM by aberge
RAD68RAD68-034reviewedTestable 2 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.179Section 4.68.4.1.2.3.22/13/17 11:48:07 AM by aberge
RAD68RAD68-035reviewedTestable 2 1 XDSDocumentEntry Attribute: typeCodeDisplayNameshall be filled by the source actor using the code meaning text of the corresponding performed Procedure Code Sequence (0008,1032) valued in typeCode. 179Section 4.68.4.1.2.3.22/13/17 11:48:10 AM by aberge