Sovereign Cloud for Healthcare
Health data is the most sensitive category most organisations will ever hold. Certifications (HDS in France, IRAP for Australian health, sectoral rules elsewhere) plus privacy law make residency and control non-negotiable.
Health-data requirements
| Regime | Jurisdiction | Cloud relevance |
|---|---|---|
| HDS (Hébergement de Données de Santé) | 🇫🇷 France | Certification required to host French health data |
| My Health Records + Privacy Act | 🇦🇺 Australia | Residency expectations and APP compliance |
| GDPR (special categories) | 🇪🇺 EU | Health = Article 9 special-category data; strict conditions |
| IRAP / ISM | 🇦🇺 Australia | Assessment for public health systems |
| NHS data regimes | 🇬🇧 United Kingdom | Health data residency and security standards |
Provider options
| Provider | Health-relevant qualifications | Fit | Profile |
|---|---|---|---|
| OVHcloud | HDS, SecNumCloud | French health-data hosting | Read → |
| AUCloud | IRAP, ISO 27001 | Australian public health | Read → |
| AWS | IRAP, HIPAA-eligible | Global health platforms | Read → |
| Microsoft Azure | IRAP, HDS-compatible | Health AI and platforms | Read → |
| S3NS | HDS (targeted) | French sovereign AI for health | Read → |
AI in healthcare
Clinical AI raises the stakes: models trained on patient data, inference on identifiable data, and the EU AI Act's high-risk classification for medical AI. Sovereign AI procurement for health should pin down training location, prompt retention and de-identification policy. See Sovereign AI.