Curriculum & schedule

Seven days, one complete arc

The week moves through the full lifecycle of an ML-for-health project — each day closing one gap from idea to bedside. Days pair a morning and an afternoon lecture with hands-on small-group and workshop time, and each content day builds a part of your private Project Workbook.

Accepted students: start with the Before you arrive checklist — readings, your specialty track, accounts to set up, and what to bring.

1Day

Mon · Jun 22 · Frame

Problems in ML4H

An interesting topic → a real, well-posed health problem with stakeholders.

AM lecture: Peter Szolovits (MIT) PM lecture: Emily Alsentzer (Stanford)

Morning. An opening block — welcome, orientation to how the week works, and a brief icebreaker — then a field-level frame: what ML4H is, what is shared across health problems, and what AI can and cannot do. A first small group reframes your project as a problem, not a method.

Afternoon. An afternoon lecture walks a real project from messy problem-formulation toward clinical use, then a problem clinic within your data-modality track. The day closes with a small group where you refine your problem framing.

Key questions. What is the unmet health need? Who are the stakeholders? What historical, societal, or scientific gaps challenge the problem — and how is a problem different from a method?

Full day outline →

2Day

Tue · Jun 23 · Interrogate

Data

A problem → the data that actually exists to attack it.

AM lecture: Tom Pollard (MIT) PM lectures: Solly Sieberts (Sage Bionetworks) & Jineta Banerjee (Sage Bionetworks)

Morning. Health data as a first-class citizen — the data-generating process, structured clinical data, de-identification, and access mechanics (PhysioNet, DUAs). Small groups map their own data-generating process and access plan.

Afternoon. Two afternoon lectures from Sage Bionetworks on the other half of the picture: research-cohort and genomics data (GWAS, multi-omics, longitudinal phenotyping), and the Synapse / data-fabric model for governed sharing across consortia and patient communities. Small groups refine the access plan and complete a data specification, followed by a data clinic within your modality track.

Key questions. What is the data-generating process for your project? What data exists independent of your AI system, and what biases does its provenance create?

Full day outline →

3Day

Wed · Jun 24 · Critique

Evaluation & Study Design

Data → a credible way to know whether a solution works.

AM lecture: Shalmali Joshi (Columbia) PM lecture: Olawale Salaudeen (MIT)

Morning. Study design and evaluation — estimands, utility-aligned metrics, statistical power, fairness, and threats to validity. Small groups dissect a provided evaluation case study.

Afternoon. An afternoon lecture on evaluation pitfalls and disaggregated metrics. Small groups define their evaluation plan, then a workshop to build an evaluation notebook for your own project, from a blank notebook.

Key questions. What would count as success, and how would you measure it credibly? What is your estimand? Which metrics track clinical utility, and how will you evaluate across subgroups?

Full day outline →

4Day

Thu · Jun 25 · Build

Methods & Modeling

A definition of success → a model designed to reach it.

AM lecture: Matthew McDermott (Columbia) PM lecture: Walter Gerych (WPI)

Morning. Method selection, health-specific inductive biases, and foundation versus task-specific models. Small groups draft a one-slide method / model proposal.

Afternoon. An afternoon lecture on trustworthy-by-construction methods, structured peer review of proposals, and a workshop to build a methods / modeling notebook for your own project (a prompt-a-thon alternative is offered for LLM-centric projects).

Key questions. What method fits your data and your Day 3 metrics? Should you fine-tune, prompt, or train from scratch — and a foundation or task-specific model?

Full day outline →

5Day

Fri · Jun 26 · Stress-test

Deployment

A model that works in a notebook → a system that survives a real clinic.

AM lecture: Muhammad Mamdani (Unity Health / U Toronto) PM lecture: Inioluwa Deborah Raji (UC Berkeley)

Morning. Real-world deployment war stories — workflow integration, clinician adoption, monitoring, and drift. Each group red-teams its members’ projects as a whole: imagine the project is built and deployed, then find where and why it would fail in the real world.

Afternoon. An afternoon lecture on bias, ethics, and accountability in deployment, continued red-teaming, and a fireside chat with a practicing clinician / patient voice on ML4H deployment.

Key questions. How do you red-team a deployed model? What mistakes does it make, and how does it treat patient populations differently? How do you simulate deployment, deploy, and audit?

Full day outline →

6Day

Sat · Jun 27 · Present

Practice Job Talks

A week of project work → the research story you can tell on the job market.

Moderated by: Camp faculty

Morning. Concurrent practice job-talk sessions, run in parallel rooms with faculty moderators. Each presenter gives a short job-talk-style presentation of their research and fields questions, as they would on the academic or industry market; the rest of the room listens and gives feedback. The day is geared toward participants on or near the research job market, but everyone benefits from giving and hearing the talks.

Afternoon. Job talks continue in parallel blocks through the afternoon, so everyone presenting gets a full slot and live feedback from faculty and peers.

Key questions. Can you tell the story of your research as a job talk — the problem, your approach, why it matters, and where it is going — and field hard questions about it?

Full day outline →

7Day

Sun · Jun 28 · Synthesize

Poster Session & Networking

A week of project thinking → a poster that tells the whole story.

Led by: All instructors & organizers

Morning. A cohort poster session, run in two rounds so everyone can both present their work and browse others’. Each poster walks the project arc — problem → data → evaluation → method → deployment — before an invited interdisciplinary audience.

Afternoon. Closing remarks and a reflection that returns to the Day 1 spine, then lunch and networking to close out the week.

Key questions. Can you tell your project as a coherent end-to-end arc on a single poster, apply the week’s lessons to revise it, and situate the work in ML4H as a field?

Full day outline →

A typical day

The daily rhythm

Days 1–5 share one consistent five-block structure: morning lecture → small group → afternoon lecture → workshop → closing small group. The shape is deliberate — you get a frame, apply it to your project, get content that sharpens your thinking, then revise your work. Every content day ends with a small group, not a lecture, so the last thing you do each day is improve your own project — Days 1–4 build that day’s Project Workbook part, and Day 5’s closing block is the group stress-test. Day 1 uses the same structure with an 8:30 opening block in place of the handoff; Day 6 is practice job talks, and Day 7 is a poster session and networking.

Those small groups are fixed home groups you stay in all week, with a peer facilitator who rotates daily. See your group and the facilitator rotation.

9:00
Morning handoff (Day 1: an 8:30 opening block — check-in, welcome & orientation, icebreaker)
9:15
Morning lecture — frames the day
10:30
Coffee break
11:00
Small Group 1 — apply the frame to your project
12:30
Lunch
1:30
Afternoon lecture — a concrete case or counterpoint
2:45
Workshop — a notebook (Days 3–4), specialty breakout (Days 1–2), or fireside (Day 5)
4:15
Small Group 2 (closing) — talk through how your thinking moved today
5:45
Daily wrap — quick recap and look ahead
6:00
Dinner

Suggested readings

Readings by day

Each content day has a short suggested-reading list. They’re also on each day’s page; the full set is collected here.

Day 2 — Data

  1. Johnson et al. (2023), MIMIC-IV, a freely accessible electronic health record dataset. Scientific Data.
  2. Roberts et al. (2021), Common pitfalls and recommendations for using machine learning to detect and prognosticate for COVID-19 using chest radiographs and CT scans. Nature Machine Intelligence.
  3. Mehra et al. (2020, RETRACTED), Hydroxychloroquine or chloroquine for treatment of COVID-19: a multinational registry analysis (the Surgisphere scandal). The Lancet.
  4. Yuan et al. (2021), Temporal bias in case-control design: preventing reliable predictions of the future. Nature Communications.
  5. Bareinboim & Pearl (2016), Causal inference and the data-fusion problem. PNAS.
  6. Einav et al. (2018), Predictive modeling of U.S. health care spending in late life. Science.
  7. Chandra, Cutler & Song (2011), Who Ordered That? The economics of treatment choices in medical care. Handbook of Health Economics.
  8. Fleming et al. (2024), MedAlign: a clinician-generated dataset for instruction following with EHRs. AAAI.
  9. Gebru et al. (2021), Datasheets for Datasets. Communications of the ACM.
  10. Gianfrancesco et al. (2018), Potential biases in machine learning algorithms using electronic health record data. JAMA Internal Medicine.
  11. Sjoding et al. (2020), Racial bias in pulse oximetry measurement. NEJM.
  12. Gichoya et al. (2022), AI recognition of patient race in medical imaging: a modelling study. Lancet Digital Health.
  13. Johnson et al. (2018), A comparative analysis of sepsis identification methods in an electronic database (how the cohort definition changes the data). Critical Care Medicine.
  14. Homer et al. (2008), Resolving individuals contributing trace amounts of DNA to highly complex mixtures (the genomic re-identification result behind controlled access). PLoS Genetics.
  15. MEDS (2025), An emerging data standard and ecosystem for health-AI research. NEJM AI.
  16. Overhage et al. (2012), Validation of a common data model for active safety surveillance research (the OMOP CDM). JAMIA.
  17. Agniel, Kohane & Weber (2018), Biases in EHR data due to processes within the healthcare system — when a lab is measured can be more informative than its value. BMJ.

How the days work

Concept in the morning, hands-on after

Concept sessions in the morning are paired with hands-on work after. Days 3 and 4 close with a build-your-own-notebook workshop on your own project — you start from a blank notebook (no template), with an AI coding assistant if you like.

The deliverable from each day is added to your growing Project Workbook — so by the final day, the week’s work exists as a single, coherent reference you present and carry home.

Readings. Each content day has a short required reading list (around five papers); these will be posted here ahead of the camp.