TRV-2026-1513Version 1 · Certified

Written 2026-10-16 01:09:10 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1513
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-16T01:09:10.869039Z
status: published
lens: g_space
sector: health
headline: A hybrid deep learning framework for automated treatment planning in cervical cancer radiotherapy
dek: Background Radiation therapy treatment planning is a time-consuming trial-and-error process, and the plan quality is heavily dependent on planners' experiences, resulting in a strong demand for automated planning methods that can rapidly generate uniformly high-quality plans. Purpose This study aimed to develop a hybrid automated deep learning-based plan optimization (HALO) framework, integrating deep learning fluence prediction and optimization, multileaf collimator (MLC) sequencing, and GPU-accelerated Monte C…
gain_title: In 20 test patients, a hybrid deep learning planning system produced deliverable cervical cancer IMRT plans within 3 minutes while lowering dose to the bladder and small intestine.
problem_title: (none)
trace_subject: (none)
gain_reading: In 20 test patients, a hybrid deep learning planning system produced deliverable cervical cancer IMRT plans within 3 minutes while lowering dose to the bladder and small intestine.
gain_evidence: the entire treatment planning time was within 3 minutes
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built HALO, a framework that predicts fluence maps from patient CT anatomy with a neural network, refines them against dose-volume constraints, converts them into deliverable MLC segments, and computes dose with a GPU-accelerated Monte Carlo engine.

The work matters because manual radiotherapy planning is slow and depends on planner experience, so a fast automated tool could make plan quality more uniform. The evidence comes from a small retrospective set of 120 plans, so wider clinical performance is still untested.
limitation: The framework was developed and evaluated on only 120 plans, with just 20 patients in the test set, and the authors claim clinical feasibility rather than demonstrated patient outcomes.
tag: Evidence-backed gain
key_points: The network was trained on 90 of 120 clinical cervical cancer IMRT plans, with 10 used for validation and 20 for testing. | Fluence prediction reached a median mean absolute error of 0.055 and a structural similarity index of 0.94. | Fluence optimization time fell by an average of 82.6% when deep learning prediction was used. | Bladder V50Gy and small intestine V35Gy decreased while target homogeneity and conformity were preserved. | Patient-specific IMRT quality assurance gave a mean gamma passing rate of 97.37 ± 1.01% under the 2%/2 mm criterion.
rundown: The authors describe radiation treatment planning as a time-consuming trial-and-error process whose quality depends heavily on planner experience, which motivated an automated approach that can generate uniformly high-quality plans.

The pipeline has several modules: a dose-guided Fluence Prediction Network that takes CT anatomy and predicts 3D dose distribution and fluence maps, an optimization step to meet dose-volume constraints, MLC sequencing into deliverable segments, and Monte Carlo dose calculation.

On the 20 test patients, organ-at-risk doses dropped, with small intestine V35Gy decreasing from 31.5 ± 8.2% to 29.2 ± 7.5% (p = 0.024). The authors conclude the framework is clinically feasible and could serve as a stand-alone planning platform.
sources:
- peer_reviewed | Journal of Applied Clinical Medical Physics | https://doi.org/10.1002/acm2.70806 | 2026-10-01
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
59a7637c7a125bb5771eb149587718448e011aa8f6a7f51315b719a81d602005
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1513 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.