Anonymize PHI disclosed to public health authorities under §164.512(b) – CCPA/HIPAA-compliant de-identification per 45 CFR §164.512(b)

Covered entities may disclose PHI to public health authorities for disease surveillance, vital statistics, and outbreak investigation under 45 CFR §164.512(b) without patient authorization. anonym.legal de-identifies public health disclosures that exceed the minimum-necessary standard, reducing re-identification risk in case reports, notifiable-disease notifications, and adverse-event submissions shared with health departments.

When this applies

Apply this workflow when a covered entity is preparing reportable-disease case reports or adverse-event notifications for a public health authority and wishes to minimize the PHI disclosed beyond what the authority has specified as required under the minimum-necessary standard of §164.502(b).

  1. Upload the case report or notifiable-disease notification form to anonym.legal.
  2. Review the public health authority's minimum-necessary data elements specification; configure the engine to retain only those fields.
  3. The engine removes identifiers not required by the authority — typically street address, phone number, and full date of birth when only year is required — while retaining reportable data elements: disease code, county or ZIP code, onset date, and demographic stratum.
  4. Free-text clinical narratives in case reports are scanned for additional identifiers beyond the retained minimum-necessary fields and those are removed.
  5. The de-identified or minimized case report is prepared for transmission to the public health authority.
  6. A processing log documents which fields were retained as minimum-necessary and which were removed.

What you provide

  • Reportable-disease case report or adverse-event notification form
  • Public health authority's minimum-necessary data element specification
  • List of fields to be retained for epidemiological analysis

Limitations & cautions

  • §164.512(b) permits disclosure of identifiable PHI to public health authorities without patient authorization; de-identification is not required by the rule itself but reduces exposure risk. Confirm with legal counsel whether the specific disclosure requires de-identification or only minimum-necessary limiting.
  • Some notifiable-disease reporting systems require identified data for contact tracing; full de-identification is not appropriate for those disclosures.
  • Public health authority systems that receive identifiable case reports are themselves subject to applicable law; this workflow addresses the covered entity's Privacy Rule obligations only.

FAQ

Does HIPAA permit disclosing identifiable PHI to the CDC or state health departments?

Yes. Under §164.512(b), a covered entity may disclose PHI to a public health authority authorized by law to collect or receive such information for the purpose of preventing or controlling disease, injury, or disability. No patient authorization is required for these mandatory or permitted public health reporting disclosures.

What is the 'minimum necessary' standard for public health disclosures?

Under §164.502(b), covered entities must make reasonable efforts to limit PHI disclosed to the amount reasonably necessary to accomplish the purpose. For public health reporting, this means disclosing the data elements the authority has specified as needed, not an entire medical record.

Can the de-identified public health report be used for internal quality improvement after submission?

Yes. A de-identified version of the case report may be retained for internal epidemiological trend analysis or quality improvement without Privacy Rule restrictions, because it is no longer PHI.

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.