Update of QC History with the Results of a QC Sample

• Update of QC History with the Results of a QC Sample
  • Types of QC History Records Written
  • Content of a QC History Record
  • Subsequent Searching of QC History Records
  • Ignored Composite QC Statuses reflected in QC History Record

This topic explains the update of QC history with results of a QC sample.

The QC history table contains records of accuracy and precision assessments.

Types of QC History Records Written

If a scheme version analyte's Saved to QC History is selected, when a related sample scheme analyte in a lab-scope job receives a numeric result for the first time, then the outcome of any accuracy or precision assessments are written to QC history. For the same sample scheme analyte, if the Numeric Final Value, Workflow Status or Composite QC Status is updated, then those details in QC history are updated.

Note: The outcome of any accuracy or precision assessments relating to org-scope jobs are not written to QC history. QC history only contains the outcome of any accuracy or precision assessments relating to lab-scope jobs.

The following table lists the analytical type recorded in the QC history for QC samples according to the primary and secondary analytical type for the samples.

SSA's Primary Analytical Type	SSA's Secondary Analytical Type		QC history record's Analytical Type	QC history record's QC Type Code	QC history's Linked QC Type Code
Unknown	Blank		Blank	Sample Scheme Analyte's Secondary QC Type Code	<empty>
Unknown	Standard		Standard	Sample Scheme Analyte's Secondary QC Type Code	<empty>
Blank			Blank	Sample Scheme Analyte's Primary QC Type Code	<empty>
Blank	Duplicate	Causes two records to be written to QC history.	Blank	Sample Scheme Analyte Primary QC Type Code	Sample Scheme Analyte Secondary QC Type Code
Duplicate	Sample Scheme Analyte Secondary QC Type Code	<empty>
Blank	Replicate	Causes two records to be written to QC history.	Blank	Sample Scheme Analyte Primary QC Type Code	Sample Scheme Analyte Secondary QC Type Code
Replicate	Sample Scheme Analyte Secondary QC Type Code	<empty>
Standard			Standard	Sample Scheme Analyte Primary QC Type Code	Sample Scheme Analyte Secondary QC Type Code
Standard	Duplicate	Causes two records to be written to QC history.	Standard	Sample Scheme Analyte Primary QC Type Code	Sample Scheme Analyte Secondary QC Type Code
Duplicate	Sample Scheme Analyte Secondary QC Type Code	<empty>
Standard	Replicate	Causes two records to be written to QC history.	Standard	Sample Scheme Analyte Primary QC Type Code	Sample Scheme Analyte Secondary QC Type Code
Replicate
Spike			If the ALLOW_STANDARDS_AS_SPIKES application preference is defined and selected then this is set to Standard. If the ALLOW_STANDARDS_AS_SPIKES application preference is not defined, or is defined and is cleared then this is set to Spike	Sample Scheme Analyte Primary QC Type Code	<empty>
Spike	Duplicate	Causes two records to be written to QC history.	If the ALLOW_STANDARDS_AS_SPIKES application preference is defined and selected then this is set to Standard. If the ALLOW_STANDARDS_AS_SPIKES application preference is not defined, or is defined and is cleared then this is set to Spike	Sample Scheme Analyte Primary QC Type Code	Sample Scheme Analyte Secondary QC Type Code
Duplicate	Sample Scheme Analyte Secondary QC Type Code	<empty>
Spike	Replicate	Causes two records to be written to QC history.	If the ALLOW_STANDARDS_AS_SPIKES application preference is defined and selected then this is set to Standard. If the ALLOW_STANDARDS_AS_SPIKES application preference is not defined, or is defined and is cleared then this is set to Spike	Sample Scheme Analyte Primary QC Type Code	Sample Scheme Analyte Secondary QC Type Code
Replicate	Sample Scheme Analyte Secondary QC Type Code	<empty>

Content of a QC History Record

The following details can be seen in the CCQCHS—QC History Summary application for each discrete observation of an accuracy or precision assessment:

• Is Active—Check box used as a criteria to search for discrete observations.
• Analytical Type—For a precision assessment, the analytical type of the assessment, based upon whether the sample's Primary Analytical Type or Secondary Analytical Type was Duplicate or Replicate. For an accuracy assessment, the analytical type of the assessment, based upon whether the sample's Primary Analytical Type or Secondary Analytical Type was Blank, Standard or Spike.
• QC Type Code—The QC type associated with the sample.
• QC Type Name—The name of the QC type associated with the sample.
• Analysis Job Name—The name of the job in which the result was entered, that is, either the production, internal or laboratory batch job.
• Analysis Job Type—The type of job in which the result was entered, either Production, Internal or Lab Batch.
• Original Job Name—The name of the job in which the sample was originally registered, that is, the production or internal job, and may be different to the Analysis Job Name if the analysis job was a laboratory batch job. When a QC history record is written for a sample scheme analyte that receives a result in context of a production job the QC history record contains a link to only the production job. When a QC history record is written for a sample scheme analyte that receives a result in context of a laboratory batch job the QC history record contains a link to both the laboratory batch job and the related production job. If the QC sample is a duplicate or replicate QC sample from a production job, then a link is also put in to the original production sample from which the duplicate or replicate QC sample was made.
• Standard Code—The code of the standard associated with the blank, standard or spike QC history record. Applicable only where the Analytical Type is Blank, Standard or Spike.
• Standard Name—The name of the standard associated with the blank, standard or spike QC history record. Applicable only where the Analytical Type is Blank, Standard or Spike.
• Standard Description—The description of the standard associated with the blank, standard or spike QC history record. Applicable only where the Analytical Type is Blank, Standard or Spike.
• Sample Name—The name of the sample.
• Client Sample Name—The client's name for the sample.
• Sample Description—The description of the sample.
• Standard Lot Code—The code of the standard lot associated with the blank, standard or spike QC history record. Applicable only where the Analytical Type is Blank, Standard or Spike.
• Standard Lot Number—The number of the standard lot associated with the blank, standard or spike QC history record. Applicable only where the Analytical Type is Blank, Standard or Spike.
• Scheme Code—The code of the scheme associated with the QC history record.
• Scheme Name—The name of the scheme associated with the QC history record.
• Scheme Version—The version number of the scheme associated with the QC history record.
• Scheme Version Name—e name of the scheme version sample scheme analyte the QC history record.
• Analyte Code—The code of the analyte associated with the QC history record.
• Analyte Name—The name of the analyte associated with the QC history record.
• Analysed Date—The date on which the result was analysed.
• Unit Code—The code of the analysis unit associated with the QC history record.
• Unit Name—The name of the analysis unit associated with the QC history record.
• Numeric Final Value—The sample scheme analyte's Numeric Final Result. For spike QC samples, this is set to the sample scheme analyte's Numeric Final Value—spike original sample scheme analyte's Numeric Final Value.
• Internal Target Value—The analytical target result for a blank, standard or spike QC sample, determined from the specification sample scheme analyte unit's Internal Target Value, for the sample's standard lot.
• Recovery—The recovery determined for a blank, standard or spike QC sample.
• Parent Numeric Final Value—The original sample scheme analyte's Numeric Final Value, only applicable for a duplicate or replicate QC sample.
• RPD—The relative percentage difference between the duplicate or replicate's result and the original sample's result, only applicable for a duplicate or replicate QC sample.
• QC Status—The composite QC status from the sample scheme analyte.
• User Code—The code of the user who analysed the result.
• User Name—The name of the user who analysed the result.
• Instrument Code—The code of the instrument associated with the sample scheme analyte reading.

Note: When results are captured from instruments, the system preserves the value of the instrument code found in the lower panel of Workbook under the Instrument Code column even if those results are later re-entered or recalculated. This value is also stored in CCQCHS - Update QC History Summary under the Instrument Code column. The instrument code retention can be disabled via Workbook Script. If disabled, then any new results will not be linked to the original Instrument Code.

• Instrument Name—The name of the instrument associated with the sample scheme analyte reading.
• Application—The name of the application in which the result was entered.
• Client Code—The code of the original production or internal job's client.
• Client Name—The name of the original production or internal job's client.
• Project Code—The code of the original production or internal job's project.
• Project Name—The name of the original production or internal job's project.
• Notes—Additional notes that are entered for the QC history record.

Subsequent Searching of QC History Records

When searching for QC history records in the CCQCHS—QC History Summary application, an aggregation of records by a common analytical type, QC type, standard, standard lot, scheme, scheme version, analyte and unit is displayed:

• Count (# Observations)—The number of observations recorded so far for the QC type.
• Target—The target value for the reading.
• Mean / Mean Abs Diff—The mean (or average), or mean absolute difference calculated for the result of the QC assessment.
• Bias / Mean Abs % Diff—The bias value calculated on the result of the QC assessment, or mean absolute difference calculated as a percentage for the result of the QC assessment.
• Std Dev / Std Dev Abs % Diff—The standard deviation calculated on the result of the QC assessment, or standard deviation absolute difference calculated as a percentage for the result of the QC assessment. This value provides an indication of the amount of variation in the observed result against the specification associated with the QC sample.
• RSD—The relative standard deviation calculated on the result of the QC assessment. The resulting value is calculated as a ratio of the standard deviation to the mean for the QC assessment result.
• Min / Min Abs % Diff—The minimum value detected in the QC assessment result, or minimum absolute difference calculated as a percentage for the result of the QC assessment.
• Max / Max Abs % Diff—The maximum value detected in the QC assessment result, or maximum absolute difference calculated as a percentage for the result of the QC assessment.

Ignored Composite QC Statuses reflected in QC History Record

When writing or updating a QC history's Standard Status and the sample scheme analyte's Composite QC Status is Ignore Failure and Standard Status is Failure, then the QC history's Standard Status is written to indicate both the ignore and the standard status, as follows:

• If a sample scheme analyte's Composite QC Status is Ignore Failure and Standard Status is Lower Failure, then the QC history's Standard Status is written as Ignore Lower Failure.
• If a sample scheme analyte's Composite QC Status is Ignore Failure and Standard Status is Upper Failure, then the QC history's Standard Status is written as Ignore Upper Failure.
• If a sample scheme analyte's Composite QC Status is Ignore Failure and Standard Status is Lower Warning, then the QC history's Standard Status is written as Lower Warning.
• If a sample scheme analyte's Composite QC Status is Ignore Failure and Standard Status is Upper Warning, then the QC history's Standard Status is written as Upper Warning.
• If a sample scheme analyte's Composite QC Status is Ignore Failure and Standard Status is Pass, then the QC history's Standard Status is written as Pass.

When writing or updating the QC history's Precision Status and the sample scheme analyte's Composite QC Status is Ignore Failure and Precision Status is Failure, then the QC history's Precision Status is written to indicate both the ignore and the precision status, as follows:

• If a sample scheme analyte's Composite QC Status is Ignore Failure and Precision Status is Failure, then the QC history's Precision Status is written as Ignore Failure.
• If a sample scheme analyte's Composite QC Status is Ignore Failure and Precision Status is Warning, then the QC history's Precision Status is written as Warning.
• If a sample scheme analyte's Composite QC Status is Ignore Failure and Precision Status is Pass, then the QC history's Precision Status is written as Pass.