All apps

De-identification · Privacy / Data-Governance leads

↔ shared

CuRE Curtain

De-identification review — inspect de-id transforms and re-identification risk, and gate data releases

Overview

De-identification review — inspect de-id transforms and re-identification risk, and gate data releases. Curtain renders the de-identification and risk work computed by Conduct and Calculate against one governed OMOP record — not a bolt-on privacy tool with its own copy of the data

Key capabilities

  • De-identification review and approval
  • Re-identification-risk inspection (k-anonymity & risk scoring)
  • Human-in-the-loop release gating
  • Audit-ready privacy-review trail
  • Field-level de-id transform review (approve/query)
  • Privacy-utility frontier comparing achieved k-anonymity and retained data across de-identification configurations

Example differentiators

  • The de-id review workbench renders the k / l / t thresholds an officer tunes against Calculate's returned artifact — per-class pass rates, the binding k-anonymity floor, suppressed-row count, and the utility-vs-privacy retention tradeoff — not a single binary pass/fail flag; and when the technique carries no risk model it says so rather than showing a fabricated number
  • Curtain renders the de-identification and risk work computed by Conduct and Calculate against one governed OMOP record — not a bolt-on privacy tool with its own copy of the data
  • Re-identification risk is scored on the same governed substrate the rest of CuRE analyzes, so privacy review and analytics never drift apart
  • Release gating is a human-in-the-loop review over Conduct's release engine — de-identification decisions are inspectable, not a black box
  • Built on the platform's audit and e-signature primitives, so privacy review shares one validation story with the rest of the evidence chain
  • The review surface extends toward the attacker-model numbers a privacy officer signs an Expert Determination on — prosecutor, journalist and marketer risk plus population uniqueness — and toward monitoring how a release's risk moves as the underlying record grows, each arriving as a Calculate methodology artifact Curtain renders rather than an estimator of its own
Try out a feature

Re-identification risk assessment

One example from CuRE Curtain. Synthetic data, runs in your browser

Tune k-anonymity, l-diversity, t-closeness, and the generalization budget on a synthetic OMOP release, and watch the equivalence classes reform, the privacy↔utility tradeoff shift, and the export gate open or close — computed live in your browser by the same generalize-then-suppress fixed point the product runs

A synthetic release of 140 records — quasi-identifiers age, zip, sex and a sensitive diagnosis.

Minimum equivalence-class size. Classes smaller than k are generalized or suppressed.

Distinct diagnoses required per class — guards against the homogeneity attack.

Max EMD between class and global sensitive distribution (numeric attributes).

How far age can bin (10→20→40…) and ZIP can truncate (5→3→*) before a class is suppressed instead.

Over-suppressed
46 records suppressed to satisfy the thresholds — loosen k / l or raise the generalization budget to keep more.
🔒
Records released
94
of 140 · 67% retained
Suppressed
46
too identifying to release
Classes clearing gate
6/14
min class size 1
Privacy posture
43%
classes passing k·l·t

Privacy ↔ utility tradeoff

Privacy (classes passing)
43%
Utility (records retained)
67%

Tighten k or l and privacy rises but utility falls as more records suppress; spend more generalization budget to recover utility by merging classes instead. That is the officer's whole job — and it is a real fixed-point computation here, not a mockup.

Equivalence classes · generalized [age | zip | sex]

Generalized quasi-identifierSizeℓkltDisposition
0-39 · 020 · *96✗✓✓Suppressed · k
80-119 · 021 · *83✗✓✓Suppressed · k
40-79 · 020 · *86✗✓✓Suppressed · k
0-39 · 024 · *75✗✓✓Suppressed · k
40-79 · 024 · *65✗✓✓Suppressed · k
80-119 · 020 · *42✗✓✓Suppressed · k
0-39 · 021 · *33✗✓✓Suppressed · k
80-119 · 024 · *11✗✗✓Suppressed · k/l
20-29 · 021 · *257✓✓✓Released
60-69 · 021 · *165✓✓✓Released
40-49 · 021 · *166✓✓✓Released
30-39 · 021 · *154✓✓✓Released
70-79 · 021 · *115✓✓✓Released
50-59 · 021 · *116✓✓✓Released

Each row is an equivalence class after generalization — note how age widens into decade bins, zip truncates to three digits, and sex redacts to *. k-anonymity, l-diversity (distinct diagnoses), and t-closeness are computed in your browser for every class; nothing calls a backend.

These are the published re-identification measures: k-anonymity, l-diversity and t-closeness. Change a setting and the release gate opens or closes, and you can see what that setting costs in detail lost. In the product, Curtain puts these same measures in front of a privacy officer deciding a release under HIPAA Expert Determination (45 CFR §164.514)

See CuRE Curtain in action

Every research ecosystem is unique. Let's discuss how CuRE can be configured for your needs