TRV-2026-2409Published recordJournalism

The impact of temporal resampling on the safety of clinical reinforcement learning: A simulated trial

Author summary Artificial Intelligence (AI) models could help future doctors by recommending personalised treatments for patients. These models are currently trained and tested using historical patient records rather than real patients. Medical decisions happen at unpredictable intervals, but before training an AI model, researchers usually shift and align the timings of recorded decisions into a regular schedule (‘temporal resampling’). This makes training the AI models easier with standard techniques. We inves…

Health · The Trace (a gain and a problem) · first published 2026-11-07 · v1 · read the full story · raw data (JSON)

The gain

In a simulated trial, offline reinforcement learning models trained on unedited, naturally timed insulin data outperformed the simulated clinician baseline, and retrospective safety tests predicted their performance accurately.

The problem

In a simulated trial with 30 virtual type 1 diabetes patients, resampling decision timings cut AI insulin-dosing performance by up to 60%, and standard retrospective tests predicted 1.5–3x better returns than the models achieved.

What this doesn’t fix

The simulated environments have simpler observations and random, state-independent decision intervals, which may limit generalisability to complex real clinical settings, and only model-free algorithms were tested.

Sources

Your take

What do you make of this one?

Cite this record

Truvace Impact Record TRV-2026-2409, v1: “The impact of temporal resampling on the safety of clinical reinforcement learning: A simulated trial.” Truvace, 2026-11-07. /record/TRV-2026-2409 (accessed on the day you copy it). sha256 6f45f47a518c8e5e…

Change history

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

  1. Publishedv16f45f47a518c…

    Certified into the record

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2409 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.