TRV-2026-1489Certified recordPeer-reviewed

Matching Surgical Datasets to Prediction Tasks: NSQIP and Non-NSQIP Artificial Intelligence Models Across Specialties

Background Surgical artificial intelligence models depend on training data that may not capture predictors required for specific outcomes. We compared discrimination of models derived from the American College of Surgeons National Surgical Quality Improvement Program (NSQIP) with models using non-NSQIP datasets across surgical specialties and prediction tasks. Study design Structured searches of PubMed, Scopus, and EMBASE identified adult surgical prediction models published from October 1, 2015, through January…

Health · Problem Space — documented harm · certified 2026-10-15 · v1 · article view · machine-readable

Current reading — problem

Across 295 surgical prediction models, those trained on the standardized NSQIP database had lower average discrimination than models from other datasets, and the gap depended on the outcome predicted.

What this doesn’t fix

The authors report that the differences between NSQIP and non-NSQIP models were outcome-dependent and sensitive to precision weighting, so the pooled gap does not hold uniformly across tasks.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1489, v1: “Matching Surgical Datasets to Prediction Tasks: NSQIP and Non-NSQIP Artificial Intelligence Models Across Specialties.” Truvace, 2026-10-15. /record/TRV-2026-1489 (accessed at citation time). sha256 2c7c937e9e12eeea…

Calibration history

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

  1. Certifiedv12c7c937e9e12…

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