TRV-2026-2392Published recordPeer-reviewed

Multi-omics-driven predictive modelling of antimicrobial resistance emergence in African food value chains under climate change scenarios.

Antimicrobial resistance (AMR) poses a critical threat to food safety, particularly in African food systems where surveillance infrastructure is limited and climate change is accelerating microbial adaptation. Traditional microbiological risk assessment approaches fail to capture the biological complexity of AMR emergence across food value chains. This study developed an integrated multi-omics and machine learning framework to predict AMR emergence across Nigerian food value chains under projected climate scenar…

Health · Good Space (a documented gain) · first published 2026-11-06 · v1 · read the full story · raw data (JSON)

The gain

In a study of 487 food and 192 environmental samples from three Nigerian locations, an XGBoost model combining multiple omics datasets predicted antimicrobial resistance emergence with an AUROC of 0.942, a 16.3% improvement over single-omics approaches.

What this doesn’t fix

The study was cross-sectional, sampling only three Nigerian locations, and the Vibrio increases are climate-scenario projections rather than observed outcomes.

Sources

Your take

What do you make of this one?

Cite this record

Truvace Impact Record TRV-2026-2392, v1: “Multi-omics-driven predictive modelling of antimicrobial resistance emergence in African food value chains under climate change scenarios..” Truvace, 2026-11-06. /record/TRV-2026-2392 (accessed on the day you copy it). sha256 1df6c508a8a35158…

Change history

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv11df6c508a8a3…

    Certified into the record

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

Download any version from /api/record/TRV-2026-2392 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.