2012-227 - Laserfiche WebLink

Home Browse Search

Table 3 TvjDical Data Qualifier Codes to be used when Reporting Microbiological Data to the DEP under the Overflow Purchase Order or Contract others may aRL311 Fier Value reported is the arithmetic mean (average) of two or more determinations. This code shall be used if the reported value is the average of results Rule for two or more discrete and separate samples. These samples shall have been processed and analyzed independently. Do not use this code if the data A are the result of replicate analysis on the same sample aliquot, extract or di estate. Contract Requirement Two or more replicates of the same volume of sample are run and the data averaged. Results based upon colony counts outside the acceptable range. This code applies to microbiological tests and specifically to membrane filter colony Rule counts . The code is to be used if the colony count is generated from a plate in which the total number of coliform colonies is outside the method indicated ideal range. This code is not to be used if a 100 mL sample has been filtered and the colony count is less than the lower value of the ideal B range . Contract Based on colony counts outside the method specified range of 20 — 60 colonies per membrane filter. This code is not required if a J00 mL sample Requirement has been run the densftv reported is below 20 and onIv this sample value was reported Estimated value. A "J" value shall be accompanied by a detailed explanation to justify the reason(s) for designating the value as estimated. Where possible, the organization shall report whether the actual value is estimated to be less than or greater than the reported value. A "J" value shall not be used as a substitute for K, L, M, T, V, or Y, however, if additional reasons exist for identifying the value as an estimate (e.g., matrix spiked failed to meet acceptance criteria), the "J" code may be added to a K, L, M, T, V, or Y. Examples of situations in which a "J" code must be reported include: Rule instances where a quality control item associated with the reported value failed to meet the established quality control criteria (the specific failure i must be identified); instances when the sample matrix interfered with the ability to make any accurate determination; instances when data are J questionable because of improper laboratory or field protocols (e.g., composite sample was collected instead of a grab sample); instances when the analyte was detected at or above the method detection limit in a blank other than the method blank (such as calibration blank or field-generated blanks and the value of 10 times the blank value was equal to or greater than the associated sample value); or instances when the field or laboratory calibrations or calibration verifications did not meet calibration acceptance criteria. Contract In addition to the above examples, other "J" code situations are: quality control duplicate failures, ongoing precision recovery (OPR) spike failures, Requirement matrix s ike allures, incubation period or tem erature allures, other QC check allures. Rule Sampled, but analysis lost or not performed. O Contract Sample taken but analysis lost, invalidated, or not performed. Requirement Sample held beyond the accepted holding time. This code shall be used if the value is derived from a sample that was prepared or analyzed after the Q Rule approved holding time restrictions for sample preparation or analysis. Revision Date: 02/09 DEP Agreement No. G0353, Attachment J, Page 13 of 14