<H3>Special Instructions</H3><p> <p> PDC and PDS actors which support the <b>Merge option</b> run this test. If your system    supports the Link/Unlink option, run test PAM_ID_Mgmt_Link.</p> <p>Patient Names created by the Patient Demographics Supplier will follow a pattern to make things easy    to follow. The last name shall have 2 components (with no separators):</p> <ol>     <li>The letters Pam</li>     <li>3-5 letters that distinquish your company/system</li> </ol> <p>In the test instructions, names will look like this:     <center>Pam<b>system^</b>letters</center> where <b>system</b> marks your system. </p> </p><H3>Description</H3><p>This test is based on the use case defined in the PAM profile. </p><ol>     <li> Create Patient: Pam<b>system</b>. The Patient Demographics Supplier creates a new patient      Pam<b>system</b>^Ab. Fill in DOB, Sex and other demographics as if this was a known patient.     Patient Demographics Supplier sends A28 message to Patient Demographics Consumer to inform consumer of     patient information. </li>     <li>Patient Ab now changes first name to 'Cd'. Patient Demographics Supplier sends A31 message to     indicate new patient name: Pam<b>system</b>. At this point, Patient Demographics Consumer should     provide a screen capture or database dump in the logs to indicate it now has the updated name in     its local database. The Connectathon Monitor will review later.</li>     <li>A new, but unknown, patient is now entered in the Patient Demographics Supplier system. Patient     Demographics Supplier should create the patient Pam<b>system</b>^Ef as a new patient with limited     demographics. Patient Demographics Supplier sends A28 message to Patient Demographics Consumer to inform     consumer of patient information. Patient Demographics Consumer should perform a screen capture or     database dump to indicate it now has Pam<b>system</b>^Ef entered in its system.</li>     <li>Patient Demographics Supplier now understands that Ef is the same as Cd. Patient Demographics Supplier     sends A40 merge message to Patient Demographics Consumer. The surviving patient in the database     should be Pam<b>system</b>^Cd. Patient Demographics Consumer should perform a screen capture or     database dump that indicates Pam<b>system</b>^Ef is no longer active/available (depends on your     implementation). </li>     <li>Bonus points that will not be graded: If you can somehow demonstrate clinical records that     existed under the individual records for Cd and Ef that are now merged under Cd, that is the     intent of the A40 merge operation. This will not be evaluated by the Connectathon monitor.</li> </ol><H3>Evaluation</H3><p> The Connectathon monitor will ask the Patient Demographics Consumer to show database dumps or    screen captures that show the state of the system at three different points in time: <ol>      <li>After the demographic update to change the name from Ab to Cd.</li>      <li>After sending the demographic for the (unknown) Ef.</li>      <li>After the merge of Ef and Cd (with Cd surviving). Ef should no longer be visible.</li>.    </ol> If the Patient Identity Consumer cannot show this with screen captures or log information,    the Connectathon monitor will ask to see the test performed in real time. </p>  