TRV-2026-1237Certified recordPeer-reviewed

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

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…

Health · Good Space — documented gain · certified 2026-10-01 · v1 · article view · machine-readable

Current reading — gain

VoxelMorph achieved comparable deformable registration accuracy to clinical algorithms on thoracic 4D-CT, reaching 0.98 median lung Dice and 36.83 HU median MAE with shorter processing times in the evaluated implementation.

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.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1237, v1: “Comparative evaluation of VoxelMorpand conventional deformable image registration algorithms for thoracic 4D-CT in radiotherapy.” Truvace, 2026-10-01. /record/TRV-2026-1237 (accessed at citation time). sha256 8976fe971dc267d3…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv18976fe971dc2…

    Certified into the record

Verify this record
How to verify without trusting this page

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