CCSAMPMULTIEDIT—Update Multiple Samples 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.
  • Add Tests from Sample—Add tests from a selected sample to the current samples.
Header

  • Client Sample Name

    The client's name for the sample.

  • Description

    The description of the job.

Primary Details Tab

The primary details of the sample.

Note: In multiple sample update mode, only a sub-set of the fields can be updated.

  • Primary Analytical Type

    The primary analytical type of the sample that denotes the type of QC assessment that the sample primarily undergoes:

    • Unknown

    • Duplicate

    • Replicate

    • Standard

    • Blank

    • Spike.

    This field cannot be updated in multiple sample update since it is not applicable to all samples.

  • Primary QC Type Code

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

    This field cannot be updated in multiple sample update since it is not applicable to all samples.

  • Secondary Analytical Type

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

    • Duplicate

    • Replicate

    • Blank

    • Standard

    • Spike.

    This field cannot be updated in multiple sample update since it is not applicable to all samples.

  • Secondary QC Type Code

    The code of the secondary QC type that is a sub-classification of the Secondary Analytical Type.

    This field cannot be updated in multiple sample update since it is not applicable to all samples.

  • Parent Client Sample Name

    No functional use in core CCLAS. Represents the parent sample of the client sample.

    This field cannot be updated in multiple sample update since it is not applicable to all samples.

  • Standard Code

    The code of the standard associated with the sample.

    This field cannot be updated in multiple sample update since it is not applicable to all samples.

  • Standard Lot Code

    The code of the current standard lot for the standard associated with the sample. A standard lot may be selected from the drop-down list that contains active standards lots for the standard where the Stock Level is greater than zero, and the Expiry date-time is after the current system date-time, as configured in the CCSTND—Standard application. Defaults to the standard's Current Standard Lot Code.

    Applicable only where the Primary Analytical Type or Secondary Analytical Type is Blank, Standard or Spike.

    This field cannot be updated in multiple sample update since it is not applicable to all 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.

  • 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

    The number of containers required to hold the sample.

  • Delivered By

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

  • Priority

    The priority of the sample with respect to other samples in the system. Defaults to 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 samples' 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 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

    The default setting for a report request sample's Reportable check box when a report request is created for labels, which indicates whether the sample is included in the generated labels by default.

    Note : Unknown samples are always included in a labels report request, but a duplicate, replicate, blank, standard or spike QC sample is only included in a labels report request if the sample's Generate Label is selected.

  • Generate Paperwork

    The default setting for a report request sample's Reportable check box when a report request is created for paperwork, which indicates whether the sample is included in the generated paperwork by default.

    Note: Unknown samples are always included in a paperwork report request, but a duplicate, replicate, blank, standard or spike QC sample is only included in a paperwork report request if the sample's Generate Label is selected.

  • Reportable

    The default setting for a report request sample's Reportable check box in a certificate report request.

    Note: that unknown samples are always included in a certificate report request, but a duplicate, replicate, blank, standard or spike QC sample is only included in a report request if the sample's Reportable is selected.

  • Number of Hours

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

Notes Tab

Notes associated with the sample.

Tests Tab

The schemes and analytes assigned to the sample for testing.

  • Registered Schemes and Analytes Grid

    • Grid flows

      • Change Reporting Details for all Samples—For selected analytes, the ability to update reporting unit, factor report detection limits, apply a new rounding table, and update reportability, for all samples in the multi-sample update.

      • Remove Analyte from all Samples—Remove the selected analytes from all of the samples in the multiple sample update.

      • Remove Scheme from all Samples—Remove selected schemes from all of the samples in the multiple update.

      • Remove Scheme with Related QC — Remove selected schemes from the samples and its related QC samples and if the QC last scheme has been removed from the QC, it deletes the QC as well.

        Note: The Remove Scheme with Related QC service can remove the scheme from the sample even if the sample is batched. See Maintaining Sample Tests sections for related information.

    • Scheme row—Add to All

      Indicates whether to add the scheme to all samples in the multiple sample update.

    • Scheme row—Scheme Name

      The name of the scheme.

    • Scheme row—Scheme Code

      The code of the scheme on the job. Display only. Expand the job scheme to display its job scheme analytes.

    • Scheme row—Version Number

      The version number of the scheme on the sample.

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

      Not displayed on the grid by default but can be added via showing individual grid items.

    • Scheme row—Subcontract Laboratory's Org Code

      The code of the organisation associated with the Subcontract Laboratory Code.

      Hidden on the grid by default, but added by showing individual grid items.

    • Scheme row—Description

      The description of the scheme. Display only.

    • Scheme row—Invoiceable

      The default setting for an invoice sample scheme'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'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 setting 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—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—QC Mask Code

      The QC mask used when appending or overwriting QC samples for a job. 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, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.

      During the append/overwrite QC sample process, all sample schemes associated with a job scheme are divided into groups based on this QC mask, and the QC mask is then applied to that group of samples for the sob scheme.

      If the scheme's Scheme Type is Sample Preparation, then the selected QC mask cannot contain any QC mask members that have an Analytical Type of Replicate since these types of QC samples only pertain to the analytical process.

      If the 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.

    • 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—Include in Job QC

      Indicates whether the sample scheme is included in an update or overwrite QC process. Defaults to checked. Note that a job scheme's Include in Job QC defaults to the inverse of the scheme version's Batch Across Jobs flag, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.

      For a sample to be included in an update QC process on a job scheme, the job scheme's Included in Job QC must be selected and the sample scheme's Include in Job QC must be selected. Note that a sample scheme's Include in Job QC check box is cleared by the system once the sample scheme is included in a update QC process.

      For a sample to be included in an overwrite QC process on a job scheme, the job scheme's Included in Job QC must be selected and the job's Workflow Status must be Registered or Not Started. In this process, existing QC samples are deleted, and the sample scheme's Include in Job QC check boxes are all re-checked, then the same process as update QC runs.

    • Scheme row—Section Code

      The code of the section associated with the scheme.

    • Scheme row—Instrument Group Code

      The code of the instrument group associated with the scheme.

    • 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 samples in the multi-update, 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, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope 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.

    • Analyte row—Add to All

      Indicates whether to add the analyte to all samples in the multiple sample update.

    • Analyte row—Analyte Name

      The name of the analyte. Display only.

    • Analyte row—Analyte Code

      The code of the analyte on the job scheme. Display only.

    • 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—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, 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—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, below which, there is no confidence in a value. 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, above which, there is no confidence in a value, so needs 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—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—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 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.

      A report request sample scheme analyte's Report Unit Code is the unit the reportable result is presented in for the report.

      • 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 results for the sample scheme analytes.

      • SVA.reportLowerDL * --> SSA.reportLowerDL

        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 results for the sample scheme analytes.

      • SVA.reportUpperDL * --> SSA.reportUpperDL

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

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

      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—Mandatory Profile

      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.

Biofields Tab

The biofields associated with the sample.

  • Grid flows

    • Lookup CCBFLD—Search for biofields.

  • Add to All

    Indicates whether to add the biofield to all samples in the multiple sample update.

  • Biofield Code

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

  • Biofield Name

    The name of the biofield.

  • Description

    The description of the biofield.

  • Biofield Value

    The value of the sample biofield.

  • Reportable

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