 | LabWare LIMS includes a fully comprehensive Audit Trail facility. The Audit Trail mechanism of LabWare LIMS is in continuous operation, monitoring all activities and data transactions, and storing these activities with operator, date and time information, along with the previous value and the new value. Certain activities will require reasons (known as Prompt Auditing), and the reasons can be either selected from a pre-defined list or typed in from scratch. Even if an Activity does not normally incur a Prompt Audit, the user can volunteer an Audit Reason by selecting the Audit Reason option from any LabWare LIMS menu.
When any data is accessed (such as a sample), a history button is displayed. If the button is pressed, or the Audit History command is selected from the menu, then the full history of the data is displayed. This includes creation and modification activities, along with the User ID, the date / time and any Audit Reason that was entered.
A unique feature of LabWare LIMS is the ability to reconstruct data, such as a sample, purely from the Audit Trail information. In fact, this same feature allows data to be viewed "as it was" at any point in time, regardless of how many modifications have occurred since that time.
Audit Trail information is stored for all data within LabWare LIMS. This includes both dynamic data (such as Samples, Tests and Results) and Static Data (such as Analysis and Product Specification Definitions). All configuration elements are also fully audit trailed, such as modifications to Event Triggers. If any type of data uses LabWare LIMS' built-in version control, then each individual version is self-contained.
As the Audit Trail contains a large amount of detailed information, it is normally necessary to see a subset, such as modifications to result values or chain of custody data. The Audit Reporting element of LabWare LIMS allows any portion of the Audit Trail to be reported either to screen or to print-out, focusing on the type or nature of the changes.
|