TRV-2026-1730Version 1 · Certified

Written 2026-10-17 18:13:48 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1730
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-17T18:13:48.660648Z
status: published
lens: p_space
sector: health
headline: Reliability, quality, and readability of large language models in carpal tunnel syndrome: A comparative cross-linguistic, cross-sectional observational study
dek: BackgroundAI-based chatbots are increasingly used for health information, while cross-linguistic studies suggest that response performance may vary by language. Given the high prevalence of carpal tunnel syndrome (CTS), this study evaluated the reliability, quality, patient education suitability, and readability of AI-generated responses to CTS questions in English and Turkish.Materials and methodsSeventeen patient-centered CTS questions were directed to ChatGPT ® (GPT-5 Mini), Gemini ® 3 Flash, and Claude ® 4.5…
gain_title: (none)
problem_title: None of the three tested chatbots produced carpal tunnel syndrome answers at recommended readability levels in English or Turkish, and quality varied by model and language.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: None of the three tested chatbots produced carpal tunnel syndrome answers at recommended readability levels in English or Turkish, and quality varied by model and language.
problem_evidence: None of the models met recommended readability levels in either language. | AI-generated CTS information varied by model and language.
quick_read: Researchers put seventeen patient-style questions about carpal tunnel syndrome to ChatGPT (GPT-5 Mini), Gemini 3 Flash and Claude 4.5 Sonnet. Each question was asked in English and Turkish across 102 independent sessions, and the answers were scored for reliability, quality, patient-education suitability and readability.

The findings matter because patients increasingly turn to chatbots for health information, and answers that are hard to read or uneven across languages may limit their usefulness. The authors recommend treating chatbots as supplementary sources only. The abstract does not directly measure factual clinical accuracy, so how correct the advice was remains unresolved.
limitation: The mDISCERN instrument partly reflects whether references are provided and does not directly assess factual clinical accuracy, so score differences between models should be interpreted cautiously.
tag: Evidence-backed problem
key_points: The study compared three chatbots: ChatGPT (GPT-5 Mini), Gemini 3 Flash and Claude 4.5 Sonnet. | Seventeen patient-centered questions were asked in English and Turkish using zero-shot prompting across 102 independent sessions. | Responses were scored with mDISCERN, Global Quality Score and the Patient Education Materials Assessment Tool. | Readability was measured with the Flesch Reading Ease for English and the Ateşman Index for Turkish. | Significant differences between models were found in English across all metrics.
rundown: The design was a cross-sectional observational comparison. The statistical analysis used Friedman and Wilcoxon tests with Bonferroni correction to compare models and languages.

Reliability was assessed with mDISCERN, quality with the Global Quality Score, and patient-education suitability with PEMAT. In English, significant differences between models appeared on every one of these metrics.

The authors caution that mDISCERN partly reflects whether references are provided, so score differences should be read carefully. They conclude that chatbots should supplement, not replace, other sources of carpal tunnel information for patients.
sources:
- peer_reviewed | Journal of Back and Musculoskeletal Rehabilitation | https://doi.org/10.1177/10538127261492778 | 2026-10-08
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
1ffb5329939cf5f90f6d37954a4344d91162b20e26850bf6efd28294a349aa7b
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

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