Flows:

• Close—Close this form.
• Save—Save form updates.
• Save as—Save the current entity as a new entity.
• Delete—Delete the current entity.
• User screen—Open the custom form contained in the SchemeAnalyteUser.SCR screen file, if it exists, to enter custom details for the scheme analyte.

Form:

• From MLB code—The code of the originating scheme analyte from the master library.
• Short name—A descriptive short name for the scheme analyte.
• Analyte name—The name of the scheme analyte.
• Userdefined name—The custom, or local, name of the scheme analyte.
• Description—The description of the scheme analyte.
• Analyte type—The type of analyte. Either:
  • DAT—Date data type.
  • NUM—Numeric data type.
  • OLE—Object Linking & Embedding data type, typically a document or image file.
  • STR—String data type.
• Analysis unit code—The code of the unit in which results for the analyte are stored.
• Analysis detection limit—The lowest limit at which the analyte is detectable using this scheme.
• Analysis upper limit—The highest limit at which the analyte is detectable using this scheme. Set to 0 to indicate no upper limit.
• Limiting repeatability—The anticipated precision for repeat and duplicate samples, expressed in a percentage. This is automatically set to 10% for a new analyte, and is typically adjusted after analytical performance is evaluated. This precision should be a future that is much greater than the Analysis detection limit.
• Statistical detection limit—The statistical detection limit used in analysing quality, and used in conjunction with the Limiting repeatability to describe precision limits closer to the Analysis detection limit. Results of blank samples must be less than this value for the analysis to pass quality control evaluation. The statistical detection limit is normally set to the same value as the Analysis detection limit, and is typically adjusted after analytical performance is evaluated.
• Upper scheme—The code of the alternate scheme to use where the analyte measures higher than the Analysis upper limit. The code of the upper scheme is displayed on reports where the analytical value is higher than the Reporting upper limit. To indicate that no upper scheme test is to performed, leave Upper scheme blank, or set Upper scheme to the current scheme code.
• Upper analyte—The code of the analyte within the alternate scheme to use where the analyte measures higher than the Analysis upper limit. The code of the upper analyte is displayed on reports where the analytical value is higher than the Reporting upper limit.
• Formula—The formula used to calculate the value for the analyte. The formula is entered without a leading equals sign (=). Note that the {Scheme}.{Analyte} syntax should always be used in formulas to ensure that a situation does not arise where just using {Analyte} causes confusion with column names in tables. Also, if formulas are used for analytes that are loaded into an inverted spreadsheet in the Data Entry module, then it is mandatory that the formula be written with the {Scheme} component as well.
• fx—Test the formula.
• QC active?—Indicates whether the results of the analyte are subjected to quality control assessment:
  • If enabled, then the quality control check on this analyte must pass before a sample's result is released for reporting. That is, results require validation before they are reported. Validation does not mean that results are passed; results are just accepted as a true result.

  • If disabled, then results do not require validation, or to pass quality control checks, before they are reported.

• Status active?—Indicates whether the completion of the analyte contributes towards completion of the scheme, and ultimately, the sample:
  • If enabled, then completion is required for the analyte for the sample to ultimately become completed.
  • If disabled, then the status of the analyte has no impact upon sample completion.
• Reporting active?—Indicates whether the analyte is included in a reportable result set.
• Invoicing active?—Indicates whether line items for invoices are calculated using the analyte.
• Valid items—A lookup list used to validate result entry, activated by clicking the F6 button from a cell in the Data Entry spreadsheet.
• Reporting unit code—The code of the unit in which results for the analyte are reported.
• Rounding table code—The code of the rounding table used to round reportable results for the analyte.
• Reporting detection limit—The lowest limit at which it is reported that the analyte is detectable using this scheme. This value can be the same as the Analysis detection limit, but set to a higher value to exclude those values closer to the Analysis detection limit which would otherwise be reported.
• Reporting upper limit—The highest limit at which it is reported that the analyte is detectable using this scheme. Set to 0 to indicate no upper limit.
• Formatting mask—The formatting mask used to display a result in a reportable result set.
• Column width—The width of the data column for the analyte on the spreadsheet in the Data Entry application.
• Sequence—The sequence in which the analyte is registered when added to a job scheme.
• Rep sequence—The sequence in which the analyte is included in a reportable result set.
• MDE Formatting mask—The formatting mask used to display a result for the analyte in the Data Entry application.
• Price code—Only relevant for schemes with a Price type of ANA (Analytical).
• Lower limit 1, Lower limit 2, Upper limit 1, Upper limit 2—Analytical limits for the analyte in the scheme:
  • Where Lower limit 1 and Lower limit 2 are both numerical, and the result of the analyte is lower than Lower limit 2, then the result fails quality control.
  • Where Lower limit 1 is numerical and Lower limit 2 is a string, and the result of the analyte is lower than Lower limit 1, then the result fails quality control.
  • Where Lower limit 1 and Lower limit 2 are both strings, then neither limit is used to check the analysis.

  • Where Upper limit 1 and Upper limit 2 are both numerical, and the result of the analyte is higher than Upper limit 2, then the result fails quality control.

  • Where Upper limit 1 is numerical and Upper limit 2 is a string, and the result of the analyte is higher than Upper limit 1, then the result fails quality control.
  • Where Upper limit 1 and Upper limit 2 are both strings, then neither limit is used to check the analysis.