TRV-2026-2202Version 1 · Certified

Written 2026-10-23 06:45:27 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2202
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-23T06:45:27.152346Z
status: published
lens: p_space
sector: health
headline: ROECSG report: Real-world implementation patterns and perceptions of artificial intelligence in radiation oncology
dek: Purpose: While international surveys have examined radiation oncology professionals' attitudes toward artificial intelligence (AI) and documented generally low early utilization, actual implementation patterns and the depth of integration among engaged practitioners remain unclear. This multi-institutional survey aims to characterize current AI implementation, identify critical barriers to optimization, and evaluate the psychological factors driving clinical trust.
Methods and materials: A de-identified survey c…
gain_title: (none)
problem_title: AI implementation in radiation oncology is concentrated in auto-contouring, with limited use in diagnosis and planning, while understanding is middling and transparency and validation barriers block deeper adoption.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: AI implementation in radiation oncology is concentrated in auto-contouring, with limited use in diagnosis and planning, while understanding is middling and transparency and validation barriers block deeper adoption.
problem_evidence: Qualitative analysis identified transparency (38%) and validation protocols (31%) as the primary barriers to deeper implementation
quick_read: A multi-institutional survey of 80 radiation oncology professionals, mostly radiation oncologists and medical physicists, examined how AI is actually used in clinics. Most respondents reported using AI, but use centered on auto-contouring, with far less in diagnosis, prognostication, and treatment planning.

The findings suggest enthusiasm is running ahead of understanding, since respondents rated their technical grasp near the scale midpoint yet mostly welcomed more AI. Authors call for institutional governance and AI-literacy education, but the sample was self-selected, so the results may not represent the wider field.
limitation: The study used a convenience sample of 80 respondents, and the authors note that self-selection likely inflates the reported AI use rate relative to the broader field.
tag: Evidence-backed problem
key_points: 85.0% (68/80) of respondents reported current AI use, though self-selection likely inflates this figure. | Auto-contouring accounted for 88.2% of AI users, versus 14.7% for diagnosis/prognostication and 23.5% for treatment planning. | 60.3% of users employed AI for task automation without influencing clinical judgment. | Trust correlated with perceived time savings (r = 0.57), clarity of use (r = 0.54), and technical understanding (r = 0.51). | Transparency (38%) and validation protocols (31%) were the main barriers to deeper implementation.
rundown: The survey used a de-identified instrument covering six domains, distributed through a medical physics listserv and at the 2025 AAPM Annual Meeting. It used 6-point Likert scales to reduce central tendency bias, and analyzed data with Pearson correlations and Welch's t-tests.

Respondents were 46.3% radiation oncologists and 37.5% medical physicists. Mean trust in AI was 3.55 and self-rated understanding was 3.44, yet 88.8% welcomed greater AI integration.

Qualitative responses were analyzed with inductive thematic analysis (κ = 0.78). The authors conclude that the gap between enthusiasm and understanding calls for active institutional governance and standardized AI-literacy education.
sources:
- peer_reviewed | Journal of Applied Clinical Medical Physics | https://doi.org/10.1002/acm2.70871 | 2026-11-01
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
b07186706b06afca1b5b68c4dddb893f955c00dc5ebf4b3f28db38f3f65e2421
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

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