1. Who in healthcare is involved
The healthcare sector is listed in Annex I of Directive (EU) 2022/2555. The list covers healthcare providers, reference laboratories, research and development activities on medicinal products, manufacturers of basic pharmaceutical products and certain manufacturers of medical devices considered critical in a health emergency. Not all facilities are covered in the same way: what matters is the actual activity and the size of the organisation.
A small private facility may fall outside the scope, while a larger one may fall within it. The first step is to read the definitions with your own activity in mind and to ask your adviser or the competent authority for confirmation. GDPR applies regardless of NIS2, so patient data must be protected in every case, even if your facility is outside the directive's scope.
2. Clinical data and availability: two goals to hold together
Health data is one of the special categories of personal data under the GDPR and requires greater care: access by role, logging of operations, minimisation of the data collected. At the same time, the clinical record, bookings and diagnostic images must be available when needed. A system locked by an attack can compromise care just as a data leak compromises confidentiality. For this reason, every choice must be assessed on both fronts.
Measures should therefore be decided together. Overly rigid access controls can block a ward at night; availability without controls exposes the data. For each system, establish which objective prevails in the event of a conflict, write it into the continuity plan and have it approved by whoever is accountable for the facility, so that the choice does not fall on the individual operator during an emergency.
3. Connected devices: the inventory that is usually missing
Diagnostic instruments, pumps, monitors, radiology equipment and laboratory systems are often connected to the network. Many have long lifecycles, operating systems that are no longer updated or technical support that works remotely. Every connected device should be inventoried, along with its manufacturer or maintainer, the network it is connected to and the access methods used. A device without an identified owner is the hardest to protect.
Separating the clinical device network from the administrative network is often the most effective and least costly measure. Ask your maintenance supplier how it separates connections, which remote accesses it uses and how they are recorded. If you do not receive a clear and verifiable answer, that is a signal to investigate before renewing the contract. It is not a judgement on the supplier, but a request for clarity that any good supplier should be able to meet.
4. Software and remote maintenance suppliers
Many healthcare systems are run by external suppliers: clinical software, booking systems, image archiving, device support. Every supplier with access to your systems forms part of your risk management. The contract must state who can access, with which credentials, for which activities and how the facility will be alerted in the event of an incident, rather than leaving these arrangements to unwritten practice.
The most overlooked point is remote maintenance. Support access left open, active even when nobody is using it, is a door that is always open. Require that access is enabled on request, logged and disabled at the end of the work, and keep the logs together with the service reports. That way, if audited, you can show who intervened, when and with which privileges, without reconstructing everything after the fact.
5. What to check, area by area
The table collects the essential questions. It is not a complete checklist, but it helps order priorities and assign responsibility for each area. Each row is designed for a short meeting between clinical management, the IT department and purchasing, with a written answer to revisit at the next meeting. Anyone without an answer at the meeting must name a person and a date by which one will be provided.
| Area | Question to ask | Who usually answers |
|---|---|---|
| Clinical data | Which systems hold it and who can access them? | Clinical management with the systems manager |
| Connected devices | Which equipment is on the network and with which operating system? | Clinical engineering with the IT department |
| Suppliers | Which remote accesses exist and who controls them? | Contract manager with the IT department |
| Continuity | How do we work if a system is down for hours? | Management with department heads |
6. The obligations in practice, and the deadlines
NIS2 requires risk management, incident response procedures, business continuity, supply chain security and staff training, with the measures approved by the management body. For entities within scope, the reporting deadlines are an early warning within 24 hours of becoming aware of a significant incident and a notification within 72 hours. The required measures must be written down, not just practised.
If the personal data involved is health data, the breach must also be assessed under the GDPR, which requires notification to the data protection authority within 72 hours where the conditions apply. The two assessments run in parallel, so it is best to have a single incident management process with two clearly defined notification routes and a named contact for each. The contact must know what to communicate and to whom, without having to search for the template during an emergency.
- Risk analysis and system security policies
- Procedures to detect, contain and document incidents
- Verified backups and recovery plans for clinical systems
- Access control, with multi-factor authentication where possible
- Management of supplier and remote maintenance access
- Regular staff training
7. How to get started
This week, build a list of the devices and systems connected to the network, with each one's supplier, and a list of active remote access accounts. Compare them with the maintenance contracts in force. You will quickly see which accesses have no owner and which part of the network should be separated first, and you will be able to bring your adviser a concrete basis for the assessment.
Frequently Asked Questions
Is a small private clinic covered by NIS2?
It is not possible to say in the abstract. The healthcare sector is included, but the scope depends on the type of activity and on size, with exceptions for some categories. A small facility may fall outside the scope, but its obligations on the processing of personal data remain. Check your position with your adviser before drawing a conclusion.
Does the GDPR alone cover the security of health data?
The GDPR covers the protection of personal data, through principles such as minimisation and confidentiality. NIS2 concerns the resilience of services and the management of cyber risk at organisational level. These are two different things that overlap only in part. For a facility subject to both, a single incident management process with two notification routes is needed.
Do I have to replace old devices to be compliant?
The directive does not require replacing a device because of its age. It requires its risk to be managed: inventory, network separation, access control and plans for cases where it cannot be updated. Replacement becomes the right choice when residual risk cannot be managed, but this should be decided case by case with the manufacturer and the department.
What guarantees should I ask from the maintenance supplier?
Ask in writing how it manages remote access, who authorises it, how it is recorded and within what timeframe it will alert the facility of an incident. Also ask which sub-suppliers work on the systems. Do not accept a generic statement: you want verifiable answers, linked to the contract. A serious supplier provides them without difficulty.
Who within the facility should deal with NIS2?
Responsibility for risk management rests with the management body, which must approve the measures and oversee their implementation. In practice you need an operational contact, often the systems manager, to coordinate IT, clinical engineering, clinical management and purchasing. Define roles in writing, so that responsibility is not lost in handovers.