By · Last updated 2026-06-05

Rudi kwa BlogHuduma za Afya

HIPAA OCR: Uvunjaji 725, Rekodi Milioni 275

HHS OCR iliripoti uvunjaji 725 wa HIPAA mwaka 2024 uliathiri rekodi milioni 275 — kiwango cha juu zaidi kilichowahi kurekodi. Gharama ya wastani ya uvunjaji wa huduma za afya ni dola milioni 10.22.

June 5, 202610 dakika kusoma
HIPAA enforcementPHI de-identificationOCR HHShealthcare breachHIPAA Security Rule

HIPAA OCR: Uvunjaji 725, Rekodi Milioni 275

Imesasishwa kwa 2026

Ofisi ya Haki za Kiraia ya HHS (OCR) ilihesabu uvunjaji 725 wa data ya huduma za afya mwaka 2024. Uvunjaji huo uliathiri rekodi milioni 275 za wagonjwa. Jumla hiyo ni ya juu zaidi iliyowahi kurekodi katika mwaka mmoja.

Gharama ya wastani kwa kila uvunjaji wa huduma za afya ilifikia dola milioni 10.22 mwaka 2025. Ripoti ya Gharama ya Uvunjaji wa Data ya IBM inaonyesha nambari hiyo. Gharama inashughulikia faini za kiraia, ada za kisheria, taarifa za wagonjwa, ufuatiliaji wa mikopo, na kupoteza imani.

Miaka 2025 na 2026 ni muhimu kwa vyombo vilivyo na bima na washirika wao wa biashara. Sasisho lililopendekezwa la Kanuni ya Usalama ya HIPAA kutoka Machi 2025 litaongeza seti kubwa zaidi ya sheria za kiufundi tangu 2003.

Kilichosababisha Uvunjaji 725 Mwaka 2024

Mlango wa OCR unakusanya kushindwa kwa 2024 katika aina nne.

Udukuzi na matukio ya IT yalisababisha 74% ya uvunjaji ulioripotiwa. Ransomware, mashambulio ya seva, na udanganyifu wa barua pepe ni aina kuu. Washambuliaji sasa wanalenga mitandao nzima. Shambulio moja linaweza kuvuta rekodi kutoka kwenye mfumo mzima wa EHR mara moja.

Upatikanaji na ufafanuzi usioidhinishwa ulisababisha 18% ya uvunjaji. Udhibiti mbaya wa upatikanaji, matumizi mabaya ya watu wa ndani, na makosa ya mpokeaji mwingine yote yanashughulikiwa hapa.

Matukio ya wahusika wengine yalichangia 35% ya uvunjaji wa 2024. Kushindwa kulianza kwa mshirika wa biashara — si chombo kilichofunikwa. Change Healthcare (kitengo cha UnitedHealth Group) peke yake ilifichua rekodi zaidi ya milioni 190 za wagonjwa. Hiyo ni uvunjaji mkubwa zaidi wa data ya afya wa Marekani kuwahi kurekodi.

Wizi au upotezaji wa vyombo vinavyobebeka ulisababisha 8% ya uvunjaji. Kompyuta za mkononi, anatoa za USB, na rekodi za karatasi zilizopotea au kuibiwa bila usimbuaji.

Aina 18 za PHI Chini ya Njia ya Salama

Njia ya Salama ya HIPAA (45 CFR §164.514(b)) inahitaji kuondolewa kwa aina 18 zote za data ya mgonjwa. Timu nyingi zinajua orodha. Sehemu ngumu ni utambuzi kwa kiwango kikubwa.

  1. Majina — wagonjwa, wanafamilia, waajiri
  2. Data ya kijiografia — eneo lolote dogo kuliko jimbo
  3. Tarehe — kulazwa, kutolewa, kuzaliwa, kufariki (mwaka unaweza kubaki)
  4. Nambari za simu
  5. Nambari za faksi
  6. Anwani za barua pepe
  7. Nambari za usalama wa jamii
  8. Nambari za rekodi za matibabu (umbizo linatofautiana kwa mfumo wa EHR)
  9. Nambari za wanachama wa mpango wa afya
  10. Nambari za akaunti
  11. Nambari za vyeti na leseni — matibabu, DEA, jimbo
  12. Vitambulisho vya magari — nambari za VIN na sahani
  13. Vitambulisho vya vifaa — nambari za serial na nambari za kipekee za kifaa
  14. URL za wavuti
  15. Anwani za IP
  16. Data ya biometric — alama za vidole na alama za sauti
  17. Picha za uso kamili na picha zinazofanana
  18. Kitambulisho, nambari, au sifa nyingine yoyote ya kipekee

Aina 18 ndiyo ngumu zaidi kukamata. Nambari yoyote inayounganisha rekodi na mgonjwa maalum lazima iondolewe — hata bila muundo uliowekwa.

Kwa mwongozo wa hatua kwa hatua wa kusafisha aina zote 18 kutoka kwa rekodi za kliniki, angalia Kutoa utambulisho wa HIPAA Safe Harbor kwa utafiti wa huduma za afya.

Sheria Tano Mpya Katika Sasisho Lililopendekezwa la Usalama

Sasisho lililopendekezwa la Kanuni ya Usalama ya HIPAA (Machi 2025) linaongeza wajibu tano.

Ukaguzi wa usimbuaji wa kila mwaka. Vyombo vilivyofunikwa lazima vithibitishe kwamba data yote ya wagonjwa iliyohifadhiwa inatumia AES-256 au sawa. Usimamizi wa ufunguo lazima ukidhi viwango vilivyoandikwa.

Taratibu zilizoandikwa za kutoa utambulisho. Data yoyote ya wagonjwa inayotumiwa katika utafiti, mafunzo ya AI, au uchanganuzi inahitaji hatua zilizoandikwa. Kumbuka ya sera haitoshi. Rekodi za kiufundi zenye uthibitisho wa uthibitishaji zinahitajika.

Ukaguzi wa usalama wa washirika wa biashara. Washirika wa biashara lazima wapite ukaguzi maalum wa kiufundi kabla hawajaanza. Mikataba ilikuwa inashughulikia hili bila maelezo ya kiufundi.

Uthibitishaji wa vipengele vingi (MFA). Wafanyakazi wote wenye ufikiaji wa data ya kielektroniki ya wagonjwa lazima watumie MFA. Mifumo ya zamani haiko isipokuwa.

Mazoezi ya mwitikio wa matukio. Mazoezi ya kila mwaka na majaribio ya kiufundi yanahitajika. Timu lazima zihifadhi rekodi za matokeo.

Mafunzo Kutoka Change Healthcare

Uvunjaji wa Change Healthcare (Februari 2024) ulionyesha jinsi hatari ya kimfumo inavyoonekana. Change Healthcare ilishughulikia miamala bilioni 15 kwa mwaka. IliUnganisha watoa huduma, walipa, na maduka ya dawa kama kituo cha uhamishaji.

Uvunjaji ulianza na akaunti moja ya upatikanaji wa mbali. Akaunti hiyo haikuwa na MFA. Washambuliaji walisogea kwenye mtandao kwa siku tisa. Kisha wakazindua ransomware.

Somo ni wazi. Mshirika wa biashara mwenye ufikiaji mkubwa wa miamala ya afya ni hatari kwa kila mshirika anaogusa. Mfumo wa zamani haukuundwa kwa watoa huduma wanaoshughulikia theluthi moja ya miamala yote ya afya ya Marekani.

MFA, mgawanyiko wa mtandao, na ukaguzi wa washirika wa biashara wa kanuni iliyopendekezwa yote yanafuatilia tukio hili.

Kwa kuondoa PHI kutoka kwa umbizo la rekodi mahususi za hospitali, angalia Utambuzi wa MRN wa HIPAA na mifumo mahususi ya hospitali. Kwa muundo wa zero-knowledge unaoweka data ya wagonjwa nje ya mtandao, angalia PHI ya wingu inayozingatia HIPAA na muundo wa zero-knowledge.

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.