By · Last updated 2026-04-02

Rudi kwa BlogHuduma za Afya

LLMs Zinakosa 50% ya PHI ya Kliniki

Utafiti wa 2025 uligundua kuwa LLMs zinakosa zaidi ya 50% ya PHI ya kliniki katika hati za lugha nyingi. 34.8% ya maingizo yote ya ChatGPT yana data nyeti.

April 2, 20269 dakika kusoma
LLM PHI detectionHIPAA de-identificationclinical NLPSafe Harbor methodhealthcare AI compliance

Tatizo la Kiwango cha Kukosa 50%

Utafiti wa 2025 (arXiv:2509.14464) ulijaribu zana za LLM kwenye rekodi za kliniki. Matokeo yalikuwa mabaya. Zana hizi ziliskosa zaidi ya 50% ya PHI ya kliniki katika hati za lugha nyingi. Sababu ni rahisi. LLMs zimejengwa kwa matokeo ya maandishi. Hazijajengwa kwa kazi ya ugunduzi wa kumbukumbu kubwa ambayo HIPAA inahitaji.

HIPAA Safe Harbor inaorodhesha aina 18 za vitambulisho vinavyolindwa. Majina, tarehe, nambari za simu, SSNs, MRNs, vitambulisho vya mpango wa afya, vitambulisho vya kifaa, na anwani za IP. Kila moja inahitaji mantiki yake ya ugunduzi.

Maelezo ya kliniki yanafanya hili kuwa gumu zaidi. Chukua mfano huu: "Pt. John D., DOB 4/12/67, MRN 1234567, admitted 03/15/24, Dr. Smith ordered ECG." Sentensi moja. Vitambulisho vitano vinavyolindwa. Vingi vinatumia maumbo ya kufupishua. Mfano uliojengwa kwa maana ya kliniki mara nyingi unashindwa kazi ya ugunduzi.

LLMs Zinakosa Nini na Kwa Nini

Zana za LLM zinashindwa kwenye rekodi za kliniki kwa njia maalum.

Vitambulisho vya maumbo mafupi: Maelezo ya kliniki yanatumia mkato. DOB, MRN, na Pt. ni maumbo ya kawaida. Mfano ulioratibishwa kwa maana ya kliniki unaweza kutoweza kuandika alama "Pt. John D." kama jina. Uchimbaji wa data nyeti unahitaji lengo tofauti.

Tarehe zinazolingana na muktadha: Si tarehe zote zinawasilisha hatari sawa. "Umri wa miaka 67" ni alama laini. "DOB 4/12/67" ni kitambulisho cha moja kwa moja kinachohifadhiwa. "03/15/24" kama tarehe ya kulazwa pia inalindwa. Kulinganisha na mfumo peke yake hakutoshi.

Miundo ya nje ya Marekani: Cyberhaven (Q4 2025) iligundua kuwa 34.8% ya maingizo yote ya ChatGPT yana data nyeti, ikiwemo PII ya lugha nyingi. Katika huduma za afya, hii inamaanisha vitambulisho vya rekodi nje ya Marekani, miundo ya tarehe ya kanda, na aina za kitambulisho cha afya cha ndani. Zana zilizofunzwa nchini Marekani zinakosa hizi kwa uthabiti.

Vitambulisho vya hospitali maalum: Hospitali zinatumia miundo yao ya MRN, vitambulisho vya wafanyakazi, na misimbo ya tovuti. Hizi hazipo katika data ya mafunzo ya kawaida ya NER. Zana ambazo hazina uungaji mkono wa vitengo maalum hazitazipata.

Hatari ya Dataset ya Utafiti

Hospitali inayojenga dataset ya utafiti kutoka maelezo 500,000 inakabiliwa na tatizo halisi la uzingatiaji. HIPAA inahitaji kiwango cha "hatari ndogo sana" kwenye data iliyotambuliwa. Zana inayokosa nusu ya vitambulisho vyote vinavyolindwa haiwezi kukidhi kiwango hicho.

Makumbusho ya utafiti si data safi. Maelezo yanajumuisha idara nyingi, vipindi vya wakati, na wakati mwingine lugha. Zana inayofanya kazi kwenye data ya bili inaweza kushindwa kwenye maelezo ya masimulizi. Data nyeti katika maandishi huru haina lebo ya sehemu.

Uidhinishaji wa IRB unaongeza madai zaidi. Taasisi lazima zionyeshe njia iliyotumika, aina za vitambulisho vilivyoondolewa, na ukaguzi uliofanywa. Zana inayokosa nusu ya rekodi zote haiwezi kukidhi madai hayo.

Angalia muhtasari wetu wa uzingatiaji na mazoea ya usalama jinsi anonym.legal inavyounga mkono kazi ya HIPAA.

Suluhisho la Tabaka Tatu

Utafiti wa 2025 uligundua mfumo mmoja wazi. Zana zilizo na viwango vya chini zaidi vya kukosa zilitumia tabaka tatu za ugunduzi.

Tabaka la kwanza -- regex: Inapata vitambulisho vilivyoundwa. SSNs, MRNs, nambari za simu, vitambulisho vya mpango wa afya. Inategemewa kwenye miundo ya kudumu.

Tabaka la pili -- NER: Inatumia mifano ya transformer. Inapata majina, tarehe, na data nyeti katika maandishi ya masimulizi. Inafanya kazi ambapo regex haiwezi.

Tabaka la tatu -- vitengo maalum: Inashughulikia maumbo maalum ya tovuti. Mifumo ya MRN ya kibinafsi, vitambulisho vya wafanyakazi, misimbo ya kituo. Hakuna mfano wa kawaida unaoshughulikia hizi.

Zana za ML safi zinapungua kwenye maumbo mafupi na maandishi yasiyo ya Kiingereza. Zana za regex safi zinakosa data nyeti ambazo hazina lebo ya sehemu. Hakuna inayotosha peke yake.

Ni usanifu wa tabaka tatu tu uliofika viwango vya chini ya 5% vya kukosa katika utafiti. Hicho ndicho kiwango cha uzingatiaji wa HIPAA Safe Harbor.

Angalia mwongozo wetu kuhusu utambulifu wa HIPAA Safe Harbor kwa utafiti wa huduma za afya kwa hatua za mwisho.

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.