<H3>Special Instructions</H3><p>  <p>The Clinical Data Source and Clinical Data Consumer run this test only if they support the Medications Option      in the QED profile.</p>  <p>The Clinical Data Source needs to complete the QED_Preload test before starting this test.      This test will tell you which medications 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 medications to standardize the test process.</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>The data for the Sources is found in the QED_Preload test. We are using a wiki page to construct      the content. That gives you the opportunity to help us improve the test content. You can find the wiki      page at <a href="http://ihewiki.wustl.edu/wiki/index.php/QED_Preload">http://ihewiki.wustl.edu/wiki/index.php/QED_Preload</a>.  </p> <H3>Description</H3>  <p>The purpose of QED_QueryMedications is for the Clinical Data Consumer to execute several queries      with a Clinical Data Source in real time in the presence of a monitor. The required queries are listed below.      You are free to negotiate and try other queries, but these will not be evaluated.</p>  <p>The Clinical Data Consumer shall provide these query parameters in the query per PCC 2: Table 3.1-1   <ul>    <li>includeCarePlanAttachment</li>    <li>patientId</li>   </ul>   The Clinical Data Source shall use those parameters to formulate the response. If the Consumer provides   other optional parameters (see PCC 2: Table 3.1-1), the Source shall also use those parameters to formulate   the response. </p>  <p>The goal of this test is to query for all active medications. If consumers provide a value for <em>careProvisionCode</em>,        they should use the value CURMEDLIST. Acceptable but not encouraged values for this test are RXCAT, MEDLIST, and        HISTMEDLIST. For this test, do not use DISCHMEDLIST.  <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>  <ol>   <li>PatientId 110: Qed, Zero: Source knows about patient, but returns zero medications.</li>   <li>PatientId 120: Qed, One: Should return one defined medication.</li>   <li>PatientId 130: Qed, Two: Should return two defined medications.</li>   <li>PatientId 140: Qed, Four: Source does not know about patient and returns KEY204 detected issue alert.</li>   <li>PatientId 150: Qed, Five: This is optional. If the Consumer can manage, send a query with a code that is        not recognized by the 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 medications 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 medications are available for each patient.</p> 