Reviewing Table Audits in the CCLAS 6 Database
Overview
Table audits are details of changes made to entities due to an audit rule existing for the entity.
Laboratories are configured with significant data that needs to be monitored to confirm correct business process is followed around the data modification. For example, if a scheme is changed, the testing regime in a job can be significantly different. Therefore, restrictions are placed upon changing such data, and when it is changed, those changes are audited. The CCLAS auditing capability allows organisations to determine which data is important for audit requirements by establishing audit rules.
As part of ISO17025 and Good Laboratory Practices (GPL), any changes to reference data (the static data, that is, the laboratory's analytical configuration, as compared to job/sample-centric dynamic data), must be protected and changes audited. This is important as many users may have access to this sensitive content and inadvertently make editing errors and want to revert back to the previous content.
A laboratory head or QC manager may want to keep track of which staff are changing what data.
Once an audit rule is created, the rule takes effect when you log out and back in again, upon which, when an update is made to any entity matching the audit rules, the update is audited.
Process
Where CCLAS 6 is configured for Writing Audits to the CCLAS 6 Database, then table audits can be reviewed from with the CCLAS 6 application.
Table audits can be searched and reviewed in the MSEADT—Audit Data application. Users with sufficient security access may update table audits.
An individual table audit can be opened to view the Auditing Details, Data Details and Column Details.
Note that, for any delete event, the audit event will contain the field values as they were prior to the delete event.
Related processes...