TRV-2026-1650Certified recordPeer-reviewed

An Explainable Machine Learning Model Integrating Clinical Parameters for Identifying Left Atrial Appendage Thrombus in Non-valvular Atrial Fibrillation

Objective This study aimed to develop a predictive model for left atrial appendage thrombus (LAAT) in patients with non-valvular atrial fibrillation by integrating clinical and echocardiographic features using machine learning algorithms. The SHapley Additive exPlanations (SHAP) framework was applied to interpret the model and quantify the contribution of each predictor, thereby enhancing the accuracy and clinical interpretability of LAAT risk prediction. Methods In this retrospective study, 325 patients with no…

Health · Good Space — documented gain · certified 2026-10-17 · v1 · article view · machine-readable

Current reading — gain

A machine learning model with SHAP explanations uses readily available clinical and echocardiographic variables to predict thrombus in the left atrial appendage, which may support individualized anticoagulation decisions.

What this doesn’t fix

The model was developed in a retrospective study of 325 patients at a single institution, so its generalizability and prospective clinical performance are not established in the supplied text.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1650, v1: “An Explainable Machine Learning Model Integrating Clinical Parameters for Identifying Left Atrial Appendage Thrombus in Non-valvular Atrial Fibrillation.” Truvace, 2026-10-17. /record/TRV-2026-1650 (accessed at citation time). sha256 82b635599ec482a6…

Calibration history

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

  1. Certifiedv182b635599ec4…

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