Locating Jobs for Analysis

• Locating Jobs for Analysis
  • Overview
  • Process
    • Resetting Laboratory Batch Jobs
      • Conditions for Calculating Expiry and Warning Dates after Resetting Laboratory Batch Jobs

Overview

Jobs are located for analysis using specific criteria. The list of jobs can then be passed through to a workbook search, to then open a workbook session. (Note that workbook sessions can also be searched by manually entering job names in the workbook search.)

Process

Jobs are located for analysis using the CCWKBK—Workbook Search application, with search criteria based on properties of the job, samples and tests.

Locate jobs for analysis

Jobs returned from a search can be exported to a report. Refer to Generating Grid Reports. Available report templates are defined in the SEARCH_REPORT_CCWKBK application preference.

A job can be opened to display the CCWKBK—Workbook Detail screen that shows the samples in the job.

Once jobs are returned from a search, the following row flows are available to access other workbook-related applications pertaining to the job.

• Open Batch Sample Maintenance—Displays the CCBTSM—Batch Sample Maintenance Detail screen for maintaining samples in a batch job. Refer to Maintaining Batch Samples.

• Modify QC Sample—Displays the CCQCSM—QC Sample Modification Detail screen for modifying QC samples for a scheme in the job. Refer to Maintaining Batch Samples.

• Open Sample Grid—Displays the CCSGRD—Sample Grid Detail screen for Applying Sample Gridding to the job.

• Open CCWKOP—Displays the CCWKOP—Search Open Workbook screen for Locating Workbooks.

• Open Worklist—Opens the Open Sample dialog box for Loading a Worklist.

• Open Workbook—Displays the CCWKOP—Workbook Open Detail screen in normal mode with samples across and scheme-analytes down the page.

  The workbook is populated with all sample types and racks from the selected job, and all schemes and analytes from the job. The grid is displays with final results data, and the opens read-write. Refer to:

Resetting Laboratory Batch Jobs

Selected laboratory batch jobs returned from a search can be delinked, such that, for each production sample scheme analyte where the Lab Batch Job Code matches a selected laboratory batch job, then the sample scheme analyte's Lab Batch Job Code and Lab Batch Sample Code are cleared, essentially removing the production sample scheme analyte from the laboratory batch job.

Reset laboratory batch jobs

Where a selected laboratory batch job is locked by another user, (refer to Maintaining Job Locks for more details), then the de-linking is rejected and an error message returned: Job currently locked by user [UserCode] at [LockedDateTime].

Otherwise, for each selected laboratory batch job that is not locked by another user, then the CCJobBatchMaintenance.Delink service is run, with the JobDTO passed in as a parameter.

Note that the laboratory batch job is not deleted, however after a delinking, the job only contains production sample scheme analytes that are still linked to the laboratory batch job.

Also note that for any QC sample within the laboratory batch job that has a QC Source of 3 (created when Batching Samples for Analysis and QC samples are created for the laboratory batch job), then these samples remain in the laboratory batch as they belong to it and not to any production job, however:

• For a replicate QC sample, the sample's Dup Original Sample Code is cleared since the original replicated sample is de-linked from the laboratory batch job.
• For a spike QC sample, the sample's Spike Original Sample Code is cleared since the original spiked sample is de-linked from the laboratory batch job.
• Each sample scheme associated with the sample has the sample scheme's Workflow Status set to Not Analysed, which, after a workflow status cascade, results in the sample's Workflow Status being set to Not Analysed, so that the laboratory batch job is not left in a state where it can never be completed.

Conditions for Calculating Expiry and Warning Dates after Resetting Laboratory Batch Jobs

For a sample scheme with a precursor scheme, Holding Time is counted from the Completed Date of the precursor sample scheme. Where a precursor sample scheme is included in a laboratory batch job, the sequel sample scheme's Completed Date in the laboratory batch job is used to determine the sequel sample scheme's Expiry Date in the production job. Therefore, when a sample is de-linked from a laboratory batch job, then the sequel sample scheme's Expiry Date in the production job is redetermined to counted from the sequel sample scheme's Completed Date in the production job.

An unknown or duplicate sample scheme's Expires On and Warning On dates or an unknown or duplicate sample scheme analyte's Expires On and Warning On dates are calculated using the the sample scheme's Holding Time and scheme version's Warning Time or the sample scheme analyte's Holding Time and scheme version's Warning Time, respectively, and:

• If a sample scheme has a Precursor Scheme Code, then the precursor sample scheme's Completed Date
• If a sample scheme does not have a Precursor Scheme Code, then the sample's Sampled Date and Received Date.

This process is performed by the holding time engine. Refer to Using Sample Expiry.

Note that Expires On and Warning On dates are NOT determined for replicate, blank, standard or spike sample schemes and sample scheme analytes, even where their sample schemes contain holding and/or warning times, respectively.