<H3>Special Instructions</H3><p> <p>Each Secure Node and Secure Application runs <b>one instance</b> of this test.</p> <p>ATNA_Logging is a supplement to the ATNA_Inquisition test. Secure nodes need to run this test    as well as it will give you experience with more than one Audit Record Repository.</p> <p>The Reliable Syslog protocol has been placed on hold by the ITI Technical Committee; only the    BSD syslog protocol shall be used.</p> <p>ATNA allows the Secure Node to select from two different schemas. However, the Secure Node    should not mix schemas; it should implement one schema for the system. Audit Record Repository    actors are required to support both schemas.</p> </p><H3>Description</H3> <p>The purpose of the ATNA_Logging test is for your ATNA Secure Node or Secure Application to send    one or more audit messages to an Audit Record Repository. At the Connectathon, it is likely you    will be assigned to work with a specific Audit Record Repository. Please use your assigned    Repository. The type of audit message depends on the nature of the Secure Node/Application.</p><p>The top priority for testing would be an event that involves access to PHI that would result in    an audit message that includes a Patient ID. We have a well known patient to use, and want the    Secure Nodes to generate an event for that patient if possible.</p><p>If the Secure Node does not generate an audit message that includes a patient ID, we will    accept a different audit message.</p><p>Assuming a PHI event, the Secure Node should generate an audit record with the patient ID that    corresposponds to the well know patient FARNSWORTH^STEVE. This global ID is fixed by the    Connectathon test plan: 101^^^IHE and 1.3.6.1.4.1.21367.2009.1.2.300 and ISO^PI.</p><p>If your system generates an audit record using a local ID for FARNSWORTH, make sure you inform    the Connectathon monitor. The test steps list both audit message schemas; run the test with a    single schema. That means you will omit one test step.</p><H3>Evaluation</H3><p>For a PHI related log message, the Connectathon Monitor will ask the Audit Record Repository    for a list of PHI related events for the FARNSWORTH patient from the Secure Node that    participated in the test.</p><p>If the Secure Node does not generate an event with the FARNSWORTH patient ID, the Connectathon    Monitor will ask the Audit Record Repository to show the last one or two log messages from the    Secure Node.</p><p>     <strong>NB: For some systems that do not have the assigning authority (e.g., Imaging PACS), send     the audit message with that field empty.</strong> </p> 