<H3>Special Instructions</H3><p> <strong>DO NOT DO THIS TEST IS YOU ALREADY HAVE DONE ARI_GSPS WITH THE SAME PARTNER</strong> <p>The Image Manager/Archive must complete a Modality-Image Manager test before this test can be run with the Image Display actor. This ensures images are already available on the IM.</p> <p>This test is used in the ARI , NMI and SWF profiles; it tests the required query/retrieve transactions between and ID and IM actor.</p> <p>This test can be replaced by ARI_GSPS for Image Displays that support GSPS objects.</p> </p> <H3>Description</H3> <p>Here we test the ARI Option Multiple Sources. Do not run the test if you do not support that option</p> <p>In order to claim support for this profile option, an Image Display shall be able to query and retrieve from multiple Image Manager/Image Archives.</p> <p>There is no requirement as to whether the multiple queries or retrieves are done concurrently or sequentially.</p> <p>Image Displays shall have the ability to be configured to access multiple Image Manager/Image Archives (respectively).</p> <p>Image Managers shall also support the Patient Information Reconciliation integration profile in order to ensure that the information gathered from them is as accurate as possible. Since having actors in different ADT (patient identifier) domains could result in unpredictable query results, this option assumes that all actors are members of the same ADT domain (i.e., it can be assumed that a given patient identifier uniquely refers to a single patient).</p> <p>An Image Display supporting this profile option may be configured to initially query only its local information source; however, it shall be possible to query multiple sources with a single user request.</p> <p>When an Image Display and Report Reader are combined, a single user request shall suffice to trigger a query of multiple sources for both images (and anything else stored in an Image Manager/Image Archive) and reports.</p> <p>If communication with an information source fails, an Image Display shall provide the information it received from the other sources. In addition, the Image Display shall inform the user that they are viewing potentially incomplete results.</p> <p>When an Image Display performs a study-level or series-level query to multiple sources and finds the study/series referenced in multiple places, the study/series is either duplicated or the study/series is split across the systems. When the user requests a retrieval of the study/series an Image Display shall collate the information, determine if the information is actually duplicated or split, and present to the user a consolidated view of results. The consolidated view of results may be shown and updated either as responses are received or when the final response has been received from the last responding information source.</p> <p>A participating Image Display shall manage duplicate instances in a manner that avoids redundant retrieve.</p>  <H3>Evaluation</H3> <p> <em>Evaluators and participants should note that this section contains all query keys documented in the Technical Framework. At the North American Connectathon in Chicago, many Display vendors were surprised that these are requirements. We are *not* failing systems this year if you do not support everything below. However, the Connectathon Monitor will verify that you have a reasonable implementation that allows you to query the Image Manager using different parameters.</em> </p> <p>On the <strong>Image Display:</strong> </p> <ul> <li>The Connectathon Monitor will ask the operator to demonstrate its support for the DICOM Study Root Q/R Information Model and Hierarchical Search.</li> <li>It will demonstrate on its User Interface the ability to offer its user the following attributes as selection criteria (ie these required query keys for the Image Displays SCU (RAD TF-2 Table 4.14-1). Query the Image Manager for combinations of:</li>  <li> <strong>STUDY LEVEL</strong> Query Keys:     <ul> 	   <li>Study Date (0008,0020)</li>         <li>Study Time (0008,0030) </li>        <li>Accession Number (0008,0050)</li>         <li>Patient Name (0010,0010) </li>        <li>Study ID (0020,0010) </li>        <li>Study Instance UID (0020,000D)</li>         <li>Modalities in Study (0008,0061) </li>        <li>Referring Physician’s Name (0008,0090)</li> 	 </ul> </li> <li> <strong>SERIES LEVEL</strong> Query Keys:     <ul> 	   <li>Modality (0008,0020)</li>         <li>Series Number (0020,0011) </li>        <li>Series Instance UID (0020,000E) </li>        <li>Requested Procedure ID (0040,1001) </li>        <li>Scheduled Procedure Step ID (0040,0009)</li>         <li>PPS Start Date (0040,0244)</li>         <li>PPS Start Time (0040,0245)</li>  	 </ul> </li> <li> <strong>IMAGE LEVEL</strong> Query Keys:     <ul> 	   <li>Instance Number (0020,0013)</li>        <li>SOP Instance UID (0008,0016)</li> 	 </ul> </li> </ul><p>Verify the ability to retrieve by study, by series and by image. Images should be retrieved and displayed. GSPS objects should be displayed if supported. For evaluation, the Project Manager should make sure that the Image Display can query the Image Manager and return results. Retrieving the images will ensure that the Image Manager faithfully reproduces the data that it stores. (Detailed rendering evaluation is done in the Display tests in the Content profiles.)</p> 