mass-spectrometry-qc-criteria-definition
Summary
Define quantitative quality control criteria for LC-MS runs by specifying acceptance thresholds for internal standard detection, peak intensity, retention time windows, and mass accuracy. This skill enables automated and user-defined QC checks to flag failing samples during or after data acquisition.
When to use
When setting up a new LC-MS QC workflow or modifying existing QC rules: you have access to internal standards and target analytes, know their expected retention times and m/z values, and need to establish pass/fail boundaries for sample acceptance before or concurrent with instrument runs.
When NOT to use
- Input data are already QC-passed or curated; criteria definition is not needed for validation of known-good samples.
- No internal standards or reference compounds are available for the LC-MS method; criteria cannot be anchored to reliable calibration points.
- The analysis requires post-hoc statistical filtering (e.g., sample abundance filtering or outlier detection) rather than instrument-level acceptance thresholds.
Inputs
- Processed LC-MS data (mzML or vendor format .raw files)
- Internal standard compound identifiers and expected m/z values
- Target analyte m/z values or compound lists
- QC configuration file specifying retention time windows, m/z tolerances, and intensity thresholds
Outputs
- QC report with per-sample pass/fail status
- Flagged QC violations (retention time drift, mass accuracy deviation, intensity out of range)
- Diagnostic metrics (detected m/z, observed retention time, peak intensity per sample)
- Optional: Slack or email notifications for QC failures
How to apply
Load processed LC-MS data (mzML or vendor format via MSConvert) and define QC criteria as configuration parameters: (1) specify retention time windows for internal standards and target analytes; (2) set m/z tolerances (ppm) for mass accuracy; (3) establish intensity thresholds for peak detection and internal standard presence; (4) optionally configure custom user-defined rules beyond automated checks. During QC execution, the system verifies each sample against these thresholds: internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance. Aggregate results assign binary pass/fail status per sample.
Related tools
Evaluation signals
- QC criteria are measurable and reproducible: retention time windows ±tolerance, m/z tolerance in ppm, intensity threshold in absolute or relative units.
- All samples in the QC report have binary pass/fail assignment; no samples lack a status.
- Flagged violations are traceable to specific criteria boundaries (e.g., 'internal standard m/z 447.2 not detected within ±5 ppm' or 'retention time 8.2 min outside window 7.9–8.1 min').
- Pass/fail status correlates with downstream data utility: samples marked fail show known problems (e.g., drift, contamination, instrument malfunction) and would benefit from re-analysis or exclusion.
- User-defined custom rules in configuration file are applied consistently across the sample batch without omission or conflict.
Limitations
- Criteria definition requires a priori knowledge of internal standard m/z, retention time, and expected intensity range; criteria cannot be derived de novo from data alone.
- Rapid QC-MS has been tested extensively on Thermo Fisher mass spectrometers and Thermo .raw files; behavior on Agilent, Bruker, Sciex, or Waters formats may include bugs or unsupported workflows.
- Criteria are method-specific and instrument-specific; transfer between different LC-MS instruments, columns, or mobile phases requires re-validation and possible threshold adjustment.
- QC checks operate on peak-level and compound-level metrics; they do not detect all sources of run failure (e.g., gradient malfunction, detector saturation, or systematic bias in untargeted detection).
Evidence
- [other] Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes.: "Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes."
- [other] Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance.: "Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance."
- [readme] Automated and user-defined quality control checks during instrument runs: "Automated and user-defined quality control checks during instrument runs"
- [readme] Because MSConvert converts raw acquired data into open mzML format before routing it to the data processing pipeline: "Because MSConvert converts raw acquired data into open mzML format before routing it to the data processing pipeline"
- [readme] Rapid QC-MS has only been tested extensively on Thermo Fisher mass spectrometers, Thermo acquisition sequences, and Thermo RAW files. As such, it is expected that there may be bugs and issues with processing data of other vendor formats.: "Rapid QC-MS has only been tested extensively on Thermo Fisher mass spectrometers, Thermo acquisition sequences, and Thermo RAW files. As such, it is expected that there may be bugs and issues with"
1---2name: mass-spectrometry-qc-criteria-definition3description: Use when when setting up a new LC-MS QC workflow or modifying existing QC rules: you have access to internal standards and target analytes, know their expected retention times and m/z values, and need to establish pass/fail boundaries for sample acceptance before or concurrent with instrument runs.4license: CC-BY-4.05---67# mass-spectrometry-qc-criteria-definition89## Summary1011Define quantitative quality control criteria for LC-MS runs by specifying acceptance thresholds for internal standard detection, peak intensity, retention time windows, and mass accuracy. This skill enables automated and user-defined QC checks to flag failing samples during or after data acquisition.1213## When to use1415When setting up a new LC-MS QC workflow or modifying existing QC rules: you have access to internal standards and target analytes, know their expected retention times and m/z values, and need to establish pass/fail boundaries for sample acceptance before or concurrent with instrument runs.1617## When NOT to use1819- Input data are already QC-passed or curated; criteria definition is not needed for validation of known-good samples.20- No internal standards or reference compounds are available for the LC-MS method; criteria cannot be anchored to reliable calibration points.21- The analysis requires post-hoc statistical filtering (e.g., sample abundance filtering or outlier detection) rather than instrument-level acceptance thresholds.2223## Inputs2425- Processed LC-MS data (mzML or vendor format .raw files)26- Internal standard compound identifiers and expected m/z values27- Target analyte m/z values or compound lists28- QC configuration file specifying retention time windows, m/z tolerances, and intensity thresholds2930## Outputs3132- QC report with per-sample pass/fail status33- Flagged QC violations (retention time drift, mass accuracy deviation, intensity out of range)34- Diagnostic metrics (detected m/z, observed retention time, peak intensity per sample)35- Optional: Slack or email notifications for QC failures3637## How to apply3839Load processed LC-MS data (mzML or vendor format via MSConvert) and define QC criteria as configuration parameters: (1) specify retention time windows for internal standards and target analytes; (2) set m/z tolerances (ppm) for mass accuracy; (3) establish intensity thresholds for peak detection and internal standard presence; (4) optionally configure custom user-defined rules beyond automated checks. During QC execution, the system verifies each sample against these thresholds: internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance. Aggregate results assign binary pass/fail status per sample.4041## Related tools4243- **MSConvert** (Converts vendor-format LC-MS raw data (e.g., Thermo .raw) to standardized mzML format for QC criteria evaluation) — https://proteowizard.sourceforge.io/tools/msconvert.html44- **MS-DIAL** (Performs data processing and peak identification prior to QC criteria application) — http://prime.psc.riken.jp/compms/msdial/main.html45- **Rapid QC-MS** (Orchestrates QC criteria definition, automated/user-defined checks, and real-time reporting against LC-MS runs) — https://github.com/czbiohub-sf/Rapid-QC-MS4647## Evaluation signals4849- QC criteria are measurable and reproducible: retention time windows ±tolerance, m/z tolerance in ppm, intensity threshold in absolute or relative units.50- All samples in the QC report have binary pass/fail assignment; no samples lack a status.51- Flagged violations are traceable to specific criteria boundaries (e.g., 'internal standard m/z 447.2 not detected within ±5 ppm' or 'retention time 8.2 min outside window 7.9–8.1 min').52- Pass/fail status correlates with downstream data utility: samples marked fail show known problems (e.g., drift, contamination, instrument malfunction) and would benefit from re-analysis or exclusion.53- User-defined custom rules in configuration file are applied consistently across the sample batch without omission or conflict.5455## Limitations5657- Criteria definition requires a priori knowledge of internal standard m/z, retention time, and expected intensity range; criteria cannot be derived de novo from data alone.58- Rapid QC-MS has been tested extensively on Thermo Fisher mass spectrometers and Thermo .raw files; behavior on Agilent, Bruker, Sciex, or Waters formats may include bugs or unsupported workflows.59- Criteria are method-specific and instrument-specific; transfer between different LC-MS instruments, columns, or mobile phases requires re-validation and possible threshold adjustment.60- QC checks operate on peak-level and compound-level metrics; they do not detect all sources of run failure (e.g., gradient malfunction, detector saturation, or systematic bias in untargeted detection).6162## Evidence6364- [other] Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes.: "Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes."65- [other] Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance.: "Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance."66- [readme] Automated and user-defined quality control checks during instrument runs: "Automated and user-defined quality control checks during instrument runs"67- [readme] Because MSConvert converts raw acquired data into open mzML format before routing it to the data processing pipeline: "Because MSConvert converts raw acquired data into open mzML format before routing it to the data processing pipeline"68- [readme] Rapid QC-MS has only been tested extensively on Thermo Fisher mass spectrometers, Thermo acquisition sequences, and Thermo RAW files. As such, it is expected that there may be bugs and issues with processing data of other vendor formats.: "Rapid QC-MS has only been tested extensively on Thermo Fisher mass spectrometers, Thermo acquisition sequences, and Thermo RAW files. As such, it is expected that there may be bugs and issues with"
HolobiomicsLab