<H3>Special Instructions</H3><p> <p>This test is run by PIX Patient Identity Source and PIX Manager actors which support the Pediatric    Demographics option.  These actors are only required to run one instance of this test during the connectathon (rather than 3 tests with different partners); however, you may be asked to run this test with another system if we are short of partners to test this option.</p> <p>The Patient Identity Source must run test <i>PIX_PDO_Source_Loads_Twin_Data</i> first to ensure it is ready to send these patients to the PIX Manager.</p> <p>A PIX Consumer is identified as 'optional' in this test because it does not need to execute this test for its own connectathon results, but a PIX Consumer is needed by the PIX Manager to help execute some queries.</p> </p><H3>Description</H3><p>Patient Identity Source actors which support the Pediatric Demographics option must support the    ITI-30 transaction and provide values, when available for these Pediatric Demographic fields:</p><ul>     <li>Mother's Maiden Name</li>     <li>Patient Home Telephone</li>     <li>Patient Multiple Birth Indicator</li>     <li>Patient Birth Order</li>     <li>Last update Date/Time</li>     <li>Last Update Facililty</li> </ul><p>This test consists of three parts.  Each part is a pre-requisite for the next.  Eg. If the two systems are not successful with the first part, don't proceed to the next parts unless the problem is fixed.</p><ol> <li> <b>Part one:</b> Patient Identity Source send two patients to the PIX Manager to ensure that all 6 pediatric demographic fields are supported by both the Patient Identity Source and PIX Manager systems.</li> <li> <b>Part two:</b>  Patient Identity Source sends the "twin" data to the PIX Manager.  For the NA2009 Connectathon, the spreadsheet containing this twin   demographic data is located here: <i>   http://ihewiki.wustl.edu/wiki/images/d/d3/Connectathon_TwinUseCases.xls</i> </li> <li> <b>Part three:</b>  PIX Consumer queries the PIX Manager for twin data.</li> </ol><p> <b>Part one details:</b>  The Patient Identity Source will first send information for these two patients to the PIX    Manager. The purpose of this portion of the test is to ensure that both systems support ITI-30 and can send /    store values for these fields.   If this is successful, then the ability of the PIX Manager to match based on these fields is     tested in the remaining test steps.</p><table width="700" border="3" cellspacing="0" cellpadding="0">     <tr>      <td>&nbsp;</td>     <td>&nbsp;</td>     <td>       <div align="center">        <strong>Patient 1 </strong>       </div>      </td>     <td>       <div align="center">        <strong>Patient 2 </strong>       </div>      </td>     </tr>     <tr>      <td>PID-3</td>     <td>Patient Identifier List </td>     <td>       <div align="center">as created by your system </div>      </td>     <td>       <div align="center">as created by your system </div>      </td>     </tr>     <tr>      <td>PID-5</td>     <td>Patient Name </td>     <td>       <div align="center">PDO-your-system^One^M <i>eg. PDO_PIX_MGR_ABC^One^M</i> </div>      </td>     <td>       <div align="center">PDO-your-system^Two^M <i>eg. PDO_PIX_MGR_ABC^Two^M</i> </div>      </td>     </tr>     <tr>      <td width="99">PID-6</td>     <td width="193">Mother's Maiden Name </td>     <td width="186">       <div align="center">PDO-maiden^Mom</div>      </td>     <td width="208">       <div align="center">PDO-maiden^Mom</div>      </td>     </tr>     <tr>      <td>PID-13</td>     <td>Patient Home Telephone </td>     <td>       <div align="center">888-555-1212</div>      </td>     <td>       <div align="center">888-555-1212</div>      </td>     </tr>     <tr>      <td>PID-24</td>     <td>Patient Multiple Birth Indicator </td>     <td>       <div align="center">Y</div>      </td>     <td>       <div align="center">Y</div>      </td>     </tr>     <tr>      <td>PID-25</td>     <td>Patient Birth Order </td>     <td>       <div align="center">1</div>      </td>     <td>       <div align="center">2</div>      </td>     </tr>     <tr>      <td>PID-33</td>     <td>Last Update Date/Time </td>     <td>       <div align="center">as provided by Pat ID Source </div>      </td>     <td>       <div align="center">as provided by Pat ID Source </div>      </td>     </tr>     <tr>      <td>PID-34</td>     <td>Last Update Facility </td>     <td>       <div align="center">as provided by Pat ID Source </div>      </td>     <td>       <div align="center">as provided by Pat ID Source </div>      </td>     </tr> </table><H3>Evaluation</H3><p> <b>Verify PART ONE:  </b>On the <strong>PIX Manager</strong>, the Connectathon monitor will verify that the two patients    sent by the Patient Identity Source are stored. Refer to the values in the test description. This    may be verified by displaying these patients on a user interface on the PIX Manager, or by seeing    these values in the PIX Manager database.</p><p>The monitor may ask to see a copy of the ADT^A28 message received.</p><ul>     <li>PID-6 Mother's Maiden Name</li>     <li>PID-13 Patient Home Telephone</li>     <li>PID-24 Patient Multiple Birth Indicator</li>     <li>PID-25 Patient Birth Order</li>     <li>PID-33 Last Update Date/Time</li>     <li>PID-34 Last Update Facililty</li> </ul><p>If the Patient Identity Source cannot send value for all of these fields, it does not pass this    test. </p><p>If the PIX Manager did not store values for all of these fields for both patients, it does not    pass this test.</p><p>There is no individual verification for PART TWO where twin demographics are sent to the PIX Manager.  If that is not done, PART THREE will not work. For the NA2009 Connectathon, the spreadsheet containing this twin    demographic data is located here: <i>     http://ihewiki.wustl.edu/wiki/images/d/d3/Connectathon_TwinUseCases.xls</i>   </p><p> <b>Verify PART THREE:  </b>The best method is to visit the PIX Consumer and re-execute several queries.  You may be able to evaluate the contents of queries and responses if they were captured in the chat window.  Note that the matching algorithm on the PIX Manager is not mandated by the profile.  However, the PIX Manager must demonstrate to the satisfaction of the Connectathon monitor that it has used the extra pediatric demographics to distinguish between twin records.</p> 