<H3>Special Instructions</H3><p> <p>This tests the transactions required by both Patient Encounter Suppliers and Consumers in the    PAM profile. The various options in the profile are tested in    <b>PAM_Adv_Encounter_Management.</b> </p> <p>At the beginning of this test, the Patient Encounter Supplier should admit the following    patients using <b>ADT^A01^ADT_A01</b>. Note that the patient's first name is the kudu system name (or    vendor name) of the receiving system, the Patient Encounter Consumer:</p> <ol>     <li>Pampatientone^PEC-kudu-system-name</li>     <li>Pampatienttwo^PEC-kudu-system-name</li>     <li>Pampatientthree^PEC-kudu-system-name</li>     <li>Pamdischarged^PEC-kudu-system-name</li>     <li>Pammerge^PEC-kudu-system-name</li> </ol> </p><H3>Description</H3><p>This tests the exchange of messages between Patient Encounter Suppliers and Patient Encounter    Consumers for the following events: </p><ul>     <li>Admit inpatient, and cancel admit</li>     <li>Register outpatient</li>     <li>Discharge patient, and cancel discharge</li>     <li>Update patient information</li>     <li>Merge patient identifier list</li> </ul><p>Support for messaging associated with these events is required by the PAM profile.</p><H3>Evaluation</H3><p>The PEC is required to ACK all messages received from the PES.</p><p>On the <strong>Patient Encounter Consumer</strong>, the Connectathon monitor will verify that    the messages were received and the patient's status has been updated on the PEC system:</p><ul>     <li>Pampatienttwo is not an inpatient (his admission was cancelled</li>     <li>Pampatientthree is an inpatient (his discharge was cancelled)</li>     <li>Pamdischarged is discharged or has status "visit ended"</li>    <li>Pampatientmerge is the subsumed patient from the merge.</li>    <li>Pampatientone's birthdate is 1911-11-11.</li> <li>Pampatientone  is the surviving patient from the merge </li>      </ul> 