health · digital · family: the model was never trained on this
perfect on competition day, blind in the clinic
AI diabetic retinopathy screening achieves competition-grade accuracy but fails in real clinical deployment
Problem statement
Deep learning models for diabetic retinopathy (DR) screening achieve >95% sensitivity and >90% specificity on curated competition datasets (Kaggle 2015, APTOS 2019), yet real-world deployments consistently underperform. Google Health's deployment in Thai clinics found that 21% of images were rejected as ungradable (vs. <5% in competitions), nurses struggled with the camera equipment, internet connectivity was unreliable, and patients left before receiving results. The gap is not algorithmic — it is a system-level mismatch between competition conditions and clinical reality.
Why this matters
Diabetic retinopathy affects ~100 million people globally and is the leading cause of preventable blindness in working-age adults. Screening by trained ophthalmologists is effective but infeasible at scale in LMICs where ophthalmologist-to-patient ratios can exceed 1:500,000. AI screening promised to close this gap, but the competition-to-deployment failure has slowed adoption by years and eroded clinical trust in AI diagnostics more broadly. The pattern extends beyond DR to other imaging-based screening applications (cervical cancer, skin cancer, tuberculosis).
What’s been tried and why it hasn’t worked
Competition models are trained on high-quality fundus photographs taken by skilled technicians with standardized cameras in controlled lighting. Real-world images come from diverse camera models (desktop fundoscopes, smartphone attachments, handheld devices), are taken by minimally trained staff, and include artifacts from poor dilation, media opacities, and patient movement. Domain adaptation and image quality filtering help but create a tradeoff: strict quality filters reject too many images (defeating the purpose of screening), while permissive filters let through images that generate false diagnoses. Transfer learning on local datasets requires ground truth labels that are expensive to obtain in exactly the settings where AI screening is most needed. The Beede et al. study showed that even when the algorithm performed well, workflow failures (internet outages, nurse unfamiliarity, patient flow disruptions) degraded end-to-end performance.
What would unlock progress
Three complementary approaches: (1) camera-agnostic model architectures that explicitly handle image quality variation as an input feature rather than a rejection criterion; (2) offline-capable deployment systems that don't depend on cloud connectivity for inference; (3) co-design of the screening workflow with actual clinical staff in target settings before, not after, algorithm development. The deeper lesson is that AI medical device development must integrate human factors engineering from the start rather than optimizing accuracy on clean data and hoping deployment works.
Entry points for student teams
A team can reproduce the deployment gap at a desk instead of buying cameras: take a public DR-graded fundus set and apply a simulated acquisition-degradation pipeline — defocus and motion blur, uneven or reduced illumination, JPEG compression, and cropped field of view — then measure how a model trained on clean images loses sensitivity at each degradation level and how many images its quality filter rejects along the way. The DDR dataset (https://github.com/nkicsl/DDR-dataset, MIT-licensed, direct download) and the 45-image CC-BY High-Resolution Fundus set (https://www5.cs.fau.de/research/data/fundus-images/) need no registration; the EyeQ re-annotation supplies Good/Usable/Reject quality labels for 28,792 EyePACS images (https://github.com/HzFu/EyeQ) so the simulated degradation can be calibrated against real clinical quality grades, though those images must be pulled from the Kaggle EyePACS competition (https://www.kaggle.com/c/diabetic-retinopathy-detection, free account plus rules acceptance) and Messidor-2 requires a signed registration form (https://www.adcis.net/en/third-party/messidor2/). Alternatively, a team could design a screening workflow prototype that addresses the specific failure modes identified in the Beede study — image-quality feedback at the moment of capture, offline operation, nurse-friendly interface — and test it in a mock clinic with role-played patient flow rather than in a live one. Skills: machine learning, human-computer interaction, clinical workflow design, mobile development.
Genome — every gene is a door
Structural cousins — same reason stuck, other fields
Sources
Kaggle Diabetic Retinopathy Detection competition (2015) and APTOS 2019 competition post-mortems; Beede et al., "A Human-Centered Evaluation of a Deep Learning System Deployed in Clinics for the Detection of Diabetic Retinopathy," CHI 2020, Google Health Thailand deployment reports go to source ↗
verification notes (working record)
The collection team’s own sourcing notes for this brief, kept verbatim:
Tier 3 pilot brief sourced from Kaggle competition post-mortem analyses. The Kaggle DR Detection (2015) and APTOS (2019) competitions are among the most-discussed examples of the competition-to-deployment gap in ML. The Beede et al. CHI 2020 paper documenting Google Health's Thai deployment failures is a landmark study in human-centered AI evaluation. Cross-references: health-aravind-telemedicine-retinal-screening-dropout (same clinical domain, different failure mode — patient follow-through rather than algorithm deployment), digital-algorithmic-fairness-measurement-gap (ML model fairness challenges).
Reconciliation 2026-08-21: The C37 entry-point triage flag was upheld — the first door asked students to "collect fundus images from multiple camera types (including smartphone attachments)," which means imaging human eyes with several $10–30k fundus cameras under IRB, not a semester's work. It is replaced by a simulated acquisition-degradation study on public DR-graded images, which asks the same research question (how does performance fall as capture quality falls) without a camera or a patient. Resources verified by fetch this session: DDR (https://github.com/nkicsl/DDR-dataset — MIT license, direct Google Drive download, no registration), the High-Resolution Fundus database (https://www5.cs.fau.de/research/data/fundus-images/ — 45 images across healthy/DR/glaucoma, CC BY 4.0, direct download, no registration), EyeQ (https://github.com/HzFu/EyeQ — 28,792 EyePACS images re-annotated Good/Usable/Reject, labels shipped as CSVs in the repo), the Kaggle EyePACS competition (https://www.kaggle.com/c/diabetic-retinopathy-detection — live, free account plus rules acceptance, labeled as such), and Messidor-2 (https://www.adcis.net/en/third-party/messidor2/ — free for research but its own page states "a form with personal information needs to be completed to download the databases," so it is labeled registration-gated rather than public). Whole-section check under the per-door rule: the second door (workflow prototype from the Beede failure modes) was unflagged and is genuinely facility-free, so the brief was never at zero doors; it was tightened only by saying the test happens in a mock clinic, since "prototype a clinical workflow" can quietly read as clinic access. Genome Tags untouched.