TRV-2026-1852Version 1 · Certified

Written 2026-10-18 18:14:42 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1852
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-18T18:14:42.033326Z
status: published
lens: g_space
sector: health
headline: Algorithm-assisted personalized risk communication to encourage flu vaccination in the USA: three randomized field trials
dek: Artificial intelligence (AI) is increasingly used in healthcare to identify high-risk patients. Laboratory studies are mixed regarding patient attitudes towards AI use. Here we field-tested whether informing patients of their risk for influenza and its complications can serve as an effective behaviour-change intervention to increase vaccination, and whether disclosing AI use in the risk determination or providing personalized reasons for the algorithm's prediction (a form of explainable AI) influence message eff…
gain_title: Telling patients a machine learning algorithm had flagged them as high risk for flu complications raised vaccination slightly more than a generic reminder or no message.
problem_title: (none)
trace_subject: (none)
gain_reading: Telling patients a machine learning algorithm had flagged them as high risk for flu complications raised vaccination slightly more than a generic reminder or no message.
gain_evidence: High-risk nudges increased vaccination
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers ran three preregistered randomized controlled trials with over 90,000 patients of US healthcare systems. A previously validated machine learning algorithm identified patients at high risk for influenza and its complications, and these patients received no message or one of several messages encouraging vaccination.

The findings suggest that personalized risk information can be a low-cost way to nudge vaccination, though the gains are small in absolute terms. Patients did not react differently when messages named the algorithm or explained its predictions, so disclosure appears unlikely to deter or help uptake in this setting.
limitation: 
tag: Evidence-backed gain
key_points: The trials enrolled over 90,000 unique healthcare system patients in the USA across three preregistered randomized controlled trials. | Patients told of their high risk were vaccinated 1.1-1.4 percentage points more than those sent a simple reminder. | Compared with patients who received no message, the high-risk messages raised vaccination by 1.7-3.5 percentage points. | Vaccination was similar whether or not messages disclosed algorithm involvement or gave personalized reasons for the prediction.
rundown: The study tested whether informing patients of their personal risk for influenza and its complications works as a behaviour-change intervention. The primary outcome was influenza vaccination, and the comparison groups included non-messaged patients and patients sent a plain reminder.

A second question was whether disclosing AI use in the risk determination, or giving personalized reasons for the algorithm's prediction as a form of explainable AI, changed how effective the message was. Vaccination rates were similar across these arms, so patients were neither averse to nor appreciative of algorithm use or explainability.

The authors note that earlier laboratory studies on patient attitudes toward AI were mixed, and describe this as a realistic health application. The work was partially funded by the National Institute on Aging of the National Institutes of Health.
sources:
- peer_reviewed | Nature Human Behaviour | https://doi.org/10.1038/s41562-026-02603-4 | 2026-10-05
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
fa891c5df5b3b37ccd11f3ef9f4d2d0d3ed0758970d82f918560e2440a8e3fce
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

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