MRI‐TRUS registration methodology for TRUS‐guided HDR prostate brachytherapy
Bibliographic record
Abstract
PURPOSE: High-dose-rate (HDR) prostate brachytherapy is an established technique for whole-gland treatment. For transrectal ultrasound (TRUS)-guided HDR prostate brachytherapy, image fusion with a magnetic resonance image (MRI) can be performed to make use of its soft-tissue contrast. The MIM treatment planning system has recently introduced image registration specifically for HDR prostate brachytherapy and has incorporated a Predictive Fusion workflow, which allows clinicians to attempt to compensate for differences in patient positioning between imaging modalities. In this study, we investigate the accuracy of the MIM algorithms for MRI-TRUS fusion, including the Predictive Fusion workflow. MATERIALS AND METHODS: A radiation oncologist contoured the prostate gland on both TRUS and MRI. Four registration methodologies to fuse the MRI and the TRUS images were considered: rigid registration (RR), contour-based (CB) deformable registration, Predictive Fusion followed by RR (pfRR), and Predictive Fusion followed by CB deformable registration (pfCB). Registrations were compared using the mean distance to agreement and the Dice similarity coefficient for the prostate as contoured on TRUS and the registered MRI prostate contour. RESULTS: Twenty patients treated with HDR prostate brachytherapy at our center were included in this retrospective evaluation. For the cohort, mean distance to agreement was 2.1 ± 0.8 mm, 0.60 ± 0.08 mm, 2.0 ± 0.5 mm, and 0.59 ± 0.06 mm for RR, CB, pfRR, and pfCB, respectively. Dice similarity coefficients were 0.80 ± 0.05, 0.93 ± 0.02, 0.81 ± 0.03, and 0.93 ± 0.01 for RR, CB, pfRR, and pfCB, respectively. The inclusion of the Predictive Fusion workflow did not significantly improve the quality of the registration. CONCLUSIONS: The CB deformable registration algorithm in the MIM treatment planning system yielded the best geometric registration indices. MIM offers a commercial platform allowing for easier access and integration into clinical departments with the potential to play an integral role in future focal therapy applications for prostate cancer.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".