TruaceTracing the truth around AIThursday, August 27, 2026
TRV-2026-0907Certified recordPeer-reviewed

Predicting Synchronous Liver Metastasis in Pancreatic Cancer Using CT Radiomics and Clinical Features: A Machine Learning Approach

Rationale and objectives To address the challenge of preoperative prediction of synchronous liver metastasis (LM) in pancreatic cancer (PC), we developed and validated machine learning models integrating clinical and computed tomography (CT) radiomics features, and compared the performance and interpretability of linear (linear discriminant analysis [LDA]) versus nonlinear (multilayer perceptron [MLP]) architectures. Materials and methods This retrospective study enrolled 340 patients with pancreatic ductal aden…

Health · The Trace — both readings · certified 2026-08-27 · v1 · article view · machine-readable

Current reading — gain

Integrated machine learning models using CT radiomics and clinical predictors achieved accurate preoperative prediction of synchronous liver metastasis in pancreatic ductal adenocarcinoma in validation, intended to assist decisions on surveillance versus biopsy or neoadjuvant therapy for indeterminate subcentimeter CT-

Current reading — problem

The linear LDA model showed unstable performance and poor discrimination in lymph-node-negative and pancreatic head tumor subgroups despite overall validation AUC.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0907, v1: “Predicting Synchronous Liver Metastasis in Pancreatic Cancer Using CT Radiomics and Clinical Features: A Machine Learning Approach.” Truvace, 2026-08-27. /record/TRV-2026-0907 (accessed at citation time). sha256 282f0df419b2cdd3

Calibration history

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

  1. Certifiedv1282f0df419b2

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