De-identification and synthetic data generation solve the same problem in fundamentally different ways. De-identification takes real patient records and subtracts information — names, dates, ZIP codes — hoping that what remains cannot be traced back. Differentially-private synthesis generates entirely new records under a mathematical ceiling on how much any real patient can influence the output. The first is a policy whose strength depends on what attackers know. The second is a guarantee that holds no matter what they know.
How de-identification works — and why it keeps failing
Under HIPAA, de-identification takes one of two paths: Safe Harbor (remove 18 enumerated identifier types) or Expert Determination (a statistician certifies re-identification risk as "very small"). Both are subtraction: the records that remain are still real people's medical histories, minus the fields someone decided were identifying.
The failure mode is auxiliary information. Landmark work by Latanya Sweeney showed that 87% of Americans are uniquely identifiable by ZIP code, birth date, and sex alone — three fields that routinely survive masking policies. Every subsequent decade added demonstrations: re-identification of "anonymous" movie ratings, genomic datasets, hospital discharge records, and location traces. The pattern is structural, not accidental: a masking policy defends against the auxiliary data its designer imagined. Attackers get to use auxiliary data the designer never imagined — including datasets that don't exist yet.
How differentially-private synthesis works
Instead of subtracting from real records, a differentially-private pipeline extracts statistics from the source data through noise-calibrated releases, then generates artificial records from those protected statistics. Differential privacy guarantees that the presence or absence of any single patient changes the probability of any output by at most a bounded factor (eε). The bound is a theorem, not an assessment: it holds against any attacker, any auxiliary dataset, and any future technique, because it constrains the generation process itself rather than guessing what an adversary might know.
Side by side
| Property | De-identification / masking | DP synthesis |
|---|---|---|
| What ships | Real records, minus identifiers | Artificial records, statistically fitted |
| Privacy basis | Policy + expert judgment | Mathematical proof (ε, δ stated) |
| Auxiliary-data attacks | Principal failure mode | Covered by the guarantee |
| Future-proofness | Degrades as data accumulates | Bound is permanent |
| Statistical utility | Masking distorts joints and correlations | Fidelity measured and reported; tails deliberately smoothed |
| Regulatory direction (EU) | Under increasing scrutiny | DP named among recognised anonymisation measures in EDPB draft guidance |
The regulatory trajectory
The EDPB's draft anonymisation guidelines (July 2026) apply a singling-out / linkability / inference test to claimed anonymisation and treat synthetic data as anonymous only where identification is effectively precluded — while naming differential privacy among recognised anonymisation measures. In the US, HIPAA's Safe Harbor remains lawful, but the science it rests on ages every year, and expert determinations increasingly have to account for the modern auxiliary-data landscape. The direction of travel on both continents favours methods whose privacy can be demonstrated rather than asserted.
Honest caveat: the guarantee is not free. Differential privacy deliberately smooths distribution tails, which is why DP synthetic data is excellent for testing, development, feasibility, and ML benchmarking — and genuinely unsuitable for rare-disease cohorts and safety-signal detection. A provider should tell you this before you ask. (Full suitability table: What Is Synthetic Health Data?)
Frequently asked questions
Is de-identified data still personal data?
Under HIPAA, properly de-identified data is no longer PHI. Under the GDPR, the answer depends on whether individuals can still be singled out, linked, or inferred — a test de-identified data can fail when auxiliary data enables re-identification. That gap between the two regimes is precisely where re-identification research has done its damage.
Why does de-identification destroy statistical utility?
The fields most useful for analysis — dates, geography, rare diagnoses — are the most identifying, so masking policies target them first. Generalizing dates to years or truncating ZIP codes breaks the temporal and geographic joints that analytics depends on. Synthesis preserves the learned joint structure instead and reports the fidelity it achieved.
Does differential privacy mean the synthetic data is exactly as useful as real data?
No. The privacy budget (ε) is a dial between disclosure protection and statistical precision; small cohorts and rare categories lose the most. Trustworthy synthetic data ships with a measured fidelity report, so you know what was preserved rather than assuming it.
Can I combine both — de-identify first, then synthesize?
Synthesis pipelines typically consume identified or pseudonymized source data inside the data holder's environment, so pre-masking mostly just degrades what the model can learn. The privacy guarantee should come from the synthesis mechanism, not from input masking.
- L. Sweeney, "Simple Demographics Often Identify People Uniquely" (Carnegie Mellon, 2000) — the 87% result
- HHS: HIPAA de-identification guidance — Safe Harbor and Expert Determination
- EDPB Draft Guidelines 02/2026 on Anonymisation (July 2026)
- Synthetix Health Research: What Is Synthetic Health Data?
Continue reading in Research:
Working with clinical data that can't move?
Synthetix Health builds certified synthetic healthcare data infrastructure — ε-differential-privacy synthesis with a certificate and audit trail attached to every dataset.
Talk to us