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

Machine learning-based prediction of postoperative nausea and vomiting after spinal anesthesia: A retrospective observational study

Postoperative nausea and vomiting (PONV) is a frequent and serious complication after surgery. PONV also reduces patient satisfaction with surgery under spinal anesthesia and increases medical costs due to prolonged hospitalization. The purpose of this study is to apply artificial intelligence (AI) machine learning analysis to identify risk factors for PONV in patients undergoing surgery with spinal anesthesia. This retrospective study used artificial intelligence to analyze data of adult patients (aged ≥20 year…

Health · G Space — documented gain · certified 2026-08-06 · v1 · article view · machine-readable

Current reading — gain

An ensemble of five machine learning algorithms applied to spinal anesthesia cases identified actionable risk factors for postoperative nausea and vomiting, with postoperative fentanyl as the strongest contributor, and was described as accurate enough to support PONV prediction.

What this doesn’t fix

Findings come from a single-center retrospective dataset with propensity matching that reduced the analytic cohort to 538 of 4,574 patients, limiting generalizability and causal inference.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0665, v1: “Machine learning-based prediction of postoperative nausea and vomiting after spinal anesthesia: A retrospective observational study.” Truvace, 2026-08-06. /record/TRV-2026-0665 (accessed at citation time). sha256 0465dd16633a5429

Calibration history

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

  1. Certifiedv10465dd16633a

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