52/100

Moderate evidence

GainPublished recordScienceGood Space

Predicting Hormesis Effects of GenX in Zebrafish via Interpretable Machine Learning: Insights From SHAP Analysis

Truvace record
TRV-2026-1242raw data (JSON)
Version
v3Revised
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
10a4a1f85f05…check it

Hexafluoropropylene oxide-dimer acid (GenX), a prominent alternative to legacy per- and polyfluoroalkyl substances (PFAS), poses a significant challenge to traditional linear risk assessment models due to its ability to induce hormesis-a biphasic "low-dose stimulation, high-dose inhibition" response. This study established an interpretable machine learning (ML) framework to identify and predict GenX-induced non-monotonic dose-response (NMDR) relationships in zebrafish (Danio rerio). By integrating 263 independen…

The gain

An interpretable machine learning model predicted GenX's low-dose-stimulation, high-dose-inhibition effects in zebrafish with 91.25% accuracy (AUC 0.977) across 263 experimental records.

Sources

1 on file
  1. IUBMB Lifedoi:10.1002/iub.70135
    Peer-reviewed2026-10-01

Cite this record

v3

Truvace Impact Record TRV-2026-1242, v3: “Predicting Hormesis Effects of GenX in Zebrafish via Interpretable Machine Learning: Insights From SHAP Analysis.” Truvace, 2026-11-05. /record/TRV-2026-1242 (accessed on the day you copy it). sha256 10a4a1f85f051a6d…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv310a4a1f85f05…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv265bf6f367395…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  3. Publishedv1e05c56472cbc…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1242 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.