TRV-2026-1361Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1361 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-14T22:01:41.931556Z status: published lens: p_space sector: health headline: Can General-purpose Multimodal AI Reliably Measure Cobb Angles? A Head-to-head Diagnostic Agreement Study of GPT-5.1 and Gemini 3.1 Pro in Adolescent Idiopathic Scoliosis dek: General-purpose multimodal artificial intelligence (AI) models can interpret radiographs through natural-language prompts, but their quantitative agreement and anatomical traceability in adolescent idiopathic scoliosis remain uncertain. We compared GPT-5.1 and Gemini 3.1 Pro with a joint expert-consensus reference on 125 anonymized standing coronal whole-spine radiographs. Each model evaluated each image once in an independent chat session using the same standardized prompt; only the first response was retained.… gain_title: (none) problem_title: Neither GPT-5.1 nor Gemini 3.1 Pro agreed closely enough with expert consensus on case-level Cobb angles and end-vertebra identification to measure scoliosis curves autonomously. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: Neither GPT-5.1 nor Gemini 3.1 Pro agreed closely enough with expert consensus on case-level Cobb angles and end-vertebra identification to measure scoliosis curves autonomously. problem_evidence: neither model demonstrated sufficient case-level agreement and end-vertebra concordance to support autonomous Cobb-angle measurement quick_read: Researchers gave 125 anonymized standing whole-spine radiographs to GPT-5.1 and Gemini 3.1 Pro, each prompted once in a separate chat session, and compared their Cobb angle measurements with a joint expert-consensus reference. Gemini 3.1 Pro agreed with the reference more closely than GPT-5.1 on every main measure reported. The result matters because general-purpose chat models can read images from plain-language prompts, which could tempt clinical use in adolescent idiopathic scoliosis. Even the stronger model fell short of what autonomous measurement would need, and the study could not establish absolute accuracy or whether the models give repeatable answers. limitation: Results are relative to expert consensus and do not establish absolute measurement accuracy or model repeatability, since each image was assessed once per model in a single session. tag: Evidence-backed problem key_points: Gemini 3.1 Pro had an ICC of 0.842 versus 0.587 for GPT-5.1. | Mean absolute error was 5.06° for Gemini versus 9.62° for GPT-5.1, and Gemini's mean bias was 3.46° versus 8.68°. | Gemini placed 61.6% of measurements within 5° of the reference, versus 24.8% for GPT-5.1. | Exact upper end-vertebra agreement was 14.4% versus 8.8%, and exact lower end-vertebra agreement was under 20% for both models. rundown: The study used 125 anonymized standing coronal whole-spine radiographs. Each model evaluated each image once, using the same standardized prompt in an independent session, and only the first response was kept. Outcomes included intraclass correlation, mean absolute error, Bland-Altman analysis, error-threshold performance, categorical agreement, and end-vertebra concordance. Categorical agreement favored Gemini 3.1 Pro: 80.0% versus 52.8% for angle-derived severity categories and 78.4% versus 52.8% for prompt-constrained management categories. Both differences were reported as paired P < 0.001. The authors concluded that Gemini performed better under the tested single-session protocol but that neither model supported autonomous Cobb angle measurement, and that expert verification remains necessary. sources: - peer_reviewed | Journal of Imaging Informatics in Medicine | https://doi.org/10.1007/s10278-026-02394-0 | 2026-10-13 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- d6bd4756bae89db41398429406c4152cac628c2a3e1abe33d883289b573fccc3
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1361 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.
ace