Independent reporting on data, AI and digital regulation in Luxembourg

Public sector · News

Health data hosting in Luxembourg: no prior certification and no central register, government confirms

Luxembourg requires no specific certification for IT providers hosting patient data and keeps no central register of them, the government said on 2 November 2026.

Key takeaways

  • In a joint answer dated 2 November 2026 to parliamentary question No. 4718 by MP Liz Braz, the Ministers of Health and of Digitalisation confirm that neither the GDPR nor the NIS2 law of 5 May 2026 requires a prior approval or certification for providers hosting health data.
  • The CNPD keeps no central register of the processors, sub-processors and cloud providers active in health in Luxembourg; a general map would need a legal basis with a prior notification duty.
  • The Agence eSanté attestation for connecting software to the shared care record (DSP) covers only exchanges with the national platform, not the provider's hosting, backups or business continuity, and has no periodic renewal.
  • The answer states it would be for the national legislator to create a specific approval or certification scheme, for example along the lines of French law; it announces no such project.
  • The provider hit by the August 2026 incident informed the Agence eSanté on 27 August 2026; the Agency's systems were not affected.

Luxembourg imposes no specific certification or prior approval on the IT providers that host, process or back up patient data for doctors, and no authority holds a central register of them. That is the substance of a joint answer by the Minister of Health and Social Security, Martine Deprez, and the Minister for Digitalisation, dated 2 November 2026, to parliamentary question No. 4718 filed on 7 September 2026 by LSAP MP Liz Braz after a cyber incident at an IT provider serving medical practices.

What the government said

The answer walks through three frameworks and finds no prior check in any of them.

Framework Authority Prior or periodic check of hosting providers?
GDPR (Articles 28 and 32) CNPD No. Control happens after the fact, under the accountability principle
NIS2 law of 5 May 2026, in force since 10 May 2026 ILR No approval or certification before the service is provided
DSP connection attestation (grand-ducal regulation of 6 December 2019) Agence eSanté Covers only exchanges with the national platform; no periodic renewal

The NIS2 law applies automatically to medium and large entities in health, digital infrastructure and B2B ICT service management. Small and micro providers are not automatically in scope, although the ILR can identify one as an essential entity. Entities in scope must self-register with the ILR.

The CNPD, the answer says, has no central register of the controllers, processors, sub-processors and cloud providers active in health. Building a general map would need, at the very least, a legal basis with a duty to notify the regulator in advance. The GDPR also prescribes no backup architecture or geographic redundancy, only “appropriate” measures that can restore access to data in good time.

On a possible dedicated regime, the answer states that it would be for the national legislator to create one, citing Article L. 1111-8 of the French public health code, which requires a certificate from an accredited body. No bill or timetable is announced.

Why it matters

Who, in your practice or clinic, knows where the backups of your patient records physically sit, and who else holds them?

No authority checks this for you. The DSP attestation tells you the software talks correctly to the national platform. It says nothing about whether your provider can restore your data after a cyberattack. The answer is explicit on that point.

The good news: the GDPR already hands the controller the tools. Article 28 gives you the right to authorise every sub-processor and to audit your provider.

The provider at the origin of the question informed the Agence eSanté on 27 August 2026. The Agency checked its own systems and interfaces, found them unaffected, and asked to receive the provider’s conclusions. According to the question, the incident interrupted access to medical software and patient histories.

What to do now

  1. Ask your IT provider in writing for the full list of sub-processors and cloud providers, with the location of primary and backup infrastructure.
  2. Check that your contract contains the Article 28(3)(h) GDPR audit right and use it: ask for evidence of a tested restore.
  3. Ask whether backups are isolated so that an attack on the main system cannot also encrypt them.
  4. If you are an IT provider of medium or large size, confirm your NIS2 registration with the ILR; see the Luxembourg NIS2 law overview.
  5. Do not treat encryption or the DSP attestation as proof of compliance. Document your own risk assessment.

Questions & answers

Do IT providers hosting patient data in Luxembourg need a certification?

No. According to the government's answer of 2 November 2026, neither the GDPR nor the NIS2 law of 5 May 2026 makes a specific approval, certification or audit a precondition for hosting health data. GDPR codes of conduct and certifications exist but are voluntary.

Can a Luxembourg doctor's IT provider pass patient data to a cloud sub-processor?

Only with the doctor's prior written authorisation, specific or general, under Article 28(2) GDPR. With a general authorisation the provider must announce any added or replaced sub-processor so the doctor can object, and the initial provider remains fully liable.

Does the Agence eSanté DSP attestation prove a provider's hosting is secure?

No. The attestation certifies that the software's exchanges with the national platform meet the DSP interoperability rules. It does not assess the software's intrinsic security, the hosting infrastructure, backups or business continuity.

Does encrypting health data remove GDPR obligations?

No. The answer states that encryption is a security measure under Article 32 GDPR but does not change the data's status as personal data, so information, sub-processing and control obligations still apply.

Sources

  1. Réponse commune à la question parlementaire n° 4718 (2 November 2026) · Chambre des Députés
  2. Question parlementaire n° 4718, Sécurité de l'hébergement des données de santé (7 September 2026) · Chambre des Députés
  3. Question parlementaire n° 4718, dossier · Chambre des Députés

Written and fact-checked against primary sources.