60/100

Moderate evidence

Published recordHealthGeneral

Identification of key molecular targets in nicotine-induced spontaneous abortion through network toxicology and multi-omics integration

Truvace record
TRV-2026-1190raw data (JSON)
Version
v3Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
dcb5c1b505aa…check it

Introduction Spontaneous abortion (SA) remains a prevalent reproductive health challenge, with tobacco-derived nicotine emerging as a significant risk factor. This study sought to decipher the molecular underpinnings of nicotine-induced pregnancy loss through comprehensive multi-omics profiling to identify novel biomarkers and potential intervention targets. Methods An integrated bioinformatics approach was implemented combining network toxicology, transcriptomic profiling, and machine learning algorithms to elu…

The gain

Mendelian randomization and machine learning analysis found RAD50 and FGF2 causally linked to nicotine-associated spontaneous abortion, identifying candidate biomarkers and targets.

Sources

1 on file
  1. Tobacco Induced Diseasesdoi:10.18332/tid/230997
    Peer-reviewed2026-09-22

Cite this record

v3

Truvace Impact Record TRV-2026-1190, v3: “Identification of key molecular targets in nicotine-induced spontaneous abortion through network toxicology and multi-omics integration.” Truvace, 2026-11-04. /record/TRV-2026-1190 (accessed on the day you copy it). sha256 dcb5c1b505aac5e7…

Change history

3 versions

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

  1. Revisedv3dcb5c1b505aa…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain activity_only, problem absent).

  2. Revisedv26369027c6aa3…

    Direction audit: the problem line described the method, not an outcome; restated as the finding.

  3. Publishedv17bdd298b5aa6…

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