<H3>Special Instructions</H3><p>
 <p>This is a complex test to set up.   Do the "XCA_Simple_" Query and Retrieve tests before trying this one.  Then, you can just add an additional "remote/responding" community to what you already got working in the previous test.</p>
 <p> Each Initiating Gateway should run this test just once. </p>
 <p>
 <u><strong>Systems needed to run this test:</strong></u>
 </p>
 <p>In the "local/initiating" community (it is permissible choose a Consumer system from the same vendor as the Initiating Gateway):
 <ul>
 
 <li>XDS.b. Document Consumer (helping with the test)</li>
    
 <li>Initiating Gateway</li>
  </ul>
 <p>There are two "remote/responding" communities (it is permissible choose Registry/Repository/Source systems from the same vendor as the Responding Gateway):</p>
 <ul>  
 <li>Responding Gateway (2)</li>
 <li>XDS.b Document Source (2) (helping)</li>
 <li>XDS.b Document Registry (2) (helping)</li>
 <li>XDS.b Document Repository (2) (helping)</li>
 </ul>
 <p>
 <p>
    
 <strong>
     <u>Test Configuration:</u>
    </strong>
 </p>
 <ul>
    
 <li>There are 3 communities:' one 'local/initiating' and two
     'remote/responding' communities, all of which are XDS.b Affinity Domains. The
     'local' community only needs a Document Consumer in this test.' The
     Document Consumer configures the Initiating Gateway as its Registry/Repository.</li>
 <li>To simplify testing, the Assigning Authority is the same for the Patient IDs in the 
     'remote' and 'local' communities.  Use the 'Master' assigning authority value identified in kudu under Configuration-->XDS Codes/OIDs.</li>
 <li>The HIMSS Registration Tool is used to send the Patient ID for the XCA test patient to the Registries in the 'remote' community.  Several test patients with last name "XCA" have been created for you in the HIMSS Registration tool.   Refer to <a href="http://ihewiki.wustl.edu/wiki/index.php/Europe_2009#References_.26_Preparation_for_Connectathon_week">the spreadsheet of connectathon patients</a>.</li>
   <li>The XCA profile does not define how the Gateways learn of the Patient IDs.  The Gateways may use the HIMSS Registration Tool to receive an HL7v2 or v3 feed, or do this by some other means.
 </li>
 <li>Two pairs of XDS.b Registries and Repositories are needed to help with this test (and
     the next retrieve test) ' one Registry and Repository will be in the Affinity Domain
     of each of the remote communities.</li>
 </ul>
 
 <p>
    
 <strong>
     <u>Pre-Test Setup:</u>
    </strong>
 
 </p>
 <p>The Gateways ensure they have been configured to know about the XCA test patients.</p>
 <p>In both "remote/responding" communities, set up documents that can be queried:</p>
 <ul>
    
 <li>ITI-8 or ITI-44 - Patient Identity Source (HIMSS Registration Tool)  in 'remote
     community' sends ID for Patient XCA, Amy PatID=WIEN5008 to the
     Registry in both of the 'remote' communitiets</li>
 <li>Document Source in remote community uses PIX or PDQ Query to get Master Patient ID for patient XCA,
     Amy PatID=WIEN5008</li>
    
 <li>ITI-41 Document Source creates a document for patient XCA^Amy and sends it to the Repository (Provide & Reg
     Doc Set)</li>
    
 <li>ITI-42 Document Repository registers the document with the Document Registry</li>
    
 <li>Repeat previous 2 steps to have a total of 3 documents available in each remote community for XCA^Amy.</li>
 </ul>
 
 
 
 <H3>Description</H3>
 <p>This tests the ability of the Initiating Gateway to respond to a query request from a Document
    Consumer in its XDS.b affinity domain and to translate the query into a Cross-Gateway Query to
    more than one Reponding Gateway.' </p>
 <p>This tests the ability of the Responding Gateway respond to an incoming Cross-Gateway Retrieve
    by sending a query request its local Registry and returning the response to the Initiating
    Gateway.</p>
 <p>This tests the ability of the Initiating Gateway to return the query results received from all
    of the Responding Gateways to the Document Consumer it its community.</p>
 <H3>Evaluation</H3>
 <p>On the <strong>Document Consumer </strong>in the Initiating Gateway's community,
    verify: </p>
 <ul>
    
 <li>A consolidated list of the documents registered in both of the remote Registries for Patient
     ID WIEN5008 displayed</li>
 </ul>
 <p>Ideally, you would have a Doc Consumer query each remote registry separately, showing the individual community's documents for that patient, and then you query the Initiating Gateway and see a consolidated list.</p>