TRV-2026-2210Certified recordPeer-reviewed

Impression-regularized finetuning enables small language models to extract cervical spine fractures from radiology reports

We assessed whether small, open-weight large language models (LLMs) can accurately extract vertebral-level acute cervical spine fracture labels from CT radiology reports while supporting on-premises deployment, and whether impression-regularized finetuning improves accuracy, data efficiency, and temporal stability. In this single-center retrospective study, 8,567 adult cervical spine CT reports (2017-2022) were labeled for acute occipital condyle and C1-C7 fractures with neuroradiologist oversight. Reports from…

Health · Good Space — documented gain · certified 2026-10-23 · v1 · article view · machine-readable

Current reading — gain

A regularized finetuning method raised small open-weight models' accuracy at extracting vertebral-level fracture labels, bringing a 4B model close to a much larger zero-shot model while allowing privacy-preserving local use.

What this doesn’t fix

The study is single-center and retrospective, and the remaining errors were mainly tied to ambiguous report language and label-boundary cases, so generalizability beyond this setting is not shown.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2210, v1: “Impression-regularized finetuning enables small language models to extract cervical spine fractures from radiology reports.” Truvace, 2026-10-23. /record/TRV-2026-2210 (accessed at citation time). sha256 836456391deed8f5…

Calibration history

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

  1. Certifiedv1836456391dee…

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