TRV-2026-1662Version 1 · Certified

Written 2026-10-17 06:53:58 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1662
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-17T06:53:58.598012Z
status: published
lens: p_space
sector: health
headline: Integrity of artificial intelligence and machine learning evidence in spine surgery: a critical appraisal of systematic reviews
dek: Objective Artificial intelligence (AI) and machine learning (ML) are increasingly integrated into spine surgery across diagnostic, perioperative, and predictive applications, driven by their potential to enhance accuracy, efficiency, and patient safety. As this literature on AI and ML in spine surgery rapidly expands, concerns have emerged regarding selective reporting and overemphasis on algorithmic performance without adequate attention to transparency, bias, or clinical applicability. Such practices raise the…
gain_title: (none)
problem_title: Spin appeared in 86.5% of abstracts of AI and machine learning spine surgery systematic reviews, overstating conclusions and casting doubt on how reliably clinicians can interpret the evidence.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: Spin appeared in 86.5% of abstracts of AI and machine learning spine surgery systematic reviews, overstating conclusions and casting doubt on how reliably clinicians can interpret the evidence.
problem_evidence: Spin was present in 32 of 37 (86.5%) abstracts. | most often overstating conclusions, selectively reporting outcomes, and making inappropriate generalizations
quick_read: Researchers searched PubMed, Scopus, and Embase for systematic reviews and meta-analyses of AI and machine learning in spine surgery. They narrowed 273 records to 37 eligible reviews and scored each for 15 types of spin and for methodological quality using AMSTAR 2.

The finding matters because systematic reviews strongly shape clinical interpretation, and inflated claims about algorithm performance could mislead decisions about diagnostic, perioperative, and predictive tools. The abstract describes association patterns but does not show that the spin changed patient care, so the downstream clinical effects remain untested.
limitation: 
tag: Evidence-backed problem
key_points: 32 of 37 reviews (86.5%) had spin in their abstracts, and every one of the 15 spin types was observed. | The most common spin types were type 5 (51.35%), type 3 (48.65%), and type 9 (48.65%). | Lower journal impact factors and reduced AMSTAR 2 confidence ratings were significantly associated with spin. | The authors call for greater transparency, adherence to reporting standards, and methodological rigor.
rundown: The review followed PRISMA guidelines. After 90 duplicates and 124 ineligible titles or abstracts were removed, a further 22 studies were excluded, leaving 37 reviews for assessment.

Study characteristics recorded included PRISMA adherence, publication year, and level of evidence. Associations with spin were tested using chi-square, Mann-Whitney U, and Kruskal-Wallis tests and Spearman's rank correlation.

The authors say the literature has expanded rapidly, with concern about selective reporting and overemphasis on algorithmic performance rather than transparency, bias, or clinical applicability. They conclude that addressing these biases is critical for reliable evidence synthesis and informed clinical decision-making.
sources:
- peer_reviewed | Journal of Neurosurgery: Spine | https://doi.org/10.3171/2026.4.spine251808 | 2026-10-09
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
8411fa442e5462a34cb9736de7c0a64195549b204a015d89d0e1f722bc53ce42
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

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