Maintaining Job Tests

Overview

A scheme denotes one of the steps performed on a sample for analytical process to occur. A scheme denotes either a sample preparation, analytical preparation, analytical or miscellaneous process. Analytical preparation and analytical schemes can have analytes which specify a type of analytical result.

At the job level, the job scheme (JS) represents a composite of all related sample schemes in the job, and the job scheme analyte (JSA) represents a composite of all related sample scheme analytes in the job.

Job Scheme and Job Scheme Analyte Scope

Schemes exist either at the organisation level or at the laboratory level, that is, schemes with org-scope or lab-scope. Those at the organisational level can be enabled for use by a laboratory, upon which, an enabled-scope scheme is created (and possibly updated) by the laboratory.

Schemes and their associated version and analytes are maintained using the CCSCHM—Scheme application. Refer to Maintaining Schemes.

Only org-scope schemes can be registered on samples contained within an org-scope template job.

Only lab-scope or enabled-scope schemes can be registered on samples contained within a lab-scope job, template or otherwise.

Job schemes are scoped by the related job, scheme and scheme version.

Job scheme analytes are scoped by the related job scheme.

Process

System-synchronised Job Schemes

At the job level, the job scheme (JS) and job scheme analyte (JSA) are records created and deleted by the system to keep in sync with sample schemes and sample scheme analytes being created or deleted. That is:

  • Job schemes only exist where the scheme is registered on one or more samples of the job.

  • Job scheme analytes only exist where the analyte is registered on one or more samples of the job.

Apart from containing composite details of the sample schemes and sample scheme analytes related to them, a job scheme and job scheme analyte has additional properties, some of which default from the scheme or scheme version, and scheme version analyte, respectively.

When a job scheme is created by the system, various properties are inherited from the scheme or scheme version. When a job scheme analyte or job scheme analyte is created by the system, various properties are inherited from the scheme version analyte.

  • Where an org-scope scheme or analyte is added, these properties are taken from the enabled-scope scheme, scheme version or scheme version analyte.

  • Where a lab-scope scheme or analyte is added, these properties are taken from the lab-scope scheme, scheme version or scheme version analyte.

Upon Maintaining Job Tests

Upon maintaining tests on jobs, the event is audited. Refer to Reviewing Operational Data Audits.

Maintain job tests

Job Scheme and Job Scheme Analyte Sequence within the Job

The initial order of schemes and analytes in a job scheme comes from the master scheme, as displayed in the lower grid of the Tests tab in the CCSAMP—Sample application.

You can sequence analytes within a scheme version and also re-sequence job schemes within a job. The scheme and scheme-analyte sequences at the job level influence the scheme and analyte order when the job is opened in the CCWKBK—Workbook application.

Scheme—Reporting Details

For a certificate report, a report request scheme's Reportable defaults to the job scheme's Reportable.

A job scheme's Report Name and Report Description are used to enhance the identity of the scheme in a report.

A report request scheme's Report Name and Report Description defaults as follows.

  • If the job scheme's Report Name is not empty, then it is used.

  • Otherwise, if the scheme's Report Name is not empty, then it is used.

  • Otherwise, if job scheme's Report Description is not empty, then it is used.

  • Otherwise if the scheme's Report Description is not empty, then it is used. The enabled-scope scheme is used if an org-scope scheme is registered in the job.

A report request scheme's Report Name and Report Description defaults as follows.

  • If the job scheme's Report Name is not empty, then it is used.

  • Otherwise, if the scheme version's Report Name is not empty, then it is used.

  • Otherwise, if job scheme's Report Description is not empty, then it is used.

  • Otherwise if the scheme version's Report Description is not empty, then it is used. The enabled-scope scheme version is used if an org-scope scheme is registered in the job.

The Report Sequence has no core functional use, but may be used by report templates or scripts to resequence the schemes within a job on a report. A job scheme's Report Sequence defaults to the scheme's Report Sequence.

Report Header Text, Report Footer Text and Result Header Text can be added to a job scheme for informational or reporting purposes.

A job scheme's Report Header Text, Report Footer Text and Result Header Text default from the template job scheme when a template job is used to register a job scheme, and from the scheme version when it is registered using a master scheme, but note that they are linked to new text entities containing the defaulted text.

Canned comments are available to quickly entered pre-canned text. When canned comments are accessed for a given note field, the canned comments are filtered by Canned Comment Type and Canned Comment Subtype.

  • The Canned Comment Type of GLOBAL, JOB, SAMPLE or SCHEME, and the Canned Comment Subtype of GLOBAL, REGISTRATION, RECEIPT, ANALYSIS, RELEASE, VALIDATION, REPORT or INVOICE.

or:

Scheme—Considering a Job Scheme in Context of QC Placements

When Creating QC Samples using QC Masks for a job scheme, the QC masks on related sample schemes are only processed where the job scheme's Included in Job QC is selected.

A job scheme's Include In Job QC defaults to the interim sample scheme's Include In Job QC when a sample group is expanded and causes the job scheme to be created. The interim sample scheme's Include in Job QC defaults to the inverse of the scheme's Batch Across Jobs.

Depending on the test, the samples analysed for some schemes are always included in a laboratory batch to achieve efficiencies in the analytical process, whilst other tests are always analysed in context of the registered job. This can change from job to job, however the scheme's Batch Across Jobs can be set to dictate the default setting for whether a job scheme is Included in Job QC.

Scheme—Configuring Automatic Validation

A job scheme's Auto-validate indicates whether results for related sample schemes are validated automatically when the result achieves a Workflow Status of Released.

Scheme—Subcontracting Details

A job scheme's Laboratory Code indicates the subcontracting laboratory that can be used analyse related sample scheme analytes.

Samples for subcontracting can be located by laboratory.

Scheme—Invoicing Details

Where the scheme's Price Type is Sample-Based, Scheme-Based or Unit-Based, a job scheme analyte's Price Code is used to determine the base and block price for the job scheme from the price book or quote used for invoicing, or the price book used for job costing.

A job scheme's Price Code can be updated to link to another price code that has a Price Type of Sample-Based, Scheme-Based or Unit-Based, according to the price type.

A job invoice scheme's Price Code defaults to the job scheme's Price Code.

The pricing derived from the price book can be overridden by the job scheme's Fixed Base Price and/or Fixed Block Price.

Note: The job scheme's Price Code still has to be selected for the job scheme to be invoiced, however, in this case, the job scheme's Price Code is referenced in the invoice, but the base price and block price are superceded by the entered values, as follows:

  • If the job scheme's Fixed Base Price is entered, then this supercedes the base price determined from the price book price schedule.
  • If the job scheme's Fixed Block Price is entered, then this supercedes the block price determined from the price book schedule, and the fixed price is applied as the price (that is, the entire invoiced entity is treated as a block size of one).

A job invoice scheme's Price Code and Number of Units default to the job scheme's Price Code and Number of Units, respectively.

Scheme—Linked Schemes

Some tests always share common racks of samples for analysis, whilst other tests always use their own racks for analysis. This can change from job to job, however, the linked scheme relationships on the master scheme dictate the default link scheme relationships between job schemes (if both a from and to scheme is registered on the job). Linked schemes only apply to analytical preparation and analytical schemes.

Where job schemes use the same rack for analysis, when Creating QC Samples using QC Masks to create QC samples for the job scheme and fill racks with the unknown and QC samples to analyse for that job scheme, if a job scheme is a linked-from job scheme and has its QC masks applied to create QC samples and apply the rack layout, then the same QC samples and rack layout is used for the linked-to job schemes.

When Appending or Overwriting QC Samples for a Job, linked job schemes are processed such that the QC masks used are from the first linked-from job scheme to determine the QC samples and rack layout, which is then applied to the linked-to job schemes.

QC sample additions or deletions are synchronised when Maintaining Batch Samples.

When Opening a Workbook Session, only the first linked-from job scheme is allowed to be opened after a search for workbooks with weight/volume mode.

Job scheme links default to the linked scheme relationships contained within the master scheme, when both schemes are registered on the job.

When an org-scope scheme is registered on a lab-scope job, the master scheme from where linked scheme relationships are determined is the enabled-scope scheme.

The first linked-from job scheme is determined by the 'from' and 'to' linked scheme relationships between the job schemes, such that, the 'from' job scheme is deemed the first linked-from job scheme, regardless of where it is registered in the job. Where more than one scheme link relationship is in play, that is, multiple 'from' linked job schemes exist in the job, then the first (by job scheme registration sequence) is used as the first linked-from job scheme.

Examples:

  • Where a job has schemes A, B and C registered in that sequence, and linked job schemes A-->C and B-->C exist, then A is the primary 'from' linked job scheme as it is registered before B.

  • Where a job has schemes C, B and A registered in that sequence, and linked job schemes A-->C and B-->C exist, then B is the primary 'from' linked job scheme as it is registered before A.

Scheme—Job Scheme Notes

Analysis and report notes can be added to a job scheme for informational or reporting purposes.

Canned comments are available to quickly entered pre-canned text. When canned comments are accessed for a given note field, the canned comments are filtered by Canned Comment Type and Canned Comment Subtype.

  • The Canned Comment Type of GLOBAL, JOB, SAMPLE or SCHEME, and the Canned Comment Subtype of GLOBAL, REGISTRATION, RECEIPT, ANALYSIS, RELEASE, VALIDATION, REPORT or INVOICE.

or:

Analyte—Reporting Details

For a certificate report, a report request scheme analyte's Reportable defaults to the job scheme analyte's Reportable.

A job scheme analyte's Report Name and Report Description are used to enhance the identity of the analyte in a report.

A report request scheme analyte's Report Name and Report Description defaults as follows.

  • If the job scheme analyte's Report Name is not empty, then it is used.

  • Otherwise, if the scheme version analyte's Report Name is not empty, then it is used.

  • Otherwise, if job scheme analyte's Report Description is not empty, then it is used.

  • Otherwise if the scheme version analyte's Report Description is not empty, then it is used. The enabled-scope scheme version analyte is used if an org-scope scheme is registered in the job.

The Report Sequence has no core functional use, but may be used by report templates or scripts to resequence the analytes within a job scheme on a report. A job scheme analyte's Report Sequence defaults to the scheme version analyte's Report Sequence.

Analyte—Invoicing Details

Where the scheme's Price Type is Analyte-Based, a job scheme analyte's Price Code is used to determine the base and block price for the job scheme analyte from the price book or quote used for invoicing, or the price book used for job costing.

A job scheme analyte's Price Code can be updated to link to another price code that has a Price Type of Analyte-Based.

A job invoice scheme analyte's Price Code defaults to the job scheme analyte's Price Code.

The pricing derived from the price book can be overridden by the job scheme analyte's Fixed Base Price and/or Fixed Block Price.

Note: The job scheme analyte's Price Code still has to be selected for the job scheme analyte to be invoiced, however, in this case, the job scheme analyte's Price Code is referenced in the invoice, but the base price and block price are superceded by the entered values, as follows:

  • If the job scheme analyte's Fixed Base Price is entered, then this supercedes the base price determined from the price book price schedule.
  • If the job scheme analyte's Fixed Block Price is entered, then this supercedes the block price determined from the price book schedule, and the fixed price is applied as the price (that is, the entire invoiced entity is treated as a block size of one).

A job invoice scheme analyte's Price Code defaults to the job scheme analyte's Price Code.

Opening the Sample Grid for a Job Scheme

A sample grid shows the intersections between samples and tests for a job scheme and indicates where sample schemes and sample scheme analytes are registered for samples, and where a sample scheme or sample scheme analyte is marked as listed not received, insufficient sample, not analysed or no result, or is active for analysis using the CCSGRD—Sample Grid application.

Job Test Grid Flows

Set Scheme Workflow Status

Updates the workflow status of the selected job schemes that have no associated job scheme analytes. This function allows users to manually set the workflow status of miscellaneous or preparation schemes to Not Started, Started, or Completed. This change in status is still under the rules of validation rights. See Set Scheme Workflow Status for a Job for more information.

Remove Scheme

The Remove Scheme grid flow action on the Job Update form allows authorised users to remove selected schemes from all samples in the job. When a scheme is removed, the system removes the scheme from all samples in the job, deletes the associated scheme-analyte records, and records the action in the audit trail to ensure consistent and traceable updates.

There are conditions where removing the scheme is not allowed. These are the ff:

  • The job is Cancelled or Finalised.
  • The job is locked by another user.
  • The scheme is referenced by a Report Request.
  • The scheme exists in a Job Invoice where the invoice status is not Initial or Draft.
  • Samples for the scheme are included in a Lab Batch.

If any of these conditions exist, the system prevents the action and displays an appropriate error message. See Remove Scheme from Job Tests for the steps to remove schemes from the job.

Update QC Sample Analytes

Adds missing analytes to QC samples when analytes exist on one sample scheme but are missing from related or subsequent sample schemes. See Maintaining Batch Samples for more information.