CancerSignalOriginGateChecker

Cancer Signal Origin Gate

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

Utility description: Cancer Signal Origin Gate

Cancer Signal Origin Gate Checker — Tissue of Origin (TOO) Prediction Validation

ℹ️  Utility performs automatic validation of tissue of origin classification results in Multi-Cancer Early Detection (MCED) tests according to FDA SaMD and CAP requirements:
     • Confidence Threshold: Comparison of prediction probability with validated minimum threshold.
     • Supporting Features: Verification of sufficient molecular evidence (methylation, fragmentation).
     • Discrimination: Assessment of gap between first and second most likely tissues.
     • Model Version: Guarantee of using only validated ML classifier version.

⚠️  IMPORTANT: 
     • False-positive TOO determination leads to unnecessary invasive diagnostic procedures.
     • Low-confidence results must be accompanied by appropriate caveat in report.

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

Input format:
SampleID,PredictedTissue,ProbabilityScore,ConfidenceThreshold,SecondBestTissue,SecondBestScore,SupportingFeaturesCount,MinSupportingFeatures,ClassifierVersion,ValidatedClassifierVersion,SignalDetected

Example:
  MCED-001,Lung,0.92,0.7,Thyroid,0.05,45,10,v3.2.1,v3.2.1,true

📍 Scope of Application (Usage Where):
     • MCED Screening: Filtering results before issuance to patient/physician.
     • Clinical Trials: Stratification of participants by prediction confidence.
     • Regulatory Reporting: Documentation of classifier performance.
     • ML Quality Control: Monitoring model drift in production.

— WHY IS THIS NEEDED?
TOO classifiers are probabilistic models, not deterministic tests.
Without strict gating, low-confidence predictions may be mistakenly interpreted as diagnosis.
Automated gate ensures balance between detection sensitivity and localization specificity.

⚠️  CRITICAL:
• Confidence Threshold: Must be set based on validation data (PPV/NPV).
• Margin: Small gap between top-1 and top-2 indicates signal ambiguity.
• Features: Insufficient supporting features make prediction statistically unreliable.
• Version Control: Use of unvalidated model version is unacceptable in clinic.

Key features:
• Multi-factor prediction confidence assessment
• Automatic filtering of no-cancer-signal results
• ML model version compliance check
• Discrimination margin calculation
• Structured physician report generation

Critical parameters:
• Probability Score: ≥ Confidence Threshold
• Supporting Features: ≥ Min Limit
• Margin (Top1 - Top2): > 0.1
• Classifier Version: Exact match with validated

💡 Usage tips:
1. Threshold Calibration: Adjust Confidence Threshold to clinical context (screening vs diagnostics).
2. Explainability: Retain list of supporting features for potential audit.
3. Drift Monitoring: Regularly compare score distribution with validation cohort.
4. Communication: Clearly articulate confidence level in clinical report.
5. Revalidation: Recalculate thresholds upon model update.

⚠️ Note: This utility is an ML prediction validation tool. It does not replace clinical correlation with history and imaging but ensures statistical reliability of automated conclusion.

input.csv

SampleID,PredictedTissue,ProbabilityScore,ConfidenceThreshold,SecondBestTissue,SecondBestScore,SupportingFeaturesCount,MinSupportingFeatures,ClassifierVersion,ValidatedClassifierVersion,SignalDetected
MCED-2026-001,Lung,0.92,0.7,Thyroid,0.05,45,10,v3.2.1,v3.2.1,true
MCED-2026-002,Colon,0.65,0.7,Rectum,0.58,8,10,v3.2.1,v3.2.1,true
MCED-2026-003,None,0.02,0.7,None,0.01,0,10,v3.2.1,v3.2.1,false
MCED-2026-004,Liver,0.85,0.7,Pancreas,0.12,32,10,v3.2.0,v3.2.1,true

URS & FS — User Requirements and Functional Specification

This document describes the controlled interface and behaviour of CancerSignalOriginGateChecker for Cancer Signal Origin Gate 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.
  • • Confidence Threshold: Comparison of prediction probability with validated minimum threshold.
  • • Low-confidence results must be accompanied by appropriate caveat in report.
  • ⚠️ CRITICAL:
  • • Confidence Threshold: Must be set based on validation data (PPV/NPV).
  • Critical parameters:
  • • Probability Score: ≥ Confidence Threshold
  • • Supporting Features: ≥ Min Limit
  • • Margin (Top1 - Top2): > 0.1

URS — User Requirements Specification

IDRequirementCriticalityAcceptance criterion
URS-001The utility shall accept an input.csv file for Cancer Signal Origin Gate 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 vocabularyMCED-2026-001Sample or laboratory specimen identifier.
2PredictedTissuestring / controlled vocabularyLungControlled input parameter for deterministic QC rules.
3ProbabilityScoredecimal0.92Controlled input parameter for deterministic QC rules.
4ConfidenceThresholdstring / controlled vocabulary0.7Controlled input parameter for deterministic QC rules.
5SecondBestTissuestring / controlled vocabularyThyroidControlled input parameter for deterministic QC rules.
6SecondBestScoredecimal0.05Controlled input parameter for deterministic QC rules.
7SupportingFeaturesCountinteger / decimal45Count parameter used for microbiological, particulate or cellular control.
8MinSupportingFeaturesdecimal10Controlled input parameter for deterministic QC rules.
9ClassifierVersionstring / controlled vocabularyv3.2.1Controlled input parameter for deterministic QC rules.
10ValidatedClassifierVersionstring / controlled vocabularyv3.2.1Controlled input parameter for deterministic QC rules.
11SignalDetectedstring / controlled vocabularytrueControlled input parameter for deterministic QC rules.
SampleID,PredictedTissue,ProbabilityScore,ConfidenceThreshold,SecondBestTissue,SecondBestScore,SupportingFeaturesCount,MinSupportingFeatures,ClassifierVersion,ValidatedClassifierVersion,SignalDetected
MCED-2026-001,Lung,0.92,0.7,Thyroid,0.05,45,10,v3.2.1,v3.2.1,true
MCED-2026-002,Colon,0.65,0.7,Rectum,0.58,8,10,v3.2.1,v3.2.1,true
MCED-2026-003,None,0.02,0.7,None,0.01,0,10,v3.2.1,v3.2.1,false

Input validation rules

IDFieldRuleCriticality
VR-001SampleIDThe field shall match an approved dictionary or accepted string representation.High
VR-002PredictedTissueThe field shall match an approved dictionary or accepted string representation.High
VR-003ProbabilityScoreThe field shall match an approved dictionary or accepted string representation.High
VR-004ConfidenceThresholdThe field shall match an approved dictionary or accepted string representation.Medium
VR-005SecondBestTissueThe field shall match an approved dictionary or accepted string representation.Medium
VR-006SecondBestScoreThe field shall match an approved dictionary or accepted string representation.Medium
VR-007SupportingFeaturesCountThe field shall match an approved dictionary or accepted string representation.Medium
VR-008MinSupportingFeaturesThe field shall match an approved dictionary or accepted string representation.Medium
VR-009ClassifierVersionThe field shall match an approved dictionary or accepted string representation.Medium
VR-010ValidatedClassifierVersionThe field shall match an approved dictionary or accepted string representation.Medium
VR-011SignalDetectedThe 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 Cancer Signal Origin Gate 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": "cancersignalorigingatechecker",
  "utilityFolder": "CancerSignalOriginGateChecker",
  "package": "LiquidBiopsy",
  "overallStatus": "PASS|WARNING|FAIL",
  "sourceFile": "input.csv",
  "processedAtUtc": "2026-06-10T00:00:00Z",
  "checks": [
    {
      "parameter": "SampleID",
      "value": "MCED-2026-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-001"
    },
    {
      "parameter": "PredictedTissue",
      "value": "Lung",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-002"
    },
    {
      "parameter": "ProbabilityScore",
      "value": "0.92",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-003"
    },
    {
      "parameter": "ConfidenceThreshold",
      "value": "0.7",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-004"
    },
    {
      "parameter": "SecondBestTissue",
      "value": "Thyroid",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-005"
    },
    {
      "parameter": "SecondBestScore",
      "value": "0.05",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-006"
    },
    {
      "parameter": "SupportingFeaturesCount",
      "value": "45",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-007"
    },
    {
      "parameter": "MinSupportingFeatures",
      "value": "10",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-008"
    },
    {
      "parameter": "ClassifierVersion",
      "value": "v3.2.1",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-009"
    },
    {
      "parameter": "ValidatedClassifierVersion",
      "value": "v3.2.1",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-010"
    },
    {
      "parameter": "SignalDetected",
      "value": "true",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-011"
    }
  ],
  "criticalFindings": [],
  "warnings": [],
  "audit": {
    "inputHash": "sha256:<calculated at runtime>",
    "rulesVersion": "<utility executable version>",
    "documentation": "CancerSignalOriginGateChecker.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

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