<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 immunizations 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 immunizations to standardize the test process.</p> <p>The Clinical Data Consumer runs this test only if it supports the Query Immunizations option      in the QED profile.</p> <p>The QED profile requires support for a specific query that returns all immunizations (IMMUCAT). This      test will discuss the ability to send other queries that are not required by either the Consumer or 	 Clinical Data Source. If you want to test those queries, you (both Consumer and Clinical Data Source) need to contact 	 each other in advance of the Connectathon and negotiate those other query parameters. 	 The Connectathon Manager will help you document this, but will not require optional queries.</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_QueryImmunizations 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 shall request all immunizations using the value IMMUCAT (PCC 2:4.5.2.2)</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> <ol>  <li>Qed, Zero: Should return zero immunizations.</li>  <li> Qed, One: Should return one defined immunization.</li>  <li>Qed, Two: Should return two defined immunizations.</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 immunizations 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 immunizations are available for each patient.</p> 