anonym.legal

By · Last updated 2026-04-28

Terug naar BlogGezondheidszorg

HIPAA: Volledige Detectie van de 18 PHI-identificatoren

HIPAA Safe Harbor vereist het verwijderen van alle 18 PHI-categorieën. De meeste tools dekken 12-14. Hier leest u welke worden gemist en waarom volledige dekking vereist is.

April 28, 20269 min lezen
HIPAA 18 identifiersPHI complete detectionMRN detectionNPI DEA numbersHIPAA Safe Harbor compliance

De 18 PHI-categorieën

HIPAA Safe Harbor (45 CFR §164.514(b)) vereist verwijdering van alle 18 categorieën beschermde gezondheidsinformatie:

  1. Namen — voor- en achternamen, initialen
  2. Geografische gegevens kleiner dan staat — postcodes, adressen, steden
  3. Datums (behalve jaar) — geboortedatum, opnamedatum, ontslagdatum
  4. Telefoonnummers
  5. Faxnummers
  6. E-mailadressen
  7. Sociale-zekerheidsnummers
  8. Medische recordnummers (MRN)
  9. Ziekteverzekeringsnummers
  10. Accountnummers
  11. Certificaat-/licentienummers
  12. Voertuigidentificatoren — kentekenplaten, VIN-nummers
  13. Apparaatidentificatoren — serienummers, implantatiecodes
  14. Web-URL's — persoonlijke websites
  15. IP-adressen
  16. Biometrische identificatoren — vingerafdrukken, stemafdrukken
  17. Volledige gezichtsfoto's
  18. Unieke identificatoren — die niet elders zijn gedekt

Welke Tools Routinematig Missen

Apparaatidentificatoren (13): Pacemaker-serienummers, infuuspompcodes en andere medische apparaat-ID's worden door de meeste NLP-tools zelden gedetecteerd.

Voertuigidentificatoren (12): Kentekenplaatverwijzingen in klinische notities ("patiënt was bestuurder in auto met kenteken...") worden gemist.

Certificaatnummers (11): Beroepslicentienummers van zorgverleners in klinische documentatie zijn PHI wanneer ze patiënten identificeren.

Biometrische identificatoren (16): Beschrijvingen van biometrische kenmerken in forensische of medische context.

Volledige Dekking Vereist Hybride Aanpak

Regex alleen dekt categorieën 4-15 (gestructureerde formaten). NLP is nodig voor categorieën 1, 2, 3 (namen, plaatsen, datums in vrije tekst). Aangepaste entiteiten zijn nodig voor categorie 18 (organisatiespecifieke unieke identifiers).

Bekijk de entiteitsdetectiepagina en HIPAA-nalevingsdocumentatie.

Bronnen

Gerelateerde Artikelen

Gezondheidszorg

HIPAA OCR: 725 Breaches, 275M Records

HHS OCR reported 725 HIPAA breaches in 2024 affecting 275M records — the highest ever. $10.22M average healthcare breach cost.

Gezondheidszorg

Handwritten Form OCR & PII Detection

A mid-size hospital processes 50,000 handwritten intake forms per year. Manual PII redaction at this volume requires 0.5 FTE.

Gezondheidszorg

HHS 2025: AI Clinical Notes Need PHI

AI transcription systems can inadvertently put Patient A's PHI in Patient B's record. Here's why real-time PHI detection before EHR commit is the control.

Klaar om uw gegevens te beschermen?

Begin met het anonimiseren van PII met 285+ entiteitstypen in 48 talen.

Start Gratis ProefperiodeBekijk Kenmerken

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.

Related reading

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.