CCREGNSMPLSCHANA—Sample Scheme Analyte 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

  • Sample Name

    The name of the sample.

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

  • Analyte Code

    The code of the analyte on the sample.

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

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

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

Primary Details Tab

The primary details of the sample scheme analyte.

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

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

  • Workflow Active

    No functional use in core CCLAS. This flag is taken from the master scheme version analyte.

  • Required On

    The date-time at which the sample scheme analyte's results must be reported.

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

  • Expires On

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

    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.

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

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

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

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

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

  • 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 above the Internal Upper DL and the Internal Lower DL Critical is selected.

  • 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 below the Internal Upper DL and the Internal Upper DL Critical is selected.

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

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

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

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

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

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

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

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

  • Template Sample Code

    The code of the template sample used to register the sample scheme analyte. Display only.

    Where a sample scheme analyte 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 analyte.

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

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

  • Notes

    The notes regarding the analysis of the sample scheme analyte.

    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_SAMPLESCHEMEANALYTE_REPORT_CATEGORIES application preference.

Status Tab

The current status of the Sample Scheme Analyte.

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

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

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

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

  • 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 analyte was started, in which the sample scheme analyte's Workflow Status was first set to Analysed.

  • Analysed On

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

  • Released On

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

  • Released By

    The code of the user who released the sample scheme analyte.

  • Validated On

    No functional use in core CCLAS.

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

  • Validated By

    No functional use in core CCLAS.

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

  • Last Reported On

    No functional use in core CCLAS.

  • Last Invoiced On

    No functional use in core CCLAS.