anonym.legal

By · Last updated 2026-04-30

Tagasi BlogisseTervishoid

Kohandatud MRN tuvastamine ilma koodita HIPAA jaoks

Meditsiinilise juhtumi numbrid on haiglapohised - iga tervishoiususteem kasutab erinevat vormingut. HIPAA Safe Harbor nouab MRN-ide eemaldamist.

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

MRN-i vormingu probleem

USAs on umbes 6100 haiglat. Igal on oma EHR-susteem. Igal on oma meditsiinilise juhtumi numbri (MRN) vorming. Uksainus riiklik standard puudub. Joint Commission nouab, et haiglad saaksid patsiente tuvastada - kuid ei kehtesta vormingureeglit.

Vormingud varieeruvad oluliselt. Moned on 7-kohalised taisarvud. Teised on 8-kohalised taisarvud. Moned kasutavad eesliiteid nagu HOSP-, MRN- voi PT-. Teised lisavad asutuse koode nagu SVHS- voi CHOP-. Moned poimitavad numbrisse registreerumisaasta.

HIPAA Safe Harbor loetleb patsiendi juhtumi numbrid identifikaatori tyyp 8-na 18-st (45 CFR paragrahv 164.514(b)(2)). Koik 18 tuleb eemaldada. Reegel ei piira seda uhega kindla vorminguga. Kui teie haigla kasutab kohandatud vormingut, peate selle tuvastama. Toorits, mis selle vahele jatab, ei tali Safe Harbori noude - isegi kui see eemaldab koik teised 17 tyypi.

Miks koodilahedus ebaonnestub

Standardne viis kohandatud juhtumi numbri vormingu lisamiseks de-identifitseerimise torujuhtmesse on Microsoft Presidio laiendamine. See tahendab Pythoni kirjutamist.

Arendaja loob klassi, mis laiendab EntityRecognizer klassi. Ta kirjutab regulaaravaldise, uhendab selle Presidio registriga, testib ja haldab seda. Vastavusmeeskondade jaoks - kes harva kodeerivad - on see tostlik takkis. Iga vormingumuutus vajab insenerist.

Tervishoiuinsenerid on haljas. Nad keskenduvad EHR-i integreerimisele ja kliiniliste sustoomide. Vastavuse tooritsad ei ole harvasti nende prioriteet.

Koodivaba mustri toovoong

Juhendatav mustrilahenemine eemaldab koodietapi.

Vastavusofficer avab veebirakenduses kohandatud uksuste looja. Ta kleebib viis naitenumbrit oma sustoomist - naiteks:

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

Ta klopsib Loo muster. Tehisintellekt loeb struktuuri ja tagastab:

  • Muster: SVHS-\d{7}
  • Usaldusvaarused: korge
  • Soovitatav nimi: HOSPITAL-MRN
  • Soovitatav asendus: [MRN]

Officer kleebib veel viis naidisnumbrit. Muster laab labi. Ta salvestab selle HIPAA-i eelsaattesse.

Sellest hetkest alates tuvastab iga seanss - veebirakendus, Office'i lisamoodul, lauarakendus ja API - selle vormingu standardses PHI-laskes. Koodi pole vaja.

GDPR-i teadusuuringute markas

GDPR-i artikkel 89 nab pseudonymiseerimise teaduse andmekogumite jaoks. Kohandatud uksused asetavad asutusepohised identifikaatorid ulatuse alla - sulgedes langa, mille uldised toritsad avatud jatavad.

Mida saate

See toovoong votab uhe pareva. Kohandatud kood votab nadali.

Vastavusofficer maaratleb mustri, testib seda ja voetab kasutusse. Piletit pole. Ootamist pole. Eelsaade haldab kohandatud uiksust koos standardse 17 Safe Harbor identifikaatoriga.

Kui jarmine kliiniliste markustuste partii joob, on koik 18 identifikaatorityypi kaetud. Safe Harbor on laimulik.

Vaadake HIPAA Safe Harbor de-identifitseerimine tervishoiuuuringutele, kuidas Safe Harbor praktikas toimib. Haiglakohaseid tuvastusmustreid vaata haigla-kohaseid MRN-i vormingute tuvastamine ilma inseneerimiseta.

Allikad

Seotud Artiklid

Tervishoid

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.

Tervishoid

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.

Tervishoid

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.

Kas olete valmis oma andmeid kaitsma?

Alustage PII anonüümitamist 285+ üksustüübi abil 48 keeles.

Alusta Tasuta KatsetVaata Funktsioone

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.