CCSAMP—Sample Detail

Processes associated with this form

Form content...

Screen flows

Submit—Validate and save the changes.
Refresh—Reload the original data. Any changes made since the last submit are lost.
New—Create a new sample.
Delete—Confirm and delete the current sample.
New Search—Return to the Search screen and clear the search results and the search criteria.
Change Sample Owner—Change the owner of the sample.
Add Tests from Sample—Add tests from a selected sample to the current sample. Refresh tests in the Tests grid by selecting the Refresh Added Tests grid flow option.
Approve—Approve the entity for export so that it can be used globally by all laboratories. This updates the entity's Approve Date and user who has approved the entity. This action only applies to org-scope entities and is only valid for entities in the user’s current organisation.
Unapprove—Reverse the approval of the entity that was previously approved for export. This clears the entity's Approved Date and user who previously approved the entity. This action only applies to org-scope entities, and is only valid for entities in the user’s current organisation.

Header

Start from New Rack

Only relevant if the screen is opened to create a new sample group for a registered job. Indicates whether to start a new rack when placing the samples for this new sample group, or whether to fill up the last rack if it still has slots available and the job is not started.
Organisation Code

The code of the associated organisation. Display only.
Is Template

Indicates whether the sample belongs to a template job, so is considered a template sample. Display only.
Schedule

Only relevant if the screen is opened to create a new sample group or update an existing sample within a schedule job. Indicates whether the sample belongs to a schedule job, so is considered a stream sample that can be scheduled for registration. Display only.
Client Sample Name

This field is only relevant if the screen is opened to review or update a sample. Contains the expanded form of the samples' client sample name.
Client Sample Name/Syntax

This field is only relevant if the screen is opened to create a sample group within a registered job, or update a template sample within a template job. Contains the unexpanded form of the samples' client sample name.

If a template sample in a template job is specified, then the list of client sample names or the syntax is kept unexpanded upon submit and is expanded later on when the template sample is used to make a create a non-template job from it.
Production Client Sample Name Syntax Code

Only relevant if the screen is opened to create a new sample group or update an existing sample within a schedule job. The code of the syntax used to create client sample names for draft or production samples that are generated from a stream sample in a schedule job. A syntax may be selected from the drop-down list that contains active syntaxes in scope with a Syntax Type of Sample, as configured in the CCSNTX—Syntax application. Click the field hyperlink to display the CCSNTX—Search Syntax screen, select the appropriate value and click Select and Return to populate the field with the selected value.
Sample Code

The system-generated, organisation-wide, unique identification code of the sample. This field is mandatory

For sample creation:
- A Sample Code is generated by the syntax that is in scope and has a Syntax Type of Other and a Syntax Code of SAMPLE_CODE_SYNTAX.
- Where the syntax is not found, then an error is raised.
- Where the syntax is found by the syntax cannot generate a code, then an error is raised.
- Where the entered or generated Sample Code is not unique within the organisation, then an error is raised.
- Where the entered or generated Sample Code does not satisfy code validation, that is, if the code contains non-printable characters, then an error is raised.
This field is hidden on the CCSAMP—Sample Detail screen by default.
Sample Name

Only relevant if the screen is opened to update an existing sample within a registered, template or draft job. The name of the sample. Display only if the sample is not a template sample; updatable for a template sample.
Production Sample Description Syntax Code

Only relevant if the screen is opened to create a new sample group or update an existing sample within a schedule job. The code of the syntax used to create sample descriptions for draft or production samples that are generated from the stream sample in a schedule job. A syntax may be selected from the drop-down list that contains active syntaxes in scope with a Syntax Type of Sample, as configured in the CCSNTX—Syntax application. Click the field hyperlink to display the CCSNTX—Search Syntax screen, select the appropriate value and click Select and Return to populate the field with the selected value.
Description

If the screen is opened to create a new sample group within a schedule job or update an existing sample within a production, internal, proposal, draft or schedule job, this is the sample description.

If the screen is opened to create a new sample group within a production, internal, proposal or draft job or update an existing sample within a template job, this contains either the list of descriptions or the code of the syntax used to create descriptions for samples that are generated from the expanded sample group or template sample. Note that the description is kept in its unexpanded form when creating or updating a template sample.

Primary Details Tab

The primary details of the sample.

Archive Status

The archive status of the sample indicating the location in which the sample is stored. Display only. This can be:
- Online—The sample is located in the Live Production Environment.
- Archived—The sample is located in the Archive Repository.
- Offline—The sample is located in the Off-line Storage.
Primary Analytical Type

Denotes the type of QC assessment the sample primarily undergoes.
Primary QC Type Code

A sub-classification of the Primary Analytical Type.
Secondary Analytical Type

The secondary analytical type of the sample that denotes the type of QC assessment the sample undergoes after the primary assessment.
Secondary QC Type Code

A sub-classification of the Secondary Analytical Type.
No. of Duplicates

Only relevant for stream samples within a schedule job, where the sample's Primary Analytical Type is Unknown. The number of duplicate QC samples to be created for the sample. Default is 0.
Dup QC Type Code

Only relevant for stream samples within a schedule job, where the sample's Primary Analytical Type is Unknown. The code of the primary QC type that is a sub-classification of the Duplicate primary analytical type, for duplicate QC samples that are created for the stream sample. A QC type may be selected from the drop-down list that contains active QC types in scope, as configured in the CCQCTP—QC Type application. Click the field hyperlink to display the CCQCTP—Search QC Type screen, select the appropriate value and click Select and Return to populate the field with the selected value.
Parent Client Sample Name

No functional use in core CCLAS. Indicates the parent sample.
Dup Original Client Sample Name

The client sample name of the duplicate original sample, the sample used to create the duplicate/replicate QC sample.
Dup Original Sample Code

The code of the duplicate original sample, the sample used to create the duplicate/replicate QC sample.
Dup Original Sample Name

The name of the duplicate original sample, the sample used to create the duplicate/replicate QC sample.
Standard Code

Only applicable where the Primary Analytical Type or Secondary Analytical Type is Blank, Standard or Spike. The code of the standard associated with the sample.
Standard Lot Code

Only applicable where the Primary Analytical Type or Secondary Analytical Type is Blank, Standard or Spike. The code of the current lot of the standard.
Client Code

Only applicable where the sample's Template is selected.

The code of the client associated with the template sample. A client may be selected from the drop-down list that contains active clients in scope, as configured in the CCCLNT—Client application. Click the field hyperlink to display the CCCLNT—Search Client screen, select the appropriate value and click Select and Return to populate the field with the selected value.
Client Group Code

Only applicable where the sample's Template is selected.

The code of the client group associated with the template sample. A client group may be selected from the drop-down list that contains active client groups in scope, as configured in the CCCLGP—Client Group application. Click the field hyperlink to display the CCCLGP—Search Client Group screen, select the appropriate value and click Select and Return to populate the field with the selected value.
Sample Type Code

The code of the associated sample type.
Sample Point Code

The code of the associated sample point.
Sampled On

The date-time at which the sample was taken.
Sampling Started On

The date-time at which the sampling started. This must be on or before the sampled On date-time.
Sampled By

The name of the person who took the sample. (Note that this person does not have to be a CCLAS user.)
Number of Containers

Number of containers required to hold the sample.
Delivered By

Name of the person who delivered the sample. (Note that this person does not have to be a CCLAS user.)
Registered On

The date-time at which the sample was registered, upon which in the sample's Workflow Status was set to Registered. Display only.
Registered By

The code of the user who registered the sample. Display only.
Auto-receive Sample

Only applicable for samples that belong to jobs that have a Job Type of Schedule or Template.

Indicates whether a production sample created from a template sample, or a draft or production sample created from a stream sample in a schedule job, has the sample's Received Date set or left empty.
Priority

The priority of the sample with respect to other samples in the system. Defaults the associated job's Priority. Entered in the format xN, where x is an integer and N is a code for a date-time period: S (second), N (minute), H (hour), D (day), M (month), Y (year). For example, 10D (10 days), 30N (30 minutes).

It is possible to sort samples prior to batching by the job's or sample's Priority. This process takes the different priority units into account, for example, 1W (week) is equivalent to 7D (days), 60S (seconds) is equivalent to 1N (minute), or 30D (days) is equivalent to 1M (month).
Possible On

Although this should be the possible date-time at which the sample's results can be reported, based on the longest duration of sample analysis, currently this is the same as Required On. An update to Possible On is persisted where the date-time provided is valid, and later than the Received On date-time where one is defined, otherwise an error message displays upon submit.
Received On

The date-time at which the sample was received by the laboratory.
- When a job is created by copying another job, for each sample created in the destination job, the sample's Received Date is set to the destination job's Received Date, such that, if the destination job's Received Date is empty, then the sample's Received Date is empty also.
- When a group sample is created, the sample's Received Date defaults to the job's Received Date. If the job's Received Date is empty, then the sample's Received Date is empty also. If the sample's Received Date is cleared or updated during sample entry, then it is not overridden with the job's Received Date. All samples expanded from the group sample are given the same Received Date.
- When a sample is created by copying another non-template sample, the destination sample's Received Date is set to the source sample's Received Date. If the source sample's Received Date is empty, then the destination sample's Received Date is empty also.
- When a sample is created from a template sample and the template sample's Is Auto Received is selected, then the sample's Received Date is set to the job's Received Date, such that, if the job's Received Date is empty, then the sample's Received Date is empty also. When a sample is created from a template and the template sample's Is Auto Received check box is cleared, then the sample's Received Date is left empty.
- When a sample is created as a composite sample, then the composite sample's Received Date is set to the first component sample's Received Date, such that, if the first component sample's Received Date is empty, then the composite sample's Received Date is empty also. The date-time at which the sample was received by the laboratory.
- When a sample's Received On date-time is updated, then Received By is set to the current user.
- When a sample's Received On date-time is cleared, then Received By is cleared also.
Received By

The code of the user who received the sample into the laboratory.
Required On

The date-time at which the sample's results must be reported.
Agreed On

The date-time at which it is agreed with the client that the report of the sample's analysis is available.
Include in Job QC

No functional use in core CCLAS.
Auto-validate Sample

No functional use in core CCLAS. Represents whether samples are auto validated, however, the AUTO_VALIDATE_SAMPLES and AUTO_VALIDATE_LAB_BATCH_SAMPLES application preferences control this.
Generate Label

Indicates whether the sample is included in label generation.
Generate Paperwork

Indicates whether the sample is included in the generated paperwork.
Reportable

Indicates whether the sample is included in certificate reports.
Number of Hours

No functionality in core CCLAS. Represents the number of hours used to complete the analysis.
Invoiceable

The default setting for a job invoice sample's Invoiceable check box when a job invoice is created, which indicates whether the sample is included in invoice line items by default.
Price Book Code

No functional use in core CCLAS.
Include in costs

Indicates whether the sample is included in job cost line items.
Discount

No functional use in core CCLAS.
Fixed Price

No functional use in core CCLAS.
Fixed Price

No functional use in core CCLAS.
Template Price Code

The code of the packaging associated with the template sample. A price code may be selected from the drop-down list that contains active price codes in scope with a Price Type of Sample-Based, as configured in the CCPRCCODE—Price Code application. Click the field hyperlink to display the CCPRCCODE—Search Price Code screen, select the appropriate value and click Select and Return to populate the field with the selected value.

Any sample scheme or sample scheme analyte registered using the template sample is linked to the template sample and the template price code so that they are priced using the package pricing instead of regular scheme and analyte pricing which uses the job scheme's price code and job scheme analyte's price code.
Is Active

Indicates whether the template sample is active for use. Default is checked.

Notes Tab

Notes associated with the sample.

Rich text formatting can be used to control the appearance of the information, with basic formatting ribbon and hyperlink entry field. For example, the name of a contact can be entered in bold, the telephone number in italics, and hyperlinks can be used. The formatting is saved along with the actual content. Canned comment functionality is accessed via the F2 function key and is used to insert chunks of text from the selected Canned Comment Code whose drop-down selection list is populated with canned comments filtered by Canned Comment Type, Canned Comment Subtype and Category Code. The following preferences are used to default the category codes available in the Category Code drop-down selection list, based upon the particular notes field being updated:

If any of these preferences are updated, they are applied on application launch or refresh.

If the respective preference is not defined, then the drop-down list of available canned comment codes comprises ALL active canned comments with a Canned Comment Type of GLOBAL, JOB, SAMPLE or SCHEME, and a Canned Comment Subtype of GLOBAL, REGISTRATION, RECEIPT, ANALYSIS, RELEASE, VALIDATION, AUTHORISATION, REPORT or INVOICE.

As soon as a canned comment code is entered or selected from the drop-down list, the canned comment long form content is embedded into the note field. Note that Cancel can be clicked at any time to exit canned comment selection.

Registration Notes

Notes regarding the registration of the sample. Registration notes are populated automatically with the sample client's and sample project's job notes, but only when the sample's registration notes are initially empty. The drop-down list of available canned comment codes is filtered based by active canned comments with a Canned Comment Type of SAMPLE, a Canned Comment Subtype of REGISTRATION, and the Category Code defaults to the value of the NOTES_SAMPLE_REGISTRATION_CATEGORIES application preference.
Analysis Notes

Notes regarding the analytical requirements of the samples. The drop-down list of available canned comment codes is filtered by active canned comments with a Canned Comment Type of SAMPLE and a Canned Comment Subtype of ANALYSIS, and the Category Code defaults to the value of the NOTES_SAMPLE_ANALYSIS_CATEGORIES application preference.
Report Notes

Notes regarding the reporting requirements of the sample. The drop-down list of available canned comment codes is filtered by active canned comments with a Canned Comment Type of SAMPLE and a Canned Comment Subtype of REPORT, and the Category Code defaults to the value of the NOTES_SAMPLE_REPORT_CATEGORIES application preference.

Biofields Tab

The biofields associated with the sample.

Grid flows
- Lookup CCBFLD—Open the CCBFLD—Search Biofield screen to perform a search.
Biofield Code

The code of the biofield associated with the sample. A biofield may be selected from the drop-down list that contains active sample biofields in scope, as configured in the CCBFLD—Biofield application. Click the field hyperlink to display the CCBFLD—Search Biofield screen, select the appropriate value and click Select and Return to populate the fieldwith the selected value.

Scope rules apply. If the scope of the entity is org-scope then the drop-down list for the linked entity contains org-scope entities only, and the entity can be linked to org-scope entities only. If the scope of the entity is lab-scope then the drop-down list for the linked entity contains both org-scope and lab-scope entities, and the entity can be linked to either org-scope or lab-scope entities.

Line of business rules apply. The drop-down list for the linked entity is filtered further to contain only those org-scope entities that have no associated line of business or a line of business that matches one of the laboratory's lines of business. The entity can be linked to an org-scope entity only where the org-scope entity has no associated line of business or a line of business that matches one of the laboratory's lines of business.
Name

The name of the biofield.
Description

the description of the biofield.
Biofield Value

the value of the biofield on the sample.
Reportable

Indicates whether the biofield is reportable, that is, whether it is included in reporting data result sets.

Tests Tab

The schemes and analytes assigned to the sample (or sample group) for testing. Analyte-level details for the sample are displayed in ascending order of the sample scheme analyte's Registration Sequence.

Some sample scheme and sample scheme analyte fields are visible on the grid, some of which may be directly updated there; other properties are only visible or updatable by opening the sample scheme or sample scheme analyte. Schemes or analytes can be added or deleted from samples on this tab, by accessing master schemes, template samples or production samples.

Sample scheme analytes cannot be re-sequenced within a sample scheme; all sequencing is managed at job level.

If a sample is part of a laboratory batch job, then the sample scheme and sample scheme analyte details are disabled in the CCSAMP—Sample Detail screens.

Sample Schemes and Analytes Grid
- Grid flows
  - Remove Analyte—Remove selected analytes from the sample.
  - Remove Scheme—Remove selected schemes from the sample.
  - Change Reporting Details—For selected analytes, the ability to update reporting unit, factor report detection limits, apply a new rounding table, and update reportability.
  - Remove Scheme with Related QC — Remove selected schemes from the sample and its related QC samples. If the scheme removed is the last scheme in the QC, then user has the option to also remove the QC sample.
    
    Note: Remove Scheme with Related QC has an extended capability where it can perform the service even when the sample is has been batched. Remove Scheme and Remove Analyte cannot perform the service if it has been batched. Remove Scheme with Related QC can perform all the same functions of Remove Scheme, but with the added capability of being able to perform the service even if the sample has been batched. System Administrators can opt to hide Remove Scheme if preferred.
- Scheme row—Include in Auto Reg
  
  Only relevant where the screen is opened for a stream sample within a schedule job.
  
  Indicates whether the stream sample scheme is included in automatic registration when the schedule job is used to create a sample scheme within a production job.
- Scheme row—Include in Manual Reg
  
  Only relevant where the screen is opened for a stream sample within a schedule job.
  
  Indicates whether the stream sample scheme is included in manual registration when the schedule job is used to create a sample scheme within a production job.
- Scheme row—Scheme Name
  
  The name of the scheme on the sample. Display only.
- Scheme row—Template Sample Code
  
  The code of the template sample used to register the sample scheme. By default, this individual grid column is hidden on the grid. Display only.
  
  Where a sample scheme is registered using a template sample, if the template sample is associated with a Package Price Code, then the sample scheme inherits the package price code. This ensures that the sample scheme is priced under the package pricing and not under the price code on the related job scheme.
- Scheme row—Scheme Code
  
  The code of the scheme on the sample. Display only. Expand the sample scheme to display its sample scheme analytes.
- Scheme row—Version Number
  
  The version number of the scheme on the sample. Display only.
- Scheme row—Subcontract Laboratory Code
  
  The code of the laboratory subcontracted to prepare/analyse the sample scheme. A subcontract laboratory may be selected from the drop-down list that contains active laboratories that are members of the laboratory group defined by the SUBCONTRACT_LABS application preference, excluding the current laboratory. Click the field hyperlink to display the CCLBRT—Search Laboratory screen, select the appropriate value and click Select and Return to populate the field with the selected value. Note, however, that the selected value is validated against the laboratories contained in the drop-down list on submit. Defaults to the scheme version's Default Sub Contract Lab Code, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Scheme row—Subcontract Laboratory's Org Code
  
  The code of the organisation associated with the subcontract laboratory.
  
  Not displayed on the grid by default but can be added via showing individual grid items.
- Scheme row—Priority
  
  The priority of the scheme with respect to other schemes registered on the sample. Defaults to the scheme's Priority, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample. Entered in the format xN, where x is an integer and N is a code for a date-time period: S (second), N (minute), H (hour), D (day), M (month), Y (year). For example, 10D (10 days), 30N (30 minutes).
  
  If a sample scheme's Priority is updated, then the sample scheme's Required On date-time immediately recalculates automatically based on the sample's Received On plus the sample scheme's Priority plus any non-working days due to holidays. If the sample's Received On date-time and/or the sample scheme's Priority is cleared, then the sample scheme's Required On is cleared automatically.
- Scheme row—Possible On
  
  Although this should be the possible date-time at which the sample's results can be reported, based on the longest duration of sample analysis, currently this is the same as Required On. Possible On can be updated if the date-time provided is valid and the date-time is later than the Received On (or Received On is not defined), otherwise an error message displays upon submit. If Required On is changed, Possible On changes to match it.
- Scheme row—Required On
  
  The date-time at which the sample scheme's results must be reported.
  
  If a sample scheme's Priority is updated, then the sample scheme's Required On date-time immediately recalculates automatically based on the sample's Received On plus the sample scheme's Priority plus any non-working days due to holidays. If the sample's Received On date-time and/or the sample scheme's Priority is cleared, then the sample scheme's Required On is cleared automatically.
- Scheme row—Scheme Duration
  
  No functionality in core CCLAS. Represents the duration of the scheme.
- Scheme row—Holding Time
  
  The holding time for the sample scheme. Defaults to the scheme version's Holding TIme, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
  
  Holding times are configured and used to avoid sample expiry. Holding time is the maximum time that a sample has to be prepared by, analysed and validated for a sample scheme before the sample deteriorates to such a point that the correctness of an analytical result would be questionable. The point of deterioration is known as the Expiry Date.
  
  For this reason, any sample scheme analyte that has exceeded the sample scheme's or sample scheme analyte's Holding Time cannot have results entered. A Warning Date can be calculated (back from the expiry date) so that this information can be displayed to the batching operator as a warning that the expiry date is approaching. In addition, a script or report could be configured to warn of expected deterioration.
  - For a sample scheme with no precursor scheme, Holding Time is counted from the earliest of the sample's Received On or Sampled On date.
  - For a sample scheme with a precursor scheme, Holding Time is counted from the Completed Date of the precursor scheme.
  When a duplicate sample is created, the sample scheme and sample scheme analyte's holding times, warning times, possible dates and expiry dates for duplicate samples default to those set on the original sample.
  
  Note: Holding time can be made tighter for individual sample scheme analytes.
- Scheme row—Internal Cost
  
  No functional use in core CCLAS. Represents the internal cost of the method for one sample undergoing the scheme.
- Scheme row—Include in Job QC
  
  Indicates whether the sample scheme is included in the job scheme's sample stream used by an Append/Update QC process to add QC samples to the job. This flag is toggled to false by the system after the sample scheme is consumed by this process.
- Scheme row—QC Mask Code
  
  The QC mask used when appending or overwriting QC samples for a job, such that, all sample schemes associated with a job scheme in the Append/Overwrite QC Sample process, are divided into groups based on this QC Mask Code, and the QC mask members are then enacted upon that group of samples for the job scheme to create QC samples for the job scheme. A QC mask may be selected from the drop-down list that contains active QC masks in scope, as configured in the CCQCMK—QC Mask application. Click the field hyperlink to display the CCQCMK—Search QC Mask screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the scheme version's QC Mask Code.
  
  Where a scheme's Scheme Type is Sample Preparation, then the selected QC mask cannot have any QC mask members that have an Analytical Type of REPLICATE since these types of QC samples only pertain to the analytical process.
  
  Where a scheme's Scheme Type is Analytical Preparation or Analytical, then the selected QC mask cannot have any QC mask members that have an Analytical Type of DUPLICATE since these types of QC samples only pertain to the sample preparation process.
  
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample
- Scheme row—No. of Replicates
  
  Only applicable for stream samples within a schedule job, where the sample's Primary Analytical Type is Unknown.
  
  The number of replicate QC samples to be created for the sample scheme. Default is 0.
- Scheme row—Replicate QC Type Code
  
  The code of the primary QC type that is a sub-classification of the Replicate primary analytical type, for replicate QC samples that are created for the stream sample scheme. A QC type may be selected from the drop-down list that contains active QC types in scope that have an Analytical Type of Replicate, as configured in the CCQCTP—QC Type application. Click the field hyperlink to display the CCQCTP—Search QC Type screen, select the appropriate value and click Select and Return to populate the field with the selected value.
- Scheme row—Labels
  
  Only applicable for stream samples within a schedule job. No functional use in core CCLAS 6. Represents automatic label creation for jobs created from a schedule job.
  
  The existing functionality is that when a production job is created using a schedule job, or from a draft job raised from a schedule job, where labels are automatically generated for the production job, then the labels report request sample scheme analyte's Reportable flag defaults to the scheme version analyte's Include on Worksheet. The report request sample scheme's Is Reportable flag defaults to true if at least one report request sample scheme analyte's Is Reportable flag is true. The report request scheme's Is Reportable defaults to checked if at least one report request sample scheme's Is Reportable flag is true. The report request scheme analyte's Is Reportable defaults to checked if at least one report request sample scheme analyte's Is Reportable flag is true.
- Scheme row—Paperworks
  
  Only applicable for stream samples within a schedule job. No functional use in core CCLAS 6. Represents automatic paperwork creation for jobs created from a schedule job.
  
  The existing functionality is that when a production job is created using a schedule job, or from a draft job raised from a schedule job, where paperwork are automatically generated for the production job, then the paperwork report request sample scheme analyte's Reportable flag defaults to the scheme version analyte's Include on Worksheet. The report request sample scheme's Is Reportable flag defaults to true if at least one report request sample scheme analyte's Is Reportable flag is true. The report request scheme's Is Reportable defaults to checked if at least one report request sample scheme's Is Reportable flag is true. The report request scheme analyte's Is Reportable defaults to checked if at least one report request sample scheme analyte's Is Reportable flag is true.
- Scheme row—Precursor Scheme Code
  
  A precursor scheme is a scheme that must be process in the laboratory before one or more sequel schemes are processes. This typically includes analytical preparation scheme work that occur before analytical scheme work. A precursor sample scheme may be selected from the drop-down list that contains other sample schemes associated with the sample, where a precursor relationship exists in the master scheme table. A sample's precursor scheme relationships default from the scheme's precursor scheme relationships, where the schemes are registered on the sample.
  - A precursor sample scheme's state controls which sample schemes are available for batching and which sequel sample schemes may be expired for analysis.
  - A precursor sample scheme's Ready Date can be used as a sample search criteria when searching for samples to batch.
  - A precursor sample scheme's Completed Date is used to determine a sequel sample scheme's Warning Date and Expiry Date and sequel sample scheme analyte's Warning Date and Expiry Date, which can be used to lock sequel sample scheme analyte's cell in a workbook session.
  - A precursor sample scheme defaults to the precursor scheme relationships contained within the master scheme, when both schemes are registered on the sample. When a scheme is registered on a sample, if an existing sample scheme is a precursor or sequel of the new sample scheme, then a precursor sample scheme relationship is established.
  - A master scheme can have a list of precursor schemes, and one or more of those precursor schemes can be configured to be registered automatically when the sequel scheme is registered on the sample, as long as the precursor scheme is either a lab-scope scheme or an org-scope scheme that is enabled for laboratory use.
  - Where more than one sample scheme is a precursor of a sequel sample scheme, when the sequel sample scheme is registered, the sample scheme's Precursor Scheme Code is set to the first precursor sample scheme, based on alphanumerical order, after which it can be updated to link to a different precursor sample scheme. A precursor scheme scenario could be that you do not want to include samples in the count for analysis until their preparation is at least started, or one sample scheme may have a varying preparation pathway, or different samples may have a different combination of precursor schemes and sequel schemes.
  - When an org-scope scheme is registered on a lab-scope job, the master scheme from where precursor scheme relationships are determined is the enabled-scope scheme.
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample
- Scheme row—Limit Specification Code
  
  The scheme specification used to assess results against, to then set the sample scheme analyte's Scheme Limit Status. A specification may be selected from the drop-down list that contains active specifications in scope with a Specification Type of Scheme, as configured in the CCSPFN—Specification application. Click the field hyperlink to display the CCSPFN—Search Specification screen, select the appropriate value and click Select and Return to populate the field with the selected value.
- Scheme row—Reportable
  
  The default setting for a report request sample scheme's reportability in a certificate report request. Defaults to the scheme's Reportable check box, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
  
  Note: This flag does not cascade down nor up to set a sample's reportability or a sample scheme analyte's reportability.
- Scheme row—Report Sequence
  No functional use in CCLAS. Represents the sequence of the sample scheme in a certificate report, with respect to other sample schemes, to override registered scheme sequence, from the enabled-scope scheme when an org-scheme scheme is registered on a lab-scope sample. For use by SQL scripts when using DSC reporting.
- Scheme row—Invoiceable
  
  The default setting for an invoice sample scheme analyte's invoiceability in an invoice. Defaults to the scheme's Invoiceable check box, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
  
  A job invoice sample's Invoiceable defaults to the sample 's Invoiceable check box, and the job invoice scheme analyte's Invoiceable defaults to the scheme version analyte's Invoiceable. Whilst these two flags determine the invoiceability of the sample scheme analyte in the job invoice, an invoice sample scheme analyte's Invoiceable setting allows individual sample scheme analytes in the invoice sample test grid to be excluded from the invoice, so the invoiced client is not charged for that component.
  
  Note: This flag does not cascade up to set a sample's invoiceability or a sample scheme's invoiceability.
  
  The default setting for an invoice sample scheme's invoiceability in an invoice. A job invoice sample's Invoiceable defaults to the sample 's Invoiceable check box, and the job invoice scheme's Invoiceable defaults to the scheme's Invoiceable. Whilst these two flags determine the invoiceability of the sample scheme in the job invoice, an invoice sample scheme's Invoiceable flag allows individual sample schemes in the invoice sample test grid to be excluded from the invoice, so the invoiced client is not charged for that component.
  
  Note: This flag does not cascade down nor up to set a sample's invoiceability or a sample scheme analyte's invoiceability.
- Scheme row—Number of Hours
  
  No functional use in core CCLAS. Represents the number of hours used to complete the sample scheme.
  
  Note: Where a scheme has a Price Type of Unit-Based, the job scheme's Number of Units is used to determine the price of the job scheme.
- Scheme row—Ready Date
  
  The date-time at which the sample scheme is ready for analysis to proceed, such that, any sequel sample scheme of this sample scheme is available for batching given that the precursor sample scheme's Ready Date is at or earlier than the current system date-time.
  
  Where a scheme version's Waiting Time is defined, when a sample scheme's Workflow Status becomes Started, then the sample scheme's Ready Date is set to the sample scheme's Started Date + the scheme version's Waiting Time.
  
  Note: This calculation does NOT take into consideration holidays or a section's non-working time periods. If a scheme version's Waiting Time is not defined, then the sample scheme's Ready Date is left empty.
- Scheme row—Rack No.
  
  The number of the rack containing the sample scheme. The rack size is determined from the container type's Default Number of Containers for the scheme's Container Type Code. An update or overwrite QC process on a job scheme sets this, as can a re-rack action on a job scheme in the CCQCSM—QC Sample Modification application.
- Scheme row—Package Price Code
  
  The code of the package pricing associated with the sample scheme. Display only.
  
  When a sample scheme is associated with a Template Sample Code because it is registered using a template sample, if the template sample is associated with a Package Price Code, then the sample scheme inherits the package price code. This ensures that the sample scheme is priced under the package pricing and not under the price code on the related job scheme.
  
  A package price on a sample scheme can only be removed by removing the entire package pricing from the sample so that it is removed from all associated sample schemes and sample scheme analytes.
- Scheme row—Composite QC Status
  
  The status of the sample scheme indicating the stage it is at in its life-cycle. Display only. This can be:
  - Not Started
  - Listed Not Received
  - Insufficient Sample
  - Not Analysed
  - No Result
  - Started
  - Analysed
  - Released
  - Completed.
  Not displayed on the grid by default but can be added via showing individual grid items.
- Scheme row—Composite Specification Status
  
  The composite specification status of the sample scheme indicating the status of the underlying analytical results against all sample specifications. Display only. This can be:
  - Not Tested
  - Not Required
  - Pass
  - Failure.
  Not displayed on the grid by default but can be added via showing individual grid items.
- Scheme row—Workflow Status
  
  The status of the sample scheme indicating the stage it is at in its life-cycle. Display only. This can be:
  - Not Started
  - Listed Not Received
  - Insufficient Sample
  - Not Analysed
  - No Result
  - Started
  - Analysed
  - Released
  - Completed.
  Not displayed on the grid by default but can be added via showing individual grid items.
- Scheme row—Default Workflow Status
  
  Only applicable when the sample belongs to a schedule or template job.
  
  The default workflow status of a sample scheme created from this template or schedule sample scheme:
  - Not Started
  - Insufficient Sample
  - Not Analysed
  - No Result.
  Not displayed on the grid by default but can be added via showing individual grid items.
- Analyte row—Include in Auto Reg
  
  Only relevant when the screen is opened for a stream sample within a schedule job.
  
  Indicates whether the stream sample scheme analyte is included in automatic registration when the schedule job is used to create a sample scheme analyte within a production job.
- Analyte row—Include in Manual Reg
  
  Only relevant when the screen is opened for a stream sample within a schedule job.
  
  Indicates whether the stream sample scheme analyte is included in manual registration when the schedule job is used to create a sample scheme analyte within a production job.
- Analyte row—Analyte Code
  
  The code of the analyte on the sample.
- Analyte row—Analyte Name
  
  The name of the analyte on the sample.
- Template Sample Code
  
  The code of the template sample used to register the sample scheme analyte. Display only.
- Analyte row—Required On
  
  The date-time at which the sample scheme analyte's results must be reported.
- Analyte row—Holding Time
  
  The holding time for the sample scheme analyte. Defaults to the scheme version analyte's Holding Time, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
  
  Holding times are configured and used to avoid sample expiry. Holding time is the maximum time that a sample has to be prepared by, analysed and validated for a sample scheme before the sample deteriorates to such a point that the correctness of an analytical result would be questionable. The point of deterioration is known as the Expiry Date.
  
  For this reason, any sample scheme analyte that has exceeded the sample scheme's or sample scheme analyte's Holding Time cannot have results entered. A Warning Date can be calculated (back from the expiry date) so that this information can be displayed to the batching operator as a warning that the expiry date is approaching. In addition, a script or report could be configured to warn of expected deterioration.
  - For a sample scheme with no precursor scheme, Holding Time is counted from the earliest of the sample's Received On or Sampled On date.
  - For a sample scheme with a precursor scheme, Holding Time is counted from the Completed Date of the precursor scheme.
  When a duplicate sample is created, the sample scheme and sample scheme analyte's holding times, warning times, possible dates and expiry dates for duplicate samples default to those set on the original sample.
  
  Note: Where a sample scheme analyte's Holding Time is not defined, if the sample scheme's Holding Time is defined, then that applies.
- Analyte row—Include on Worksheet
  
  The default setting for a report request sample scheme analyte's reportability in a paperwork or labels report request. Defaults to the scheme version analyte's Include on Worksheets check box, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Unit Code
  
  The code of the analysis unit associated with the sample scheme analyte. Defaults to the scheme version analyte's Unit Code, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Int Lower DL
  
  The lower detection limit of the analyte, that is, the lowest acceptable value in the detection range, and tied to the instrument's or human's ability to detect amounts. There would be no confidence in values that read below the internal lower detection limit. Defaults to the scheme version analyte's Internal Lower DL, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Int Upper DL
  
  The upper detection limit of the analyte, that is, the highest acceptable value in the detection range, and tied to the instrument's or human's ability to detect amounts. There would be no confidence in values that read above the internal upper detection limit as the amount is so great, a more reliable test is required to determine it. Defaults to the scheme version analyte's Internal Upper DL, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Int Lower DL Critical
  
  Indicates whether to set the Workflow Status of an unknown sample scheme analyte to Check after a detection limit assessment of the result sets the Internal Detection Limit Status to Lower Failure. Defaults to the scheme version analyte's Internal Lower DL Critical, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Int Upper DL Critical
  
  Indicates whether to set the Workflow Status of an unknown sample scheme analyte to Check after a detection limit assessment of the result sets the Internal Detection Limit Status to Upper Failure. Defaults to the scheme version analyte's Internal Upper DL Critical, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Lower Template Sample Code
  The template sample whose tests can be registered on the sample if the sample scheme analyte's Workflow Status is Check due to the result being below the Internal Upper DL and the Internal Lower DL Critical is selected. This field is updatable.
- Analyte row—Upper Template Sample Code
  
  The template sample whose tests can be registered on the sample if the sample scheme analyte's Workflow Status is Check due to the result being above the Internal Upper DL and the Internal Upper DL Critical is selected. This field is updatable.
- Analyte row—QC Active
  
  Indicates whether the sample scheme analyte undergoes QC assessment. Where the analyte does not undergo QC assessment, any QC statuses on related sample scheme analytes are set to Not Required.
- Analyte row—Workflow Active
  
  No functional use in core CCLAS. This flag is taken from the master scheme version analyte.
- Analyte row—Reportable
  
  The default reportable setting for a report request sample scheme analyte created from this sample scheme analyte, for a certificate report. A report request sample scheme analyte's Reportable flag indicates whether the report request sample scheme analyte's result is included in the reportable result set. Defaults to the scheme version analyte's Reportable flag, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
  
  Note: This flag does not cascade up to set a sample's reportability or a sample scheme's reportability.
- Analyte row—Report Sequence
  
  No functional use in CCLAS. Represents the sequence of the sample scheme analyte in a certificate report, with respect to other sample scheme analytes, to override registered scheme sequence, from the enabled-scope scheme when an org-scheme scheme is registered on a lab-scope sample. For use by SQL scripts when using DSC reporting.
- Analyte row—Report Unit Code
  
  The code of the default report unit assigned to a report request sample scheme analyte created from this sample scheme analyte. A report request sample scheme analyte's Report Unit Code is the unit the reportable result is presented in for the report. A unit may be selected from the drop-down list that contains active units in scope, as configured in the CCUNIT—Unit application. Click the field hyperlink to display the CCUNIT—Search Unit screen, select the appropriate value and click Select and Return to populate the field with the selected value.
  - SVA.reportUnitCode * --> SSA.reportUnitCode
    
    A sample scheme analyte's Report Unit Code defaults to the scheme version analyte's Report Unit Code and can be updated.
  - SVA.reportUnitCode * --> RRSA.reportUnitCode
    
    A report request scheme analyte's Report Unit Code defaults to the scheme version analyte's Report Unit Code and can be updated to subsequently push down to report request scheme version analytes, or as a header in a report.
  - SSA.reportUnitCode --> RRSSA.reportUnitCode
    
    A report request sample scheme analyte's Report Unit Code defaults to the sample scheme analyte's Report Unit Code, and is used to generate the report request sample scheme analyte's Formatted Final Value, defaults to the sample scheme analyte's Report Unit Code. It is only possible to see a report request sample scheme analyte's Report Unit Code when the sample is selected as the first sample in a multiple report request sample update.
  - RRSSA --> Used when rounding results for the report.
    
    When a report is generated for a report request, the sample scheme analyte's Numeric Final Value undergoes unit conversion if the report request sample scheme analyte's Report Unit Code is different to the sample scheme analyte's Unit Code, to determine the reportable numeric value, which is then rounded to produce the report request sample scheme analyte's Formatted Final Value.
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Report Lower DL
  
  The default lower detection limit for rounding and reporting a result for the sample scheme analyte.
  - SVA.reportLowerDL * --> SSA.reportLowerDL
    
    A sample scheme analyte's Report Lower DL defaults to the scheme version analyte's Report Lower DL and can be updated.
  - SVA.reportLowerDL * --> RRSA.reportLowerDL
    
    A report request scheme analyte's Report Lower DL defaults to the scheme version analyte's Report Lower DL and can be updated to subsequently push down to report request scheme version analytes, or as a header in a report.
  - SSA.reportLowerDL --> RRSSA.reportLowerDL
    
    A report request sample scheme analyte's Report Lower DL defaults to the sample scheme analyte's Report Lower DL, and is used to generate the report request sample scheme analyte's Formatted Final Value, defaults to the sample scheme analyte's Report Lower DL. It is only possible to see a report request sample scheme analyte's Report Lower DL when the sample is selected as the first sample in a multiple report request sample update.
  - RRSSA --> Used when rounding results for the report.
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Report Upper DL
  
  The default upper detection limit for rounding and reporting a result for the sample scheme analyte.
  - SVA.reportUpperDL * --> SSA.reportUpperDL
    
    A sample scheme analyte's Report Upper DL defaults to the scheme version analyte's Report Upper DL and can be updated.
  - SVA.reportUpperDL * --> RRSA.reportUpperDL
    
    A report request scheme analyte's Report Upper DL defaults to the scheme version analyte's Report Upper DL and can be updated to subsequently push down to report request scheme version analytes, or as a header in a report.
  - SSA.reportUpperDL --> RRSSA.reportUpperDL
    
    A report request sample scheme analyte's Report Upper DL defaults to the sample scheme analyte's Report Upper DL, and is used to generate the report request sample scheme analyte's Formatted Final Value, defaults to the sample scheme analyte's Report Upper DL. It is only possible to see a report request sample scheme analyte's Report Upper DL when the sample is selected as the first sample in a multiple report request sample update.
  - RRSSA --> Used when rounding results for the report.
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Rounding Table Code
  
  Only applicable when Rounding Method Type is Table or Script (for use in the script).
  
  The code of the default rounding table assigned to a report request sample scheme analyte created from this sample scheme analyte. A rounding table may be selected from the drop-down list that contains active rounding tables in scope, as configured in the CCRNDT—Rounding Table application, click the field hyperlink to display the CCRNDT—Search Rounding Table screen, select the appropriate value and click Select and Return to populate the field with the selected value.
  
  A report request sample scheme analyte's Rounding Table is used to round a result during the report process.
  - SVA.roundingTableCode * --> SSA.roundingTableCode
    
    Defaults to the scheme version analyte's Rounding Table Code and can be updated.
  - SVA.roundingTableCode * --> RRSA.roundingTableCode
    
    A report request scheme analyte's Rounding Table Code defaults to the scheme version analyte's Rounding Table Code and can be updated to subsequently push down to report request scheme version analytes, or as a header in a report.
  - SSA.roundingTableCode --> RRSSA.roundingTableCode
    
    A report request sample scheme analyte's Rounding Table Code defaults to the sample scheme analyte's Rounding Table Code, and is used to generate the report request sample scheme analyte's Formatted Final Value, defaults to the sample scheme analyte's Rounding Table Code. It is only possible to see a report request sample scheme analyte's Rounding Table Code when the sample is selected as the first sample in a multiple report request sample update.
  - RRSSA --> Used when rounding results for the report when the sample scheme analyte's Rounding Method Type is Table.
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Analyte row—Invoiceable
  
  The default setting for an invoice sample scheme analyte's invoiceability in an invoice. Defaults to the scheme version analyte's Invoiceable check box, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
  
  A job invoice sample's Invoiceable defaults to the sample 's Invoiceable check box, and the job invoice scheme analyte's Invoiceable defaults to the scheme version analyte's Invoiceable. Whilst these two flags determine the invoiceability of the sample scheme analyte in the job invoice, an invoice sample scheme analyte's Invoiceable setting allows individual sample scheme analytes in the invoice sample test grid to be excluded from the invoice, so the invoiced client is not charged for that component.
  
  Note: This flag does not cascade up to set a sample's Invoiceability or a sample scheme's Invoiceability.
- Analyte row—Dilution Factor
  
  The factor, as a percentage, by which the sample scheme analyte result is to be, or was, corrected for dilution, as entered in a workbook session using the Data Mode of Dilution mode, prior to the raw numeric result being entered.
  
  Not displayed on the grid by default but can be added via showing individual grid items.
- Analyte row—Package Price Code
  
  The code of the package pricing associated with the sample scheme analyte. Display only.
  
  When a sample scheme analyte is associated with a Template Sample Code because it is registered using a template sample, if the template sample is associated with a Package Price Code, then the sample scheme analyte inherits the package price code. This ensures that the sample scheme analyte is priced under the package pricing and not under the price code on the related job scheme.
  
  A package price on a sample scheme analyte can only be removed by removing the entire package pricing from the sample so that it is removed from all associated sample schemes and sample scheme analytes.
- Analyte row—Composite QC Status
  
  The composite QC status of the sample scheme analyte indicating the status of the underlying analytical results. Display only. This can be:
  - Not Tested
  - Not Required
  - Pass
  - Warning
  - Failure.
  Not displayed on the grid by default but can be added via showing individual grid items.
- Analyte row—Composite Specification Status
  
  The composite specification status of the sample scheme analyte indicating the status of the underlying analytical results against all sample specifications. Display only. This can be:
  - Not Tested
  - Not Required
  - Pass
  - Warning
  - Failure.
  Not displayed on the grid by default but can be added via showing individual grid items.
- Analyte row—Workflow Status
  
  The status of the sample scheme analyte indicating the stage it is at in its life-cycle. Display only. This can be:
  - Not Started
  - Check
  - Repeat
  - Listed Not Received
  - Insufficient Sample
  - Not Analysed
  - No Result
  - Analysed
  - Released
  - Completed.
  Not displayed on the grid by default but can be added via showing individual grid items.
- Analyte row—Default Workflow Status
  
  Only applicable when the sample belongs to a schedule or template job.
  
  The default workflow status of a sample scheme analyte created from this template or schedule sample scheme analyte:
  - Not Started
  - Insufficient Sample
  - Not Analysed
  - No Result.
Scheme and Analyte Search Criteria
- Grid flows
  - Search Schemes—Search for available schemes using the given criteria and display the related scheme, version and analyte details in the scheme analyte grid.
  - Refresh Added Tests—Apply a refresh of the tests grid after adding tests from samples.
- Scheme Code
  
  Filter schemes returned from the search by code. A scheme may be selected from the drop-down list that contains active schemes in scope, as configured in the CCSCHM—Scheme application. Click the field hyperlink to display the CCSCHM—Search Scheme screen, select the appropriate value and click Select and Return to populate the field with the selected value. The % wildcard character is available for use in the criteria field.
  
  For an org-scope (template) job, the list of schemes that display from a scheme search are those which are not yet registered on the sample and includes org-scope schemes that have a published scheme version, and it is the highest published scheme version that is added to the sample.
  
  For a lab-scope job, the list of schemes that display from a scheme search are those which are not yet registered on the sample and includes a) enabled-scope schemes which are org-scope schemes that have no line of business or a line of business matching one of the laboratory's lines of business, which were subsequently enabled for laboratory use, and it is the highest enabled scheme version that is added to the sample, and b) lab-scope schemes, and it is the highest published scheme version that is added to the sample.
- Scheme Name
  
  Filter schemes returned from the search by the name of a scheme. The % wildcard character is available for use in the criteria field.
- Analyte Code
  
  Filter schemes returned from the search by the code of an analyte in a scheme version analyte related to the scheme. An analyte may be selected from the drop-down list that contains active analytes in a scheme version analyte associated with the selected scheme in the Scheme Code search criteria, or if no Scheme Code is selected, then from all active analytes in scope. The % wildcard character is available for use in the criteria field.
- Analyte Name
  
  Filter schemes returned from the search by the name of an analyte in a scheme version analyte related to the scheme. The % wildcard character is available for use in the criteria field.
- Scheme Type
  
  Filter schemes returned from the search by the scheme type. Hidden on the form by default, but added by personalising the form.
- Section Name
  
  Filter schemes returned from the search by the name of the section associated with the scheme. Hidden on the form by default, but added by personalising the form.
- Section Description
  
  Filter schemes returned from the search by the description of the section associated with the scheme. Hidden on the form by default, but added by personalising the form.
- Method Name
  
  Filter schemes returned from the search by the name of the method associated with the scheme version. Hidden on the form by default, but added by personalising the form.
- Method Description
  
  Filter schemes returned from the search by the description of the method associated with the scheme version. Hidden on the form by default, but added by personalising the form.
- Filter Option
  
  Indicates whether to apply the filtering to schemes or to schemes and analytes:
  - Filter Schemes—Return schemes that match the criteria and ALL of their analytes
  - Filter Schemes and Analytes—Return schemes and analytes that match the criteria.
Available Schemes and Analytes Grid
- Grid row flows
  - Add Scheme with Mandatory Analytes—Add the scheme and its mandatory analytes to the sample.
  - Add Entire Scheme—Add the scheme with all its analytes to the sample.
- Grid flows
  - Add Scheme(s) With Mandatory Analytes—Add selected schemes and their mandatory analytes to the sample.
  - Add Analytes—Add selected analytes to the sample.
  - Add Entire Scheme(s)—Add selected schemes with all their analytes to the sample.
- Available Schemes Row—Organisation Scope
  
  Indicates whether this entity is available organisation-wide or laboratory-wide.
  - Checked—The entity is available to users who are logged into any laboratory within the organisation.
  - Unchecked—The entity is only available to users who are logged into the current laboratory.
  A sample's scope is inherited from the job's scope.
  
  The selection in this field can determine the visibility for other fields in this form, and the content of various drop-down selection lists.
- Available Schemes Row—Category Code
  
  A category assigned to the scheme. Selected from categories with a Category Type of SCHEMES.
- Available Schemes Row—Scheme Code
  
  The code of the scheme available to the Laboratory for registration on samples.
- Available Schemes Row—Scheme Version
  
  The number of the highest published active version of the scheme.
- Available Schemes Row—Section Code
  
  The code of the section associated with the scheme.
- Available Schemes Row—Scheme Name
  
  The name of the scheme on the sample.
- Available Schemes Row—Scheme Description
  
  The description of the scheme on the sample.
- Available Schemes Row—Line of Business Code
  
  The code of the line of business associated with the scheme.
- Available Schemes Row—Status
  
  The status of the scheme version:
  - Draft—The scheme version is under development.
  - Published—An org-scope scheme is ready for laboratory use in registration via enabling the scheme (re-enabling of a scheme that is already enabled by a laboratory results in the highest published scheme version being enabled by the laboratory, if it is not already enabled); a lab-scope scheme is ready for laboratory use in registration.
  - Suspended—The scheme version is no longer the highest-published scheme version, so any use of the scheme accesses the next highest-published scheme version available to the laboratory.
- Available Analytes Row—Analyte Code
  
  The code of the analyte available to the laboratory for registration on samples.
- Available Analytes Row—Analyte Name
  
  The name of the analyte.
- Available Analytes Row—Int DL
  
  The lower detection limit of the analyte, that is, the lowest acceptable value in the detection range, and tied to the instrument's or human's ability to detect amounts. There would be no confidence in values that read below the internal lower detection limit.
- Available Analytes Row—Int UL
  
  The upper detection limit of the analyte, that is, the highest acceptable value in the detection range, and tied to the instrument's or human's ability to detect amounts. There would be no confidence in values that read above the internal upper detection limit as the amount is so great, a more reliable test is required to determine it.
- Available Analytes Row—Reportable
  
  The default setting for a sample scheme analyte's Reportable check box which ultimately sets the reportability of the analyte in certificate report requests.
- Available Analytes Row—Rep Seq
  
  No functional use in CCLAS. Represents the sequence of the job scheme analyte in a certificate report, with respect to other job scheme analytes, to override registered scheme analyte sequence, from the enabled-scope scheme when an org-scheme scheme is registered on a lab-scope sample. For use by SQL scripts when using DSC reporting
- Available Analytes Row—Rep Name
  
  The reportable name for the analyte. Defaults to Analyte Code, but with the first character in uppercase and subsequent characters in lowercase, for readability.
  
  A sample scheme analyte's Report Name defaults to the scheme version analyte's Report Name.
  
  When a report request is generated and the analyte is added to it, the report request scheme analyte's Report Name defaults to the sample scheme analyte's Report Name.
- Available Analytes Row—Rep Description
  
  The reportable description of the analyte. Defaults to the scheme version analyte's Report Description.
  
  A report request scheme analyte's Report Description defaults to the sample scheme analyte's Report Description.
- Available Analytes Row—Report Lower DL
  
  The default lower detection limit for rounding and reporting a result for the scheme version analyte.
  - SVA.reportLowerDL * --> SSA.reportLowerDL
    
    A sample scheme analyte's Report Lower DL defaults to the scheme version analyte's Report Lower DL.
  - SVA.reportLowerDL * --> RRSA.reportLowerDL
    
    A report request scheme analyte's Report Lower DL defaults to the scheme version analyte's Report Lower DL and can be updated to subsequently push down to report request scheme version analytes, or as a header in a report.
  - SSA.reportLowerDL --> RRSSA.reportLowerDL
    
    A report request sample scheme analyte's Report Lower DL defaults to the sample scheme analyte's Report Lower DL, and is used to generate the report request sample scheme analyte's Formatted Final Value. It is only possible to see a report request sample scheme analyte's Report Lower DL when the sample is selected as the first sample in a multiple report request sample update.
  - RRSSA --> Used when rounding results for the report.
    
    * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Available Analytes Row—Report Upper DL
  
  The default upper detection limit for rounding and reporting a result for the scheme version analyte.
  - SVA.reportUpperDL * --> SSA.reportUpperDL
    
    A sample scheme analyte's Report Upper DL defaultsto the scheme version analyte's Report Upper DL and can be updated.
  - SVA.reportUpperDL * --> RRSA.reportUpperDL
    
    A report request scheme analyte's Report Upper DL defaults to the scheme version analyte's Report Upper DL and can be updated to subsequently push down to report request scheme version analytes, or as a header in a report.
  - SSA.reportUpperDL --> RRSSA.reportUpperDL
    
    A report request sample scheme analyte's Report Upper DL defaults to the sample scheme analyte's Report Upper DL, and is used to generate the report request sample scheme analyte's Formatted Final Value. It is only possible to see a report request sample scheme analyte's Report Upper DL when the sample is selected as the first sample in a multiple report request sample update.
  - RRSSA --> Used when rounding results for the report.
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Available Analytes Row—Rep Unit
  
  The default unit for rounding and reporting a result for the scheme version analyte. A unit may be selected from the drop-down list that contains active units in scope, as configured in the CCUNIT—Unit application. Click the field hyperlink to display the CCUNIT—Search Unit screen, select the appropriate value and click Select and Return to populate the field with the selected value.
  - SVA.reportUnitCode * --> SSA.reportUnitCode
    
    A sample scheme analyte's Report Unit Code defaults to the scheme version analyte's Report Unit Code and can be updated.
  - SVA.reportUnitCode * --> RRSA.reportUnitCode
    
    A report request scheme analyte's Report Unit Code defaults to the scheme version analyte's Report Unit Code and can be updated to subsequently push down to report request scheme version analytes, or as a header in a report.
  - SSA.reportUnitCode --> RRSSA.reportUnitCode
    
    A report request sample scheme analyte's Report Unit Code defaults to the sample scheme analyte's Report Unit Code, and is used to generate the report request sample scheme analyte's Formatted Final Value. It is only possible to see a report request sample scheme analyte's Report Unit Code when the sample is selected as the first sample in a multiple report request sample update.
  - RRSSA --> Used when rounding results for the report.
    
    When a report is generated for a report request, the sample scheme analyte's Numeric Final Value undergoes unit conversion if the report request sample scheme analyte's Report Unit Code is different to the sample scheme analyte's Unit Code, to determine the reportable numeric value, which is then rounded to produce the report request sample scheme analyte's Formatted Final Value.
  * From the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.
- Available Analytes Row—Parent Analyte Code
  
  The code of parent analyte, such that, if populated, indicates that this analyte is a sub-analyte of the parent analyte. Workbook allows columns holding sub-analytes to be collapsed to just display the parent analyte.
- Available Analytes Row—Is Auto Add
  
  Indicates whether the analyte is registered automatically on the sample when the scheme is registered on a sample during registration.
- Available Analytes Row—Unit Code
  
  The default units in which an analytical result for this analyte is captured.

Specifications Tab

The product, product specifications, and other specifications associated with the sample, and the analytical limits related to those specifications.

This tab is not displayed for laboratory batch samples.

Product Code

The code of the product associated with the sample. A product may be selected from the drop-down list that contains active products in scope, as configured in the CCPRDRT—Product application. Click the field hyperlink to display the CCPRDT—Search Product screen, select the appropriate value and click Select and Return to populate the field with the selected value.

Scope rules apply. If the scope of the entity is org-scope then the drop-down list for the linked entity contains org-scope entities only, and the entity can be linked to org-scope entities only. If the scope of the entity is lab-scope then the drop-down list for the linked entity contains both org-scope and lab-scope entities, and the entity can be linked to either org-scope or lab-scope entities.

Line of business rules apply. The drop-down list for the linked entity is filtered further to contain only those org-scope entities that have no associated line of business or a line of business that matches one of the laboratory's lines of business. The entity can be linked to an org-scope entity only where the org-scope entity has no associated line of business or a line of business that matches one of the laboratory's lines of business.
Specifications Grid

The grid displaying all specifications on the sample.
- Grid flows
  - Lookup CCSPFN—Search for and add specifications to the sample.
- Specification Code
  
  The code of a specification associated with the sample.
- Specification Status
  
  The status of the sample's specification:
  - Not Tested
  - Not Required
  - Pass
  - Warning
  - Lower Warning
  - Upper Warning
  - Trend Warning
  - Failure
  - Lower Failure
  - Upper Failure
  - Trend Failure
  - Ignore Failure
  - Ignore Lower Failure
  - Ignore Upper Failure
  - Ignore Trend Failure.
- Primary Specification
  
  Indicates whether the sample specification is the primary specification whose sample specification's Status is rolled into the sample's Composite QC Status.
- Reportable
- Indicates whether a sample specification is included in reporting record sets.
- Linked To Sample Product
  
  Indicates whether the sample specification is associated with the sample product.
- Specification Limits Grid
  
  The specification limits applicable to the sample.
  - Row Number
    
    The row number within the grid.
    
    Hidden on the grid by default.
  - Specification Code
    
    The code of the specification, from the sample scheme analyte specification.
  - Scheme Code
    
    The code of the scheme, from the sample scheme analyte specification.
  - Version Number
    
    The version number of the scheme, from the sample scheme analyte specification.
  - Analyte Code
    
    The code of the analyte, from the sample scheme analyte specification.
  - Specification Status
    
    The status of the specification, from the sample scheme analyte specification. Display only.
    
    Hidden on the grid by default.
  - Analyte Data Type
    
    The type of data expected for the analytical result for the analyte. Display only. This can be:
    - Numeric Only—A numeric value is expected; only numeric result values are stored.
    - Numeric—A numeric value is expected, however, depending on permissions, a string value can be entered; only a numeric result or string result is stored.
    - Text—A text string is expected; a string result is stored.
    - Boolean—0 or 1 is expected; a Boolean result is stored.
    - Date—A date string is expected (for example, 01/12/2014); a date result is stored.
    - Datetime—A date-time string is expected (for example, 01/12/2014 14:15:11); a date-time result is stored.
    - Image—An image upload is expected; the image result points to the EFS file containing the image.
    - Document—A document upload is expected; the document result points to the EFS file containing the document.
    Hidden on the grid by default.
  - Limit Check Method
    
    The limit check method for the analyte on the specification, that is, the method by which the limits are entered.
    
    Note: that limits are assessed against the entered or calculated absolute values.
    
    This can be:
    - Absolute
    - Relative
    - List
    - By Script (Reserved for future use)
    Different fields display depending on the option. If the Limit Check Method is either Absolute or Relative, then numeric fields are optional.
    
    During the update of a standard specification type, if the Limit Check Method is toggled between Relative and Absolute, then all values for the numeric fields are preserved regardless of whether they are visible on the screen.
    
    During the update of a standard specification type, if the Limit Check Method is Absolute, then all the numeric fields can be manually edited including those that are previously calculated.
    
    If the Limit Check Method is Relative, then the values in the non-displayed fields are preserved.
    - ```
    Internal Percentage Warning Value = 1.96 / 3.09 x ( ( 100 x scheme version analyte's Rep Statistical Detection Limit / Internal Target Value ) + scheme version analyte's Rep Limiting Repeatability)
```
- ```
Internal Percentage Failure = (100 x scheme version analyte's Rep Statistical Detection Limit / Internal Target Value ) + scheme version analyte's Rep Limiting Repeatability)
```
    - ```
    Report Percentage Warning Value = 1.96 / 3.09 x ( ( 100 x scheme version analyte's Rep Statistical Detection Limit / Report Target Value ) + scheme version analyte's Rep Limiting Repeatability)
```
- ```
Report Percentage Failure Value = ( 100 x scheme version analyte's Rep Statistical Detection Limit / Report Target Value ) + scheme version analyte's Rep Limiting Repeatability
```
  - Unit Code
    
    The unit of comparison on the specification.
  - Boolean Value
    
    The confidence Boolean value for the analyte on the specification.
    
    Hidden on the grid by default.
  - Confidence Category Code
    
    The code of the confidence category for the analyte on the specification.
    
    Hidden on the grid by default.
  - Description
    
    The description of the analytical limits on the specification.
  - Reportable Limits
    
    The description of the reportable limits on the specification.
  - Spike Adjustment Factor
    
    The spike adjustment factor for the analyte on the specification.
    
    Hidden on the grid by default.
  - Spike Adjustment Description
    
    The spike adjustment description for the analyte on the specification.
    
    Hidden on the grid by default.
  - Spike Recovery Min Value
    
    The spike recovery minimum value for the analyte on the specification.
    
    Hidden on the grid by default.
  - Spike Recovery Min Warning Value
    
    The spike recovery minimum warning value for the analyte on the specification.
    
    Hidden on the grid by default.
  - Spike Recovery Max Value
    
    The spike recovery maximum value for the analyte on the specification.
    
    Hidden on the grid by default.
  - Spike Recovery Max Warning Value
    
    The spike recovery maximum warning value for the analyte on the specification.
    
    Hidden on the grid by default.
  - Specification List
    
    The list of target values for the analyte on the specification, combined from the text specification list where the analyte has an Analyte Data Type of Text or from the numeric specification list otherwise, used by the system to assess the specification.
  - Critical for Sample Validation
    
    Indicates whether the specification is critical for sample validation for the analyte on the specification.
  - Critical for Sample Grade
    
    Indicates whether the specification is critical for sample grade for the analyte on the specification.
    
    Hidden on the grid by default.
  - Reportable
    
    Indicates whether the specification limits and assessment for the sample scheme analyte specification are included in a report record set.
    
    Displayed to provide visibility of the critical specification limit details during sample registration and maintenance. Additionally, the Reportable check box field is updatable, however, these details are only persisted as a sample scheme version analyte specification record when an update is made to one of the report limit fields, otherwise the persistence of this record is delayed until a result for the sample scheme analyte is assessed against the as is, or updated limits, in which case, the sample scheme analyte specification's Specification Status contains the assessment outcome. Note that these reportable limits are NOT used in specification assessment of the results (it is the internal limits of the specification scheme version analyte that are used). The report limits are only present for reporting purposes.
  - Lower Report Text Limit
    
    The reportable absolute minimum value, and whether this value is inclusive or not, at which a reportable failure is presumed for the sample scheme analyte specification, based on the given Unit Code, and expressed as text.
    
    Displayed to provide visibility of the critical specification limit details during sample registration and maintenance. Additionally, the field is updatable, however, these details are only persisted as a Sample Scheme Version Analyte Specification record when an update is made to one of the report limit fields, otherwise, the persistence of this record is delayed until a result for the sample scheme analyte is assessed against the specification scheme version analyte's internal limits, in which case, the sample scheme analyte specification's Specification Status contains the assessment outcome.
    
    Note: These reportable limits are NOT used in specification assessment of the results (it is the internal limits of the specification scheme version analyte that are used). The report limits are only present for reporting purposes.
  - Upper Report Text Limit
    
    The reportable absolute maximum value, and whether this value is inclusive or not, at which a reportable failure is presumed for the sample scheme analyte specification, based on the given Unit Code, and expressed as text.
    
    Displayed to provide visibility of the critical specification limit details during sample registration and maintenance. Additionally, the field is updatable, however, these details are only persisted as a Sample Scheme Version Analyte Specification record when an update is made to one of the report limit fields, otherwise, the persistence of this record is delayed until a result for the sample scheme analyte is assessed against the specification scheme version analyte's internal limits, in which case, the sample scheme analyte specification's Specification Status contains the assessment outcome.
    
    Note: These reportable limits are NOT used in specification assessment of the results (it is the internal limits of the specification scheme version analyte that are used). The report limits are only present for reporting purposes.
  - Lower Report Numeric Limit
    
    The reportable absolute minimum value at which a reportable failure is presumed for the sample scheme analyte specification, based on the given Unit Code.
    
    Displayed to provide visibility of the critical specification limit details during sample registration and maintenance. Additionally, the field is updatable, however, these details are only persisted as a Sample Scheme Version Analyte Specification record when an update is made to one of the report limit fields, otherwise, the persistence of this record is delayed until a result for the sample scheme analyte is assessed against the specification scheme version analyte's internal limits, in which case, the sample scheme analyte specification's Specification Status contains the assessment outcome.
    
    Note: These reportable limits are NOT used in specification assessment of the results (it is the internal limits of the specification scheme version analyte that are used). The report limits are only present for reporting purposes.
  - Upper Report Numeric Limit
    
    The reportable absolute maximum value at which a reportable failure is presumed for the sample scheme analyte specification, based on the given Unit Code.
    
    Displayed to provide visibility of the critical specification limit details during sample registration and maintenance. Additionally, the field is updatable, however, these details are only persisted as a Sample Scheme Version Analyte Specification record when an update is made to one of the report limit fields, otherwise, the persistence of this record is delayed until a result for the sample scheme analyte is assessed against the specification scheme version analyte's internal limits, in which case, the sample scheme analyte specification's Specification Status contains the assessment outcome.
    
    Note: These reportable limits are NOT used in specification assessment of the results (it is the internal limits of the specification scheme version analyte that are used). The report limits are only present for reporting purposes.
  - Internal Specification
    
    The description of the internal limits for the analyte on the specification; defaults to a concatenation of the individual limits.
  - Internal Target Value
    
    The internal target value for the analyte on the specification, based on the given Unit Code, used by the system to calculate the absolute limits where the Limit Check Method is Absolute or Relative.
    
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits. The system always uses absolute limits for QC assessment.
  - Internal Min Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The minimum value, at, or below, which a failure occurs, for limit assessment.
    
    Where the Internal Min Inclusive check box is:
    - Checked—The Internal Min Value is included within the acceptable range, such that, any result below the limit returns a Lower Failure.
    - Unchecked—The Internal Min Value is not included within the acceptable range, such that, any result at, or below, the limit returns a Lower Failure.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Internal Min Inclusive
    
    Only displayed where the Limit Check Method is Absolute.
    
    Indicates whether the Internal Min Value is included within the acceptable range, for limit assessment. Where:
    - Checked—Any result below the Internal Min Value returns a Lower Failure.
    - Unchecked—Any result equal to, or below, the Internal Min Value returns a Lower Failure.
    Hidden on the grid by default.
  - Internal Max Warning Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The minimum warning value, at, or below, which a warning occurs, for limit assessment.
    
    Where the Internal Min Warning Inclusive check box is:
    - Checked—The Internal Min Warning Value is included within the acceptable range, such that, any result below the limit, but not within a lower failure range, returns a Lower Warning.
    - Unchecked—The Internal Min Warning Value is not included within the acceptable range, such that, any result at, or below, but not within a lower failure range, returns a Lower Warning.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Internal Min Warning Inclusive
    
    Only displayed where the Limit Check Method is Absolute.
    
    Indicates whether the Internal Min Warning Value is included within the acceptable range, for limit assessment. Where:
    - Checked—Any result below the Internal Min Warning Value, but not within a lower failure range, returns a Lower Warning.
    - Unchecked—Any result equal to, or below, the Internal Min Warning Value, but not within a lower failure range, returns a Lower Warning.
    Hidden on the grid by default.
  - Internal Max Warning Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The maximum warning value, at, or above, which a warning occurs, for limit assessment.
    
    Where the Internal Max Warning Inclusive check box is:
    - Checked—The Internal Max Warning Value is included within the acceptable range, such that, any result above the limit, but not within an upper failure range, returns an Upper Warning.
    - Unchecked, then the Internal Max Warning Value is not included within the acceptable range, such that, any result at, or above, but not within an upper failure range, returns an Upper Warning.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Internal Max Warning Inclusive
    
    Only displayed where the Limit Check Method is Absolute.
    
    Indicates whether the Internal Max Warning Value is included within the acceptable range, for limit assessment. Where:
    - Checked—Any result above the Internal Max Warning Value, but not within an upper failure range, returns an Upper Warning.
    - Unchecked—Any result equal to, or above, the Internal Max Warning Value, but not within an upper failure range, returns an Upper Warning.
      
      Hidden on the grid by default.
  - Internal Max Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The maximum value, at, or above, which a failure occurs, for limit assessment.
    
    Where the Internal Max Inclusive check box is:
    - Checked, then the Internal Max Value is included within the acceptable range, such that, any result above the limit returns an Upper Failure.
    - Unchecked, then the Internal Max Value is not included within the acceptable range, such that, any result at, or above, the limit returns an Upper Failure.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Internal Max Inclusive
    
    This field is displayed only where the Limit Check Method is Absolute.
    
    Indicates whether the Internal Max Value is included within the acceptable range, for limit assessment. Where:
    - Checked—Any result above the Internal Max Value returns an Upper Failure.
    - Unchecked—Any result equal to, or above, the Internal Max Value returns an Upper Failure.
    Hidden on the grid by default.
  - Report Specification
    
    The description of the reportable limits for the analyte on the specification. Defaults to a concatenation of the individual limits.
  - Report Target Value
    
    The reportable target value for the analyte on the specification, based on the given Unit Code, for inclusion on a certificate report.
    
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Report Min Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The minimum value, at, or below, which a failure occurs, for inclusion on a certificate report.
    
    Where the Report Min Inclusive check box is:
    - Checked—The Report Min Value is included within the acceptable range, such that, any result below the limit returns a Lower Failure.
    - Unchecked—The Report Min Value is not included within the acceptable range, such that, any result at, or below, the limit returns a Lower Failure.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Report Min Inclusive
    
    Only displayed where the Limit Check Method is Absolute.
    
    Indicates whether the Report Min Value is included within the acceptable range, for inclusion on a certificate report. Where:
    - Checked—Any result below the Report Min Value returns a Lower Failure.
    - Unchecked—Any result equal to, or below, the Report Min Value returns a Lower Failure.
    Hidden on the grid by default.
  - Report Min Warning Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The internal minimum warning value, at, or below, which a warning occurs, for inclusion on a certificate report.
    
    Where the Internal Min Warning Inclusive check box is:
    - Checked—The Internal Min Warning Value is included within the acceptable range, such that, any result below the limit, but not within a lower failure range, returns a Lower Warning.
    - Unchecked—The Internal Min Warning Value is not included within the acceptable range, such that, any result at, or below, but not within a lower failure range, returns a Lower Warning.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Report Min Warning Inclusive
    
    Only displayed where the Limit Check Method is Absolute.
    
    Indicates whether the Report Min Warning Value is included within the acceptable range, for inclusion on a certificate report. Where:
    - Checked—Any result below the Report Min Warning Value, but not within a lower failure range, returns a Lower Warning.
    - Unchecked—Any result equal to, or below, the Report Min Warning Value, but not within a lower failure range, returns a Lower Warning.
    Hidden on the grid by default.
  - Report Max Warning Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The maximum warning value, at, or above, which a warning occurs, for inclusion on a certificate report.
    
    Where the Report Max Warning Inclusive check box is:
    - Checked—The Report Max Warning Value is included within the acceptable range, such that, any result above the limit, but not within an upper failure range, returns an Upper Warning.
    - Unchecked—The Report Max Warning Value is not included within the acceptable range, such that, any result at, or above, but not within an upper failure range, returns an Upper Warning.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Report Max Warning Inclusive
    
    Only displayed where the Limit Check Method is Absolute.
    
    Indicates whether the Report Max Warning Value is included within the acceptable range, for inclusion on a certificate report. Where:
    - Checked—Any result above the Report Max Warning Value, but not within an upper failure range, returns an Upper Warning.
    - Unchecked—Any result equal to, or above, the Report Max Warning Value, but not within an upper failure range, returns an Upper Warning.
    Hidden on the grid by default.
  - Report Max Value
    
    Only displayed where the Limit Check Method is Absolute.
    
    The maximum value, at, or above, which a failure occurs, for inclusion on a certificate report.
    
    Where the Report Max Inclusive check box is
    - Checked—The Report Max Value is included within the acceptable range, such that, any result above the limit returns an Upper Failure.
    - Unchecked—The Report Max Value is not included within the acceptable range, such that, any result at, or above, the limit returns an Upper Failure.
    Note: When relative limits are entered, then the system calculates an accompanying set of absolute limits.
  - Report Max Inclusive
    
    Only displayed where the Limit Check Method is Absolute.
    
    Indicates whether the Report Max Value is included within the acceptable range, for inclusion on a certificate report. Where:
    - Checked—Any result above the Report Max Value returns an Upper Failure.
    - Unchecked—Any result equal to, or above, the Report Max Value returns an Upper Failure.
    Hidden on the grid by default.
  - Is Case Sensitive
    
    Indicates whether the list of target values for the analyte on the specification, where the analyte has an Analyte Data Type of Text, are case-sensitive, used by the system to assess the specification.
    
    Hidden on the grid by default.
  - Product Specification Results Notes
    
    Notes regarding the performance of the sample against the product specifications.
    
    Rich text formatting can be used to control the appearance of the information, with basic formatting ribbon and hyperlink entry field. For example, the name of a contact can be entered in bold, the telephone number in italics, and hyperlinks can be used. The formatting is saved along with the actual content. Canned comment functionality is accessed via the F2 function key and is used to enter chunks of text from a selected Canned Comment Code.
    
    The drop-down list of available canned comment codes is filtered based on the scope of canned comment with respect to the entity having canned comments entered, and either:
    - 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:
    - The list of category codes entered in the Category Code. The category codes are initially populated from the categories whose code appears in the related preference, where the preference changes according to the particular notes field being updated:
    As soon as a canned comment code is entered or selected from the drop-down list, the canned comment long form content is embedded into the note field. Note that Cancel can be clicked at any time to exit canned comment selection.
    
    The canned comment tool uses a Canned Comment Type of SAMPLE and a Canned Comment Subtype of ANALYSIS, and the Category Code defaults to the value of the NOTES_SAMPLE_PRODUCT_CATEGORIES application preference.

Portions Tab

The sample portions associated with the sample.

The tab is only displayed for a production, internal or lab-scope template job.

If the SAM_TRACK_REG_AT_SAMPLE_REG application preference is cleared then the Portions tab does not display, and portions cannot be created manually or automatically during sample registration.

If the SAM_TRACK_REG_AT_SAMPLE_REG application preference is checked then the Portions tab displays, allowing portions to be created and updated during sample registration for jobs that have a Job Type of Production or Internal.

The initial grid contains rows based upon the value of Number of Containers, allowing you to add/update/delete portions, and upon submit the portions are persisted. The following changes to sample portions are audited enabling managers to track when a sample portion has moved and by whom:

When a portion is created for a sample or sample group,
When a portion's Multiple Capacity Container Type Code or Container Name is updated,
When a portion's Sample Handling Code is updated,
When a portion is deleted.

Grid during Sample Create

The portions to be initially assigned to each sample expanded from the sample group.

If the SAM_TRACK_REG_WHEN_JOB_COMPLETE application preference is cleared, then default portions display based upon the value in the SAM_TRACK_REG_NUMBER_OF_CONTAINERS application preference, and portions can be added, updated or deleted, and upon submit, the portions are applied to each sample expanded from the sample group. If the SAM_TRACK_REG_WHEN_JOB_COMPLETE application preference is checked, then no initial sample portions can be created until the job's Workflow Status is Completed.
- Portion Type
  
  The type of sample portion.
  - As Registered (Default)—A portion of sample that originates from the client. A preparation facility can split additional As Registered portions from an initial As Registered portion submitted from a client.
  - Laboratory—A portion of sample, usually split from an As Registered portion, and used for a specific test or tests on the sample.
- Location Code
  
  The code of the location associated with the portion.
- Location Hierarchy
  
  The hierarchical location associated with the portion. A location may be selected from the drop-down list that contains active locations in scope, as configured in the CCLCTN—Location application. Each location's hierarchy precedes its location code. The list is filterable using % and _ wildcards. Click the field hyperlink to display the CCLCTN—Search Location screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the location referenced in the SAM_TRACK_REG_LOCATION application preference.
  
  Note: A portion's location cannot be cleared. If the intention is to assign the portion to a disposed or end-of-life status, use a location that represents that.
- Single Capacity Container Type Code
  
  The code of the single-capacity container type associated with the portion, that is, the type of container that holds one sample portion. A container type may be selected from the drop-down list that contains active container types in scope with a Capacity Type of Single, as configured in the CCCNTP—Container Type application. Click the field hyperlink to display the CCCNTP—Search Container Type screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the single-capacity container type referenced in the SAM_TRACK_REG_SINGLE_CONTAINER_TYPE application preference.
- Sample Handling Code
  
  The code of the sample handling actioned upon the portion. A sample handling action may be selected from the drop-down list that contains active sample handling actions in scope, as configured in the CCSHND—Sample Handling application. Click the field hyperlink to display the CCSHND—Search Sample Handling screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the Location Default Sample Handling Code associated with the portion's Location Code.
  
  If Sample Handling Code is updated, then the sample handling dates are updated.
- Notes
  
  Notes regarding the portion.
Grid during Sample Update

The portions assigned to the sample.
- Portion Code
  
  The code of the portion. Display only. Defaults to a sequential 3-digit numerical code, starting at 000 and incrementing by 1 for each new sample portion that is created for the sample.
- Portion Type
  
  The type of sample portion. Selected from:
  - As Registered (Default)—A portion of sample that originates from the client. A preparation facility can split additional As Registered portions from an initial As Registered portion submitted from a client.
  - Laboratory—A portion of sample, usually split from an As Registered portion, and used for a specific test or tests on the sample.
- Scheme Codes
  
  A comma-separated list of scheme codes registered on the sample, where the portion is associated with the sample schemes, typically for a laboratory portion. Display only.
- Active
  
  Indicates whether the sample portion is active for use. When cleared, this often means that the sample portion is off-site or disposed. Display only.
- Location Code
  
  The code of the location associated with the portion. Display only.
- Location Hierarchy
  
  The hierarchical location associated with the portion. A location may be selected from the drop-down list that contains active locations in scope, as configured in the CCLCTN—Location application. Each location's hierarchy precedes its location code. The list is filterable using % and _ wildcards. Click the field hyperlink to display the CCLCTN—Search Location screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the location referenced in the SAM_TRACK_REG_LOCATION application preference.
  
  Note: A portion's location cannot be cleared. If the intention is to assign the portion to a disposed or end-of-life status, use a location that represents that.
- Checked in On
  
  The date-time at which the portion was checked into the location. Display only.
- Checked in By
  
  The code of the user who checked the portion into the location. Display only.
- Single Capacity Container Type Code
  
  The code of the single-capacity container type associated with the portion, that is, the type of container that holds one sample portion. A container type may be selected from the drop-down list that contains active container types in scope with a Capacity Type of Single, as configured in the CCCNTP—Container Type application. Click the field hyperlink to display the CCCNTP—Search Container Type screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the single-capacity container type referenced in the SAM_TRACK_REG_SINGLE_CONTAINER_TYPE application preference.
- Sample Handling Code
  
  The code of the sample handling actioned upon the portion. A sample handling action may be selected from the drop-down list that contains active sample handling actions in scope, as configured in the CCSHND—Sample Handling application. Click the field hyperlink to display the CCSHND—Search Sample Handling screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the Location Default Sample Handling Code associated with the portion's Location Code.
  
  If Sample Handling Code is updated, then the sample handling dates are updated.
- Started Date
  
  The date-time at which the portion started the sample handling action. Display only.
- Started By
  
  The code of the user who started the sample handling action on the portion. Display only.
- Due Date
  
  The date-time at which the portion's sample handling action is due completion, calculated as Started Date + the sample handling's Duration. Display only.
- Multiple Capacity Container Type Code
  
  The code of the multi-capacity container type associated with the portion, that is, the type of container that holds containerised portions of this type. Display only.
- Container Name
  
  The name of the multi-capacity container assigned to the portion during containerisation. Display only.
- Notes
  
  Notes regarding the portion.

Linked Samples Tab

The list of individual constituent samples that comprise a composite sample. All fields are read-only except for the Notes field.

The Linked Samples tab is displayed only if the sample was created as a composite sample, that is, if the sample's Is Composite is selected, and is not displayed for laboratory batch samples.

Tab flows
- Add Samples—Search for and return samples so they can be associated with the current sample.
Sample Name

The name of the sample from which the composite sample was created.
Client Sample Name

The client's name for the sample.
Description

The description of the sample.
Product Code

The code of the product associated with the sample. A product may be selected from the drop-down list that contains active products in scope, as configured in the CCPRDRT—Product application. Click the field hyperlink to display the CCPRDT—Search Product screen, select the appropriate value and click Select and Return to populate the field with the selected value.

Scope rules apply. If the scope of the entity is org-scope then the drop-down list for the linked entity contains org-scope entities only, and the entity can be linked to org-scope entities only. If the scope of the entity is lab-scope then the drop-down list for the linked entity contains both org-scope and lab-scope entities, and the entity can be linked to either org-scope or lab-scope entities.

Line of business rules apply. The drop-down list for the linked entity is filtered further to contain only those org-scope entities that have no associated line of business or a line of business that matches one of the laboratory's lines of business. The entity can be linked to an org-scope entity only where the org-scope entity has no associated line of business or a line of business that matches one of the laboratory's lines of business.
Product Name

The name of the product.
Notes

Notes regarding the constituent sample. Typically this could contain the percentage of the constituent sample viz the composite sample, for example:
```
The linked constituent sample may comprise 50% of the composite sample.
```

Status Tab

The current status of the sample.

Sample Template Code

The code of the template sample, where a template sample was used to create this Sample.
Workflow Status

The status of the sample indicating the stage it is at in its life-cycle. Display only. This can be:
- Registered
- Not Started
- Listed Not Received
- Insufficient Sample
- Not Analysed
- No Result
- Started
- Analysed
- Released
- Completed.
Note: Sample validation is not indicated by a workflow status, but by the stamping of its Validated Date.
Composite QC Status
The composite QC status of the sample indicating the status of the underlying analytical results. Display only. This can be:
- Not Tested
- Not Required
- Pass
- Warning
- Failure
- Ignored Failure.
Composite Specification Status

The composite specification status of the sample indicating the status of the underlying analytical results against all sample specifications. Display only. This can be:
- Not Tested
- Not Required
- Pass
- Failure.
Last Activated On

The date-time at which the sample was last activated, upon which the sample's Workflow Status was set to Not Started.
Activated By

The code of the user who last activated the sample.
Owner Changed On

The date-time at which the owner of the sample was changed.
Owned By

The code of the user who changed the owner of the sample.
No. Schemes in Sample

The number of schemes registered for the sample.
Started On

The date-time at which the sample was started, when the sample's Workflow Status became Started.
No. Schemes Started

The number of sample schemes associated with the sample where the sample scheme's Workflow Status is Started.
Analysed On

The date-time at which the sample was analysed, when the sample's Workflow Status became Analysed.
Released On

The date-time at which the sample was released, when the sample's Workflow Status became Released.
Released By

The code of the user who released the sample.
Validated On

The date-time at which the sample was validated.
Validated By

The code of the user who validated the sample.
Authorised On

The date-time at which the sample was authorised.
Authorised By

The code of the user who authorised the sample.
First Reported On

The date-time at which the sample was first included in the generation of a preliminary or final certificate report.
Last Reported On

The date-time at which the sample was last reported.
Last Invoiced On

The date-time at which the sample was last invoiced.
Last Invoiced By

The code of the user who last invoiced the sample.
Finalised On

The date-time at which the sample was finalised.
Finalised By

The code of the user who finalised the sample.
Last Archived On

The date-time at which the sample was last archived.
Archived By

The code of the user who last archived the sample.
Approved Date

The date-time at which the org-scope template sample was approved for export. Display only. Only relevant when the Organisation Scope is selected.
Approved By

The code of the user who approved the org-scope template sample for export. Display only. Only relevant when the Organisation Scope is selected.
Job Cancelled On

The date-time at which the sample's job was cancelled, upon which the job's Workflow Status was set to Cancelled. Display only.
Job Cancelled By

The code of the user who cancelled the sample's job. Display only.
Job Cancelled/Reinstated Reason

The reason for cancelling or reinstating the sample's job. Display only.

Schedule Tab

The details of whether the stream sample is used to a generate production sample when the schedule job is used to generate draft or production samples in draft or production jobs.

Is Active For Manual Registration

Only relevant when the screen is opened for a stream sample within a schedule job.

Indicates whether the stream sample is included in manual registration when the schedule job is used to creates a sample within a draft or production job.
Is Active For Auto Registration

Only relevant when the screen is opened for a stream sample within a schedule job.

Indicates whether the stream sample is included in automatic registration when the schedule job is used to creates a sample within a production job.
Sampling Start Offset

Offset applied to the scheduled date-time, used to determine a draft/production sample's Sampling Started On date-time when the draft/production sample is created using the stream sample. The offset can be positive or negative. Entered in the format xN, where x is an integer and N is a code for a date-time period: S (second), N (minute), H (hour), D (day), M (month), Y (year). For example, 10D (10 days), 30N (30 minutes).
Sampling Date Offset

The offset applied to the scheduled date-time, used to determine a draft/production sample's Sampled On date-time when the draft/production sample is created using the stream sample. The offset can be positive or negative. Entered in the format xN, where x is an integer and N is a code for a date-time period: S (second), N (minute), H (hour), D (day), M (month), Y (year). For example, 10D (10 days), 30N (30 minutes).
Use Schedule Job Frequency

Indicates whether the stream sample is to use the same registration frequency as the schedule job.
Scheduled Times

The time of day at which the scheduled sample is used to generate a draft/production sample. A valid schedule comprises the Scheduled Months and Scheduled Times, and either the Scheduled Weeks and Scheduled Days, or the Scheduled Days of Month.
Scheduled Days

The days of the week on which the scheduled sample is used to generate a draft/production sample. A valid schedule comprises the Scheduled Months and Scheduled Times, and either the Scheduled Weeks and Scheduled Days, or the Scheduled Days of Month.
Scheduled Days of Month

The days of the month on which the scheduled sample is used to generate a draft/production sample. A valid schedule comprises the Scheduled Months and Scheduled Times, and either the Scheduled Weeks and Scheduled Days, or the Scheduled Days of Month.
Scheduled Months

The months of the year on which the scheduled sample is used to generate a draft/production sample. A valid schedule comprises the Scheduled Months and Scheduled Times, and either the Scheduled Weeks and Scheduled Days, or the Scheduled Days of Month.
Scheduled Weeks

The weeks of the year on which the scheduled sample is used to generate a draft/production sample. A valid schedule comprises the Scheduled Months and Scheduled Times, and either the Scheduled Weeks and Scheduled Days, or the Scheduled Days of Month.