Reviewing Discrete QC History Observations
When a row from the summary QC history grid is opened, the form inherits the search criteria from the QC History Summary screen, and displays the associated detailed QC history observations, that is, the individual readings of a QC sample and the related assessment outcome.
Additional searches are applied to either filter the current data on display, or to load other detailed QC history observations. Depending upon the selected grouping of data, various columns are populated or left empty, as follows:
|
Detail grid search criteria |
Application of search criteria to return detailed QC history records |
|---|---|
|
(Firstly) Group by: Analytical Type and QC Type |
Where the summary grid search criteria's (firstly) Group by is:
|
|
(Firstly) Group by: Analytical Type only |
A filter and grouping is applied by Primary Analyte Type, any filter in QC Type Code is ignored, and the QC Type Code and QC Type Name columns are left empty. |
|
(Secondly) Group by: Standard and Lot |
Where the summary grid search criteria's (secondly) Group by is:
|
|
(Secondly) Group by: Standard only |
A filter and grouping applies by Standard Code, any filter in the Standard Lot Code is ignored, the Standard Lot Code and Standard Lot Number columns are left empty, and specification code associated with the standard's Current Standard Lot displays in the Specification Code column. |
|
(Thirdly) Group by: Scheme and Version |
Where the summary grid search criteria's (thirdly) Group by is:
|
|
(Thirdly) Group by: Scheme only |
A filter and grouping applies by Scheme Code, any filter in Scheme Version is ignored, and the maximum scheme version from the data that matches the detailed QC history search criteria displays in the Scheme Version column. Note that this is the scheme version used to set chart limits. |
|
Primary Analytical Type |
Inherited from the selected row on the summary grid. |
|
QC Type Code |
Inherited from the selected row on the summary grid. |
|
Standard Code |
Inherited from the selected row on the summary grid. |
|
Standard Lot Code |
Inherited from the selected row on the summary grid. |
|
Specification Code |
Inherited from the selected row on the summary grid. |
|
Scheme Code |
Inherited from the selected row on the summary grid. |
|
Analyte Code |
Inherited from the selected row on the summary grid. |
|
Unit Code |
Inherited from the selected row on the summary grid. |
|
QC Status |
Inherited from the summary grid search criteria. |
|
Status |
Inherited from the summary grid search criteria. |
|
Instrument Code |
Inherited from the summary grid search criteria. |
|
User Code |
Inherited from the summary grid search criteria. |
|
Analysed Date |
Inherited from the summary grid search criteria |
The search criteria can be saved and named for future recall and re-use, or scheduled on a regular basis using a scheduled script (refer to the QC History API).
Reports can be produced based on the discrete QC history observations returned to the grid. QC history reporting can be extended with scripting, for example, to include charts. Refer to the QC History API.
Charts can be produced on the discrete contamination, accuracy or precision observations for a selected QC type. All search criteria on the QC History Detail screen is passed into the service to extract the data for the chart, so that, the records extracted for a chart matches the data on the data grid. For example, where a Client Code and Project Code selection criteria is provided in the QC History Detail search, when records are extracted for charting, then the chart's data also matches the Client Code and Project Code search criteria.
Note: Client Code and Project Code search criteria is applied to production jobs where the QC samples were analysed in context of the production jobs, or analysed in context of a laboratory batch jobs with links back to the originating production jobs.
Discrete contamination, accuracy or precision observations are made active or inactive for inclusion in reports and charts.
Returning Blank or standard QC Samples from a Filtered Search where a Laboratory Batch Job is Involved
Where the Client Code, Client Name, Project Code or Client Group Code search parameter is populated on the CCQCHS—Search QC History Summary screen, and there are blank or standard QC samples that match the other search criteria, and the blank or standard QC samples were registered directly in a laboratory batch job (with a laboratory batch job client, or client and project, that may or may not match the search criteria client, or client and project), and the laboratory batch job has at least one sample whose associated production sample is linked to the search criteria client, then the matching blank or standard QC sample is included in the search results.
Example: Given that the following samples exist:
a) By creating two production jobs for different clients, and running an Append QC process on each:
|
Job1—Client_A |
Job2—Client_B |
|---|---|
|
UNK1 |
UNK2 |
|
REP |
STD3 |
|
DUP |
BLK4 |
|
STD1 |
UNK3 |
|
BLK2 |
UNK4 |
b) By creating laboratory batch job LB1 from both Job1 and Job2, excluding UNK4 from Job2, and using QC samples from both production jobs:
|
LB1—INTERNAL |
|
UNK1 |
|
REP |
|
DUP |
|
STD1 |
|
BLK2 |
|
UNK2 |
|
STD3 |
|
BLK4 |
|
UNK3 |
c) By creating laboratory batch job LB2 from Job2, including only UNK4, and creating QC samples within the laboratory batch job:
|
LB2—INTERNAL |
|
UNK4 |
|
STD5 |
|
BLK6 |
When a QC history summary search is made for client code "Client_B", then the search results includes:
|
STD3 |
|
BLK4 |
|
STD5 |
|
BLK6 |
Returning Duplicate, Replicate or spike QC Samples from a Filtered Search where a Laboratory Batch Job is Involved
Where the Client Code, Client Name, Project Code or Client Group Code search parameter is populated on the CCQCHS—Search QC History Summary screen, and there are duplicate, replicate or spike QC samples that match the other search criteria, and the duplicate, replicate or spike QC sample were registered directly in a laboratory batch job (with a laboratory batch job client, or client and project, that may or may not match the search criteria client, or client and project), and the associated production sample for the duplicate, replicate or spike QC sample is linked to the search criteria client, then the matching duplicate, replicate or spike QC sample is included in the search results.
Activity Status of Detailed QC History Observations
Each detailed QC history observation has an activity status which is used only as a search criteria when searching for discrete observations, which affects the data used for charting.
Note: When a sample is deleted, then any QC history sample/s related to the deleted sample are retained but set to inactive, so they can still form part of the historical assessment of the laboratory's quality performance.
This does not apply when a sample scheme, sample scheme analyte or result is deleted. In these cases the QC history record remains unchanged.
- Reviewing Summarised QC History Observations
- Reviewing QC History for Instrument QC Samples
- Generating Statistical Charts from QC History Observations
- Assessing Results against Accuracy Limits
- Assessing Results against Precision Limits
- Maintaining QC Types and Assessments
- Maintaining Schemes
- Maintaining Versions of a Scheme
- Maintaining Scheme Version Analytes
- Maintaining QC Standards
- Maintaining Standard Lots for a QC Standard
- Maintaining Specifications for Standard Use
- Maintaining Analytical Limits for a Specification for Standard Use
- Ignoring a Composite QC Failure in a Workbook Session
- Applying a Custom QC Status in a Workbook Session
- Viewing QC History for a Blank, Standard or Spike in a Workbook Session
