An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 for Healthcare Organisations
High Criticality Sectors / 2026-10-11

NIS2 for Healthcare Organisations

The NIS2 Annex I health sector includes defined healthcare providers, EU reference laboratories, certain medicinal-product research and manufacturing entities, and manufacturers of specified critical medical devices. Coverage depends on the exact legal category, size and exceptions. Healthcare organisations need cybersecurity measures that protect care continuity, clinical data and systems, alongside national NIS2 notification requirements.

Identify the healthcare entity type

Annex I covers healthcare providers as defined by Directive 2011/24/EU, EU reference laboratories referred to in Regulation (EU) 2022/2371, entities researching and developing medicinal products, manufacturers of basic pharmaceutical products and pharmaceutical preparations, and manufacturers of medical devices considered critical during a public health emergency. A health technology supplier or wellness service should not assume coverage solely because it works with hospitals. Map the specific legal activity and entity.

Apply scope and classification rules

Article 2 and Article 3 determine which entities are in scope and how essential or important status is assigned. Size calculations and special inclusion routes must be assessed for the actual legal entity, with relevant national provisions taken into account. A hospital group, medicines manufacturer and clinical laboratory may have distinct operations and classifications. Preserve the rationale rather than relying on a broad statement that all healthcare organisations are essential.

Connect cybersecurity to patient safety and care delivery

For healthcare providers, system disruption can affect electronic health records, diagnostics, medication administration, medical-device connectivity, appointment systems and clinical communications. Article 21 requires proportionate risk-management measures addressing incident handling, continuity, supplier security, secure systems and testing. Security changes should be coordinated with clinical risk owners because poorly planned downtime or software updates can themselves affect patient care.

Plan for incidents affecting clinical services

An incident may involve unavailable clinical systems, compromised records or disruption to outsourced diagnostic services. Set escalation routes that connect clinicians, technology teams, information governance, senior management and relevant authorities. Significant-incident reporting under NIS2 Article 23 depends on the applicable legal criteria and national law. Data protection notifications and medical-device or patient-safety reporting may be separate duties; one filing should not automatically be assumed to satisfy another.

Produce an evidence-based improvement plan

Keep the Annex I scope analysis, inventory of care-critical systems, risk assessments, tested downtime procedures, supplier reviews and management oversight records. Exercises should examine how services continue when electronic systems are unavailable and how restoration is validated. Track remediation by patient-care impact and technical risk, and update the assessment after new facilities, equipment or care models are introduced.

Points of clarification

Does NIS2 cover all health-related businesses?

No. Coverage depends on the defined Annex I entity categories and scope rules.

Is a hospital automatically an essential entity?

Not necessarily. The classification requires assessment under Article 3 and relevant national rules.

What cybersecurity risk is particularly important in healthcare?

Maintaining safe care when clinical systems, data or connected services are disrupted.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.