<H3>Special Instructions</H3><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>In the "remote/responding" community (it is permissible choose Registry/Repository/Source systems from the same vendor as the Responding Gateway):</p>
 <ul>  
 <li>Responding Gateway</li>
 <li>XDS.b Document Source (helping)</li>
 <li>XDS.b Document Registry (helping)</li>
 <li>XDS.b Document Repository (helping)</li>
 </ul>
 <p>
    
 <strong>
     <u>Test Configuration:</u>
    </strong>
 </p>
 <ul>
    
 <li>There are 2 communities:' the
     'local/initiating' and "remote/responding" communities are both 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.' The
     'remote' community's Responding Gateway will be configured to query the
     Document Registry and retrieve from the Document Repository in its community.' In the
     'remote' community, a Document Source is needed to submit documents to be
     retrieved.</li>
    
 <li>To simplify testing, the Assigning Authority is the same for the Patient IDs in both 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 Registry 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>The NIST Registry may serve as the XDS.b Document Registry in the
     'remote' community</li>
 </ul>
 <p>
    
 <strong>
     <u>Pre-Test Setup:</u>
    </strong>
 </p>
 <p>The Gateways need to know <a href="http://ihewiki.wustl.edu/wiki/index.php/Vienna2009-XDS_homeCommunityId_OIDs#Vienna_2009_Connectathon:_homeCommunityId_OID_values_for_XCA_Gateways"> the value of their own homeCommunityId OID</a>. 
 <p>The Gateways ensure they have been configured to know about the XCA test patients.</p>
 <p>In the "remote/responding" community, 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, Alexander PatID=WIEN5007 to the
     Registry in the 'remote community'</li>
 <li>Document Source in remote community uses PIX or PDQ Query to get Master Patient ID for patient XCA,
     Alexander PatID=WIEN5007</li>
    
 <li>ITI-41 Document Source creates a document for patietn XCA^Alexander 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 send a total of 3 documents.</li>
 </ul>
 </p>
 <H3>Description</H3>
 <p>This tests the ability of the Initiating Gateway to respond to a query from a Document Consumer
    in its XDS.b affinity domain, recognize the Patient ID, and to translate the query into a Cross-Gateway Query to a
    single Reponding Gateway.' </p>
 <p>This tests the ability of the Responding Gateway respond to an incoming Cross-Gateway Query by
    querying 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 the
    Responding Gateway 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 (you should witness the query/response real-time): </p><ul>
    
 <li>A list of the documents registered in the remote Registry for Patient ID WIEN5007 
 (XUA^Alexander is
    displayed</li>
 </ul>
 <p>Verify:</p>
 <ul>
    
 <li>When the Initiating Gateway responds to a query for a patient it does not know about, it
     responds with a list of no matching documents, but not an error.</li>
 </ul>
 