Design and implementation of a prototype radiotherapy menu in a patient portal
Bibliographic record
Abstract
PURPOSE: Radiotherapy patients often face undue anxiety due to misconceptions about radiation and their inability to visualize their upcoming treatments. Access to their personal treatment plans is one way in which pre-treatment anxiety may be reduced. But radiotherapy data are quite complex, requiring specialized software for display and necessitating personalized explanations for patients to understand them. Therefore, our goal was to design and implement a novel radiotherapy menu in a patient portal to improve patient access to and understanding of their radiotherapy treatment plans. METHODS: A prototype radiotherapy menu was developed in our institution's patient portal following a participatory stakeholder co-design methodology. Customizable page templates were designed to render key radiotherapy data in the portal's patient-facing mobile phone app. DICOM-RT data were used to provide patients with relevant treatment parameters and generate pre-treatment 3D visualizations of planned treatment beams, while the mCODE data standard was used to provide post-treatment summaries of the delivered treatments. A focus group was conducted to gather initial patient feedback on the menu. RESULTS: Pre-treatment: the radiotherapy menu provides patients with a personalized treatment plan overview, including a personalized explanation of their treatment, along with an interactive 3D rendering of their body, and treatment beams for visualization. Post-treatment: a summary of the delivered radiotherapy is provided, allowing patients to retain a concise personal record of their treatment that can easily be shared with future healthcare providers. Focus group feedback was overwhelmingly positive. Patients highlighted how the intuitive presentation of their complex radiotherapy data would better prepare them for their radiation treatments. CONCLUSIONS: We successfully designed and implemented a prototype radiotherapy menu in our institution's patient portal that improves patient access to and understanding of their radiotherapy data. We used the mCODE data standard to generate post-treatment summaries in a way that is easily shareable and interoperable.
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.004 | 0.008 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.015 | 0.003 |
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".