MESA/Audit Respository

MESA/Audit Respository

Audit Record Repository Tests

Introduction

We assume you are using an interactive terminal or terminal emulator and are logged on to the MESA test system. Change directory to $MESA_TARGET/mesa_tests/actors/audit_rep. Make sure the $MESA_TARGET and $MESA_STORAGE environment variables are set properly.

Integration Profiles and Test Procedures

The Audit Record Repository only participates in the Security Integration Profile. This document lists a number of tests for such repositories. Please refer to the IHE_YR4_Test_Requirements.xls' spreadsheet to determine the required and optional tests.

Message Attributes

This section is applicable for other actors and other tests.

Message Values

This section is applicable for other actors and other tests.

Configuration

The Audit Record Repository scripts described below use an ASCII configuration file to identify parameters such as host names and port numbers. The configuration file is named audit_test.cfg and is included in the directory $MESA_TARGET/mesa_tests/rad/actors/audit_rep. Edit the file and change entries (host name, port number) that pertain to your system. Your system is identified by entries that begin with TEST. Read the Runtime Notes section of the Installation Guide to determine the proper settings for the MESA runtime environment.

Starting the MESA Servers

These instructions assume you are using a terminal emulator on Unix systems or an MS DOS command window under Windows NT. Each test uses a command line interface; there is no graphical user interface. Before you start the test procedure, you need to start several MESA servers. Make sure the appropriate database is running (PostgreSQL, SQL Server). To start the MESA servers:

1. Enter the Audit Record Repository exam directory: mesa_tests/rad/actors/audit_rep

2. Execute the appropriate script to start the servers:

   scripts/start_mesa_servers.csh  [loglevel]   (Unix)

   scripts\start_mesa_servers.bat [loglevel] (Windows)

In the unix environment, loglevel is an optional argument (0 is default). Log levels are:

0. no logging

1. errors

2. warnings

3. verbose

4. conversational (really verbose)

When you are finished running one or more tests, you can stop the servers:

   scripts/stop_mesa_servers.csh (Unix)

   scripts\stop_mesa_servers.bat (Windows)

Log files are stored in $MESA_TARGET/logs.

Audit Record Repository Tests

Each section below lists one test for an Audit Record Repository.

Test Instructions: 12xx and 15xx Tests

Each test is independent of the others. You must collect the results of one test before starting a new test.

1. Enter the Secure Node exam directory: mesa_tests/rad/actors/audit_rep.

2. Remember the MESA servers were started according to the directions in Starting the MESA Servers.

3. Start the interactive script for the desired test. Each perl script is found in <test>/<test>_client.pl. For example, to run test 1201:

   perl  1201/1201_audit_rep.pl

4. Follow the directions of the test script. In most cases, you are merely waiting for messages from the MESA applications.

5. Answer the question or questions that are presented in this document. These questions are below and in the file audit_questions.txt. Modify this file and email the responses to the Project Manager.

If you want to run a different test, start at step 3.

Audit Record Repository Test 1201: Actor Start

This sequence sends an audit record to the Audit Record Repository under test. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The Actor Start message is chosen as that is required of all actors and is independent of other IHE transactions.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers. 2. If not already done, start your Audit Record Repository server. 3. Run the script that sends one message to your Audit Record Repository:

   perl 1201/1201_audit_rep.pl

What is the type of actor that was started and what is the name of the local user?

4. Observe the data sent to your system. Create a text file labeled SYSTEM_1201.txt with the answer to this question:

What is the type of actor that was started and what is the name of the local user?

5. Submit the text file to the Project Manager (not email)

Audit Record Repository Test 1202: System Configuration

This sequence sends an audit record to the Audit Record Repository under test. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The System Configuration message is chosen as that is required of all actors and is independent of other IHE transactions.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers.

2. If not already done, start your Audit Record Repository server.

3. Run the script that sends one message to your Audit Record Repository:

   perl 1202/1202_audit_rep.pl

4. Observe the data sent to your system. Create a text file called SYSTEM_1202.txt with the ansers to these questions.

What was the configuration change?

What is the name of the local user who made the change?

5. Submit the file to the Project Manager (not email).

Audit Record Repository Test 1203: User Authentication

This sequence sends an audit record to the Audit Record Repository under test. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The User Authentication message is chosen.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers.

2. If not already done, start your Audit Record Repository server.

3. Run the script that sends one message to your Audit Record Repository:

   perl 1203/1203_audit_rep.pl

4. Observe the data sent to your system. Create a text file called SYSTEM_1203.txt with the ansers to these questions.

What is the name of the authenticated user?

5. Submit the file to the Project Manager (not email).

Audit Record Repository Test 1211: Time Synchronization

Time synchronization requires an external system that serves as an NTP server. The MESA tools do not include such a server, but they are readily available. If time permits, the Project Manager will load the time server software and allow access for participants. As of this version of the document, that is not available.

Instructions

1. Read about NTP at the site [[1]]

2. Select/locate a public NTP server. Follow any rules of etiquette posted for that server.

3. Configure your system to synchronize time with that public NTP server.

4. At exactly 13:00 local time, August 1, send an email to the Project Manager (just kidding).

Supplemental Information

We do not require proof that you have performed this test.

Audit Record Repository Test 1502: Pre-reg/Order Cancel/Reorder

This test covers all of the Audit Record messages from a sequence of events involving a number of different actors. Your system will receive all of the messages; you will then be asked to answer questions about those messages.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers.

2. If not already done, start your Audit Record Repository server.

3. Run the script that sends one message to your Audit Record Repository:

   perl 1502/1502_audit_rep.pl

4. Observe the data sent to your system. Answer these questions and email response to the Project Manager:

5. Observe the data sent to your system. Create a text file called SYSTEM_1502.txt with the ansers to these questions.

Name all of the users who had access to the patient record of BROWN^JAMES

Who was the last user who had access to the patient record of BROWN^JAMES?

6. Submit the file to the Project Manager (not email).

ATNA Audit Record Repository Test 11121: Actor Start

This sequence sends an audit record to the Audit Record Repository under test. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The Actor Start message is chosen as that is required of all actors and is independent of other IHE transactions.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers.

2. If not already done, start your Audit Record Repository server.

3. Run the script that sends one message to your Audit Record Repository:

   perl 11121/11121_audit_rep.pl

4. Observe the data sent to your system. Create a text file called SYSTEM_11121.txt with the ansers to these questions.

What is the type of actor that was started and what is the name of the local user?

5. Submit the file to the Project Manager (not email).

ATNA Audit Record Repository Test 11122: System Configuration

This sequence sends an audit record to the Audit Record Repository under test. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The System Configuration message is chosen as that is required of all actors and is independent of other IHE transactions.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers.

2. If not already done, start your Audit Record Repository server.

3. Run the script that sends one message to your Audit Record Repository:

   perl 11122/11122_audit_rep.pl

4. Observe the data sent to your system. Create a text file called SYSTEM_11122.txt with the ansers to these questions.

What was the configuration change?

What is the name of the local user who made the change?

5. Submit the file to the Project Manager (not email).

ATNA Audit Record Repository Test 11123: User Authentication

This sequence sends an audit record to the Audit Record Repository under test. This test covers the basic functionality of transmitting the message and the proper XML format of the message. The User Authentication message is chosen.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers.

2. If not already done, start your Audit Record Repository server.

3. Run the script that sends one message to your Audit Record Repository:

   perl 11123/11123_audit_rep.pl

4. Observe the data sent to your system. Create a text file called SYSTEM_11123.txt with the ansers to these questions.

What is the name of the authenticated user?

5. Submit the file to the Project Manager (not email).

ATNA Audit Record Repository Test 11125: Patient Record

This test covers all of the Audit Record messages from a sequence of events involving a number of different actors. Your system will receive all of the messages; you will then be asked to answer questions about those messages.

Instructions

1. If not already done, start the MESA servers according to the directions in Starting the MESA Servers.

2. If not already done, start your Audit Record Repository server.

3. Run the script that sends one message to your Audit Record Repository:

   perl 11125/11125_audit_rep.pl

4. Observe the data sent to your system. Create a text file called SYSTEM_11125.txt with the ansers to these questions.

Name all of the users who had access to the patient record of Sick^Patient

5. Submit the file to the Project Manager (not email).