<H3>Special Instructions</H3><p>
 <p>Patient Demographics Suppliers must run test PDQ_Load before this can be run.</p>
 <p>Run this test and then immediately follow with PDQ_Multiple_Query with the same partner.</p>
 <p>The test is designed to return one result for one patient. Depending on the search engine, you
    might get multiple patients.</p>
 <p>
 <b>NOTE:</b>
 </p>
 <ul>
    
 <li>
 <strong>Different IHE profiles treat the HL7 assigning authority (PID 3.4)   differently. The Assigning Authority has 3 subcomponents</strong>
 </li>
    
 <ol>
     
 <li>Namespace ID (text string)   </li>
     
 <li>Universal ID (OID)   </li>
     
 <li>Universal ID type (the string <strong>ISO</strong> when you use an OID) </li>
    
 </ol>
    
 <li>
 <strong>PDQ Requirements for Connectathon</strong>
 </li>
     
 <ol>
      
 <li>Patient Demographics Consumer</li>
      
 <ul>
       
 <li>If you specify a value in QPD-8, only component 4 (Assigning Authority)   shall be valued (ITI TF-2: 3.21.4.1.2.2.2).   </li>
       
 <li>If you specify a value in QPD-8, we recommend you provide all three   components of the Assigning Authority: Namespace ID, Universal ID, Universal ID   Type. </li>
      
 </ul>
      
 <li>Patient Demographics Supplier</li>
      
 <ul>
       
 <li>The TF is silent on how to format PID 3.4.   </li>
       
 <li>For the Connectathon, we will require all three components: Namespace ID,   Universal ID, Universal ID type </li>
      
 </ul>
     
 </ol>
     
 </ul>
 </p><H3>Description</H3><p>The <b>PDQ_Exact_Name</b>  test allows a PDQ Consumer actor to make a query of a PDQ Supplier using a
    search by exact name. Each consumer will make one query of a supplier.</p>
 <p>This test uses a single, known domain that is specified by the Connectathon affinity domain. The value that should be used as the Assigning Authority is the "master" OID identified in the table in the <b>PDQ_Load</b> test.<p>
 <p>The Patient Demographics Consumer shall be able to support at least one of the following
    mechanisms for specifying QPD-8 (What Domains Returned):</p><ul>
    
 <li>Transmit an empty value and receive all identifiers in all domains known by the Patient
     Demographics Supplier (one or more domains), or</li>
    
 <li>Transmit a single value and receive zero or more identifiers in a single domain, or</li>
    
 <li>Transmit multiple values and receive mutiple identifiers in those multiple domains.</li>
 </ul><p>The purpose of this test is to establish that one query is operational.</p><H3>Evaluation</H3><p>Connectathon monitor should observe query in real time and evaluate response.</p><p>The semantics of the PDQ query are not defined by the Technical Framework. Some systems may
    return more than one record for this query. The purpose of the evaluation is to determine if a
    response is returned and if the behavior is reasonable.</p><p>For example, if the supplier always returns the entire database for any name search, that would
    not be a reasonable implementation. That would fail this test.</p><p>Notes on use of QDP-8 (What Domains Returned) - Ref ITI TF-2:3.21.4.1.2.2.2</p><ul>
    
 <li>If QPD-8 is empty, the Patient Demographics Supplier shall return all Patient IDs known by
     the Patient Demographics Supplier for each patient that matches the search criteria.</li>
    
 <li>If QPD-8 is specified and the domains are recognized,the Patient Demographics Supplier shall
     return the Patient IDs for each patient that matches the search criteria. </li>
    
 <li>Any domain not recognized by the Patient Demographics Supplier is an error condition. </li>
 </ul>