56/100

Moderate evidence

GainPublished recordHealthGood Space

Comparative evaluation of VoxelMorpand conventional deformable image registration algorithms for thoracic 4D-CT in radiotherapy

Truvace record
TRV-2026-1237raw data (JSON)
Version
v2Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
47db6eb8dae0…check it

Background Deformable image registration (DIR) is essential for thoracic four-dimensional computed tomography (4D-CT)-based radiotherapy applications. Recently, deep learning-based DIR methods such as VoxelMorph have been proposed; however, their performance relative to clinically used DIR algorithms remains unclear. Purpose This study aimed to evaluate the DIR accuracy of VoxelMorph for thoracic 4D-CT and to compare it with conventional clinical and research-oriented DIR methods. Materials and methods Thoracic…

The gain

On 10 test lung cancer patients, VoxelMorph cut median CT-value error from 67.56 to 36.83 HU, close to ANACONDA (36.18) and Demons (37.39), with a median lung overlap of 0.98 and shorter processing time.

What this doesn’t fix

Findings are limited to a small test set of 10 cases from a single retrospective cohort of 64 patients and to the specific implementation conditions, requiring further validation under standardized conditions before routine clinical use.

Sources

1 on file
  1. Peer-reviewed2026-10-01

Cite this record

v2

Truvace Impact Record TRV-2026-1237, v2: “Comparative evaluation of VoxelMorpand conventional deformable image registration algorithms for thoracic 4D-CT in radiotherapy.” Truvace, 2026-11-04. /record/TRV-2026-1237 (accessed on the day you copy it). sha256 47db6eb8dae04fec…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv247db6eb8dae0…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Publishedv18976fe971dc2…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1237 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.