By · Last updated 2026-04-30

Rudi kwa BlogHuduma za Afya

Ugunduzaji Maalum wa MRN Bila Msimbo kwa HIPAA

Nambari za Rekodi za Matibabu ni maalum kwa hospitali — kila mfumo wa afya unatumia muundo tofauti. HIPAA Safe Harbor inahitaji kuondoa MRN.

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

Tatizo la Muundo wa MRN

Marekani ina hospitali karibu 6,100. Kila moja inaendesha mfumo wake wa EHR. Kila moja inatumia muundo wake wa Nambari ya Rekodi ya Matibabu. Hakuna kiwango cha kitaifa. Tume ya Pamoja inahitaji hospitali kuweza kutambua wagonjwa — lakini haiweki sheria za muundo.

Miundo inatofautiana sana. Baadhi ni nambari nzima za tarakimu 7. Nyingine ni nambari nzima za tarakimu 8. Baadhi zinatumia nambari za awali kama HOSP-, MRN-, au PT-. Nyingine zinaongeza nambari za taasisi kama SVHS- au CHOP-. Baadhi zinaingiza mwaka wa uandikishaji katika nambari.

HIPAA Safe Harbor inaorodhesha nambari za rekodi za mgonjwa kama aina ya kitambulisho nambari 8 kati ya 18. (45 CFR §164.514(b)(2)) Zote 18 lazima ziondolewe. Sheria hailimiti hii kwa muundo wowote mmoja. Ikiwa hospitali yako inatumia muundo maalum, lazima uigundue. Zana inayoikosa inashindwa Safe Harbor — hata kama inaondoa aina nyingine 17.

Kwa Nini Mbinu ya Msimbo Inashindwa

Njia ya kawaida ya kuongeza muundo maalum wa nambari ya rekodi kwenye mfululizo wa kutangua utambuzi ni kupanua Microsoft Presidio. Hiyo inamaanisha kuandika Python.

Mtengenezaji anaunda darasa linaloongeza EntityRecognizer. Wanaandika regex, wanaweka kwenye usajili wa Presidio, wanaipima, na kuisimamia. Kwa timu za uzingatifu — ambazo mara chache zinaandika msimbo — hii ni kizuizi kigumu. Kila mabadiliko ya muundo yanahitaji mhandisi.

Wahandisi wa afya wana shughuli nyingi. Wanazingatia ujumuishaji wa EHR na mifumo ya kliniki. Zana za uzingatifu mara chache ni kipaumbele chao cha juu.

Mtiririko wa Kazi wa Mfumo Bila Msimbo

Mbinu ya mwongozo wa mfumo inaondoa hatua ya uandishi wa msimbo.

Afisa wa uzingatifu anafungua Kiunda cha Vitambulisho Maalum katika programu ya wavuti. Wanabandika sampuli tano za nambari kutoka mfumo wao — kwa mfano:

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

Wanabonyeza Tengeneza Mfumo. AI inasoma muundo na kurudisha:

  • Mfumo: SVHS-\d{7}
  • Uhakika: juu
  • Jina linalopendekezwa: HOSPITAL-MRN
  • Uingizwaji unaopendekeza: [MRN]

Afisa anabandika sampuli tano zaidi. Mfumo unapita. Wanauokoa kwenye kielezo cha HIPAA.

Kutoka hapo, kila kikao — programu ya wavuti, Office Add-in, Programu ya Mezani, na API — inagundua muundo huu katika mzunguko wa kawaida wa PHI. Hakuna msimbo unaohitajika.

Kumbuka kuhusu Utafiti wa GDPR

GDPR Kifungu 89 kinahitaji pseudonymization kwa seti za data za utafiti. Vitambulisho vya kawaida huweka vitambulisho maalum vya taasisi ndani ya wigo — kufunga pengo ambalo zana za kawaida zinaacha wazi.

Unachopata

Mtiririko huu wa kazi unachukua alasiri moja. Msimbo maalum unachukua wiki nyingi.

Afisa wa uzingatifu anafafanua mfumo, anaupima, na kuudeploy. Hakuna tikiti. Hakuna kusubiri. Kielezo kinashikilia vitambulisho maalum pamoja na vitambulisho 17 vya kawaida vya Safe Harbor.

Wakati kundi la pili la maelezo ya kliniki linakimbia, aina zote 18 za vitambulisho zinashughulikiwa. Safe Harbor imekamilika.

Angalia kutangua utambulisho wa HIPAA Safe Harbor kwa utafiti wa afya kwa jinsi Safe Harbor inavyofanya kazi kwa vitendo. Kwa mifumo ya ugunduzaji maalum ya hospitali, angalia kugundua muundo wa MRN maalum wa hospitali bila uhandisi.

Vyanzo

Tayari kulinda data yako?

Anza kuanonymisha PII na aina 285+ za vitu katika lugha 48.

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.