TruaceTracing the truth around AISaturday, August 29, 2026
TRV-2026-0924Certified recordPeer-reviewed

Development and validation of a generalizable M-protein screening model using routine laboratory indicators: a multicenter retrospective study

Early detection of plasma cell disorders (PCDs) remains challenging due to limited accessibility of gold standard diagnostic methods. This study aimed to develop a simple M-protein screening model using routine laboratory indicators for clinical laboratories. A total of 5217 participants from three Chinese hospitals were enrolled. The derivation cohort (n = 3019) was randomly divided into training and internal validation cohorts. Two external validation cohorts (n = 1747 and n = 451) were included. M-protein pos…

Science · G Space — documented gain · certified 2026-08-29 · v1 · article view · machine-readable

Current reading — gain

Logistic regression screening model using routine indicators like total protein and hemoglobin achieved AUC 0.843 and provides an accessible tool for early identification of individuals at high risk of M-protein in resource-limited primary care.

What this doesn’t fix

Model development and validation were limited to participants from three Chinese hospitals, which may constrain generalizability to other populations and healthcare settings.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0924, v1: “Development and validation of a generalizable M-protein screening model using routine laboratory indicators: a multicenter retrospective study.” Truvace, 2026-08-29. /record/TRV-2026-0924 (accessed at citation time). sha256 487d1db3d1a8388d

Calibration history

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

  1. Certifiedv1487d1db3d1a8

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