Audit trails ensuring full traceability
To ensure data integrity it is a requirement by regulatory agencies to record the full history of changes that are made by users within the software. 3 SCIEX OS Software provides a system of audit trails to fully meet these requirements of electronic recordkeeping. Audit trails are files that store records of the audited events. The events that are audited are defined by the lab administrator within the audit maps on a workstation and/or project basis. The workstation-focused audit trail reports on actions around the MS control, like changes to the instrument configuration, tuning of the MS instrument or sample acquisition and also tracks potential changes of the security and audit trial settings. In comparison, any actions applied to the processing methods, such as modification of the method parameters, are linked to specific projects and are reported in the project audit trail. Workstation and project-based audit trails can be set up independently. In addition, the audit trail settings allow selecting which of the events that are audited require the operator to give reasons for the change and which ones must be confirmed by an electronic signature (Figure 4).
In order to simplify the setup, ready-to-use audit map templates are available to easily create customized audit trails tailored to the specific laboratory needs. As an example, a change in the processing parameters in the Analytics module in SCIEX OS Software caused the ‘Confirm Change Events’ window to pop up. As shown in Figure 4, the mass tolerance in the intact MAM workflow was changed from 5 to 2 Da (see reporting in the top panel). In this specific case, a reason for the change must be provided. The user can select from 10 pre-defined reasons, or free text can be typed in the respective field. Finally, the change has to be confirmed by entering the user’s password.
All changes, whether project or workstation based, can be found and visualized in the audit trail pane in the SCIEX OS Software (Figure 5). Here, audited events are listed by reporting date and time including a description of the event and the user that signed off on the change (Figure 5, top). If the change impacted the processing method, the software visualizes the data automatically (result table, peak integration and calibration curve) and allows a direct comparison of the results before and after the change (Figure 5, bottom). The example in Figure 5 refers to a quantification workflow carried out using surrogate peptides spiked in rat plasma 2 with full audit trail activated: the user modified the peak integration parameters for one of the analytes by changing its expected retention time from 3.40 to 3.1 min, which was listed in the project audit trail including the visualization of the difference introduced by the change (Figure 5).
The comprehensive audit trail function allows for retracing all steps which were taken from the raw data acquisition to the final results guaranteeing data integrity and alignment with regulatory requirements.
Audit trails can be visualized within SCIEX OS Software in an easily navigable interface that can be searched, filtered and sorted. In addition, audit trails can be exported and saved in the .csv file format. Time audit records accumulate in the project audit trail and can create large files that become difficult to manage. When an audit trail reaches a given number of records (20,000), it is automatically archived. A final archive record is added to the audit trail, and the audit trail is saved with a name indicating the type of audit trail, the date and time.