TRV-2026-1962Version 1 · Certified

Written 2026-10-20 01:10:20 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1962
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-20T01:10:20.534010Z
status: published
lens: g_space
sector: health
headline: Machine learning uncovers previously undetectable genetic deletions in cancer panel sequencing
dek: Missed genetic deletions can prevent cancer patients from receiving effective targeted therapy. Standard pipelines, such as TSO500, use bin count averaging for copy number variation detection but often overlook focal events. To address this, we developed a machine learning (ML) pipeline for deletion detection and zygosity evaluation within the MASTERsg precision oncology program. We focused on the tumor suppressor gene PTEN, whose loss confers sensitivity to mTOR/Akt inhibition. An Extreme Gradient Boosting mode…
gain_title: An XGBoost model flagged focal PTEN deletions in 33 of 204 profiled tumors that TSO500 had called wild-type, and most stainable cases tested showed reduced or absent PTEN protein.
problem_title: (none)
trace_subject: (none)
gain_reading: An XGBoost model flagged focal PTEN deletions in 33 of 204 profiled tumors that TSO500 had called wild-type, and most stainable cases tested showed reduced or absent PTEN protein.
gain_evidence: the model detected PTEN deletions in 33/204 profiled samples that were classified as PTEN wild-type by TSO500 | 75% (15/20) of stainable cases showed absent or reduced PTEN protein expression
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers in the MASTERsg precision oncology program built a machine learning pipeline to detect focal gene deletions and assess zygosity in cancer panel sequencing data. They trained an Extreme Gradient Boosting model on PTEN-deleted and wild-type tumor samples, then compared its calls with the TSO500 pipeline and CNVkit.

The work matters because PTEN loss can make tumors sensitive to mTOR/Akt inhibition, so missed deletions may mean patients are not considered for effective targeted therapy. The evidence is limited to PTEN and a modest set of samples, so broader performance and clinical benefit remain unproven.
limitation: Protein validation was possible only in 20 stainable cases out of 33 newly detected deletions, and the work centres on a single gene, PTEN.
tag: Evidence-backed gain
key_points: Standard TSO500 copy number detection relies on bin count averaging, which can overlook focal events. | The model was trained on PTEN-deleted and wild-type tumor samples and targeted the PTEN tumor suppressor gene. | It identified focal deletions missed by both TSO500 and CNVkit. | It found PTEN deletions in 33 of 204 profiled samples that TSO500 had classified as wild-type. | Among 20 stainable cases, 15 (75%) showed absent or reduced PTEN protein by immunohistochemistry.
rundown: The study starts from a diagnostic gap: panel sequencing pipelines that average read counts across bins can miss small, focal deletions. Missing such a deletion in a tumor suppressor gene can keep patients from being matched to targeted therapy.

The team developed the pipeline within the MASTERsg precision oncology program and concentrated on PTEN, whose loss is linked to sensitivity to mTOR/Akt inhibition. The classifier output also covers zygosity evaluation, not just presence or absence of a deletion.

Validation used immunohistochemistry as an orthogonal check. Deletions the model called that TSO500 and CNVkit missed were associated with concordant PTEN protein loss, and 15 of 20 stainable cases among the newly detected deletions showed absent or reduced expression.
sources:
- peer_reviewed | npj Precision Oncology | https://doi.org/10.1038/s41698-026-01756-9 | 2026-10-16
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
56d5e65486bdd5dca6077dc1585d1301019445df9f893ea6dd45467161c86677
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1962 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.