TRV-2026-1295Certified recordPeer-reviewed

A Multiparametric in vitro Strategy for Small Molecule Drug-Induced Liver Injury Risk Mitigation in Early Drug Development

Drug-induced liver injury (DILI) remains a major cause of preclinical and clinical attrition, reflecting persistent gaps in the predictive translation of preclinical safety data to human outcomes. To address these gaps, we established a refined multiparametric framework for early DILI risk prediction using a balanced reference set of 170 drugs with established clinical outcomes. Thirty physicochemical, mechanistic endpoints and exposure-related features were systematically evaluated to identify high-specificity…

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

Current reading — gain

Random Forest and flag-based models integrating exposure, lipophilicity, mitotoxicity and cytotoxicity improved early DILI risk prediction with high specificity, supporting safer molecule triage to reduce hepatotoxicity-related attrition.

What this doesn’t fix

Performance estimates are tied to a balanced reference set of 170 drugs and demonstration on contemporary Genentech portfolio molecules, limiting generalizability beyond those chemical spaces and in vitro systems.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1295, v1: “A Multiparametric in vitro Strategy for Small Molecule Drug-Induced Liver Injury Risk Mitigation in Early Drug Development.” Truvace, 2026-10-06. /record/TRV-2026-1295 (accessed at citation time). sha256 a512c07e44703c7e…

Calibration history

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

  1. Certifiedv1a512c07e4470…

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