<H3>Special Instructions</H3><p> <p>None</p> </p><H3>Description</H3><p>The ECHO_EvidenceCreator_PACS_Display test exercises the <strong><u>Echo Workflow Profile </u></strong>transactions  between an Evidence Creator, an Image Manager/Image Archive and an Image  Display. In the Echo Workflow Integration profile, the Evidence Creator must  perform a Performed Procedure Step and then   produce these documents (SR reports, not images) and store them on the  Image Manager. These documents must also be committed using the Storage  Commitment transaction.  These are a  superset of the transactions in the Evidence Documents profile, which requires  CARD-2 (storage) and CARD-3 (storage commit) only.  </p><p>    The Image Display must be able to render and display all  Templates for the SOP Classes which they accept.</p><p>    An Evidence Creator must produce documents from the  following list and an Image Manager must be able to store those documents:</p><ul>     <li>Enhanced SR</li>     <li>Comprehensive SR</li> </ul><p>The Echo Option Templates include:</p><ul>     <li>5100 Vascular Ultrasound</li>     <li>5200 Echocardiography</li> </ul><p>All supported SOP Classes and all supported Templates  within those SOP Classes must be tested and verified.   </p><p>    To aide in evaluation, it is in your best interest to  begin with an image or Modality Worklist where most of the information listed  below is known to be present, otherwise you will spend a significant amount of  time justifying the absence of the information.</p><H3>Evaluation</H3><p>On the <strong>Image Manager:</strong> </p><p>The Connectathon Monitor should observe evidence from the Image Manager that these documents     were stored. This can be a display on the Image Manager, a 3rd party display or logs or database     on the Image Manager if no display is readily available. At the Image Manager, all of the     following attributes of the Structured Report object from the Modality shall be verified to match     the original image or MWL information: (see Rad TF-2: Appendix A, Table A.2-1 and section A.3):</p><ul>      <li>Study Instance UID (0020, 000D)</li>      <li>Referenced Request Sequence (0040, A370) <ul>       <li>>Study Instance UID (0020, 000D)</li>       <li>>Referenced Study Sequence (0008, 1110)</li>       <li>>Accession Number (0008, 0050)</li>       <li>>Requested Procedure ID (0040, 1001)</li>       <li>>Requested Procedure Description (0032, 1060)</li>       <li>>Requested Procedure Code Sequence (0032, 1064)</li>      </ul>      </li>      <li>Performed Procedure Code Sequence (0040, A372)</li>      <li>Referenced Study Component Sequence<ul>       <li> >Referenced SOP Class UID (0008, 1150)</li>       <li> >Referenced SOP Instance UID (0008, 1155)</li>      </ul>      </li>      <li>Patient Name (0010, 0010)</li>      <li>Patient ID (0010, 0020)</li>      <li>Patient’s Birth Date (0010, 0030)</li>      <li>Patient’s Sex (0010, 0040)</li>      <li>Referring Physicians Name (0008, 0090)</li>      <li>Completion Flag (0040,A491)</li>     </ul><p>The Connectathon Monitor should also observe logs in the Image Manager that demonstrate the     Storage Commitment transaction. All of the following attributes shall be verified in the Storage     Commit message from the Modality:</p><ul>      <li>Referenced SOP Sequence (0008, 1199)<ul>       <li> >Reference SOP Class (0008, 1150)</li>       <li>>Referenced SOP Instance UID (0008, 1155)</li>      </ul>      </li>     </ul><p>At the <strong>Image Display:</strong> The Connectathon monitor should observe the Image     Display and its ability to interpret/render the Evidence Documents. The Connectathon monitor     should observe the original report at the Image Manger, the Acqusition Modality, the Evidence     Creator, or another Image Display and spot check the Image Display/Report creator to verify the     contents of the Structured Report are displayed correctly and completely.      </p> 