If your team runs the servers, the backups or the admin consoles for a French clinic, you may already be a health data host.
You do not need to sell "health cloud" for that to be true. You only need to touch the data on someone else's behalf.
And under the current French rulebook, being a host now means publishing where that data goes, who can reach it from outside Europe, and which of your suppliers sit in the chain.
Does your managed service count as health data hosting under the French HDS framework?
The French term is hébergeur de données de santé (health data host, "HDS"). The obligation to be certified comes from article L.1111-8 of the Code de la santé publique (CSP, the French Public Health Code). The HDS referential V2.0 sets out what certification requires.
V2.0 is the binding text today. Its cover page reads: "Version publiée par l’arrêté du 26 avril 2024 portant approbation du référentiel d'accréditation des organismes de certification et du référentiel de certification pour l'hébergement de données de santé à caractère personnel". It replaces the 2018 referential.
Three tests decide whether it reaches you.
Your role. Certification applies to anyone who "fournit tout ou partie d'un service d'hébergement de données de santé à caractère personnel et qui a la qualité de sous-traitant au sens de l’article 28 du RGPD". In plain terms: you provide all or part of a hosting service, and you act as a GDPR Article 28 processor.
The data. The data must be health data "telles que définies à l’article 4.15 du RGPD" (as defined in GDPR Article 4(15)).
The context. The data must be collected "à l’occasion d’activités de prévention, de diagnostic, de soins ou de suivi social ou médico-social" (during prevention, diagnosis, care, or social and medico-social follow-up).
Note "tout ou partie". A partial service is enough. Most MSPs who serve French healthcare clients will meet all three tests.
Which of the six HDS hosting activities do you actually perform, and when does administration and operation need its own certificate?
The referential quotes article R.1111-9 CSP, which lists six hosting activities:
- Providing and operating physical sites that house the infrastructure
- Providing and operating the hardware infrastructure
- Providing and operating the virtual infrastructure
- Providing and operating the application hosting platform
- "L'administration et l'exploitation du système d'information contenant les données de santé" (administration and operation of the system holding the health data)
- "La sauvegarde des données de santé" (backup of health data)
Activity 5 is the one MSPs need to read twice.
V2.0 defines it as "la maitrise des interventions sur les ressources mises à la disposition du client de l’Hébergeur" (control over interventions on resources made available to the client). It includes four tasks: nominative access rights with annual review, a secured access procedure, logging of accesses and their reasons, and prior validation of interventions.
Those tasks are "intrinsèques et obligatoires" (intrinsic and mandatory) to activities 1 to 4. If you do them only as part of activities 1 to 4, you do not need a separate activity 5 certificate. The text is explicit: "Il ne sera tenu de l’être que dans le cas où il exerce uniquement l’activité 5."
So the MSP that manages a client's environment on someone else's infrastructure, without providing activities 1 to 4 itself, is exactly the case that needs activity 5 certification.
Activity 6 is narrower than it sounds. It "doit être interprétée comme comprenant uniquement les sauvegardes" externalised. Backups intrinsically needed for activities 1 to 5 fall within those activities.
What does HDS V2.0 add on top of your ISO 27001 ISMS?
Exigence 01 (EXI 01) sets five conditions for a certificate. You need an ISMS certified to ISO 27001, "complétée des exigences définies au chapitre 5". Its scope must cover all your health data hosting activities. Your client contracts must meet chapter 6. You must meet the sovereignty rules in chapter 7. And you must give clients the presentation of guarantees in chapter 8.
The V2.0 change log confirms the referential now takes account of ISO 27001:2023 ("NF ISO/IEC 27001 : 2023").
Chapter 5 follows ISO 27001 clause by clause and adds HDS-specific requirements. The ones that change day-to-day MSP operations:
- Scope. The ISMS must cover all your processing of health data, "notamment les sauvegardes et les transferts de supports matériels de l’information" (EXI 04).
- Risk assessment. EXI 05 lists events you must consider at minimum. One of them is "Sujétion de l’Hébergeur ou des éventuels sous-traitants à des législations extra-européennes pouvant entrainer une violation des DSCP" (exposure to non-European laws that could lead to a breach of personal health data, DSCP).
- French language. Client interfaces must be available "au moins en langue française", and so must first-level support (EXI 07). Your Statement of Applicability must be available in French to auditors on request (EXI 08).
- Responsibility split. You must plan and control the division of security responsibilities between you and the client (EXI 13).
- Client verification. On request, you must provide the management summary of a technical audit of shared resources, by an independent auditor and dated "de moins de trois ans" (EXI 15).
The language rule is easy to miss if your service desk runs from a shared international hub.
If you already hold SecNumCloud 3.2 qualification from ANSSI, annex 1 maps ISO 27001 Annex A measures to SecNumCloud requirements. Read its caveat: "la correspondance ne signifie pas qu’il existe une équivalence". The matrix helps your application. It does not replace the HDS audit.
Where must health data be stored, and what happens when your support team works from outside the EEA?
Chapter 7 is titled "SOUVERAINETE DES DONNEES" (data sovereignty). This is where V2.0 bites hardest for MSPs with global delivery models.
The data localisation EEA rule comes first. EXI 28 applies whatever the activity, as soon as it involves storage. The host or its subcontractors "doivent stocker ces DSCP exclusivement au sein de l’Espace Economique Européen (EEE)". You must document the storage location and tell the client.
The text says the European Economic Area, not the EU.
Remote access is handled separately. Under EXI 29, access from a country outside the EEA must rest on a Commission adequacy decision under GDPR Article 45 or, failing that, on an Article 46 appropriate safeguard.
If you rely on Article 46, you must tell the client two things: that no adequacy decision exists, and which safeguards you put in place. For supplementary measures, the host "doit tenir compte" of EDPB Recommendations 01/2020 (version 2.0, adopted 18 June 2021).
For an MSP, that covers a follow-the-sun support rota, an offshore SOC, or a vendor engineer who connects from outside the EEA. Each is a remote-access path you must ground and disclose.
What must you publish about non-EEA transfers and third-country legal access?
EXI 30 covers a different exposure: the law your company, or a subcontractor, is subject to.
If you or a subcontractor in the hosting service are subject to the law of a country without an adequate level of protection, three items go in the client contract and to the certification body:
- the list of non-European laws under which you could be required to allow access not authorised by EU law, within the meaning of GDPR Article 48
- the measures you take to mitigate that risk
- the residual risks that remain despite those measures
The third item is the hard one. You have to write down what you cannot mitigate.
EXI 31 then makes it public. You must "rendre publiques et mettre à jour la cartographie des transferts des DSCP" (publish and maintain the map of health data transfers) outside the EEA, including remote access under EXI 29 and the risks under EXI 30.
The public statement takes one of three forms:
- With SecNumCloud 3.2 qualification for the certified activity: "Aucun risque d’accès imposé par la législation d’un pays tiers en violation du droit de l’Union".
- Without SecNumCloud and with no transfer outside the EEA: "Aucun transfert de données de santé à caractère personnel vers un pays tiers à l’espace économique européen".
- Without SecNumCloud and with transfers or third-country access risk: the chapter 8 table.
The information goes on "une page dédiée d’un site internet accessible". You send the URL to the certification body. The referential says that URL "a vocation à être publiée dans la liste des hébergeurs certifiés sur le site de l’ANS" (the list of certified hosts on the website of the Agence du Numérique en Santé).
Your transfer map is put "à la disposition du public" (available to the public).
What do your client contracts and your presentation of guarantees have to show about your subcontractors?
Chapter 6 opens with a duty to provide clients "un modèle de contrat conforme aux exigences règlementaires". EXI 17 to EXI 27 restate the clauses required by article R.1111-11 CSP. They include the scope of your certificate with issue and renewal dates, service quality indicators and penalties, data subject rights, the ban on using hosted data for other purposes, and reversibility.
The subcontractor rules run through both chapters:
- Contract. EXI 22 requires information on the use of external technical providers and your commitment to an equivalent level of protection, "dans le respect de l’article 28.4 du RGPD".
- Change control. You must control changes to your subcontractors' technical and organisational measures (EXI 06).
- Certificates. You give clients your HDS certificate and those of your HDS-certified subcontractors in the hosting activity (EXI 12).
- Continuity. If a certified subcontractor performs part of the service, you need a procedure for the risk "de perte ou de suspension de la certification du sous-traitant" (EXI 14).
Chapter 8 then standardises the disclosure. Its stated purpose is to let clients "avoir connaissance des différents acteurs sur lesquels leur fournisseur de service s'appuie".
The table has one row per actor. For each, it records the company name, its role (host or subcontractor), whether it is HDS certified (yes, no or exempt), whether it holds SecNumCloud 3.2, which hosting activities it performs, whether it accesses data from outside the EEA (and from which country), and whether it is subject to third-country access risk.
If your stack includes a hyperscaler, a backup vendor and a remote monitoring tool, each one is a candidate row. That is a third-party risk inventory, published to your clients.
What does 'reinforced European sovereignty by 2027 at the latest' mean for your roadmap today?
The preamble explains that V2.0 strengthens protection around transfers outside the EU, and that this is "une première étape". It continues: "des exigences renforcées en termes de souveraineté européenne seront ajoutées au plus tard en 2027, en cohérence avec les futurs référentiels européens", naming the EUCS cloud certification scheme.
That is a statement of intent. The referential says reinforced sovereignty requirements will be added by 2027 at the latest. It does not publish them, fix a date or set a transition period. Planning against requirements that do not yet exist is guesswork.
What you can do now is make V2.0 evidence easy to extend:
- Keep the EXI 28 storage map, the EXI 29 access paths and the EXI 30 law list as one register, not three documents.
- Tie each chapter 8 row to a named subcontractor contract and certificate.
- Record which activities depend on non-EEA access, so you can see your exposure if the bar rises.
How Aigis fits
Aigis treats HDS like every other source. Each EXI requirement is traced to a verbatim citation in the referential and mapped to the controls and evidence that satisfy it, next to your ISO 27001 and GDPR work. The platform keeps your subcontractor, storage and access records on one source-grounded record.
If you run services for French healthcare clients, see what that looks like for managed service providers.
FAQ
Do I need HDS certification if I only manage a client's environment hosted elsewhere? Likely yes, for activity 5. The referential says a host needs activity 5 certification "dans le cas où il exerce uniquement l’activité 5". If you also provide activities 1 to 4, the admin tasks are covered by those activities.
Can health data be stored outside the EEA under HDS V2.0? No. EXI 28 requires storage "exclusivement au sein de l’Espace Economique Européen (EEE)". Remote access from outside the EEA is a separate question under EXI 29.
Does SecNumCloud 3.2 qualification replace HDS certification? No. Annex 1 offers a correspondence matrix to ease the application and warns that correspondence does not mean equivalence. SecNumCloud qualification does change the EXI 31 public statement you publish.
Is there a fixed 2027 deadline for HDS? No. The preamble says reinforced sovereignty requirements will be added "au plus tard en 2027". No date, text or transition period is published in the referential.


