The short answer
HIPAA is US law and does not automatically apply to every organisation in the EU. It becomes relevant when US hospitals or research entities, US sites or subsidiaries, or services that process PHI are involved.
General orientation, not legal advice.
Why this matters now
HIPAA remains US law. Sitting in the EU does not by itself bring an organisation into scope. It becomes relevant when US partners, trial sites, or services that handle PHI are involved. PHI is the trigger, not every health-related fact outside that link.
What to do
- Check whether one of the three situations applies: work with US hospitals or research entities, studies with US sites or subsidiaries, or services that process PHI.
- Clarify whether an EU provider processes PHI for a covered entity as a business associate.
- Set the mapping and the contract before the project starts. Purpose limitation, consent and notification duties are cut differently from the GDPR.
What this means technically
For a bioinformatics infrastructure with a US link, the relevant pieces are data location, access layers, encryption, logging and breach workflows. Where PHI processing is spread across systems and regions, roles, key control and export paths should be modelled explicitly.
Common misunderstandings
-
Every organisation in the EU is subject to HIPAA.
HIPAA does not apply automatically. The trigger is the US partner, the US trial site, or the service that handles PHI.
-
Encryption and logs make a product HIPAA-certified.
Encryption and logs are building blocks. They are not a certification. Whether HIPAA applies depends on the US link.
Where to start
With the question of whether one of the three situations applies, and with the mapping and the contract before the start. If you want support with that, you can ask for an assessment. It does not replace US legal advice.
As of 15 November 2026
Not US legal advice and not a certification promise. As of 15 November 2026. US law needs specialised US legal advice.