ImmuneRepertoireMrdQcChecker

Immune Repertoire MRD QC

Liquid Biopsy жидкостная биопсия cfDNA ctDNA CTC exosomes NGS qPCR
Open selection

Utility description: Immune Repertoire MRD QC

Immune Repertoire MRD QC Checker — Immune Repertoire MRD Data Quality Control

ℹ️  Utility performs comprehensive quality verification of TCR/BCR-seq data for MRD monitoring according to EuroClonality-NGS, AIRR Community and NGS-MRD guidelines:
     • Sequencing Depth & UMI: Total depth and unique molecule count — foundation of MRD sensitivity.
     • PCR Duplication Control: Deduplication rate as library complexity indicator.
     • Background Noise: Noise frequency in negative controls — determines detection limit.
     • Replicate Reproducibility: Correlation between technical replicates — reliability measure.
     • Sensitivity Verification: Comparison of achieved sensitivity with protocol-required level.
     • MRD Call Reliability: Minimum read count for reliable MRD positivity call.

⚠️  IMPORTANT: 
     • MRD-negative result with insufficient sensitivity = FALSE REMISSION.
     • MRD-positive call with <10 reads = likely FALSE POSITIVE.
     • High background noise (>10⁻⁵) makes reliable MRD determination at 10⁻⁶ impossible.
     • Absence of internal sensitivity control prevents assay performance verification.

Usage:
  ImmuneRepertoireMrdQcChecker.exe                            → demo mode (console output)
  ImmuneRepertoireMrdQcChecker.exe input.csv output.json      → evaluate your data

Input format:
SampleID,PatientID,ReceptorType,Timepoint,TotalReads,MinTotalReads,UniqueMolecules_UMI,MinUniqueMolecules,UMI_Deduplication_Rate,MaxUMI_DedupRate,BackgroundNoise_Frequency,MaxBackgroundNoise,ClonotypeCount_PostDedup,ReplicateCorrelation_R,MinReplicateCorrelation,ControlClonotype_Detected,Sensitivity_Achieved,RequiredSensitivity,MRD_Positive,MRD_CloneFrequency,MRD_CloneReads,MinMRD_CloneReads

Example:
  MRD-001,PAT-001,IGH,Post-ind,5200000,1000000,480000,100000,0.65,0.80,2E-6,1E-5,35000,0.96,0.90,true,5E-6,1E-5,false,0,0,10

📍 Scope of Application (Usage Where):
     • Hematologic Oncology: MRD monitoring in ALL, CLL, multiple myeloma.
     • Clinical Trials: MRD data standardization in multi-center trials.
     • Regulatory Submissions: Confirmation of NGS-MRD assay analytical validity.
     • Transplant Medicine: Allo-HSCT efficacy assessment by clonotype dynamics.

— WHY IS THIS NEEDED?
MRD status is the strongest prognostic factor in hematology.
False-negative MRD leads to premature therapy cessation and relapse.
False-positive MRD leads to unnecessary toxic consolidation.
Automated QC guarantees that every MRD result is based on sufficient quality data.

⚠️  CRITICAL:
• Total Reads ≥ 1M: Baseline threshold for MRD at 10⁻⁵ level.
• Unique Molecules ≥ 100K: Determines real sensitivity after deduplication.
• Background Noise ≤ 10⁻⁵: Exceedance makes MRD calls unreliable.
• Sensitivity Achieved ≤ Required: MANDATORY for MRD-negative conclusions.
• MRD Clone Reads ≥ 10: Below this threshold, positive call is unreliable.
• Control Clonotype: Absence = unverifiable assay performance.

Key features:
• Eight-parameter MRD QC assessment
• Integration of physical and statistical metrics
• Automatic MRD call reliability verification
• PASS / WARNING / FAIL classification
• Compliance with EuroClonality-NGS and AIRR standards

Critical parameters:
• Total Reads: ≥ 1,000,000
• Unique Molecules: ≥ 100,000
• UMI Dedup Rate: ≤ 80%
• Background Noise: ≤ 1×10⁻⁵
• Replicate Correlation: ≥ 0.90
• Sensitivity Achieved: ≤ Required
• MRD Clone Reads: ≥ 10 (if positive)
• Control Clonotype: Detected

💡 Usage tips:
1. UMI Design: Use UMI length ≥8 nt to minimize collisions at high depth.
2. NTC Controls: Include minimum 3 NTCs per plate for accurate background estimation.
3. Spike-in Controls: Add known clonotypes for sensitivity verification.
4. Replicates: Perform minimum 2 technical replicates for each MRD sample.
5. Thresholds: Adjust MinMRD_CloneReads per panel-specific depth and noise level.

⚠️ Note: This utility assesses TECHNICAL QUALITY of MRD data. Clinical interpretation of MRD status must consider disease type, treatment phase, and prior dynamics. The utility does not replace hematologist expertise.

input.csv

SampleID,PatientID,ReceptorType,Timepoint,TotalReads,MinTotalReads,UniqueMolecules_UMI,MinUniqueMolecules,UMI_Deduplication_Rate,MaxUMI_DedupRate,BackgroundNoise_Frequency,MaxBackgroundNoise,ClonotypeCount_PostDedup,ReplicateCorrelation_R,MinReplicateCorrelation,ControlClonotype_Detected,Sensitivity_Achieved,RequiredSensitivity,MRD_Positive,MRD_CloneFrequency,MRD_CloneReads,MinMRD_CloneReads
MRD-2026-001,ALL-PAT-001,IGH,Post-induction,5200000,1000000,480000,100000,0.65,0.80,2E-6,1E-5,35000,0.96,0.90,true,5E-6,1E-5,false,0,0,10
MRD-2026-002,ALL-PAT-002,TRB,Follow-up,350000,1000000,42000,100000,0.88,0.80,5E-5,1E-5,8500,0.72,0.90,false,2E-4,1E-5,true,3E-5,5,10
MRD-2026-003,MM-PAT-003,IGK,Post-ASCT,2800000,1000000,250000,100000,0.70,0.80,8E-6,1E-5,28000,0.93,0.90,false,8E-6,1E-5,false,0,0,10

URS & FS — User Requirements and Functional Specification

This document describes the controlled interface and behaviour of ImmuneRepertoireMrdQcChecker for Immune Repertoire MRD QC Checker.

Domain limits and critical parameters

Key fragments from the source description are shown below. Before production use, limits must be verified against the approved specification, registration dossier and local SOPs.
  • • Background Noise: Noise frequency in negative controls — determines detection limit.
  • • Sensitivity Verification: Comparison of achieved sensitivity with protocol-required level.
  • • MRD-positive call with <10 reads = likely FALSE POSITIVE.
  • • High background noise (>10⁻⁵) makes reliable MRD determination at 10⁻⁶ impossible.
  • ⚠️ CRITICAL:
  • • Total Reads ≥ 1M: Baseline threshold for MRD at 10⁻⁵ level.
  • • Unique Molecules ≥ 100K: Determines real sensitivity after deduplication.
  • • Background Noise ≤ 10⁻⁵: Exceedance makes MRD calls unreliable.
  • • Sensitivity Achieved ≤ Required: MANDATORY for MRD-negative conclusions.
  • • MRD Clone Reads ≥ 10: Below this threshold, positive call is unreliable.
  • Critical parameters:
  • • Total Reads: ≥ 1,000,000
  • • Unique Molecules: ≥ 100,000
  • • UMI Dedup Rate: ≤ 80%
  • • Background Noise: ≤ 1×10⁻⁵
  • • Replicate Correlation: ≥ 0.90
  • • Sensitivity Achieved: ≤ Required
  • • MRD Clone Reads: ≥ 10 (if positive)

URS — User Requirements Specification

IDRequirementCriticalityAcceptance criterion
URS-001The utility shall accept an input.csv file for Immune Repertoire MRD QC Checker with headers defined in the data contract.HighThe file is processed without manual header editing.
URS-002The utility shall perform deterministic QC evaluation without machine learning and without probabilistic conformance decisions.HighIdentical input data, rule version and configuration produce reproducible results.
URS-003The utility shall validate mandatory fields, data types, ranges, units and domain plausibility.HighSchema, conversion and range errors are explicitly reported.
URS-004The utility shall apply domain limits and rules from the description, approved specification, registration dossier and local SOPs.HighEach check has PASS/WARNING/FAIL and a clear message.
URS-005The utility shall generate output.json with machine-readable results, source values, warnings, failures and critical findings.HighJSON is suitable for LIMS/ELN/MES integration and QA/QC review.
URS-006The utility shall preserve traceability between batch/sample, input file, applied rules and final status.HighOutput contains identifiers, checked parameters and audit metadata.
URS-007The documentation shall support IQ/OQ/PQ, CSV/CSA and review by internal QA or inspectors.MediumURS, FS, input/output contract and test scenarios are supplied with the utility.
URS-008The utility shall be used as a QC decision-support tool and not as a substitute for approved specifications and QA/QP release decision.MediumDocumentation states change control and limit-verification expectations.

input.csv contract

#FieldTypeSamplePurpose
1SampleIDstring / controlled vocabularyMRD-2026-001Sample or laboratory specimen identifier.
2PatientIDstring / controlled vocabularyALL-PAT-001Controlled input parameter for deterministic QC rules.
3ReceptorTypestring / controlled vocabularyIGHControlled input parameter for deterministic QC rules.
4Timepointstring / controlled vocabularyPost-inductionTime parameter for process, incubation, storage or analytical workflow.
5TotalReadsdecimal5200000Controlled input parameter for deterministic QC rules.
6MinTotalReadsdecimal1000000Controlled input parameter for deterministic QC rules.
7UniqueMolecules_UMIdecimal480000Controlled input parameter for deterministic QC rules.
8MinUniqueMoleculesdecimal100000Controlled input parameter for deterministic QC rules.
9UMI_Deduplication_Ratedecimal0.65Controlled input parameter for deterministic QC rules.
10MaxUMI_DedupRatedecimal0.80Controlled input parameter for deterministic QC rules.
11BackgroundNoise_Frequencydecimal2E-6Controlled input parameter for deterministic QC rules.
12MaxBackgroundNoisedecimal1E-5Controlled input parameter for deterministic QC rules.
13ClonotypeCount_PostDedupinteger / decimal35000Count parameter used for microbiological, particulate or cellular control.
14ReplicateCorrelation_Rdecimal0.96Controlled input parameter for deterministic QC rules.
15MinReplicateCorrelationinteger / decimal0.90Controlled input parameter for deterministic QC rules.
16ControlClonotype_Detectedstring / controlled vocabularytrueControl point/control sample for assay run validity.
17Sensitivity_Achieveddecimal5E-6Controlled input parameter for deterministic QC rules.
18RequiredSensitivitydecimal1E-5Controlled input parameter for deterministic QC rules.
19MRD_Positivestring / controlled vocabularyfalseControlled input parameter for deterministic QC rules.
20MRD_CloneFrequencydecimal0Controlled input parameter for deterministic QC rules.
21MRD_CloneReadsdecimal0Controlled input parameter for deterministic QC rules.
22MinMRD_CloneReadsdecimal10Controlled input parameter for deterministic QC rules.
SampleID,PatientID,ReceptorType,Timepoint,TotalReads,MinTotalReads,UniqueMolecules_UMI,MinUniqueMolecules,UMI_Deduplication_Rate,MaxUMI_DedupRate,BackgroundNoise_Frequency,MaxBackgroundNoise,ClonotypeCount_PostDedup,ReplicateCorrelation_R,MinReplicateCorrelation,ControlClonotype_Detected,Sensitivity_Achieved,RequiredSensitivity,MRD_Positive,MRD_CloneFrequency,MRD_CloneReads,MinMRD_CloneReads
MRD-2026-001,ALL-PAT-001,IGH,Post-induction,5200000,1000000,480000,100000,0.65,0.80,2E-6,1E-5,35000,0.96,0.90,true,5E-6,1E-5,false,0,0,10
MRD-2026-002,ALL-PAT-002,TRB,Follow-up,350000,1000000,42000,100000,0.88,0.80,5E-5,1E-5,8500,0.72,0.90,false,2E-4,1E-5,true,3E-5,5,10
MRD-2026-003,MM-PAT-003,IGK,Post-ASCT,2800000,1000000,250000,100000,0.70,0.80,8E-6,1E-5,28000,0.93,0.90,false,8E-6,1E-5,false,0,0,10

Input validation rules

IDFieldRuleCriticality
VR-001SampleIDThe field shall match an approved dictionary or accepted string representation.High
VR-002PatientIDThe field shall match an approved dictionary or accepted string representation.High
VR-003ReceptorTypeThe field shall match an approved dictionary or accepted string representation.High
VR-004TimepointThe field shall match an approved dictionary or accepted string representation.Medium
VR-005TotalReadsThe field shall match an approved dictionary or accepted string representation.Medium
VR-006MinTotalReadsThe field shall match an approved dictionary or accepted string representation.Medium
VR-007UniqueMolecules_UMIThe field shall match an approved dictionary or accepted string representation.Medium
VR-008MinUniqueMoleculesThe field shall match an approved dictionary or accepted string representation.Medium
VR-009UMI_Deduplication_RateThe field shall match an approved dictionary or accepted string representation.Medium
VR-010MaxUMI_DedupRateThe field shall match an approved dictionary or accepted string representation.Medium
VR-011BackgroundNoise_FrequencyThe field shall match an approved dictionary or accepted string representation.Medium
VR-012MaxBackgroundNoiseThe field shall match an approved dictionary or accepted string representation.Medium
VR-013ClonotypeCount_PostDedupThe field shall match an approved dictionary or accepted string representation.Medium
VR-014ReplicateCorrelation_RThe field shall match an approved dictionary or accepted string representation.Medium
VR-015MinReplicateCorrelationThe field shall match an approved dictionary or accepted string representation.Medium
VR-016ControlClonotype_DetectedThe field shall match an approved dictionary or accepted string representation.Medium
VR-017Sensitivity_AchievedThe field shall match an approved dictionary or accepted string representation.Medium
VR-018RequiredSensitivityThe field shall match an approved dictionary or accepted string representation.Medium
VR-019MRD_PositiveThe field shall match an approved dictionary or accepted string representation.Medium
VR-020MRD_CloneFrequencyThe field shall match an approved dictionary or accepted string representation.Medium
VR-021MRD_CloneReadsThe field shall match an approved dictionary or accepted string representation.Medium
VR-022MinMRD_CloneReadsThe field shall match an approved dictionary or accepted string representation.Medium

FS — Functional Specification

IDFunctionImplementation
FS-001CLI executionSupport execution modes: demo mode without arguments and production mode input.csv output.json.
FS-002CSV importRead input.csv in UTF-8/CSV-compatible format and validate header and expected columns.
FS-003Schema validationCheck mandatory fields, column count, unknown key fields and empty mandatory values.
FS-004Type conversionConvert numeric, flag and text values; invalid format is recorded as a row-level error.
FS-005Domain rule engineApply rules for Immune Repertoire MRD QC Checker, including critical limits from the description and approved specification.
FS-006Status aggregationProduce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance.
FS-007JSON exportWrite output.json with detailed checks, source values, warnings, failures and critical findings.
FS-008Audit supportKeep result structure suitable for review, deviation investigation and calculation reproduction.
FS-009Integration contractSupport the scenario LIMS/ELN/MES → input.csv → utility → output.json → portal/admin review.
FS-010Error handlingReturn explicit messages for missing file, empty CSV, invalid schema, output write failure and invalid format.

Example output.json

{
  "utilityId": "immunerepertoiremrdqcchecker",
  "utilityFolder": "ImmuneRepertoireMrdQcChecker",
  "package": "LiquidBiopsy",
  "overallStatus": "PASS|WARNING|FAIL",
  "sourceFile": "input.csv",
  "processedAtUtc": "2026-06-10T00:00:00Z",
  "checks": [
    {
      "parameter": "SampleID",
      "value": "MRD-2026-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-001"
    },
    {
      "parameter": "PatientID",
      "value": "ALL-PAT-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-002"
    },
    {
      "parameter": "ReceptorType",
      "value": "IGH",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-003"
    },
    {
      "parameter": "Timepoint",
      "value": "Post-induction",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-004"
    },
    {
      "parameter": "TotalReads",
      "value": "5200000",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-005"
    },
    {
      "parameter": "MinTotalReads",
      "value": "1000000",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-006"
    },
    {
      "parameter": "UniqueMolecules_UMI",
      "value": "480000",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-007"
    },
    {
      "parameter": "MinUniqueMolecules",
      "value": "100000",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-008"
    },
    {
      "parameter": "UMI_Deduplication_Rate",
      "value": "0.65",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-009"
    },
    {
      "parameter": "MaxUMI_DedupRate",
      "value": "0.80",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-010"
    },
    {
      "parameter": "BackgroundNoise_Frequency",
      "value": "2E-6",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-011"
    },
    {
      "parameter": "MaxBackgroundNoise",
      "value": "1E-5",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-012"
    }
  ],
  "criticalFindings": [],
  "warnings": [],
  "audit": {
    "inputHash": "sha256:<calculated at runtime>",
    "rulesVersion": "<utility executable version>",
    "documentation": "ImmuneRepertoireMrdQcChecker.documentation.html"
  }
}

Traceability matrix

URSFSTestEvidence
URS-001FS-001, FS-002OQ-001Verify execution and import of valid input.csv.
URS-002FS-005, FS-006OQ-004Repeat the same dataset and compare output.json.
URS-003FS-003, FS-004, FS-010OQ-002, OQ-003Verify missing columns and invalid types.
URS-004FS-005, FS-006OQ-004, PQ-001Verify critical deviations on real/boundary data.
URS-005FS-007, FS-009OQ-005Verify JSON schema and downstream-system suitability.
URS-006FS-008OQ-006Verify identifiers and audit metadata.
URS-007FS-008, FS-010IQ-001, OQ-007Verify documentation completeness and control evidence.
URS-008FS-005, FS-008PQ-002Verify review workflow and no replacement of QA decision.

IQ/OQ/PQ test scenarios

IDScenarioExpected result
IQ-001Verify executable, input.csv, documentation and checksum availability.Delivery set is complete; version is recorded.
OQ-001Valid sample row from input.csv.PASS or acceptable WARNING according to rules.
OQ-002Remove a mandatory CSV column.Schema error or FAIL with missing-column reference.
OQ-003Place a non-numeric value into a numeric field.Type-conversion error with row/field reference.
OQ-004Set a critical parameter outside the limit.FAIL and critical finding.
OQ-005Verify output.json structure.All mandatory sections are present and JSON is valid.
OQ-006Verify batch/sample traceability.Input and result identifiers match.
PQ-001Verify 3–5 real user batches/samples.Result is confirmed by QC/QA review.
PQ-002Verify deviation workflow and manual QA decision.Utility supports review but does not replace approved decision.

QA/QC and change control

  • Do not rename columns without updating validator, documentation and test set.
  • Retain input.csv, output.json, executable version and checksum.
  • Before production use, perform IQ/OQ/PQ or equivalent CSV/CSA verification.
  • Critical limits shall be verified against the approved specification, registration dossier and local SOPs.
  • The utility provides structured QC decision support; final release decision remains with QA/QP and approved procedures.

Included in packages

Immunology QC Suite

QC utility package for immunology: monoclonal antibodies, biosimilars, immunomodulators, immunosuppressants, ELISA/SPR, HCP, protein characterization, sterility and pyrogen/release checks.

Open

Liquid Biopsy QC Suite

QC and pre-analytical control package for liquid biopsy workflows: cfDNA/ctDNA, CTC, EV/exosomes, methylation, NGS/qPCR/ddPCR, sample quality, contamination, sensitivity and reporting checks.

Open