<H3>Special Instructions</H3><p> <p>None</p> </p><H3>Description</H3><p>The PDQ_Multiple_Query test requires PDQ Consumers to send different types of queries to a PDQ Supplier. Some PDQ Consumers may not have user interfaces that support all of the intended queries.</p><p>The PDQ Consumer may be an <b>Importer</b> actor in the IRWF profile.</p><p>Each query is made assuming a single domain that can be left unspecified in QDP-8 (What Domains Returned). The syntax of wild card queries is not specified by the IHE Technical Framework. There may be some negotiation between Consumer and Supplier actors.</p><H3>Evaluation</H3><p>Connectathon monitor should observe all queries in real  time and evaluate response. PDQ Consumer should demonstrate configuration/logs  indicating the PDQ Supplier that is queried.    PDQ Supplier does not need to demonstrate any results  unless there are problems. In that case, access to logs would be helpful.     The PDQ Supplier is required to support queries containing  the fields listed below.  Not all  Consumers will support all queries. Evaluate as many query combinations as are supported  by the Consumer.</p><ul>     <li>PID.3  Patient  Identifier List</li>     <li>PID.5  Patient  Name</li>     <li>PID.7  Date/Time  of Birth</li>     <li>PID.8  Administrative  Sex</li>     <li>PID.11            Patient  Address</li>     <li>PID.18            Patient  Account Number</li> </ul><p>The PDQ Supplier is required to support at least all exact  matches to the query parameters sent by the Consumer.  The Technical Framework does not further  specify matching requirements (eg wildcards, upper and lower case, alternate  spellings')      The Connectathon Monitor may ask to see a copy of the  QBP^Q22 query message to check values in the following fields:</p><ul>     <li>MSH-9            'QBP^Q22'</li>     <li>QPD-1             'IHE  PDQ Query'</li>     <li>QPD-3             <em>This field contains the query paramaters.</em> </li>     <li>QDP-8             <em>If specified, only component 4 (Assigning  Authority) has a value.</em> </li>     <li>RPC-1             'I' <em>To request an immediate reponse.</em> </li>     <li>RPC-2             <em>Note: This field, Quantity Limited Request,  is tested in PDQ_Continuation_Test.  A  value such as '25^RD' requests 25 records at a time be returned from the PDQ  Supplier.</em> </li> </ul><p>The Connectathon Monitor may ask to see a copy of the  RSP^K22 query message to check values in the following fields:</p><ul>         <li>MSH-3            <em>This field (Sending Application) contains  the value received from the PDQ Consumer in MSH-5 (Receiving Application)</em> </li>     <li>MSH-9            'RSP^K22'</li>     <li>QAK-2             'OK' <em>if data is returned</em> </li>     <li>QDP                <em>Fields in this segment are the same as those  received in the query.</em> </li>     <li>PID                 PID.3  and PID.5 <em>(Patient ID and Name) are  required.  The Supplier must also return  fields for which it has values</em> </li> </ul><p> <b>We especially want to see the query result that uses the Kudu name of the demographics supplier. This will help to show the monitor you are sending a query to the proper system.</b> </p> 