<< Click to Display Table of Contents >> Navigation: DQM > DQM Checks > Surrogate Recovery Check
|
The DQM Check for Surrogate Recovery will qualify results if surrogate recoveries fall outside Quality Control (QC) limits. The functionality for the Surrogate Recovery check is applicable for both non-deuterated surrogate compounds and deuterated monitoring compound (DMC). For all surrogate compounds, the CAS_RN must be populated in RT_ANALYTE.
Notes: •Samples are considered duplicate samples if the Sample Type ends with a 'D' •The QC_SPIKE_RECOVERY column or both of the QC_SPIKE_ADDED and QC_SPIKE_MEASURED columns must be populated in DT_RESULT_QC for this check to function. •If the sample is a duplicate sample, then DQM will look first in QC_DUP_SPIKE_RECOVERY (or QC_DUP_SPIKE_ADDED and QC_DUP_SPIKE_MEASURED). If those columns do not contain data, then QC_SPIKE_RECOVERY (or QC_SPIKE_ADDED and QC_SPIKE_MEASURED) are checked. •For duplicate samples, QC_DUP_SPIKE_RECOVERY can be substituted for all references to QC_SPIKE_RECOVERY below. •Control limits for this check are determined as described in the RT_DQM_CONTROL_LIMITS section of this page. |
Check name is EarthSoft.DQM.SurrogateRecovery = Surrogate Recovery.
This check uses three Global Parameters:
1.reportable_result – DT_RESULT.REPORTABLE_RESULT values to include in DQM datasets
2.result_type_code – DT_RESULT.RESULT_TYPE_CODE to include in DQM datasets
3.test_type_batch – AT_TEST_BATCH_ASSIGN.TEST_BATCH_TYPE to include in DQM dataset
Four parameters are available for this check. None of these parameters allow for input of analyte-specific PARAM_VALUEs. The secondSurrogate parameter requires the input of an analytical method (and only one). None of the other three parameters allow the input of an analytical method, including the parameter assoc_acid_base_yn used for surrogate associations. For more information about the use of the assoc_acid_base_yn parameter, refer to the Associations section below.
1.result_type_code_surrogate – Defaults to “SUR”.
2.secondSurrogate – If “Y”, then a second surrogate must fail a rule with the same direction of bias (e.g. REC > UCL and/or REC < UPPER_CUTOFF) before Associated Results are qualified; depends on ANALYTIC_METHOD. Defaults to “N” if no parameter is found in DQM Settings for the analytic method of the surrogate in question.
3.asso_acid_base_yn – Defaults to "N" if not found. The DQM Starter QAPP EDD has this parameter set to "Y". For some surrogates, such as acid and base surrogates for analytic method SW8270, a more specific list of Associated Results is desired. To accommodate this scenario, any DQM_QAPP_CODE where the associations are defined in RT_DQM_CONTROL_LIMITS can be selected from the Surrogate Assocation QAPP section of the Start Event Form. DQM now allows users the option of defining the associations under any DQM_QAPP_CODE so that the numerous records do not need to be repeated for each DQM QAPP and so that the user can create variations from the default, reserved QAPP_CODE (QAPP_SURR_ASSO_CAS_RN). If the new Surrogate Recovery check parameter asso_acid_base_yn = 'Y' and the RT_DQM_CONTROL_LIMITS table contains at least one record for the DQM_QAPP_CODE selected on the Start Event Form with SURR_ASSO_CAS_RN equal to the surrogate with a recovery outside of control limits, then only those CAS_RNs will be associated with the failing surrogate.
To create a surrogate-specific list of CAS_RNs to associate, enter the following for each analyte to be associated.
•DQM_QAPP_CODE = a valid DQM_QAPP_CODE or the reserved QAPP_CODE 'QAPP_SURR_ASSO_CAS_RN'
•MATRIX_CODE = This column is required as part of the primary key for this table, but the MATRIX_CODE is not used to match Associated Results from this list.
•ANALYTIC_METHOD = This column is required as part of the primary key for this table, but the ANALYTIC_METHOD is not used to match Associated Results from this list.
•RESULT_TYPE_CODE = 'TRG'. This column is required as part of the primary key for this table, but the RESULT_TYPE_CODE is not used to match Associated Results from this list.
•CAS_RN = the CAS_RN of analyte to be associated
•SURR_ASSO_CAS_RN = the CAS_RN of the surrogate
4.Dilution_factor_control_limit – Control limit for comparison of each result’s dilution factor. Results with a dilution factor over the control limit will not be evaluated. Defaults to 5.
Notes: Default parameter values listed above refer to the value provided in the DQM Starter QAPP.xlsx. |
Rule # |
Rule Description |
Result Types |
DQM_RULE |
---|---|---|---|
1 |
% Recovery > Upper Control Limit (UCL) |
Surrogate Results |
REC > UCL |
2 |
Associated Results with Detection |
ASSO. DETECTS OF REC > UCL |
|
3 |
Associated Non-Detect Results |
ASSO. NDS OF REC > UCL |
|
4 |
Lower Control Limit (LCL) > % Recovery > = Low_Cutoff |
Surrogate Results |
LCL > REC > LOW_CUTOFF |
5 |
Associated Results with Detection |
ASSO. DETECTS OF LCL > REC > LOW_CUTOFF |
|
6 |
Associated Non-Detect Results |
ASSO. NDS OF LCL > REC > LOW_CUTOFF |
|
7 |
% Recovery < Low_Cutoff |
Surrogate Results |
REC < LOW_CUTOFF |
8 |
Associated Results with Detection |
ASSO. DETECTS OF REC < LOW_CUTOFF |
|
9 |
Associated Non-Detect Results |
ASSO. NDS OF REC < LOW_CUTOFF |
|
10 |
% Recovery > Upper_Cutoff |
Surrogate Results |
REC > UPPER_CUTOFF |
11 |
Associated Results with Detection |
ASSO. DETECTS OF REC > UPPER_CUTOFF |
|
12 |
Associated Non-Detect Results |
ASSO. NDS OF REC >UPPER_CUTOFF |
Note: The RT_DQM_CONTROL_LIMITS.METHOD_ANALYTE_GROUP_CODE must be null or it must be a dataset selection on the Start Event Form. |
Where table is not indicated, it is DT_RESULT_QC. RT_DQM_CONTROL_LIMITS is discussed in more detail here.
•If QC_SPIKE_RECOVERY is Numeric,
othen surrRecovery = QC_SPIKE_RECOVERY
oelse surrRecovery = 100 * QC_SPIKE_MEASURED / QC_SPIKE_ADDED
•If RT_DQM_CONTROL_LIMITS.SURR_REC_LOWER_CUTOFF is Numeric,
othen surr_lco = RT_DQM_CONTROL_LIMITS.SURR_REC_LOWER_CUTOFF
oelse if RT_HOLDING_TIME.LOWER_SURROGATE_CUTOFF is Numeric,
▪then surr_lco = RT_HOLDING_TIME.LOWER_SURROGATE_CUTOFF
▪else surr_lco = 0.00
•If RT_DQM_CONTROL_LIMITS.SURR_RECOVERY_LCL is Numeric,
othen surr_lcl = RT_DQM_CONTROL_LIMITS.SURR_RECOVERY_LCL
oelse surr_lcl = QC_SPIKE_LCL
•If RT_DQM_CONTROL_LIMITS.SURR_RECOVERY_UCL is Numeric,
othen surr_ucl = RT_DQM_CONTROL_LIMITS.SURR_RECOVERY_UCL
oelse surr_ucl = QC_SPIKE_UCL
•If RT_DQM_CONTROL_LIMITS.SURR_REC_UPPER_CUTOFF is Numeric,
othen surr_uco = RT_DQM_CONTROL_LIMITS.SURR_REC_UPPER_CUTOFF
oelse surr_uco = 999.99
•Different qualifiers may be specified for those associated results with a detected concentration, and for those without (i.e. non-detect).
•If secondSurrogate = “Y”, then a second surrogate must fail the same rule with the same direction of bias (e.g. REC > UCL and/or REC > UPPER_CUTOFF) before Associated Results are qualified; depends on ANALYTIC_METHOD -- defaults to “N” if no parameter is found in DQM Settings for the analytic method of the surrogate in question. When any one surrogate exceeds the lower OR upper cutoffs, the check will behave as if secondsurrogate = "N".
•If asso_acid_base_yn = 'N', associated results are found using DT_TEST.TEST_ID and ANALYTIC_METHOD.
•If asso_acid_base_yn = 'Y', associated results are found using DT_TEST.TEST_ID, ANALYTIC_METHOD and RT_DQM_CONTROL_LIMITS is searched for records with SURR_ASSO_CAS_RN= cas_rn value of the surrogate and the DQM_QAPP_CODE(s) = QAPP(s) selected on the Start Event Form.
oIf a match is found in RT_DQM_CONTROL_LIMITS, then only those associated analytes matching the surrogates' DT_TEST.TEST_ID and ANALYTIC_METHOD are qualified.
oIf a match is not found, then all analytes matching the surrogates' TEST_ID and ANALYTIC_METHOD are qualified.
•If surrRecovery > surr_upper_cutoff, then qualify spike result and any associated results.
•If surr_upper_cutoff > = surrRecovery > surr_ucl, then qualify spike result and any associated results.
•If surr_lco = < surrRecovery < surr_lcl, then qualify spike result and any associated results.
•If surrRecovery < surr_lco, then qualify spike result and any associated results.
•If the associated result reason code in rt_dqm_rule.reason_code ends with a "+" then the spike result's reason code will be appended to the associated result's reason code using an underscore.
•If the associated result's rt_dqm_rule.reason_code = "+" the parent spike result's reason code will be used instead
An example remark saved to DT_RESULT_DQM_REMARK for an exception is:
•"Surrogate Recovery data in DT_RESULT_QC is NOT Numeric or is NULL."
Where table is not indicated, the table is DT_RESULT_QC.
•If QC_SPIKE_RECOVERY, QC_SPIKE_ADDED, and QC_SPIKE_MEASURED are all NULL or Not Numeric, then add error and skip result.
•If QC_SPIKE_RECOVERY is NULL or Not Numeric, and either QC_SPIKE_ADDED or QC_SPIKE_MEASURED are also NULL or Not Numeric, then add error and skip result.
•If the Lower Control Limit or the Upper Control Limit is NULL or Not Numeric in both RT_DQM_CONTROL_LIMITS and DT_RESULT_QC, then add error and skip result.
•If the Surrogate Recovery Lower Cutoff is NULL or Not Numeric in both RT_DQM_CONTROL_LIMITS and RT_HOLDING_TIME, then add warning and process result using zero for the lower cutoff value.
•If the Surrogate Recovery Upper Cutoff is NULL or Not Numeric in RT_DQM_CONTROL_LIMITS, then process result using 999.99 for the upper cutoff value.
•If the dilution factor of a test exceeds the dilution_factor_control_limit, then skip the result.
•"One of the required rules for this check is not present in the RT_DQM_RULE table."
If you receive this error, the QAPP can be updated following the How to Update Existing QAPPs documentation page.
•“The lower_surrogate_cutoff is not provided in either RT_DQM_CONTROL_LIMITS or RT_HOLDING_TIME.
The check will be processed using a value of ZERO. “Surrogate Recovery data in DT_RESULT_QC is NOT Numeric or is NULL.”
•"Surrogate Recovery data in DT_RESULT_QC is NOT Numeric or is NULL."
•"Surrogate Recovery {FIELDNAME} is missing or not numeric."
•“This check was skipped for TEST_ID = '2622720' because the Dilution Factor (10) exceeded the Dilution Factor Control Limit (5)”
Copyright © 2024 EarthSoft, Inc. • Modified: 03 Mar 2024