<H3>Special Instructions</H3> <p> One Connectathon monitor will use the RIS Mall to generate a single Patient ID for our subject. This Patient ID will be used by all systems to simplify reporting. <B>Do not generate your own ID for this patient; it will make tracking impossible. Use the Patient ID assigned by the Connectathon monitor. Find the ID by examining IHE-News for a message on this server.</B></p>  <p>This test uses the name and concept of a VIP (Very Important Person). That does not mean your system needs to take special measures to know this person is a VIP. Perhaps we are performing a routine audit 6 months after the fact on random patients. The purpose of the test is to track access to a specific patient and see how the Audit Record Repositories can assist an auditor in finding those events.</p>  <p>In most Connectathon tests, we allow client applications to drive the process. In this test, we ask Connectathon monitors to drive the process. They will assign specific clients (Secure Nodes) to Audit Record Repositories and ask the Secure Nodes to send the audit message to those repositories. As the audit records are sent, the Connectathon monitor will ask the Audit Record Repository to show evidence that the record was properly sent, formatted and stored.</p> <H3>Description</H3> <p>It is a beautifal Connectathon afternoon, and Harry Potter has just fallen off his broomstick while competing in the final Quidditch match of the school year. Foul play is suspected, but a blinding light was cast just at the instant Harry fell from the sky.</p>  <p>Harry has been taken to the infirmary under the watchful eye of Professor McGonagall. After a full battery of tests, Harry is referred to St. Mungo's Hospital for Magical Maladies and Injuries. There he will see a specialist to determine if he is the victim of a spell.</p>  <p>All of the information systems at the Hogwarts School allow access to all patient records and use auditing to detect undesirable behavior. Your Secure Node is one such information system. Determine some action that will trigger an audit record indicating someone on your system <b>(Secure Node)</b> is viewing a medical record for Harry Potter.</p>  <p>Create a character on your system, login with that character name and trigger the auditing event. This should send the event to an Audit Record Repository.</p>  <p>Professor Dumbledore suspects Hogwarts staff members are improperly trying to view Harry's records. He consults with the Audit Record Repository and asks to see log/access records from the Secure Node that indicate access to the Harry Potter account.</p>  <p>Specific steps <ul> <li>Secure nodes find the Connectathon monitor(s) in charge of security/audit records. Find which Audit Record Repository or repositories are designated to receive audit records.</li> <li>Audit Record Repositories should also determine which clients are required to send them messages.</li> <li>Secure Node generates one (or more) audit record that indicates access to the patient record for Harry Potter (patient ID assigned by the Connectathon monitor).</li> <li>After Secure Node checks with Audit Record Repository to see the audit record was received/stored, repeat the auditing step in the presence of the Connectathon monitor.</li> <li>Connectathon monitor will then consult with Audit Record Repository to examine the audit record.</li> </ul> <H3>Evaluation</H3> <p>In the real world, a security officer would ask the Audit Record Repository to generate a report or produce evidence that can be used to determine who has had access to the Harry Potter record in the last N days.</p> <p>In the Connectathon, the Connectathon monitor should examine the Audit Record Repository for evidence of the Audit Record as soon after the access to PHI has occurred as possible. This will simplify the job of the monitor (concentrate on individual systems) and will allow the client to know the reocrd has been reviewed.</p>