TRV-2026-2315Certified recordPeer-reviewed

Quality and readability of large language model–generated responses on type 2 diabetes remission: a cross-sectional balanced factorial study

Abstract Large language models (LLMs) are increasingly being explored for patient education and medical information delivery. However, their outputs may involve trade-offs among medical accuracy, comprehensiveness, empathy, and readability. Type 2 diabetes remission is a clinically nuanced concept that is readily misunderstood by patients, making it a suitable context in which to evaluate both the medical quality and patient accessibility of artificial intelligence–generated health information. To systematically…

Health · Problem Space — documented harm · certified 2026-10-30 · v1 · article view · machine-readable

Current reading — problem

Chatbot answers about type 2 diabetes remission could not be optimized on every measure at once, and the easiest-to-read answers scored lower on comprehensiveness and falsehood avoidance.

What this doesn’t fix

The correlation analysis between readability and quality did not account for clustering within question and was intended for hypothesis generation only, and findings apply only to the type 2 diabetes remission question set.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2315, v1: “Quality and readability of large language model–generated responses on type 2 diabetes remission: a cross-sectional balanced factorial study.” Truvace, 2026-10-30. /record/TRV-2026-2315 (accessed at citation time). sha256 61b04d8b26a4c0c1…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv161b04d8b26a4…

    Certified into the record

Verify this record
How to verify without trusting this page

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