Expert Determination de-identification for statistical risk analysis – CCPA/HIPAA-compliant de-identification per 45 CFR §164.514(b)(1)

Under 45 CFR §164.514(b)(1), a covered entity may de-identify PHI by having a qualified statistical or scientific expert certify that the risk of identifying any individual is very small. anonym.legal supports this method by quantifying re-identification risk across quasi-identifier combinations, producing the statistical documentation an expert needs to certify compliance.

When this applies

Use Expert Determination when the dataset must retain clinically meaningful variables — such as multi-digit ZIP codes, rare diagnosis codes, or detailed dates — that Safe Harbor would remove, and a qualified expert is available to certify the residual risk meets the §164.514(b)(1) standard.

  1. Upload the dataset and provide the expert's risk threshold (the 'very small' standard is not numerically defined in the rule; typical practice uses a re-identification probability below 0.09).
  2. The engine profiles all quasi-identifier combinations — age, ZIP, sex, race, diagnosis, admission year — and computes k-anonymity and l-diversity metrics for each combination.
  3. A risk report is generated showing the population uniqueness of each record combination, with flagged cells where re-identification probability exceeds the threshold.
  4. For flagged cells, the engine suggests targeted suppression, generalization, or data swapping interventions to bring risk below the threshold without removing the entire field.
  5. The expert reviews the risk report and the proposed interventions, applies any additional transformations, and certifies in writing that the risk is very small.
  6. The certified de-identified dataset and the expert's certification documentation are stored together as the compliance record.
  7. The transformed dataset is released for the approved secondary purpose.

What you provide

  • Dataset containing PHI fields to be evaluated
  • Expert's statistical risk threshold and preferred risk metric (k-anonymity, re-identification probability, etc.)
  • Data dictionary and list of quasi-identifier fields
  • Description of the intended secondary use and the audience who will receive the data

Limitations & cautions

  • Expert Determination requires a qualified statistical or scientific expert to certify the result; anonym.legal provides the risk quantification but does not itself constitute the expert certification required by §164.514(b)(1).
  • Re-identification risk depends on the availability of external auxiliary datasets; risk assessments should be revisited when new publicly available datasets (census updates, public health registries) are released.
  • The method requires more time and cost than Safe Harbor; for routine data releases where Safe Harbor suffices, it is not the recommended approach.

FAQ

Who qualifies as a 'qualified statistical or scientific expert' under §164.514(b)(1)?

The Privacy Rule does not enumerate specific credentials. HHS guidance indicates the expert should have knowledge of accepted statistical and scientific principles for de-identification. In practice, biostatisticians, epidemiologists, and privacy engineers with demonstrated experience in re-identification risk analysis typically perform this role.

What does 'very small' risk mean in statistical terms?

The rule does not define a numerical threshold. Academic practice and published HHS guidance commonly references re-identification probability below 0.09 (9%) at the record level, but the expert may apply a different threshold appropriate to the data sensitivity and the intended use context. The expert's documentation must explain the basis for the chosen threshold.

Can Expert Determination be applied to datasets that also include Safe Harbor de-identification?

Yes. The methods are not mutually exclusive. A hybrid approach — applying Safe Harbor to the most sensitive identifiers and Expert Determination to quasi-identifiers that cannot be fully removed — is recognized in HHS guidance as a valid de-identification strategy.

Healthcare Records

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.