Data

Day 2 — The foundation, constraint, and failure mode of health AI

Tom Pollard · MIT · June 23, 2026

AHLI HEALTH AI SUMMER CAMP 2026

Where we are on the spine

  • Yesterday: an interesting topic → a well-posed problem.
  • Today: a problem → the data that actually exists to attack it.

↩ Recap problem statements

The last decade was dominated by models.

The next will be shaped by data, governance, and deployment.

AHLI HEALTH AI SUMMER CAMP 2026

Are we okay with this?

center

AHLI HEALTH AI SUMMER CAMP 2026

Why does Google think Oreo is a palindrome?

center

AHLI HEALTH AI SUMMER CAMP 2026

They fixed it!

center

AHLI HEALTH AI SUMMER CAMP 2026

They fixed it?

center

AHLI HEALTH AI SUMMER CAMP 2026

Are we okay with this in healthcare?

center

Public health data has enabled reproducible research, benchmarks, education, and community science.

Has it enabled trustworthy, meaningful, and deployable AI for health?

AHLI HEALTH AI SUMMER CAMP 2026

COVID was a stress test

Researchers around the world turned their focus to building predictive models to beat covid.

center

AHLI HEALTH AI SUMMER CAMP 2026

What went wrong?

"...datasets spliced together from multiple sources and [containing] duplicates."

AHLI HEALTH AI SUMMER CAMP 2026

What did the algorithms learn?

"were tested on the same data they were trained on...learnt to identify duplicate patients

"learnt to use the text font to make predictions".

"learned to predict risk from a person’s position"

AHLI HEALTH AI SUMMER CAMP 2026

Surgisphere

  • Led by Sapan Desai, Vascular Surgeon (MD/PhD Chicago)
  • 100,000 patients across 671 hospitals
  • Papers in NEJM and The Lancet
  • Huge global impact
Surgsiphere website from archive.today (May 2020)
AHLI HEALTH AI SUMMER CAMP 2026

Provenance of data questioned

  • Papers retracted!
  • Huge waste of time
  • Caused confusion and distrust
AHLI HEALTH AI SUMMER CAMP 2026
AHLI HEALTH AI SUMMER CAMP 2026

This was a turning point

This should have been a turning point

AHLI HEALTH AI SUMMER CAMP 2026

These failures were not just “bad data”

They are infrastructural:

  • provenance — where did the data come from?
  • cohort logic — who was included, and why?
  • leakage control — what information was available when?
  • evaluation — what artifacts did the model learn?
  • governance — who was allowed to use the data, and how?

No one interrogated how the data came to exist and whether it was the right data for the problem.

AHLI HEALTH AI SUMMER CAMP 2026

The origin of the data

The data-generating process

AHLI HEALTH AI SUMMER CAMP 2026

Byproduct of care vs. designed for research

Byproduct of care

  • Generated while clinicians treat, document, and bill.
  • Abundant, messy, biased by workflow.
  • Most clinical data lives here.

Designed for research

  • Generated by a protocol to answer a defined question.
  • Rarer, cleaner for its purpose — still biased.
  • Benchmarks, registries, trials.

We need to ask:

  • what process created the data, and
  • what did that process make visible or invisible?
AHLI HEALTH AI SUMMER CAMP 2026

Data is not a neutral input.

It is generated by a process, for a purpose — and that shapes what you can credibly ask.

AHLI HEALTH AI SUMMER CAMP 2026

Patient timeline

Often we think about isolated sets of data. ICU data; OR data; wearables data.

Helpful to remind ourselves that we are dealing with a sequence of events

Times of health and sickness.

Typically we are viewing just snapshots of the journey.

Credit: Emily Alsentzer.
AHLI HEALTH AI SUMMER CAMP 2026

Case study — how a clinical dataset comes to exist

MIMIC as an example:

  • Deidentified critical-care data from patients admitted to a Boston Hospital
  • Built through extraction, structuring, and a substantial de-identification effort.
  • A "ready-to-use" dataset represents significant invisible work — and the choices in that work shape the data.
AHLI HEALTH AI SUMMER CAMP 2026

Critical care

AHLI HEALTH AI SUMMER CAMP 2026

Infusions

AHLI HEALTH AI SUMMER CAMP 2026

Intermittent treatment

AHLI HEALTH AI SUMMER CAMP 2026

Organ support

AHLI HEALTH AI SUMMER CAMP 2026

Waveforms

AHLI HEALTH AI SUMMER CAMP 2026

Observations, discussion, documentation

AHLI HEALTH AI SUMMER CAMP 2026

MIMIC

AHLI HEALTH AI SUMMER CAMP 2026

hadm_id=28503629

Vital signs captured only during ICU stay

Target monitoring increases frequency of measurements

AHLI HEALTH AI SUMMER CAMP 2026

Real-life data

AHLI HEALTH AI SUMMER CAMP 2026

Cleaning should visible and reusable

Encourage data processing pipelines, cohort selection to be shared in a public code repository.

AHLI HEALTH AI SUMMER CAMP 2026

Care data are selected by policy

  • Missingness is MNAR by construction — a value is absent because of a decision (not ordered ⇒ not worried).
  • In EHR data, “controls” often mean patients who were not tested, treated, coded, or escalated, not a random sample of true negatives.
  • Conditioning on a measurement (e.g. "lab was drawn") leads to sampling bias.

The data encodes the policy that produced it — and policies are not exchangeable across sites or time.

AHLI HEALTH AI SUMMER CAMP 2026

Each modality captures measurement decisions

Modality The measurement is itself a decision… …which breaks
Labs ordered when a clinician is concerned condition on "drawn" → sampling bias
Vitals sampled faster when acuity is high frequency is a severity proxy, not noise
Notes dictated selectively, templated presence ≠ incidence; documentation drift
Dx / billing codes coded for reimbursement prevalence tracks coding incentives
Imaging protocol- and referral-gated case-mix bias; site-specific acquisition
AHLI HEALTH AI SUMMER CAMP 2026

Design choices influence downstream use

AHLI HEALTH AI SUMMER CAMP 2026

Getting the data

De-identification, governance, and access

AHLI HEALTH AI SUMMER CAMP 2026

De-identification and governance

  • Data is shared under Health Insurance Portability and Accountability Act of 1996 (Safe Harbor's 18 identifiers, expert determination).

"A major goal of the Privacy Rule is to assure that individuals' health information is properly protected while allowing the flow of health information needed to provide and promote high quality health care and to protect the public's health and well being." .. "The Rule strikes a balance that permits important uses of information, while protecting the privacy of people who seek care and healing."

"There are no restrictions on the use or disclosure of de-identified health information. De-identified health information neither identifies nor provides a reasonable basis to identify an individual."

AHLI HEALTH AI SUMMER CAMP 2026

1. Manual review (time-consuming)

  • Scan infrequent values in string fields (e.g. group lab tests, review tail)
  • Scrape news articles
AHLI HEALTH AI SUMMER CAMP 2026

2. Pattern matching (predictable, fragile)

  • Known identifiers, e.g. match variations on:

    • Patient name and location
    • Dates
    • "VIP list"
  • Document structure:

    • Fields like "Name: XXX"
  • PHI structure:

    • Dates (YYYY/MM/DD)
    • Email (username@domain.tld)
AHLI HEALTH AI SUMMER CAMP 2026

3. Machine learning (unpredictable, flexible)

center

https://dl.acm.org/doi/pdf/10.1145/3368555.3384455

AHLI HEALTH AI SUMMER CAMP 2026

Deidentification is not bias-free

AHLI HEALTH AI SUMMER CAMP 2026

Access mechanics

  1. Credentialing: human-subjects training, approved identity.
  2. Data use agreement: sign and comply with the DUA.

Realistic timelines: weeks to months.

Start early — before you need the data.

AHLI HEALTH AI SUMMER CAMP 2026

Increasing value of health data makes it a target

Even well governed resources face downstream misuse.

AHLI HEALTH AI SUMMER CAMP 2026

LLMS

Researchers want to send data to external services (e.g. LLMs) for their research.

This involves sharing with a 3rd party (not allowed under our Data Use Agreement)

AHLI HEALTH AI SUMMER CAMP 2026

Membership attacks

High capacity models can memorize data. Membership attacks become a real threat.

External data: insurance claim: age, weekend accident, injuries

Released clinical data: de-identified admission: same age, same timing, same injuries

New information: clinical note shows suspected intoxication

AHLI HEALTH AI SUMMER CAMP 2026

Regulation is changing

Department of Justice recently introduced the Data Security Program

Limits sharing of deidentified health data with "Countries of Concern"

AHLI HEALTH AI SUMMER CAMP 2026

Public data enables (weak?) research

Public data enables (weak?) research

Study explored trends in publications using public datasets

“excess of 12,000 papers in 2025”

“measures to control access to open data are required”

AHLI HEALTH AI SUMMER CAMP 2026

Public datasets can create oversaturation

AHLI HEALTH AI SUMMER CAMP 2026

Standards solve syntax; representation is still open

  • A common schema — MEDS, events as (patient, time, code, value) — makes data portable.
  • How to represent irregular, multimodal, multi-scale event streams is an open research problem (e.g. tokenization, time encoding, and concept vocabularies).
  • Standardization reduces busywork, allowing you to focus on the modeling question (Day 4).
AHLI HEALTH AI SUMMER CAMP 2026

Reading between the lines

What the data hides

AHLI HEALTH AI SUMMER CAMP 2026

Provenance-driven bias

  • Time: coding, testing, and treatment change; the model learns the era.
  • Cohort definitions: cases and controls encode how patients were found.
  • Selection: the dataset contains who entered the system, not everyone at risk.
  • Documentation: codes and notes reflect workflow, incentives, and physiology.

Ask: is this signal clinical, or is it a trace of how the data were produced?

AHLI HEALTH AI SUMMER CAMP 2026

When a label is a billing artifact

A diagnosis code looks like ground truth. It isn't.

  • A code may appear because it justifies reimbursement, not because it's the primary clinical concern.
  • It may be absent for a real condition that wasn't billed.
  • Prevalence in the data tracks coding incentives as much as biology.

Train on that label, and you partly learn the hospital's billing rules.

↩ Day 1: label noise   → Day 3: estimands

AHLI HEALTH AI SUMMER CAMP 2026

Measurements are not neutral

AHLI HEALTH AI SUMMER CAMP 2026

X-rays encode race

AHLI HEALTH AI SUMMER CAMP 2026

Cohort definitions are important

A comparative analysis of sepsis identification methods in an electronic database. Crit Care Med. 2018 Apr;46(4):494–499. doi: 10.1097/CCM.0000000000002965

AHLI HEALTH AI SUMMER CAMP 2026

Different systems use different clocks

Temporal relationships between different streams may be highly informative.

Different clocks on different systems obscure these relationships.

AHLI HEALTH AI SUMMER CAMP 2026

Datasets are often a poor representation of clinical reality

Many public datasets are poor representations of clinical reality.

Promote research that isn't deployable.

AHLI HEALTH AI SUMMER CAMP 2026

Timing of laboratory tests

"the timing of when laboratory tests were ordered was more accurate than the test results in predicting survival in 118 of 174 tests

patients with normal white blood cell count values taken at 4 am have lower survival (85.4%) than patients with an abnormal measurement at 4 pm

Biases in electronic health record data due to processes within the healthcare system. BMJ 2018;361:k1479

AHLI HEALTH AI SUMMER CAMP 2026

Dataset shift

Occurs when the distribution of data changes between training and deployment

Leads to deterioration of model performance.

https://www.nejm.org/doi/full/10.1056/NEJMc2104626

AHLI HEALTH AI SUMMER CAMP 2026

Changes in ICD codes

Examined insurance claims for >18m people in the US from 2010 to 2017

Transition from ICD-9 to ICD-10 led to instantaneous +/- of >20% in the prevalence of many diagnostic categories.

https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2764197

AHLI HEALTH AI SUMMER CAMP 2026

Who is missing entirely

Perhaps the most significant bias is in the patients who never enter the data.

  • Under-served populations under-appear — or appear only at crisis.
  • Missingness is informative: absence reflects access, not health.
  • A model trained on who showed up encodes who didn't.

→ Days 3 & 5: equity   → data fusion (next)

AHLI HEALTH AI SUMMER CAMP 2026

Frontier — "more data" can make it worse

  • Combining sites is data fusion, not addition: each source carries its own selection mechanism.
  • Pooling without modeling those mechanisms can compound bias — and worsen transport to a new site.

The instinct "just get more data" is right only if you know what each source selected for.

↩ Day 1: more sites ≠ more general   → Day 5: transport

AHLI HEALTH AI SUMMER CAMP 2026

Data answers the question it was generated for

  • Spending and utilization data reflect the health system, not just health.
  • There is almost always a mismatch between what the data measures and what you want to know.
  • Name that gap explicitly — before it silently becomes your result.
AHLI HEALTH AI SUMMER CAMP 2026

Back to your own projects

Interrogating your own dataset

AHLI HEALTH AI SUMMER CAMP 2026

Four questions to ask of your data:

  1. Where did it come from — what process generated it, for what purpose?
  2. Who is missing — who never enters, who is under-measured?
  3. What does it silently encode — coding, workflow, system incentives?
  4. Does it support your Day 1 problem — or quietly change it?
AHLI HEALTH AI SUMMER CAMP 2026

The gap check

Does the data that exists actually support the problem you posed yesterday?

  • If yes — say how, specifically.
  • If no — you must revise the problem, the data plan, or both.

A problem statement without a data spec is still a wish.

AHLI HEALTH AI SUMMER CAMP 2026

Your data specification

Interrogate the data your project depends on.

Today's deliverable: Data specification sheet.
Consider what data exists, the generating process, your access plan, and the anticipated provenance-driven bias.

Next:

  • 11:00am: small group, interrogate your data
  • 1:30pm: Sage Bionetworks discuss data beyond the EHR

SPEAKER NOTES — Slide 1 (Title) Open. ~75 min, INTERROGATE mode. You built the field's reference clinical dataset — you carry unusual authority on both the concepts and the practical reality. This deck is an expanded starter (26 slides); see guides/day2-build-guide.md for the figure plan and injection map. INSTRUCTOR tags in the notes mark where to add your own material.

SPEAKER NOTES — Slide 2 (Handoff & where we are) - Run the 10-minute handoff before this slide, or fold it in — invite 2-3 participants to state their Day 1 problem in one sentence. - INSTRUCTOR: pick problems you can reference later in the lecture - (e.g., when you reach the gap check, point back to one of them). - This is the first day of the standard daily arc; model the rhythm well.

"The general idea [behind Guardian Angel] was correct. The connection to the real world was absolutely lacking."

SPEAKER NOTES — Slide 9 (The wrong frame) Set the day's thesis. Yesterday: "problem before method." Today, complicate it productively — the problem and the data co-evolve. INTERROGATE mode: the cohort interrogates whether the data they assume exists actually does, in the form they need.

- Pandemic was a wake up call for data sharing - When COVID-19 hit us in 2020, machine learning researchers around the world turned their focus to building predictive models to help beat the pandemic. - Report by the Turing Institute concluded that of the hundred of algorithms built, - None useful, some even caused harm. - What went wrong? ... - This is why today is not a “data management” lecture. It is a scientific validity lecture.

- Talk about "Frankenstein datasets" - Researchers didn't have access to the data they needed. - So they went to the web...

- As a result, the algorithms were highly problematic

- Perhaps clearest example of academic misinformation came from Surgisphere! - Led by Sepan Desai, vascular surgeon, MD/PHD Chicago - Early in the pandemic, offered dataset of 100,000 patients over 671 hospitals. - High profile papers in NEJM and The Lancet on Chloroquine (see website) - Huge global impact. Clinical trials stopped around the world.

- People began to question whether the data really existed. - All came falling down - Monumental waste of time - Worse, it caused mass confusion and distrust.

- WHO admitted it had cancelled trials without seeing the data

- If you didn’t follow along at the time.. - If you are interested in the gory details.. - I recommend this article in the Scientist. - They say this prompted calls for “reviews of how science is conducted, published, and acted upon”

- https://www.medrxiv.org/content/10.64898/2026.02.24.26347028v1.full.pdf

SPEAKER NOTES — Slide 21 (Section divider) The data-generating process is the conceptual core of the day — give it a clean break.

SPEAKER NOTES — Slide 22 (Byproduct vs designed) Core conceptual point. Hammer the byproduct-of-care idea: every quirk of clinical data — missingness, timing, coding — traces back to the fact it was generated to deliver and bill care, not to answer the participant's question. That mismatch is the day's recurring theme.

SPEAKER NOTES — Slide 23 (The central claim) The thesis, stated plainly so it holds for 75 minutes. Everything after is evidence: the generating process determines what the data can and cannot answer. Say it slowly.

We often think about isolated sets of data. Helpful to remind ourselves that this is a timeline. A set of interconnected events, each generating data. When we are looking at ICU data, we are looking at a small component.

SPEAKER NOTES — Slide 25 (Case study: MIMIC) Use MIMIC to illustrate the generating process — NOT as a product pitch. You have first-hand history. INSTRUCTOR: tell the cohort what surprised YOU about how hard "ready-to-use" was to achieve, and one shaping decision you made that downstream users inherit without knowing. The reproducibility angle is yours to press — the MIMIC Code Repository and "can you reproduce this published mortality-prediction result?" make the shaping-decisions point land; the datathon is the natural live version. → guides/instructor-resources.md. The lesson generalizes to any dataset.

SPEAKER NOTES — Slide 36 (Data is sampled from a policy) For this audience, "data is messy" is not news — formalize it. - The data is a draw from a clinical decision policy, so missingness is MNAR by construction and control definitions are selection mechanisms. - Reach for selection diagrams (Bareinboim & Pearl, data-fusion / PNAS 2016), not just the MCAR/MAR/MNAR taxonomy. - The collider point (conditioning on measurement) is the one to dwell on — it is how naive analyses fabricate signal. - a **selection diagram** is the right object (Bareinboim & Pearl). - Bareinboim & Pearl: https://www.pnas.org/doi/epdf/10.1073/pnas.1510507113 - MCAR/MAR/MNAR labels are the floor.

SPEAKER NOTES — Slide 37 (Each modality is a decision) Replaces a reference-card table with the identifiability lens this audience needs. The right two columns are the content: every modality's *presence* is a clinical decision, and conditioning on it has consequences (collider bias, spectrum bias, measurement-rate-as-severity). Pick one row to work through; the labs/collider row is the sharpest.

SPEAKER NOTES — Slide 39 (Section divider) Pivot from "where data comes from" to "how you actually get it." This section is the highest-utility content of the day for a room of PhD students.

SPEAKER NOTES — Slide 40 (De-identification & governance) Keep the practical floor (Safe Harbor vs. expert determination) to one line, then give this audience the privacy frontier they actually care about: de-identification of a dataset does not de-identify a *model* trained on it (membership inference, memorization in clinical LLMs), and the DP/synthetic-data "solutions" carry real utility and distribution-shift costs. INSTRUCTOR: name the de-id standard your institution uses.

- Time-consuming but important step is manual review. - One powerful approach is to group values and order by frequency. - Infrequent values often contain PHI. - We also use a script to gather news articles mentioning Beth Israel patients. - Remove anyone featuring in the articles. - This Yankee's fan will not appear in MIMIC

- Pattern matching is very important part of the deidentification process. - e.g. we know patient names, dates, etc, so we use this information. - e.g. dociments often follow consistent structure, such as Name: XXX - e.g. PHI entities also follow consistent structure, e.g. years, names. - While very effective, also fragile. - What I mean by fragile is that small inconsistencies in the data can lead to complete failure (e.g. a malformed date).

- We combine the previous approaches with machine learning models. - This paper describes a BERT model that we have used in the past. - Benefit is flexibility. Picks up PHI that patterns miss. - e.g. finds malformed dates that patterns missed.

SPEAKER NOTES — Slide 45 (Access mechanics) The slide participants most need. A room leaving able to actually get data is a real outcome. INSTRUCTOR: give the CURRENT PhysioNet steps and one or two pitfalls (training certificates expiring; DUA institutional sign-off lag). Be concrete about who signs the DUA at a typical university.

SPEAKER NOTES — Slide 52 (Standards vs. representation) Don't sell "structure is nice" to this audience. The framing: a schema like MEDS solves the *syntactic* portability problem, but how to *represent* irregular multimodal event streams (tokenization, temporal encoding, vocabulary) is unsolved and contested — a live research area. You plant it; McDermott harvests it on Day 4. The (patient, time, code, value) tuple is the one concrete anchor.

SPEAKER NOTES — Slide 53 (Section divider) Pivot from "how to get data" to "what is silently wrong with it." This is the INTERROGATE heart of the day.

SPEAKER NOTES — Slide 54 (Provenance-driven bias) - Time - Looks like patient at time of covid - Cohort - Signal partly represents clinician suspicion - Selection - People are missing if they never sought care - Documentation - Codes may be for billing.

SPEAKER NOTES — Slide 55 (Label-as-billing-artifact) Give the concrete "the label is really a billing artifact" example the outline asks for. INSTRUCTOR: a specific code from your experience (e.g., a sepsis or AKI definition that shifted with a billing or guideline change) makes this vivid. Connects back to Pete's Day 1 "label noise" feature and forward to Day 3 estimands.

- “Data” are not just the patient’s oxygenation. They are oxygenation as mediated by a device, skin pigmentation, clinical thresholds, and treatment protocols. - Photoplethsymogram is a device that measures your blood O2 with lght. - We know that PPGs are less accurate for patients with darker skin. - Study demonstrated this resulted in different O2 therapy for different patients.

- This is the multimodal version of “measurement decision.” An image is produced by referral, protocol, scanner, positioning, and acquisition workflow. The model receives all of that, not just the disease. - Example of the kind of research people are doing. - Study published in Lancet Digital Health - Demonstrated that AI models could detect race of patients using Chest X-rays. - Important implications in AI ethics and bias.

-

this is a multimodal physiologic record showing one cardiovascular event propagating across different measurement systems. From top to bottom, the channels appear to be: II, V, aVR — ECG leads, showing the heart’s electrical activity ABP — arterial blood pressure waveform CVP — central venous pressure PAP — pulmonary artery pressure Pleth — pulse oximeter plethysmography waveform, highlighted in orange Resp — respiration waveform - The ECG spike comes first, then the arterial pressure pulse, then the pleth pulse a little later in time - Pleth is on a different clock to ECG

-

SPEAKER NOTES — Slide 64 (Who is missing) "Who is missing entirely" is the bias that survives every downstream fix because it was never in the data. Plant the equity thread Days 3 (Salaudeen) and 5 (Raji) develop. Tie absence to access, not health. Leads into the data-fusion frontier slide.

SPEAKER NOTES — Slide 65 (Data fusion) — CORE The advanced version of the day's own thesis, for a strong room. Data fusion under heterogeneous selection can compound rather than cancel bias; "more sites" is not a generalization guarantee. Load-bearing for this audience — keep it. Callback to Pete's Day 1 shift slide; sets up Mamdani's Day 5 transport story.

SPEAKER NOTES — Slide 66 (Data answers its own question) Connect to the economics readings. Data carries the imprint of its purpose: utilization data tells you about access, incentives, and billing as much as about disease. INTERROGATE in one sentence: ask of any variable, "what was this generated to do?" — the answer bounds what it can tell you.

SPEAKER NOTES — Slide 67 (Section divider) Set up the guests. This frames the Sage Bionetworks guest lectures (Sieberts & Banerjee) as the other half of one picture, not separate topics.

SPEAKER NOTES — Slide 68 (Interrogating your dataset) This IS the structure of the deliverable and the small-group prompt. Walk the four questions slowly. Question 4 is the gap check — give it its own slide next.

SPEAKER NOTES — Slide 69 (The gap check) This is the pivotal move of the day and the reason data follows problem on the spine. INSTRUCTOR: point at one of the morning's handoff problems and run the gap check live, out loud — it models exactly what they do in small group. Some will discover their Day 1 problem needs revising; that is a success, not a failure.

SPEAKER NOTES — Slide 70 (Activity / transition) Hand off and preview the guest's contrasting half. Name the deliverable's four parts clearly — they map onto the small-group prompt and the four questions on Slide 24. End by reminding them: a problem statement without a data spec is still a wish.