net.ihe.gazelle.assets.SearchCriteria : 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
XDSIXDSI-001reviewedNot testable 0 1 The XDS-I.b specification does not repeat requirements and text for the XDS-defined Actors Document Repository, Document Registry, and Document Consumer, and does not place any new requirements on these actors.191Section 188/21/19 4:36:16 PM by aeschlimann
XDSIXDSI-004reviewedNot testable 0 5 XDS and XDS-I.b do not address transactions for the management or configuration of an XDS Affinity Domain. For example, the configuration of network addresses or the definition of what type of clinical information is to be shared is specifically left up to the policies established by the XDS Affinity Domain.191Section 188/21/19 4:36:35 PM by aeschlimann
XDSIXDSI-005reviewedNot testable 0 5 XDS and XDS-I.b do not specifically address the patient information reconciliation process necessary between the XDS Affinity Domain and any other local patient identity domains that Document Sources and Document Consumers may be members of. For a discussion of some of these issues see RAD TF-1: Appendix G.192Section 188/21/19 4:37:10 PM by aeschlimann
XDSIXDSI-006reviewedNot testable 0 5 XDS and XDS-I.b do not directly address the rendering and display of the documents retrieved by the Document and Imaging Document Consumers. Users wishing to achieve a well-defined level of display/ rendering capability simply need to request systems that combine the XDS-I.b Imaging Document Consumer Actor with an Image Display Actor from the appropriate Profile (e.g., Mammography Image, NM Image, Basic Image Review, etc.).191Section 188/21/19 4:37:29 PM by aeschlimann
XDSIXDSI-008reviewedTestable 1 1 The Imaging Document Consumer Actor shall support retrieve operations using at least one of the following transactions+ [RAD-16] Retrieve Images+ [RAD-17] Retrieve Reports+ [RAD-45] Retrieve Evidence Documents+ [RAD-55] WADO Retrieve+ [RAD-69] Retrieve Imaging Document Set192Section 18.18/26/19 5:25:26 PM by aeschlimann
XDSIXDSI-009reviewedTestable 1 1 The Imaging Document Source shall support the [RAD-68] Provide and Register Imaging Document Set - MTOM/XOP transaction with at least one of the four document types described in RAD TF 1:18.2192Section 18.18/26/19 5:25:26 PM by aeschlimann
XDSIXDSI-010reviewedTestable 0 1 If the Imaging Document Source supports the Set of DICOM Instances option, it shall support all of the following transactions:+ [RAD-16] Retrieve Images+ [RAD-17] Retrieve Presentation States+ [RAD-27] Retrieve Reports+ [RAD-31] Retrieve Key Image Note+ [RAD-45] Retrieve Evidence Documents+ [RAD-55] WADO Retrieve+ [RAD-69] Retrieve Imaging Document Set192Section 18.18/26/19 5:25:26 PM by wbars
XDSIXDSI-011reviewedTestable 1 1 This option requires the Imaging Document Source to create a DICOM manifest that references DICOM instances, and to provide and register this document to the Document Repository. The Imaging Document Source is required to ensure that the referenced images from within a published manifest are available to be retrieved. For details of the transaction affected by this option, refer to RAD TF-3: 4.68.4.1.2.1.195Section 18.2.18/26/19 5:25:26 PM by aeschlimann
XDSIXDSI-012reviewedTestable 0 1 This option requires the Imaging Document Source to provide and register an Imaging Report in a PDF format to the Document Repository. The published report may contain embedded images or pre-computed links that reference images in a non-DICOM format. The Imaging Document Source is required to ensure that image references are valid links. For details of the transaction affected by this option, refer to RAD TF-3: 4.68.4.1.2.2.195Section 18.2.18/26/19 5:25:26 PM by wbars
XDSIXDSI-013reviewedTestable 0 1 Imaging Document Source set to NONEThis option requires the Imaging Document Source to send to the Document Repository a CDA R2 document containing a Text Report. For details, refer to RAD TF-3: 4.68.4.1.2.2.195Section 18.2.18/26/19 5:25:26 PM by wbars
XDSIXDSI-014reviewedTestable 0 1 Imaging Document Source set to NONEThis option requires the Imaging Document Source to send to the Document Repository a CDA R2 document containing an Imaging Report with Structured Headings. For details, refer to RAD TF-3: 4.68.4.1.2.2.195Section 18.2.18/26/19 5:25:26 PM by wbars
XDSIXDSI-015reviewedTestable 0 1 The Imaging Document Source may share a report addendum by using XDS.b transactions to upload and register a new document as an addendum to the existing document.The addendum will be stored in a separate submission set.201Section 18.3.3.2.15/10/19 9:07:44 AM by wbars
XDSIXDSI-016reviewedTestable 1 1 When the Imaging Document Consumer retrieves a manifest from the Document Repository, it is expected to decode the Key Object Selection Document Instance in order to find the references to DICOM objects. The Imaging Document Consumer is also expected to retrieve the referenced DICOM objects using DICOM retrieve or WADO.206Section 18.4.18/21/19 5:00:14 PM by aeschlimann
XDSIXDSI-017reviewedTestable 1 1 The Imaging Document Consumer "should not make any assumptions about whether one or more studies are referenced within the Key Object Selection Document."206Section 18.4.18/26/19 5:25:26 PM by aeschlimann
XDSIXDSI-018reviewedTestable 0 5 Read Appendix G for Patient Information Reconciliation considerations. Appendix G contains suggestions but no requirements.206Section 18.55/10/19 9:07:44 AM by wbars
XDSIXDSI-019reviewedTestable 4 5 All XDS-I.b actors shall be grouped with either a Secure Node or Secure Application Actor from the ATNA Profile.207Section 18.68/21/19 5:04:17 PM by aeschlimann
XDSIXDSI-020reviewedTestable 1 5 All XDS-I.b actors ... shall ... support the Radiology Audit Trail Option207Section 18.65/10/19 10:22:56 AM by wbars
XDSIXDSI-021reviewedNot testable 0 5 Read Appendix H for other security considerations. Appendix H contains suggestions but no requirements207Section 18.68/21/19 4:41:09 PM by aeschlimann
XDSIXDSI-022reviewedTestable 0 1 Imaging Document Source set to NONEIn this option the Document Source or Integrated Document Source/Repository shall offer the ability to submit a document as a replacement for another document already in the registry/repository.If the images are changed (new images added, demographics updated, ....) the Imaging Document Source will replace the existing KOS with an updated KOS that references the new images.191Section 185/10/19 9:07:44 AM by wbars