TruaceTracing the truth around AISaturday, September 12, 2026
TRV-2026-1049Certified recordPeer-reviewed

Machine Learning for Mortality Prediction in Infective Endocarditis: A Systematic Review and Meta-Analysis

Infective endocarditis (IE) continues to be an often fatal condition despite improvements in cardiac surgical procedures and antibiotic therapy, and conventional scoring tools show poor generalizability. Machine learning (ML) addresses these limitations by capturing complex, nonlinear clinical relationships, outperforming conventional scores in predictive accuracy, though prior ML work in IE has focused on diagnosis. A PRISMA-compliant systematic review and meta-analysis of PubMed (Supplemental Digital Content,…

Health · The Trace — both readings · certified 2026-09-10 · v1 · article view · machine-readable

Current reading — gain

Supervised ML models, especially ensemble methods, predicted all-cause mortality in adult infective endocarditis with pooled AUC 0.85 for both in-hospital/early and 6-month mortality, outperforming conventional scores.

Current reading — problem

Half of included studies had identified risk of bias and clinical adoption remains limited, requiring multicenter prospective validation and interpretable frameworks before bedside use.

What this doesn’t fix

Evidence base is limited by retrospective design and bias, with 7 of 8 studies retrospective and risk of bias in half, requiring prospective multicenter validation before bedside use.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1049, v1: “Machine Learning for Mortality Prediction in Infective Endocarditis: A Systematic Review and Meta-Analysis.” Truvace, 2026-09-10. /record/TRV-2026-1049 (accessed at citation time). sha256 b0dc2586649f11d3

Calibration history

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

  1. Certifiedv1b0dc2586649f

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