62-160.670. Data Validation by the Department  

Effective on Monday, April 16, 2018
  • 1(1) All data generated for Department activities are subject to data verification and data validation to determine if the data are suitable and usable for a specified purpose. Data shall be verified and validated based on the assessment of the following:

    42(a) Completeness of the Department requested data package(s) and the response of involved parties to any Department requests for additional data;

    63(b) Integrity of samples as determined by complete and proper sample transmittal documentation, and records that demonstrate adherence to proper preservation, transport or other sample handling protocols, as applicable;

    92(c) Proper use of sample collection methods;

    99(d) Proper selection and use of analysis methods;

    107(e) Sufficient use and routine evaluation of quality control measures to establish the precision, accuracy, sensitivity, selectivity, and potential bias associated with the analytical system and associated results;

    135(f) Proper instrument calibration and verification procedures;

    142(g) Documentation of all generated data as provided in Rules 15262-160.240 153and 15462-160.340, 155F.A.C.;

    156(h) Ability to reconstruct all field sampling and laboratory procedures through the documentation and records of the laboratory or field sampling organization as provided in Rules 18262-160.240 183and 18462-160.340, 185F.A.C.;

    186(i) Ability to trace data in the final report to a specific sampling site, date and time;

    203(j) Status of the laboratory’s certification through the DOH ELCP as provided in Chapter 64E-1, F.A.C., for any given analyte or category of analytes; and,

    228(k) Appropriateness of the collected data as related to the specific data quality objectives of the Department program activity or project for which they were collected including those data being considered for secondary use.

    262(2) The Department will evaluate data according to the criteria in paragraphs (a) through (k), above, and determine if the data are usable.

    285(3) In addition to subsection (2), above, the Department shall also evaluate data according to the 301following:

    302(a) The 304outlined in the Department’s document “Department of Environmental Protection Process for Assessing Data Usability (DEP-EA-001/07),” dated March 31, 2008, which is incorporated by reference in Rule 33162-160.800, 332F.A.C.

    333(b) The description of data quality objectives and criteria for data usability assessments for the Stream Condition Index (SCI) or a BioRecon determination, as discussed in DEP-SAS-001/11, which is incorporated by reference in paragraph 36762-160.800(2)(e), 368F.A.C., and the Lake Vegetation Index (LVI), as discussed in DEP-SAS-002/11, which is incorporated by reference in paragraph 38662-160.800(2)(f), 387F.A.C.

    388(4) If the audited data 393were originally generated for a specific purpose but are being considered for a secondary use for another purpose (secondary use), and the Department determines from the evaluation process, as described in subsections 42562-160.670(2) 426and 42762-160.670(3), 428F.A.C., above, 430that the data do not meet the data quality objectives for the secondary use, the Department will recommend that the data not be used by the program that is considering the secondary use. The recommendation not to use secondary data does not impact the usability or validity of the data for the program for which the data were originally intended.

    490Rulemaking Authority 492403.061, 493403.0623 FS. 495Law Implemented 497373.026, 498373.309, 499373.409, 500373.413, 501373.414, 502373.416, 503373.4592, 504376.303, 505376.305, 506376.3071, 507403.0623, 508403.0625, 509403.087, 510403.088, 511403.0881, 512403.504, 513403.704, 514403.707, 515403.722, 516403.853 FS. 518History–New 1-1-91, Amended 2-4-93, 2-27-94, Formerly 17-160.670, Amended 3-24-96, 4-9-02, 12-3-08, 4-16-18.


Rulemaking Events:

Historical Versions(2)

Select effective date to view different version.