Configuring the Job Audit Application

Forms See also
AUDITJOB—AuditJobEdit Form

AUDITJOB—CriteriaJob Form

AUDITJOB—JobNumbers Form

AUDITJOB—UserEventRecords Form

Configuring Access to CCLAS Applications, Tables and Fields

Reviewing Operational Data Audits

Overview

The Job Audit application allows users to review operational data audits.

This process is pertinent to LIMS and laboratory managers who configure the LIMS, and the look and feel of applications to enhance laboratory processes and the user experience.

Process

Configuring the Extent of Job Auditing

The number of audits written for a job is large when you consider the job's lifetime. Various settings are used to limit this number:

  • The AuditAnalyteSelection GLOBAL setting controls whether changes for each scheme/analyte selected in the MDE application are audited separately or collectively for the scheme.
  • The AuditFormattedValueHistory GLOBAL setting controls whether changes made to the formatted value by the Jobs, On-line, Data Entry and Reports applications are audited.
  • The AuditFunctions GLOBAL setting controls which functions are audited in the Data Entry application.
  • The AuditInitialUpdates GLOBAL setting controls whether all changes to PJCSA fields by the Data Entry or On-line applications are audited, or only changes subsequent to the initial entry are audited.
  • The AuditPJCSAFields GLOBAL setting controls which fields are audited, by audit function.
  • The AuditInitialAnalyteStatus GLOBAL setting controls whether QC failures or check statuses set by the Data Entry or On-line applications are audited.
Configuring Access to the Job Audit Application

Ensure the AuditJob.exe file is located in the folder defined by the ExeDirectory GLOBAL setting. Give users, or users with specific roles, access to the application by setting the AccessLevel JOB AUDIT program setting. Once a user has sufficient access rights, they can run the Job Audit application either from the Job Audit node on the CCLAS menu or directly from the CCLAS Exe folder.

To display tips to users upon start up of the Job Audit application, enable the ShowTipOfTheDay JOB AUDIT program setting, and enter the tips, with one tip per line, in a text file, place the file in a folder under the CCLAS root folder defined by the CCLASRootDirectory GLOBAL setting, then set the TipofTheDayFile JOB AUDIT program setting to the folder and file name, for example %CCLASRootDirectory%TIPS\JOBAUDIT.TIP.

To present the list-view panel with grid lines, enable the MainListViewGrid JOB AUDIT program setting.

To maintain the window size and position between closing and launching the Job Audit application, set the Window JOB AUDIT program setting.

Configuring Job Audit Job Search

Job audit records are located either from a nominated view (refer to Configuring Database Views for Job Audit Job Search below), or directly from the database tables. Where they are located from database tables, the jobs are located either via client and project, or directly by job. The list of clients comes from the active list of clients in the PROFCLIENT table which are a subset of clients in the CLIENT table.

Access job audit data by database view, or database tables using the PROFJOB table directly, or using the CLIENT, CLIENT_PROJECT and PROFJOB tables in a drill-down:

Two methods exist to filter records returned to the list-view panel as each node is selected:

Define the columns of the grid based on the selected node type:

  • Clients node (only presented where job data is accessed by database tables using client-project-job drill-down)—Set the MainListViewColumnnJOB AUDIT program settings to specify which columns from the CLIENT table are presented in the grid.
  • Projects node (only presented where job data is accessed by database tables using client-project-job drill-down—Set the Sub1ListViewColumnnJOB AUDIT program settings to specify which columns from the CLIENT_PROJECT table are presented in the grid.
  • Jobs node—Set the Sub2ListViewColumnnJOB AUDIT program settings to specify which columns from the database view or PROFJOB table are presented in the grid.

Job audit record search often requires custom registration forms which are tailored to a laboratory's requirements. To add the name of a custom registration form to the Run main menu option in the Job Audit application, set the AuditJobScreennJOB AUDIT program setting to specify the custom forms.

Configuring Database Views for Job Audit Job Search

When searching for jobs for to review their audit trail, a database view allows for a logical presentation of data from multiple tables, with the benefits that the search then only operates on that one database view. Database views are created within the database itself.

Without using a database view, only properties from the PROFJOB table are displayed in the job list-view panel. Database views are used to construct a logical PROFJOB table. All queries on the PROFJOB or PROFJOBUSER tables are done on the view instead. Refer to Using Database Views.

Using a database view allows for the following to be displayed in the job browser:

  • Additional properties of the job (that is, those site-specific properties kept in the PROFJOBUSER table)
  • Additional properties of other objects associated with the job (for example, displaying the client name instead of the client code, displaying the contact name instead of the contact code, or contact and address details)
  • Aggregated statistics from any child table of the PROFJOB table, but grouped on the job number (for example, a dynamic count of the number of samples in a job, or a dynamic count of the samples not validated, or the number of tests in the job that belong to a particular laboratory section).

The application still maintains the links to other CCLAS EL tables, for example, CLIENT_CONTACT, PROFJOB_SCHEME.

Where the Job Audit application displays clients in a tree-view, then the PROFCLIENT_CLIENT and PROFCLIENT_PROJECT tables are joined to the defined view also.

Enable the ListViewByClient JOB AUDIT program settings to display clients in a tree-view in the Job Audit application.

Since the STAFFPROGRAMEDIT table defines the tables and views that are available from which to select the fields, these settings are not specific to the laboratory or staff code used. Therefore, if different views are used for different staff or laboratory codes, then the user must take extra care when selecting the fields for the browser column headings.

Set the browser of the specific CCLAS EL application to point to the view instead of to the PROFJOB table.

To configure the Job Audit application to point to a database view, set the BrowserView JOB AUDIT program settings to the name of the view. The view name from the Example Database View on the PROFJOB Table above is PROFILE_PJVIEW.

Set the columns on display in the browser to come from the view instead of from the PROFJOB table.

To configure the columns on display in the Job Audit application, set the Sub2ListViewColumnnJOB AUDIT program settings to the names of the columns in the view, for example:
Sub2ListViewColumn1=LABCODE,100,Lab
Sub2ListViewColumn2=PRO_JOB,100,Job
Sub2ListViewColumn3=CLI_LABCODE,100,Client Lab
Sub2ListViewColumn4=CLI_CODE,100,Client
Sub2ListViewColumn5=PROJ_CODE,100,Project
Sub2ListViewColumn6=ORDERNO,100,Order Number
Sub2ListViewColumn7=RECEIVED,120,Received,!YYMMDD HH:MM
Sub2ListViewColumn8=REQUIRED,120,Required
Sub2ListViewColumn9=PRODUCTCODE,100,Product
Sub2ListViewColumn10=JOBTYPE,50,Type
Sub2ListViewColumn11=CLI_NAME,150,Client Name
Sub2ListViewColumn12=NOUNKS,50,Number of Samples

The CCLAS EL application then looks for these fields in the view for display in the browser.

Configuring Job Audit Record Review

Once a job number is located, the job is opened to review and report the operational data audits for the job.

Set the Edit1ListViewColumnnJOB AUDIT program settings to specify which columns from the JOBAUDIT table are presented in the grid.

The InitialRecords Job Audit program setting controls the number of records initially returned to the list view.

Configuring Job Audit Reports

To add report templates to the Report main menu option in the Job Audit application, create the reports as Crystal Report templates, place them in the folder defined by the TemplateDirectory GLOBAL setting, and set the ReportLDFn JOB AUDIT program settings to each report template,