anonym.legal

By · Last updated 2026-04-30

Povratak na blogZdravstvo

Prilagodjeno otkrivanje MRN bez koda za HIPAA

Brojevi medicinskih kartona specificni su za svaku bolnicu - svaki zdravstveni sistem koristi drugaciji format. HIPAA Safe Harbor zahteva uklanjanje MRN-ova. Evo kako to uraditi bez pisanja koda.

April 30, 20268 min čitanja
custom MRN detectionHIPAA pipeline configurationno-code regexAI pattern helperhospital identifier de-identification

Problem sa formatima MRN

SAD ima oko 6.100 bolnica. Svaka koristi sopstveni EHR sistem. Svaka koristi sopstveni format broja medicinske kartone (MRN). Ne postoji nacionalni standard. Zajednicki komitet zahteva da bolnice mogu identifikovati pacijente - ali ne propisuje format.

Formati se veoma razlikuju. Neki su 7-cifren celi brojevi. Drugi su 8-cifreni. Neki koriste prefikse kao HOSP-, MRN-, ili PT-. Drugi dodaju kodove institucija kao SVHS- ili CHOP-. Neki ugraduju godinu upisa u broj.

HIPAA Safe Harbor navodi brojeve pacijentskih kartona kao identifikator tip 8 od 18. (45 CFR ss164.514(b)(2)) Svih 18 mora biti uklonjeno. Pravilo se ne ogranicava na jedan format. Ako vasa bolnica koristi prilagodjen format, morate ga detektovati. Alat koji ga propusti ne ispunjava Safe Harbor - cak i ako ukloni svih ostalih 17 tipova.

Zasto kodirski pristup ne funkcionise

Uobicajen nacin dodavanja prilagodjeog formata broja kartona u pipeline za de-identifikaciju je prosirenje Microsoft Presidio alata. To znaci pisanje Python koda.

Programer kreira klasu koja prosiruje EntityRecognizer. Pisu regularnu ekspresiju, uvezuju je u Presidio registar, testiraju i odrzavaju. Za compliance timove - koji retko kodiraju - ovo je ozbiljna prepreka. Svaka promena formata zahteva inzenjera.

Zdravstveni inzenjeri su zauzeti. Fokusiraju se na integraciju EHR-a i klinicke sisteme. Compliance alati retko su njihov prioritet.

Tok rada s obrascima bez koda

Vodjen pristup obrascima uklanja korak kodiranja.

Compliance oficir otvara Custom Entity Creator u veb aplikaciji. Nalepi pet uzoraka brojeva iz svog sistema - na primer:

SVHS-0012345
SVHS-0987654
SVHS-1122334
SVHS-4455667
SVHS-8899001

Klikne Generate Pattern. Vestacka inteligencija cita strukturu i vraca:

  • Obrazac: SVHS-\d{7}
  • Pouzdanost: visoka
  • Predlozeno ime: HOSPITAL-MRN
  • Predlozena zamena: [MRN]

Oficir nalepi jos pet uzoraka. Obrazac prolazi. Sacuvaju ga u HIPAA preset.

Od tog trenutka, svaka sesija - veb aplikacija, Office Add-in, Desktop App i API - detektuje ovaj format u standardnom PHI pregledu. Nema koda.

Napomena o GDPR istrazivanjima

GDPR clan 89 zahteva pseudonimizaciju za istrazivacke skupove podataka. Prilagodjen entiteti stavljaju identifikatore specificne za instituciju u polje delovanja - zatvarajuci jaz koji genericke alate ostavljaju otvorenim.

Sta dobijate

Ovaj tok rada traje jedan popodne. Prilagodjen kod traje nedeljama.

Compliance oficir definise obrazac, testira ga i primenjuje. Nema tiketa. Nema cekanja. Preset drzi prilagodjen entitet pored standardnih 17 Safe Harbor identifikatora.

Kada sledeci paket klinickih beleski prode kroz sistem, svih 18 tipova identifikatora je pokriveno. Safe Harbor je kompletan.

Pogledajte HIPAA Safe Harbor de-identifikaciju za zdravstvena istrazivanja za prakticne informacije o Safe Harboru. Za obrasce detekcije specificne za bolnice, pogledajte otkrivanje MRN formata specificnih za bolnice bez inzenjerske pomoci.

Izvori

Spremni da zaštitite svoje podatke?

Počnite sa anonimizacijom PII sa 285+ tipova entiteta na 48 jezika.

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.