CCREGNSMPLSCH—Sample Scheme Detail

Processes associated with this form
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 entity.
  • Save As—Create a new entity based on the information provided by an existing entity.
  • Delete—Confirm and delete the current entity.
Header

  • Client Sample Name

    The client's name for the sample.

    Scheme Code

    The code of the scheme on the sample.

  • Scheme Version

    The version number of the scheme on the sample.

  • 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.

  • Composite QC Status

    The composite QC status of the sample scheme indicating the status of the underlying analytical results. Display only. This can be:

    • Not Tested

    • Not Required

    • Pass

    • Failure.

  • 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.

Primary Details Tab

The primary details of the sample scheme.

  • 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.

  • Subcontract Laboratory Org Code

    The code of the organisation associated with the subcontract laboratory.

  • 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.

  • 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.

  • 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 Script

    No functional use in core CCLAS.

  • Expires On

    The date-time at which the sample expires for the scheme.

    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.

  • 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.

  • 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

  • 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

  • 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.

  • 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.

  • Invoicable

    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.

  • 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.

  • Internal Cost

    No functional use in core CCLAS. Represents the internal cost of the method for one sample undergoing the scheme.

  • 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.

  • Include in Auto Reg

    Only relevant where this 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.

  • 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.

  • 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.

  • 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.

  • Include in Manual Reg

    Only relevant where this 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.

  • Paperworks

    No functional use in core CCLAS. Represents automatic paperworkj 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.

  • Labels

    No functional use in core CCLAS. 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.

  • Analysis Notes

    Notes regarding the analytical requirements of the sample scheme.

    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, GLOBAL, JOB, SAMPLE or SCHEME, and the Canned Comment Subtype, GLOBAL, REGISTRATION, RECEIPT, ANALYSIS, RELEASE, VALIDATION, REPORT or INVOICE,

    or:

    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 SCHEME and a Canned Comment Subtype of ANALYSIS, and the Category Code defaults to the value of the NOTES_SAMPLESCHEME_ANALYSIS_CATEGORIES application preference.

  • Report Notes

    Notes regarding the reporting requirements of the sample scheme.

    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, GLOBAL, JOB, SAMPLE or SCHEME, and the Canned Comment Subtype, GLOBAL, REGISTRATION, RECEIPT, ANALYSIS, RELEASE, VALIDATION, REPORT or INVOICE,

    or:

    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 SCHEME and a Canned Comment Subtype of REPORT, and the Category Code defaults to the value of the NOTES_SAMPLESCHEME_REPORT_CATEGORIES application preference.

Limits Specification Tab

The scheme limits specification for the sample scheme.

  • Scheme Limits 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. Defaults to the scheme's Limit Specification Code, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample

  • Scheme Limits Specification Grid

    The set of analytical limits for the scheme limits specification.

  • Scheme

    The code of the scheme on the specification.

  • Version Number

    The version number of the scheme on the specification.

  • Analyte

    The code of the analyte on the specification.

  • Confidence Category Code

    A category assigned to the specification limits.

  • Unit Code

    The code of the unit of comparison on the specification.

  • Limit Check Method

    The method by which the limits are entered. The options are:

    • Absolute

    • Relative

    • List

    • By Script (Reserved for future use)

    Different fields display depending on the option. If the Limit Check Method is 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 UI.

    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

    Note: Limits are assessed against the entered or calculated absolute values.

  • 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. When relative limits are entered, then the system calculates an accompanying set of absolute limits.

    Note: The system always uses absolute limits for QC assessment.

Dependent Samples Tab

The duplicate, replicate and spike QC samples whose parent is the current sample.

Note: The QC samples are not searched by where the QC sample is registered for the scheme; a duplicate, replicate or spike QC sample shows here even if it is not registered for the scheme. This tab should really be at sample level.

  • Name

    The name of the dependent sample.

  • Primary Analytical Type

    The primary analytical type of the sample that denotes the type of QC assessment that the sample primarily undergoes after receiving a result:

    • Unknown

    • Duplicate

    • Replicate

    • Blank

    • Standard

    • Spike.

  • QC Type Code

    The code of the primary QC type that is a sub-classification of the Primary Analytical Type.

  • Description

    The description of the sample.

Linked Schemes Tab

A linked scheme is where the analysis is performed on the same racks of samples.

Linked sample schemes control whether weights and volumes are transferred from one sample scheme to a linked sample scheme when entering a value in weight/volume mode in a workbook session, since linking denotes that the same aliquot is used for both schemes.

  • Only the first linked job scheme is allowed to be opened after searching for workbooks with weight/volume mode.

  • Sample scheme links default to the linked scheme relationships contained within the master scheme, when both schemes are registered on the sample.

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

Refer to Conditions for Propagating Weights and Volumes when an Analyte is added to a Sample Scheme.

A sample's linked scheme relationships default from the scheme's linked scheme relationships, where the schemes are registered on the sample, from the org-scope scheme when an org-scope scheme is registered on a lab-scope sample

  • Linked From

    The parent scheme within the linked scheme relationship.

  • Linked To

    The child scheme within the linked scheme relationship.

  • Name

    The name of the linked-to scheme.

Report Header/Footer Tab

The reportable text for the sample scheme.

Status Tab

The current status of the sample scheme.

  • Composite QC Status

    The composite QC status of the sample scheme indicating the status of the underlying analytical results. Display only. This can be:

    • Not Tested

    • Not Required

    • Pass

    • Failure.

  • 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.

  • 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. Display only. This can be:

    • Not Started

    • Insufficient Sample

    • Not Analysed

    • No Result.

  • Workflow Status

    The status of the sample scheme indicating the stage it is at in its life-cycle. Display only. Display only. This can be:

    • Not Started

    • Listed Not Received

    • Insufficient Sample

    • Not Analysed

    • No Result

    • Started

    • Analysed

    • Released

    • Completed.

    This is only shown by default when the sample belongs to a registered or draft job.

  • Registered On

    The date-time at which the scheme was registered on the sample, in which the sample scheme's Workflow Status was set to Not Started.

  • Registered By

    The code of the user who registered the scheme on the sample.

  • Last Activated On

    No functional use in core CCLAS.

  • Activated By

    No functional use in core CCLAS.

  • Started On

    The date-time at which the sample scheme was started, in which the sample scheme's Workflow Status was first set to Started.

  • Analysed On

    The date-time at which the sample scheme was analysed or completed preparation, and the sample scheme's Workflow Status was set to Analysed.

  • Released On

    The date-time at which the sample scheme was released, in which the sample scheme's Workflow Status was set to Released.

  • Released By

    The code of the user who released the sample scheme.

  • Validated On

    No functional use in core CCLAS.

    Tip: Personalise the form to display the sample scheme's Completed On instead, which is the date-time at which the sample scheme was completed, in which the sample scheme's Workflow Status was set to Completed.

  • Validated By

    No functional use in core CCLAS.

    Tip: Personalise the form to display sample scheme's Completed By instead, which is the code of the user who completed the sample scheme.

  • First Reported On

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

  • Last Reported On

    No functional use in core CCLAS. Represents the date-time at which the sample scheme was last reported.

  • Last Invoiced On

    No functional use in core CCLAS. Represents the date-time at which the sample was last invoiced.