<H3>Special Instructions</H3> <p>Test <b>PIX_Seed_Mgr</b> must be run by the PIX Manager before this one can be done.</p> <p>The <b>Patient Identity Source</b> actor must demonstrate 3 capabilities.  In previous years, you may have passed this test with just the 1st item.  A customer reading an integration statement claiming support for this actor would expect to see more than one message within ITI-8 supported, so we will ask you to test:</p> <ol> <li>admit/register a patient with A01, A04, or A05</li> <li>update a patient with A08</li> <li>patient identity merge with A40</li> </ol> <p>Also, each Patient Identity Source needs to have an Assigning Authority assigned to that system for    identifying that source. That Assigning Authority will consist of a text label and an OID. This value is provided to you    by the Project Manager.  Do not    proceed with this test without that value.</p>  <p>Note:</p> <ul>     <li> <strong>Different IHE profiles treat the HL7 assigning authority (PID 3.4) differently. The Assigning Authority has 3 subcomponents</strong> </li>     <ol>      <li>Namespace ID (text string)   </li>      <li>Universal ID (OID)   </li>      <li>Universal ID type (the string <strong>ISO</strong> when you use an OID) </li>     </ol>     <li> <strong>PIX requirements for Connectathon</strong> </li>     <ol>      <li>Patient Identifier Source [ITI-8]</li>      <ul>       <li>You can send either Namespace ID, or   </li>       <li>Universal ID + Universal ID type, or   </li>       <li>All three subcomponents </li>      </ul>      <li>PIX Manager for PIX Profile (inbound feed)</li>      <ul>       <li>You will receive ADT feeds as described above   </li>       <li>You need to map these to the full assigning authority (3 components) which will be used in subsequent transactions. </li>      </ul>     </ol> </ul> </p> <H3>Description</H3> <p>The purpose of the test is to feed the Patient Identity Cross Reference (PIX) Manager with LOCAL patient    information from the Patient Identity Source.  The PIX Manager will cross-reference the information with that already   received for patients in test <b>PIX_Seed_Mgr</b> </p> <p> <strong>Each source of patient identifiers is required to have its own Assigning Authority.</strong>     Please contact the Project Manager if you do not have your own value. Using a common value (ie the 'master' patient ID) will     defeat later tests.</p> <p>The Patient Identity Source will send its local patient identifier and Assigning Authority for three patients:</p> <ol>     <li>well-known patient FARNSWORTH^STEVE</li> <li> The 2nd patient is SINGLETON^MARION (this is a patient's maiden name)</li>  <li>The 3nd patient has a last name matching the Patient Identity Source's kudu system name, and a woman's first name of MARY, eg.     patient "Ehrxyzmedical^MARY".    Use this patient with last name matching your system name, and generate your own patient ID. (This is the patient's married name.)  Later, this patient's first name is updated MARION.</li> </ol> <H3>Evaluation</H3> <p>The <b>Patient Identity Source</b> actor must demonstrate all 3 of these capabilities.  If a capability is missing, the test does not pass:</p> <ol> <li>admit/register a patient with A01 or A04 or A05</li> <li>update a patient with A08</li> <li>patient identity merge with A40</li> </ol> <p>In order to verify the test the Connectathon monitor will ask the following :</p><ul>     <li>One of the two actors will have to show the HL7 messages transmitted between the 2 actors</li>  <li>On the PIX Manager, patient FARNSWORTH, STEVE exists with the value of the local Assigning Authority assigned to the      Patient Identity Source system in this test.  It is cross-referenced to FARNSWORTH^STEVE with the 'global' ID which previously existed (from the PIX_Seed_Mgr test).  This could be done by using a PIX Consumer to query for the Patient Identity Source's local ID, and retrieve the global ID for Farnsworth (101).</li> <li>The patient SINGLETON^MARION was initially registered with the PIX Manager.  Now she has been merged with the patient whose last name matches the kudu system name of the Patient Identity Source actor in this test, eg "Ehrxyzmedical".  </li> <li>An update (A08) was sent when the patient first name was updated from Mary to Marion. There was no change in Patient ID.</li> <li>Observe the Patient ID's that were recorded during the test.  Patient ID for Ehrxyzmedical^Marion survives.  Patient ID for SINGLETON^MARION has been subsumed. </li> <li>     </ul> 