cas_rn - The unique identifier of the analyte being measured. chemical_name - The name of the analyte being measured. result_type_code - Must be either "TRG" for a target or regular result, "TIC" for tentatively identified compounds, "SUR" for surrogates, "IS" for internal standards, or "SC" for spiked compounds. reportable_result - Must be either "Yes" for results which are considered to be reportable, or "No" for other results. This field has many purposes. For example, it can be used to distinguish between multiple results where a sample is retested after dilution. It can also be used to indicate which of the first or second column result should be considered primary. The proper value of this field in both of these two examples should be provided by the laboratory (only one result should be flagged as reportable). - May be detect_flag either "Y" for detected analytes or "N" for non_detects or "TR" for trace. Use "Y" for estimated values (above detection limit but below the quantitation limit). validated_yn - Y" if the result has been validated, "N" if not. - The unique lab_sdg identifier of the sample delivery (SDG) or work order. A single sample may be assigned to multiple SDGs based on different analysis. Contains data that relate the individual samples to their Whenever MTDEQ requires the fields listed laboratory sample batch identifiers and laboratory sample analytical below be populated: Data Provider’s Batch_v1 delivery groups. The fields in this section need to match the data are sys_sample_code - The Analytical Laboratory data entered in corresponding fields in the TestResultQC_v1 collected unique identifier of the section and sample.
cas_rn - The unique identifier of the analyte being measured. chemical_name - The name of the analyte being measured. result_type_code - Must be either "TRG" for a target or regular result, "TIC" for tentatively identified compounds, "SUR" for surrogates, "IS" for internal standards, or "SC" for spiked compounds. reportable_result - Must be either "Yes" for results which are considered to be reportable, or "No" for other results. This field has many purposes. For example, it can be used to distinguish between multiple results where a sample is retested after dilution. It can also be used to indicate which of the first or second column result should be considered primary. The proper value of this field in both of these two examples should be provided by the laboratory (only one result should be flagged as reportable). detect_flag - May be either "Y" for detected analytes or "N" for non_detects or "TR" for trace. Use "Y" for estimated values (above detection limit but below the quantitation limit). validated_yn - Y" if the result has been validated, "N" if not. lab_sdg - The unique identifier of the sample delivery (SDG) or work order. A single sample may be assigned to multiple SDGs based on different analysis. Batch_v1 Contains data that relate the individual samples to their laboratory sample batch identifiers and laboratory sample delivery groups. The fields in this section need to match the data entered in corresponding fields in the TestResultQC_v1 section Data Provider’s Analytical Laboratory Whenever analytical data are collected and MTDEQ requires the fields listed below be populated: sys_sample_code - The unique identifier of the sample.