TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0758Certified recordPeer-reviewed

Identifying the presence of disc herniations in lumbar spine MRI using Gemini 3.1 Pro

Purpose Lumbar disc herniation is associated with substantial morbidity, including low back pain, radicular leg pain (sciatica), sensory disturbance, and motor deficit. Magnetic resonance imaging (MRI) is central to confirming the diagnosis in symptomatic patients and to planning surgical or interventional management. Recent advances in artificial intelligence (AI) raise the possibility of automating aspects of image interpretation to improve consistency and reduce radiologist workload. This study evaluates a ge…

Health · P Space — documented harm · certified 2026-08-14 · v1 · article view · machine-readable

Current reading — problem

When used zero-shot to identify lumbar disc herniations on sagittal MRI, Gemini 3.1 Pro produced low specificity and a substantial false-positive burden, with T1+T2 input performing worse than T1-only.

What this doesn’t fix

Evaluation was limited to zero-shot use of a generalist model on single mid-sagittal slices from a single paired cohort of 119 cases, presented as exploratory proof-of-concept rather than a validated clinical tool.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0758, v1: “Identifying the presence of disc herniations in lumbar spine MRI using Gemini 3.1 Pro.” Truvace, 2026-08-14. /record/TRV-2026-0758 (accessed at citation time). sha256 6eb6a2cb0787f7b2

Calibration history

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

  1. Certifiedv16eb6a2cb0787

    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-0758 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.