<H3>Special Instructions</H3><p> <h4>Background information </h4> <p>Experience has shown that Connectathon tests are run most efficiently if 2, or at most 3,    systems are involved in a test. Thus, most tests exercise an exchange of transactions between 2    actors.</p> <p>Later in the week, Connectathon systems are assigned to groups to test an end-to-end workflow    for all actors in profiles such as Radiology SWF, Cardiology CATH, ECHO & STRESS, and the    ITI XDS.a and XDS.b profiles. Workflow tests are executed step-by-step during an assigned 2-hour    time slot under the supervision of a Connectathon monitor who helps facilitate the process and    checks for results as transac    tions are exchanged between systems. </p> <p>This document outlines an XDS test and offers advice for Connectathon monitors and systems    involved in the test to help ensure the test run as smoothly as possible. There are 4 group tests    for XDS: <strong>XDS.a_Workflow_PDQ, </strong><strong>XDS.b_Workflow_PDQ,</strong>    <strong>XDS.a_Workflow_PIX,</strong> and <strong>XDS.b_Workflow_PIX</strong>. </p> <h4>Responsibilities of the Connectathon monitor</h4> <ul>     <li>Read the test and understand the steps</li>     <li>Gather the participants; explain the scenario; answer questions </li>     <li>Facilitate solving configuration issues </li>     <li>Spend the two hour test period walking participants through the test steps and helping     participants solve interoperability issues encountered</li>     <li>Debrief test participants after the test is over</li>     <li>Record notes on test results in kudu </li> </ul> <h4>Responsibililites of the workflow test participants</h4> <ul>     <li>Read the test and understand the steps</li>     <li>Attend the pre-test meeting with the Connectathon monitor </li>     <li>Configure your system to talk to your partners in the group test</li>     <li>If time, do preliminary point-to-point test with your partners</li>     <li>Follow the Connectathon monitor's instructions</li>     <li>During the workflow tests, there may be times when your system is not involved. You may     continue with other peer-to-peer tests you need to complete, but the workflow test takes top     priority if the Connectathon monitor comes back to you </li> </ul> <h4> Workflow test preparation</h4> <table width="700" border="3" cellspacing="0" cellpadding="0">     <tr>      <td width="99">       <div align="center">        <strong>Who</strong>       </div>      </td>     <td width="209">       <div align="center">        <strong>Task</strong>       </div>      </td>     <td width="380">       <div align="center">        <strong>Notes</strong>       </div>      </td>     </tr>     <tr>      <td>Connectathon manager </td>     <td>Create groups of systems for the workflow tests. </td>     <td>       <p>This is a non-trivial task. Factors to consider include grouping systems according to their       support for XDS.a, XDS.b, PIX, PDQ (HL7 v2.x or v3), ensuring a mix of vendors is represented       in the group, whether systems are actually working well, and potentially whether the systems       will be working together in a demonstration. A sample group assignment worksheet from a       previous Connectathon is <a href="ftp://ftp.ihe.net/Connectathon/Reference_Material/group_tests_berlin.v3.xls">here</a>.      </p>      </td>     </tr>     <tr>      <td>Connectathon manager </td>     <td>Complete checklist of parameters to be used on the test </td>     <td>Located on Connectathon wiki; includes assigning authority, list of participants and their      roles, local ID to be used...</td>     </tr>     <tr>      <td>Connectathon manager </td>     <td>Gather the group; present test details: actor assignments, configuration needs (URLs,      assigning authority, patient for test), test steps, start time</td>     <td>Ideally complete a half a day before the start of the workflow tests. This enables systems      to test individual interoperability prior to the test and avoid delays during the test.</td>     </tr>     <tr>      <td>Workflow participants </td>     <td>Create patients for the test in RIS Mall </td>     <td>Complete prior to the start of all tests. </td>     </tr>     <tr>      <td>Connectathon manager </td>     <td>Gather workflow participants; present scenario </td>     <td>'</td>     </tr>     <tr>      <td>Workflow test participants </td>     <td>Configure your systems; try point-to-point tests </td>     <td>Ensure you can talk to your test partners; if time, try a transaction or two </td>     </tr> </table> </p><H3>Description</H3><p> <strong>XDS.b_Workflow_PDQ </strong>is a test of the entire XDS workflow, including all of the    actors in the profile and actors from the PDQ profile. This test traces the Patient Identity from    an Identity Source to a Patient Demographic Supplier. XDS actors get the Patient ID through a    direct feed or by a PDQ query. If test participants successfully complete one workflow    (submit/register/query/retrieve document) and time allows, they are encouraged proceed to the    optional steps at the end of the tests. </p><p>The PDQ Patient Demographics Source actor will support either HL7 v2.x or HL7 v3. Actors will    be assigned to groups according to their profile support. </p> </p> <p>The test itself is contained in <a href=http://ihewiki.wustl.edu/wiki/index.php/Image:XDS_workflow.doc>this document</a> which connectathon monitors will use as they guide the test systems through the workflow. </p> <H3>Evaluation</H3><p>This is a group test involving multiple systems. The Connectathon monitor will run the test in    real time and visit each system at the appropriate time, looking for the arrival of requested    data.</p> 