| XDSI | XDSI-001 | reviewed | 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. | 200 | Section 18 | 1/18/17 11:03:50 AM by aberge |
|
| XDSI | XDSI-002 | reviewed | 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. | 200 | Section 18 | 1/18/17 11:05:56 AM by aberge |
|
| XDSI | XDSI-003 | reviewed | 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. | 200 | Section 18 | 1/18/17 11:06:34 AM by aberge |
|
| XDSI | XDSI-004 | reviewed | 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. | 201 | Section 18 | 1/18/17 11:07:26 AM by aberge |
|
| XDSI | XDSI-005 | reviewed | 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. | 201 | Section 18 | 1/18/17 11:38:18 AM by jdramou |
|
| XDSI | XDSI-006 | reviewed | 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.). | 201 | Section 18 | 1/18/17 11:41:20 AM by jdramou |
|
| XDSI | XDSI-007 | reviewed | 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.). | 201 | Section 18 | 1/18/17 11:41:26 AM by jdramou |
|
| XDSI | XDSI-012 | reviewed | Testable |
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. | 204 | Section 18.2.1 | 1/18/17 5:35:38 PM by jdramou |
|
| XDSI | XDSI-013 | reviewed | Testable |
0
|
1
| Imaging Document Source set to NONE | This 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. | 204 | Section 18.2.1 | 1/18/17 5:51:58 PM by jdramou |
|
| XDSI | XDSI-014 | reviewed | Testable |
0
|
1
| Imaging Document Source set to NONE | This 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. | 204 | Section 18.2.1 | 1/18/17 5:51:45 PM by jdramou |
|
| XDSI | XDSI-015 | reviewed | Testable |
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. | 211 | Section 18.3.3.2.1 | 1/18/17 5:44:41 PM by jdramou |
|
| XDSI | XDSI-018 | reviewed | Testable |
0
|
5
| | Read Appendix G for Patient Information Reconciliation considerations. Appendix G contains suggestions but no requirements. | 217 | Section 18.4.1 | 1/18/17 5:45:48 PM by jdramou |
|
| XDSI | XDSI-019 | reviewed | Testable |
0
|
5
| | All XDS-I.b actors shall be grouped with either a Secure Node or Secure Application Actor from the ATNA Profile. | 217 | Section 18.4.1 | 1/18/17 5:49:16 PM by jdramou |
|
| XDSI | XDSI-020 | reviewed | Testable |
0
|
5
| | All XDS-I.b actors ... shall ... support the Radiology Audit Trail Option | 217 | Section 18.4.1 | 1/18/17 5:49:21 PM by jdramou |
|
| XDSI | XDSI-021 | reviewed | Testable |
0
|
5
| | Read Appendix H for other security considerations. Appendix H contains suggestions but no requirements | 217 | Section 18.4.1 | 1/18/17 5:49:31 PM by jdramou |
|
| XDSI | XDSI-022 | reviewed | Testable |
0
|
1
| Imaging Document Source set to NONE | In 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. | 97 | Section 10.2.1 | 1/18/17 5:51:07 PM by jdramou |
|