← Latest papers
🤖 machine learning

Accelerating Reproducible Research in Synthetic EHR Generation

This paper introduces a lightweight, end-to-end benchmarking framework built on PyHealth that unifies codebases, training, and evaluation protocols to enable reproducible, architecture-agnostic comparison of synthetic EHR generation models, specifically targeting longitudinal ICD diagnosis codes.

Original authors: Jalen Jiang, Chufan Gao, Ethan Rasmussen, Stephen Z. Xie, Jimeng Sun

Published 2026-06-08
📖 4 min read☕ Coffee break read

Original authors: Jalen Jiang, Chufan Gao, Ethan Rasmussen, Stephen Z. Xie, Jimeng Sun

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Problem: The "Recipe" Mess

Imagine a group of chefs trying to invent a new type of cake (synthetic patient data) that tastes exactly like a real one but uses no real ingredients (protecting patient privacy).

The problem is that every chef has their own kitchen, their own measuring cups, and their own recipe books.

  • Chef A uses a specific brand of flour that only works with their mixer.
  • Chef B measures in cups, while Chef C measures in grams.
  • Chef D wrote their recipe in a language that no one else speaks anymore.

Because of this mess, no one can fairly compare who made the best cake. If you try to taste Chef A's cake against Chef B's, you don't know if the difference is because the cake is better, or just because they used different measuring tools.

The Solution: A Unified "Taste Test" Kitchen

The authors of this paper built a standardized kitchen (a benchmarking framework) where every chef must use the same tools, the same ingredients, and the same measuring cups.

They didn't just build a new cake; they built the entire testing facility so that future cakes can be compared fairly. They used a popular, community-maintained tool called PyHealth (think of it as a universal kitchen appliance) to make sure everything runs smoothly.

What They Did: Fixing the Old Recipes

The team took the most famous "cake recipes" (generative models) from the past and fixed them so they could work in this new kitchen:

  1. MedGAN & CorGAN: These were old recipes that had been simplified. The authors restored their full capabilities, allowing them to handle the entire list of medical codes (like every specific type of diabetes), not just the top 3 or 4 most common ones.
  2. PromptEHR & HALO: They updated these modern, complex recipes to work perfectly with the new equipment.
  3. The GPT-2 Baseline: They added a simple, general-purpose recipe (GPT-2) to see if a "generalist" chef could compete with the "specialist" medical chefs.

The Big Discovery: The "Long Tail" Problem

In the world of medical codes, a few diseases are super common (like the common cold), but thousands of rare diseases exist (the "long tail").

  • The Old Way: Previous researchers often ignored the rare diseases to make the math easier. They would say, "Let's just look at the top 1,000 codes." The authors argue this is like judging a chef only on how well they make a sandwich, ignoring that they can't make a soufflé.
  • The New Way: This paper forces the models to try to generate all 6,955 codes, including the very rare ones.

The Results:

  • The "Flat" Models (Old Recipes): These models were great at getting the count right (e.g., "10% of people have diabetes"). However, they failed to understand the story of the patient. They couldn't figure out which diseases happen together or in what order. They were like a chef who knows exactly how many eggs to use but doesn't know how to mix them.
  • The "Sequential" Models (New Recipes): These models (like HALO and GPT-2) were much better at understanding the story. They knew that if a patient has a heart condition, they might also have high blood pressure, and that these happen in a specific order over time.
  • The Surprise: The simple, general-purpose GPT-2 model performed surprisingly well, often beating the complex, specialized medical models at capturing the "story" of the patient, even if it wasn't perfect at the rarest details.

The Safety Check: Privacy

The team also ran strict safety tests to make sure the fake data didn't accidentally reveal who the real patients were.

  • The Test: They tried to trick the models into "remembering" real patients.
  • The Result: All the models passed. None of them leaked private information. The fake data was indistinguishable from real data in terms of privacy risk.

The Takeaway

This paper isn't about inventing a single "perfect" AI doctor. Instead, it's about building a fair playing field.

Before this, comparing different AI models was like comparing apples to oranges because everyone used different rules. Now, the authors have built a single, standardized track where every model must run the same race, using the same full list of medical codes. This allows researchers to finally see which models are actually good at creating realistic, safe, and useful synthetic patient records.

In short: They fixed the broken measuring cups, forced everyone to use the full ingredient list (including the rare spices), and proved that while some specialized chefs are good, a simple, well-tuned general chef can sometimes bake a better cake.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →