explainx.ai350K+ learn from us
TrendingAI News TodayPathwaysSkills
Pricing
explainx.ai

Upskill in AI — 16 free pathways, live workshops & bootcamps, and 50+ courses from practitioners. Plus the skills, tools, and MCP servers to practice on.

follow us

follow on google

Add explainx.ai as a preferred source

corporate training

support@explainx.ai

get started

Find your pathTake Free Evaluation

community

Join the community

learn

mind: share how you thinkpathways — start freeworkshopsbootcampscoursescompare Explainxcertificationsmock testsexplainx universitycorporate traininglearn skills & mcp

discover

skillsmcp serversexplainx mcpestacktoolsmdx readeragentsllmsdesignsdictionarypeopleagi trackerfelony benchranks

company

aboutvisionmissionteaminstructorsteach on explainxpartnershipscommunityhackathonscareers

content

daily AI newsstate of AI — live resultsblogreleasespromptsgeneratorsresource libraryfor LLMsexplainx.ai kids

solutions

all solutionsdeveloper upskillingmarketing upskillingproduct manager upskillingleadership upskilling

newsletter · weekly

Get AI news, tools, and insights in your inbox.

supportcontactprivacytermsdata rightshow we create contentsubmission guidelines

© 2026 AISOLO Technologies Pvt Ltd

explainx.ai

On this page

  • TL;DR
  • Why eNose research needed a harder benchmark
  • What the S-OH dataset contains
  • Methods and results under temporal validation
  • Demographics and confounding
  • How to run the benchmark
  • Implications for AI-for-health builders
  • Conference recognition
  • Limitations to state plainly
  • Comparison with other health ML evaluation habits
  • Integration with modern time-series foundation models
  • Data card fields to read before training
  • What clinicians will ask in pilot meetings
  • Open science citation hygiene
  • Model family details builders should reproduce
  • Designing a drift monitoring stack for eNose products
  • Regulatory and ethics framing
  • Extending the benchmark responsibly
  • Pairing Breath-Dx with agentic health workflows
  • Future cohort and hardware directions
  • Workshop path for health ML teams
  • Related reading
← Back to blog

explainx / blog

Breath-Dx: eNose Disease Screening Benchmark With Realistic Sensor Drift

Healthcare AI, Benchmarks, Time Series, Open Data, Research

Part of AI Benchmarks and Evals

Breath-Dx benchmarks 10 ML families on the public S-OH breath dataset with temporal splits that expose 0.05–0.12 AUC drops from sensor drift.

Nov 18, 2026·8 min read·Yash Thakker
add explainx.ai
go deep
Breath-Dx: eNose Disease Screening Benchmark With Realistic Sensor Drift

Breath-Dx is a new open benchmark for electronic-nose (eNose) disease screening that forces models to survive sensor drift, not just random cross-validation. Authors released the S-OH dataset on Hugging Face, code on GitHub, and arXiv paper 2611.15348 so teams can reproduce ten baseline families on 1,234 patients.

If you build health ML, the headline is simple: every method they tested lost 0.05–0.12 ROC AUC when evaluation respected time, exposing lab scores that would fail in clinics.

TL;DR

table · 2 cols
ItemDetail
DataS-OH: 1,234 patients, 9 diagnostic groups, 17-channel series
Methods10 models across tabular, CNN, GNN, and TS architectures
Drift effect−0.05 to −0.12 AUC vs random CV for all families
Peak temporal AUC~0.74–0.76 on some lung conditions
ReleaseHF dataset, GitHub splits + eval protocols
AwardAuthors cite IEEE ICDM 2026 Applied Track runner-up
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

Why eNose research needed a harder benchmark

Electronic noses promise portable, non-invasive screening from exhaled breath. Most papers use small private cohorts and random splits, which hide drift: sensors age, environments shift, and batch effects correlate with time.

Breath-Dx standardizes temporal train/test partitions on public data so ROC AUC reflects deployment reality, the same discipline InclusionMed pushes for healthcare AI indices.

What the S-OH dataset contains

Scent of Health (S-OH) is described in the paper as the largest public clinical eNose collection to date:

  • 1,234 patients
  • Nine diagnostic groups
  • 17-channel multivariate time series per participant
  • Explicit temporal splits accounting for sensor drift

Download via ivanpodd/S-OH and read the dataset card for collection protocol and label definitions before fine-tuning frontier models.

Methods and results under temporal validation

Breath-Dx evaluates four families:

  1. Feature-based tabular learners
  2. Convolutional models
  3. Graph-based models
  4. Time series architectures

Under temporal validation:

  • All ten methods lose 0.05–0.12 AUC versus random CV
  • Recurrent models show the most consistent performance across diseases
  • Specialized TS models achieve highest peaks on some tasks
  • Best temporal AUC ~0.74–0.76 for some lung conditions; others near chance

That spread matters for product roadmaps: screening UX must communicate uncertainty per condition, not a single "AI accuracy" banner.

Monitoring deployment drift when sensor baselines shift over calendar timeMonitoring deployment drift when sensor baselines shift over calendar time

Demographics and confounding

Authors emphasize demographic confounders:

  • Breath signals add independent value for some diseases
  • For others, signal adds little beyond age

Benchmark protocols in the GitHub repo document how to report stratified metrics. Copy that pattern when you ship internal health agents audited like GPT-6 healthcare pilots—subgroup tables are not optional.

How to run the benchmark

  1. Clone github.com/ivanpodd/Breath-Dx.
  2. Pull ivanpodd/S-OH with the published temporal splits.
  3. Reproduce baselines before swapping in custom transformers.
  4. Log drift curves over calendar time, not only aggregate AUC.

For time-series craft, cross-read multi-branch transformer KV work when you design long-context breath windows—different domain, same leakage pitfalls.

Implications for AI-for-health builders

Do not ship random-CV numbers in investor decks if temporal splits collapse performance. Breath-Dx gives citeable evidence that drift is universal in their study, not an edge case.

Regulatory path stays long. Benchmark success does not clear FDA/EMA pathways; treat Breath-Dx as R&D hygiene, like Sakana JFinBench for finance agents.

Open data helps audits. Public splits enable third-party replication, reducing vendor-only claims—aligned with Meta Brain2Qwerty style reproducibility expectations.

Conference recognition

In the Hugging Face paper thread, authors note IEEE ICDM 2026 Best Paper Runner-Up (Applied Track). That signals peer review interest, not clinical endorsement.

Limitations to state plainly

  • Nine groups still exclude many diseases.
  • eNose hardware varies; S-OH protocols may not transfer to consumer gadgets.
  • Temporal splits punish drift but do not simulate full prospective trials.

Comparison with other health ML evaluation habits

Many Kaggle-style medical competitions still publish random patient splits. Breath-Dx argues that practice is especially toxic for eNose because sensor aging correlates with calendar time. The 0.05–0.12 AUC penalty is not a rounding error; for screening at fixed sensitivity, it can flip cost-effectiveness models used in hospital procurement.

If you previously cited non-temporal AUC in decks, rerun tables with Breath-Dx splits before regulatory meetings. Align messaging with InclusionMed gaps on demographic reporting.

Integration with modern time-series foundation models

Teams experimenting with Chronos, Moirai, or custom transformers should treat Breath-Dx as a cheap sanity check before million-parameter finetunes. Pretraining on generic series does not immunize models against drift; the paper shows universal degradation under temporal validation.

Start with released recurrent baselines to establish floor metrics, then swap in your architecture while holding splits fixed. Log calibration curves—AUC alone hides overconfidence when prevalence shifts.

Data card fields to read before training

On ivanpodd/S-OH, verify label definitions per diagnostic group, acquisition dates tied to each patient row, sensor firmware revisions if documented, and missing channel handling rules.

Mis-reading label granularity (staging versus binary screening) is a common silent bug in health RAG pipelines, similar to JFinBench credential-level mistakes in finance agents.

What clinicians will ask in pilot meetings

Prepare answers for: (1) what happens when the sensor is recalibrated mid-study—point to temporal split design; (2) whether breath signal is independent of age—cite demographic confounder analysis; (3) which diseases are near chance even in lab data—quote per-condition AUC bands from the paper.

Open science citation hygiene

When you write about Breath-Dx, cite arXiv 2611.15348, the GitHub repository, and the Hugging Face dataset card—not aggregator rewrites. That supports reproducibility norms we use in Casey Handmer’s physics literature audit and other open benchmark coverage.

Source citation discipline for clinical AI benchmark posts that link datasets and code releasesSource citation discipline for clinical AI benchmark posts that link datasets and code releases

Model family details builders should reproduce

Breath-Dx spans feature engineering pipelines and end-to-end neural models. Tabular baselines extract hand-crafted statistics from 17-channel traces—mean, slope, spectral bins—then feed gradient boosted trees or logistic heads. Convolutional baselines treat each breath sample as a 2D map (time × channel). Graph models connect sensor nodes with learned edges, useful when cross-channel correlation shifts under drift.

Time-series transformers and State-space variants chase long-range dependencies across entire breath profiles. The paper’s point is not “transformers always win”; it is “every family overfits random splits.” When you port Hy4-class multimodal models or small SLMs to S-OH, keep the temporal split as your primary metric, with random CV labeled diagnostic only.

Designing a drift monitoring stack for eNose products

Production eNose programs need three layers Breath-Dx implies but does not ship as software:

  1. Reference gas standards on a schedule tied to calendar time, not sample count alone.
  2. Population shift dashboards comparing embedding centroids week over week.
  3. Human override when AUC drops below pre-registered thresholds.

Map layer 3 to Americans’ negative AI sentiment polls: consumers tolerate assistive screening only when false positives are explained and appealable.

Regulatory and ethics framing

EU AI Act high-risk framing may apply if breath models inform triage without clinician sign-off. Breath-Dx does not solve classification under law; it supplies evidence that uncalibrated lab AUC misleads.

Document informed consent for biometric breath collection, especially when workplace wellness programs also collect camera or wearable telemetry that employees may read as surveillance.

Extending the benchmark responsibly

Authors invite reproducible research. If you contribute new models:

  • Publish seeded splits unchanged from GitHub.
  • Report per-disease tables, not one macro AUC.
  • Disclose hardware calibration if you re-record supplemental patients.

Avoid merging S-OH with private cohorts without domain adaptation ablations—drift will reappear.

Pairing Breath-Dx with agentic health workflows

If you wire eNose scores into LLM triage agents, treat model output as features, not diagnoses. Agents should surface confidence, collection timestamp, and sensor batch ID in every summary—metadata Breath-Dx implies but agents often drop. Read AWS responsible agent roadmaps before automating patient-facing messages from breath classifiers.

Hospital IT should segment research laptops running Breath-Dx baselines from EHR-connected production VLANs, the same blast-radius discipline we recommend after Java4Shell patching sprints.

Future cohort and hardware directions

Authors point toward multi-site sensors and prospective drift correction algorithms. Until those land, treat Breath-Dx as the reference implementation for honest eNose metrics, not as proof that any single architecture is clinic-ready.

When you present results to hospital innovation boards, lead with temporal AUC and per-disease tables. Add a one-slide drift story explaining why random CV overstated past pilots. That framing prevents procurement teams from comparing Breath-Dx numbers to vendor brochures trained on leaky splits.

Workshop path for health ML teams

Structured AI workshops help teams adopt leakage-safe validation before clinical pilots. Pair Breath-Dx exercises with InclusionMed gap analysis for equity reporting.

Related reading

  • InclusionMed healthcare AI benchmark index
  • Meta Brain2Qwerty non-invasive decoding
  • Long-read genome rare disease diagnosis
  • Multi-branch transformer KV research
  • Sakana JFinBench certification benchmark
  • ScaleVLA robot vision-language backbone
Spotted something out of date? Let us know.
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

  • ✓ Free
  • ✓ One email a day, no spam
  • ✓ Unsubscribe anytime
Yash Thakker

Written by

Yash Thakker

Yash is an AI expert with over 300K learners. Join his workshops →

View Yash Thakker in People in AI →

Related posts

Nov 17, 2026

InclusionMed Index: A Healthcare AI Benchmark That Ranks Models by Role

The InclusionMed Collaboration released an open healthcare evaluation initiative on November 16, 2026. It picked five benchmarks after auditing 388 candidates, scored 22 frontier LLMs, and found top models communicate better with patients than they decide clinically.

Nov 18, 2026

Higher SWE-Bench Scores Did Not Ship More Code: Fable 5 Ban Natural Experiment

A November 2026 paper uses the 19-day Claude Fable 5 export ban as a natural experiment. When builders switched to lower-scoring models, weekly GitHub merge rates barely moved — challenging the idea that SWE-Bench Pro gains automatically mean faster delivery.

Nov 17, 2026

SWE-CoWork: Coding Agents as Digital Employees Benchmark

SWE-CoWork places coding agents inside simulated software organizations with 26 colleagues and distributed requirements. Leading models hit about 63% fail-to-pass tests but finish fewer than 8% of full assignments — a gap between partial patches and accountable delivery.