TruaceTracing the truth around AIMonday, July 13, 2026
TRV-2026-0141Certified recordPeer-reviewed

Artificial intelligence applications in sport-related concussion: an updated scoping review

OBJECTIVES: Sport-related concussion is a complex mild traumatic brain injury for which diagnosis, monitoring, and prognosis remain largely dependent on subjective clinical assessment. Artificial intelligence has emerged as a potential tool to enhance objectivity by integrating large, multimodal datasets across the concussion care pathway. DESIGN: Scoping review. METHODS: A systematic literature search was conducted across six databases (MEDLINE, EMBASE, SPORTDiscus, Scopus, Web of Science, and Cochrane Central)…

Sports · The Trace — both readings · certified 2026-07-13 · v1 · article view · machine-readable

Current reading — gain

AI models using EEG, speech, motor data, wearables and video have been applied to detect concussion and quantify head-impact exposure while reducing false-positive events.

Current reading — problem

Current AI studies for sport-related concussion are frequently constrained by small or imbalanced samples, inconsistent definitions, limited external validation, and poor model interpretability.

What this doesn’t fix

Evidence base is heterogeneous with small or imbalanced samples, inconsistent outcome definitions, limited external validation, and poor interpretability, supporting use only as decision-support.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0141, v1: “Artificial intelligence applications in sport-related concussion: an updated scoping review.” Truvace, 2026-07-13. /record/TRV-2026-0141 (accessed at citation time). sha256 4003ee0c791d9c0d

Calibration history

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

  1. Certifiedv14003ee0c791d

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