anonym.legal

By · Last updated 2026-05-13

Nazaj na blogZdravstvo

ISO 27001 in HIPAA BAA za zdravstvo

HIPAA Sporazumi s poslovnimi partnerji zahtevajo 'zadovoljiva zagotovila' o ustreznih varovalkah. ISO 27001 se neposredno ujema s HIPAA 164.

May 13, 20268 min branja
ISO 27001 HIPAA BAAhealthcare vendor certificationHIPAA satisfactory assurances164.308 security controlsOCR audit evidence

Zahteva po zadovoljivih zagorilih v BAA

HIPAA-jev Pravilnik o zasebnosti ima jasno pravilo. Pokrite subjekte morajo podpisati Sporazume s poslovnimi partnerji (BAA). BAA je obvezen za vsakega partnerja, ki ravna z zavarovanimi zdravstvenimi informacijami (PHI). Vsak BAA mora vsebovati "zadovoljiva zagotovila". Ta zagotovila potrjujejo, da ima partner prave kontrole vzpostavljene. Kljucna pravila so v 45 CFR 164.308, 164.310 in 164.312.

Izraz "zadovoljiva zagotovila" v zakonu ni natancno opredeljen. Toda smernice OCR jasno povedo eno stvar. Zagotovila morajo temeljiti na resnicnih, dokumentiranih dokazih. Bolnisnica, ki podpise BAA brez preverjanja dejanskih kontrol partnerja, ne more dokazati dolzne skrbnosti. Ce pride pri tem partnerju pozneje do krsitve, se bolnisnica soca z resno tezavo.

Torej ISO 27001 tu pomaga. Certifikacija se ujema z vecino HIPAA-jevih potreb po kontrolah. Ujemanje ni popolno. HIPAA ima nekatera zdravstveno specificna pravila, ki jih ISO 27001 ne pokriva. Toda prekrivanje je dovolj siroko za vecino preverjanj dolzne skrbnosti pri BAA.

Preslikava kontrol

Kontrole ISO 27001 Annexa A se ujemajo z vsemi tremi skupinami varoval HIPAA.

Administrativne varovalke (164.308): Kontrole A.5 do A.8 zajemajo politike, vloge, kadrovska pravila in sledenje sredstev. Ustrezajo HIPAA-jevim potrebam po formalnem programu, dodeljenih vlogah, pravilih delovne sile in rezervnih nacrtih.

Fizicne varovalke (164.310): Kontrola A.11 pokriva fizicne zastitne ukrepe in zascito objektov. Ujema se z dostopom do objektov, uporabo delovnih postaj in kontrolami naprav.

Tehnicne varovalke (164.312): Kontrole A.9, A.10, A.12 in A.13 zajemajo dostop, sifriranje in operacije. Ustrezajo HIPAA-jevim potrebam po reviziji, celovitosti in prenosu podatkov.

Primer uporabe v zdravstvenem sektorju

Regionalni zdravstveni sistem obnovi preverjanje partnerjev. Ekipa za skladnost zahteva od podjetja za de-identifikacijo dokazilo o "ustreznih varovalkah". Podjetje poslje certifikat ISO 27001 in krizno preglednico kontrol. Preglednica poveze vsako ISO kontrolo s pristonim oddelkom HIPAA - 164.308, 164.310 in 164.312.

Usluzbenec za skladnost to vnese v datoteko BAA. Ta zapis ustreza potrebam revizije OCR. Ni potrebno posebno vprasalnikovanje s 150 vprasanji.

Skratka, ISO 27001 pokritim subjektom zagotovi trdno, ze pripravljeno dokazno osnovo za dolzno skrbnost pri BAA. Preberite, kako anonym.legal izpolnjuje te zahteve, na strani o varnosti in skladnosti in v dokumentih o pravni skladnosti.

Viri

Ste pripravljeni zaščititi svoje podatke?

Začnite z anonimizacijo PII z več kot 285 tipi entitet v 48 jezikih.

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.