70/100

Moderate evidence

GainPublished recordHealthGood Space

Evaluating a large language model for radiotherapy patient scheduling under realistic clinical and operational constraints: A feasibility study

Truvace record
TRV-2026-3031raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
46f7e1ec9e1a…check it

Background: Radiation Therapy (RT) scheduling requires coordination of clinical constraints and operational objectives. Large language models (LLMs) may provide a natural-language interface for generating candidate schedules. Purpose: To evaluate the feasibility of using an existing LLM to generate RT patient schedules under clinical and operational constraints through simulation and retrospective clinical comparison. Methods: A one-year, three-linear-accelerator (LINAC) simulation included 1400 new patients acr…

The gain

In a feasibility study comparing ChatGPT-generated schedules with a clinical schedule across 2043 retrospective appointments, the AI strategies cut mean gap by 50.8%-77.1% and raised treatment-time consistency from 86.7% to 99.5%-99.9% without overtime.

What this doesn’t fix

The evidence comes from a simulation and a six-week retrospective comparison, and the authors call it a feasibility study that supports further investigation rather than deployment.

Sources

1 on file
  1. Medical Physicsdoi:10.1002/mp.70767
    Peer-reviewed2026-12-01

Cite this record

v1

Truvace Impact Record TRV-2026-3031, v1: “Evaluating a large language model for radiotherapy patient scheduling under realistic clinical and operational constraints: A feasibility study.” Truvace, 2026-11-18. /record/TRV-2026-3031 (accessed on the day you copy it). sha256 46f7e1ec9e1ad1e6…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv146f7e1ec9e1a…

    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-3031 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.