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 Hospitals
High Criticality Sectors / 2026-10-11

NIS2 for Hospitals

Hospitals can fall within the NIS2 health sector as healthcare providers defined in EU law. Whether a particular hospital is covered, and whether it is essential or important, depends on its legal entity, the NIS2 scope and classification criteria, and national implementation. Cybersecurity planning should account for safe clinical continuity as well as protection of patient information.

Why hospitals appear within the healthcare sector

Annex I of Directive (EU) 2022/2555 includes healthcare providers as defined in Article 3(g) of Directive 2011/24/EU. Hospitals delivering healthcare may satisfy that definition, but the applicable assessment is made for the organisation's legal entity. A hospital's public or private status alone is not a complete scope test. Identify the provider operating the hospital and the Member State legal rules that apply to it.

Determine classification and organisational boundaries

Articles 2 and 3 set the general scope and essential-or-important classification framework, including size criteria and exceptions. A hospital group can contain separate clinical operators, laboratories and shared-service entities. Record which organisation is responsible for the care service and which systems it operates. A hospital should not claim automatic essential status without checking the precise classification route and national designations.

Focus security measures on clinical operations

Disruption of electronic health records, imaging, laboratory reporting, pharmacy systems or connected devices can delay treatment and introduce safety risks. Apply Article 21's measures to the network and information systems supporting care, including access management, supplier security, incident handling and business continuity. Cybersecurity changes should be reviewed for clinical impact, especially where patching or isolation might interrupt patient monitoring or urgent services.

Test downtime and incident notification processes

Clinical teams should rehearse how to deliver care when critical electronic systems are unavailable, including patient identification, prescribing, communication and recovery of records. Define who decides when a cyber event is significant and how the legal team and incident responders coordinate Article 23 reporting through the national channel. Data protection and medical-device safety reporting may also be relevant, but those regimes require separate assessments rather than assuming one notification satisfies every duty.

Maintain an evidence-based hospital programme

Keep service inventories, care-critical system maps, risk assessments, recovery exercise outcomes, supplier dependencies and remediation decisions. Present material patient-care risks to the relevant management body for informed approval and oversight. Review the programme when the hospital acquires new clinical equipment, expands services or changes outsourced system providers.

Points of clarification

Are all hospitals automatically essential entities under NIS2?

No. A hospital must be assessed under the applicable NIS2 scope and classification provisions and national law.

Does NIS2 require hospitals to protect clinical systems?

Covered healthcare providers must apply proportionate cybersecurity risk-management measures to relevant network and information systems.

Can GDPR breach reporting replace NIS2 reporting?

No. The legal tests and reporting routes are separate and must be assessed independently.

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.