Audit Trails

Every auditable event can be used to force a user into giving a reason for a change (e.g. when re-counting a plate), or to force the user to re-input their passwords to confirm their identity (e.g. when locking or unlocking experiment data). Audit data includes information on date/time, user, system, details of changes made (including original & new values) and details of any reasons given for those changes.

Audit trail information is generated and saved to the database in real-time during the process of designing, creating and running studies. Authorised personnel can view plate audit trails via a hierarchical tree view of studies & test substances. This view also allows auditors to quickly observe details associated with a selected study, test substance, folder, experiment or control.

The Main Event Log lists all user actions taken within the program at all stages of conducting a study. Each event has a unique event ID and a description (such as ‘New negative control added to experiment folder’) that explains the nature of the event. Every action is listed chronologically, giving information on time, date, user etc.
Many of the recorded events include more in-depth information, which can be displayed using the Show Detail button. The main event log can also be used to access plate audit trails on a user-by-user basis. A plate auditing report, included with the Ames Report Generator, creates a protected Microsoft Word document detailing all entries & changes made to experimental plate data for any single experiment.

<< Previous | Continue tour >>