<H3>Special Instructions</H3><p> <p>The Clinical Data Source needs to complete the QED_Preload test before starting this test.      This test will tell you which problems/allergies should be stored for which patients. Follow the 	 instructions in that test and contact the PCC Project Manager if they are not clear. The goal 	 is a uniform set of problems/allergies to standardize the test process.</p> <p>The Clinical Data Consumer runs this test only if it supports the Query Problems/Allergies option      in the QED profile.</p> <p>The QED profile allows the Consumer to select different coded values to request different data      from the Clinical Data Source. In the test instructions below, the Consumer is given the option of which 	 code (or codes) to use. The Consumer is constrained to those codes and cannot invent new ones. </p> <p>The QED profile makes no recommendiation on patient identifier. We will choose a patient identifier      from one Affinity Domain. This will likely involve some hand coding. If you need PIX, PDQ or ADT 	 help, discuss with the Connectathon Manager.</p> </p><H3>Description</H3> <p>The purpose of QED_QueryProblemsAllergies is for the Clinical Data Consumer to execute several queries      with a Clinical Data Source in real time in the presence of a monitor.</p> <p>The consumer and Clinical Data Source may negotiate and try other queries. This is not a requirement.</p> <p>The Clinical Data Source has pre-loaded data for defined patients. These queries are required.      The names refer to patients with identifiers that have been pre-loaded by the Clinical Data Source.</p> <p>The Consumer shall make the queries below using codes from the following list. The Consumer      needs to support at least one of the codes. The consumer may repeat the test with different 	 codes. That would be encouraged.</p>  <p>These Care Provision Codes are taken from PCC 2:3.1.4.5.2</p> <table>     <tr> <th>Code</th><th>Returns</th><th>Template Id</th> </tr>     <tr> <td>MEDCCAT</td><td>All problem entries</td><td>Problem Entry</td> </tr>  <tr> <td>CONDLIST</td><td>All Concern Entries</td><td>Concern Entry</td> </tr>  <tr> <td>PROBLIST</td><td>ALl Problem Concerns</td><td>Problem Concern</td> </tr>     <tr> <td>INTOLIST</td><td>All Allergy Concerns</td><td>Allergy and Intolerance Concern</td> </tr>     <tr> <td>RISKLIST</td><td>All Risks</td><td>Concern Entry</td> </tr> </table><ol>      <li>Qed, Zero: Clinical Data Source knows about the patient, but returns 0 problems/allergies.</li>  <li>Qed, One: Should return 1 defined problems/allergy.</li>  <li>Qed, Two: Should return two defined problems/allergies.</li>  <li>Qed, Four: Clinical Data Source does not know about patient and returns KEY204 detected issue alert.</li>  <li>Qed, Five: This is optional. If the Consumer can manage, send a query with a code that is        not recognized by the Clinical Data Source. The Clinical Data Source should respond with a CODE_INVALID       detected issue alert.</li> </ol> <H3>Evaluation</H3> <p>The monitor evaluates this test in real time by observing the queries sent by the Clinical Data      Consumer. Each query is listed in the Description above. You should observe each query in real 	 time and make sure the Consumer retrieves the problems/allergies as stated by the test and then 	 stores and/or displays them.</p> <p>There are no requirements on the Consumer for use of the data after the query. You could imagine      they will display in real time to a user. The Consumer might decide to store the data in a database      for later work. You have to be flexible and understand the application.</p> <p>The QED_Load test will tell you which problems/allergies are available for each patient.</p> 