<H3>Special Instructions</H3><p>  <p>QED_Preload is used by QED Clinical Data Sources to load known data into their systems.      This can be done in advance of the Connectathon event.</p>  <p>The source data is under construction and can be found on our wiki page:   <ul>    <li><a href="http://ihewiki.wustl.edu/wiki/index.php/QED_Preload">http://ihewiki.wustl.edu/wiki/index.php/QED_Preload</a></li>   </ul>  </p> <H3>Description</H3> <p>The purpose of QED_Preload is for the repository to load a set of pre-defined patients with      known data. This will allow the consumer actors to know which patients are in the system      and what data will be returned.</p><p>The preload test will list 5 patients below and the general use for each patient.      Then, we will provide the actual data for each patient.</p><p>If the data specified does not make sense or cannot be created, contact the Connectathon      Manager and negotiate for proper data. You know this domain better than we do, and we do not      want to put you through (too many) contortions.</p>    <ol>    <li>Qed, Zero:   This patient will be configured so that any query for different types of data        will return 0 items. The patient is known to the Clinical Data Source, but there are no       entries for that type of data for that patient.</li>    <li>Qed, One: This patient will be configured so that any query for different types of data        will normally return 1 item (1 medication1, 1 immunization, etc.)</li>    <li>Qed, Two: This patient will be configured so that any query for different types of data        will normally return 2 items (2 medications, 2 immunizations, etc.</li>    <li>Qed, Three: Placeholder</li>    <li>Qed, Four: The Consumer will query the Source for this patient, but you should not         have this patient in your system. The goal of using this patient is to have a consumer         send a query that should result in a specific error code. Do not enter this patient in         your system, but do not be surprised when you see a query.</li>    <li>Qed, Five: This will support an optional test by the consumer. We will ask if they can send        a query with a code value that is not recognized by the repository. The repository will return       the appropriate error code. For data, you could replicate the data from Qed, One.</li>   </ol>  <H3>Evaluation</H3>  <p>The monitor will accept your word that you have done this test. Find the monitor responsible       for QED testing and tell him/her you have finished this.</p> 