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 ProfJobSchemeAnalyteUser.SCR screen file, if it exists, to enter custom details for analytes in ANA (Analytical) schemes in jobs.

Form:

• Unit code—The code of the unit in which results for the analyte are stored.
• Rep sequence—
• Detection limit—The lowest limit at which the analyte is detectable using this scheme.
• Upper limit—The highest limit at which the analyte is detectable using this scheme. Set to 0 to indicate no upper limit.
• Rep unit code—The code of the unit in which results for the analyte are reported.
• Rep 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.
• Rep 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.
• Invoice active—Indicates whether line items for invoices are calculated using the analyte.
• Table code—The code of the rounding table used to round reportable results for the analyte.
• Rep active—Indicates whether the analyte is included in a reportable result set.
• 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.
• Required—The date-time at which the job scheme analyte report is due, calculated by default using the job's priority.
• Started—The date-time at which the job scheme analyte's preparation or analysis started.
• Completed—The date-time at which the job scheme analyte's preparation or analysis completed.
• First reported—The date-time at which the results of the job scheme analyte were first reported.
• Last reported—The date-time at which the results of the job scheme analyte were last reported.
• Validated—The date-time at which the results of the job scheme analyte were validated.
• Validated by—The user who validated the results of the job scheme analyte.
• Finalised—The date-time at which the results of the job scheme analyte were finalised.
• Finalised by—The user who finalised the results of the job scheme analyte.