Auditing

Every auditable event can be used to force a user into giving a reason for a change (e.g. when editing a cell count), 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 old & new values) and details of the reasons given for those changes.

Audit trail information is automatically saved to the database in real-time during the process of designing, creating and running studies. Authorised personnel can view 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, experiment or treatment.

The Main Event Log lists all user actions taken within the program at all stages of conducting a study. Each action has a unique identifiable ID and a description (such as ‘Cell count data added to Treatment Day 2’) that explains the nature of the event. Every action is listed chronologically, giving information on time, date, user etc.

<< Previous | Continue tour >>