← Industry Guides
HealthcareCRA Guide

EU Cyber Resilience Act Guide for Healthcare IT & Clinical Software Vendors

Default class for most products that are not medical devices, such as EHR, HIS and LIMS. Outside the CRA for software under Regulation (EU) 2017/745 or (EU) 2017/746. Important Class I when the core functionality is a listed category, such as identity management (Annex III, point 1)

Healthcare IT and clinical software vendors providing electronic health record systems, clinical decision support software, hospital information systems, laboratory information management systems, and health data integration platforms to EU healthcare organisations must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. Software that is a medical device under Regulation (EU) 2017/745 or an in vitro diagnostic medical device under Regulation (EU) 2017/746 is outside the CRA (Article 2(2)). Other healthcare software with digital elements is in scope and is default class unless its core functionality matches an Annex III category. Patient data, clinical networks and links to medical devices do not change the class.

Article 13Article 14Annex IAnnex IIIArticle 13Article 6
Deadline: 11 December 2027Classification: Default class for most products that are not medical devices, such as EHR, HIS and LIMS. Outside the CRA for software under Regulation (EU) 2017/745 or (EU) 2017/746. Important Class I when the core functionality is a listed category, such as identity management (Annex III, point 1)

Last updated 26 October 2026

CRA Scope and Classification for Healthcare IT Products

Healthcare IT products within CRA scope as products with digital elements include: electronic health record (EHR) systems distributed as installed software, clinical decision support platforms, laboratory information management systems (LIMS), picture archiving and communication systems (PACS), hospital information systems (HIS), patient monitoring integration platforms, and health data interoperability middleware.

Pure Software as a Service (SaaS) platforms - where the vendor hosts the software and the hospital accesses it via a browser - are services, and the CRA does not regulate them as products (recital 12). Directive (EU) 2022/2555 (NIS2) can apply to their providers. However, on-premise installed software and hybrid platforms with installed components are within CRA scope. Software that is a medical device under Regulation (EU) 2017/745, such as clinical decision support software with a medical purpose, is outside the CRA (Article 2(2)(a)). Software that is an in vitro diagnostic medical device under Regulation (EU) 2017/746 is also outside the CRA (Article 2(2)(b)). Other products are classified by core functionality (Article 7(1)). Annex III lists no clinical or health software category, so healthcare IT products that are not devices, such as most EHR, HIS and LIMS products, are default class. An interface to medical devices, such as an EHR link to infusion pumps, does not change the class. The patient safety effect raises the risk that the Article 13(2) cybersecurity risk assessment has to address. A product whose core functionality is identity management or privileged access management (Annex III, point 1) or a VPN (Annex III, point 5) is Important Class I. Vendors should conduct a scope assessment for each product line.

CRA reference:Article 2(2), Article 7(1), Article 13(2), Annex III

Annex I Security Requirements for Clinical Software

Clinical software vendors must satisfy Annex I requirements that address the specific vulnerabilities exploited in the numerous ransomware and data breach incidents targeting healthcare organisations:

  • Authentication: Access to patient data and clinical functions must require strong authentication. Shared ward logins and default administrative credentials are prohibited under CRA's secure default configuration requirement.
  • Role-based access control: Clinical software must enforce role-based access to ensure that clinical staff access only the patient data relevant to their care role.
  • Encryption: Patient health data at rest and in transit must be encrypted. HL7 FHIR API endpoints must use TLS with current cipher suites.
  • Security update delivery: Vendors must provide security updates for critical vulnerabilities and deliver them to all active installations within a reasonable timeframe.
  • SBOM maintenance: Clinical software frequently embeds healthcare-specific libraries (HL7 FHIR, DICOM, openEHR) alongside general-purpose components. A comprehensive SBOM must be maintained for each software version.
CRA reference:Annex I

CVD Policy and Article 13 for Healthcare IT Vendors

Healthcare IT vendors have been prominent targets for ransomware and data breach attacks, with several major incidents demonstrating the life-threatening consequences of clinical system downtime. Article 13 requires a formal, publicly accessible CVD policy - essential infrastructure that many healthcare IT vendors currently lack in structured form.

  • Define the scope of covered products clearly
  • Provide a submission channel accessible to healthcare security researchers and hospital IT security teams
  • Commit to acknowledgement within 5 business days and to security update delivery within reasonable timeframes for confirmed vulnerabilities
  • Address the sensitivity of healthcare disclosures - some healthcare vulnerabilities have immediate patient safety implications requiring urgent notification to hospital customers before public disclosure

CVD Portal's triage functionality supports routing of high-severity disclosures to immediate internal escalation workflows, critical for clinical software vendors where a vulnerability may require emergency communication to hospital customers.

CRA reference:Article 13(1), and

Article 14 Incident Reporting for Healthcare IT

Article 14 incident reporting obligations for healthcare IT vendors intersect with GDPR data breach notification (Article 33 GDPR - 72 hours to supervisory authority), NIS2 obligations for healthcare operators (significant incident reporting to national authority), and healthcare-specific national regulations in some member states.

  1. ENISA under CRA Article 14 (24-hour initial notification)
  2. National data protection authority if patient data is exposed (GDPR Article 33 - 72 hours)
  3. National competent authority for healthcare operators (NIS2 - for healthcare organisations themselves, but vendors should notify customers to enable their compliance)
  4. Hospital customers directly - given patient safety implications, direct customer notification must occur simultaneously with regulatory reporting

Vendors should maintain pre-agreed emergency contact protocols with all major hospital customers so that Article 14-level incidents trigger immediate direct communication without waiting for customer discovery.

CRA reference:Article 14(1), Article 14(2)

Conformity Assessment and Healthcare Standards

Default-class healthcare IT products can use Module A internal control (Article 32(1)). An Important Class I product can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today a Class I product needs a notified body (Module B plus Module C, or Module H). Vendors should use existing healthcare IT security certifications as supporting evidence:

  • ISO 27001 certification for the vendor's information security management system demonstrates operational security maturity and can support the Annex I Part II vulnerability management assessment.
  • HL7 FHIR security conformance testing supports the technical security requirements assessment for API-based products.
  • IHE Integration Profiles security-relevant profiles (ATNA - Audit Trail and Node Authentication) provide additional conformity evidence.
  1. Authentication and access control mechanisms (reflecting the elevated risk of clinical data unauthorised access)
  2. Security update delivery capability and historical update record
  3. SBOM completeness for all embedded components
  4. CVD policy operational status

Vendors serving national health service customers may also face national cybersecurity assessment requirements. Align CRA conformity assessment with these national assessment timelines where possible.

CRA reference:Article 32, Annex VIII

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is SaaS healthcare software (cloud-hosted EHR) subject to the CRA?+

Pure SaaS healthcare software - where no software component is installed on hospital infrastructure - is primarily subject to NIS2 digital service provider obligations rather than CRA product obligations. However, if the SaaS platform includes an installed component (desktop client, local integration engine, HL7 FHIR bridge installed on hospital servers), those installed components are products with digital elements subject to CRA. Hybrid deployment models - common in EHR where some processing is on-premise for performance or data sovereignty reasons - are likely within CRA scope for the installed portions.

How do we manage CRA compliance when our clinical software integrates with hundreds of different medical devices?+

CRA compliance applies to your software product, not to the third-party medical devices it integrates with. However, you must ensure that your software's integration interfaces (HL7, DICOM, proprietary device APIs) are secure - using authenticated, encrypted connections and validating data received from integrated devices. Your SBOM should document the device integration libraries you use. Vulnerabilities in the integration layer that could affect your software's security must be patched under your CRA vulnerability management obligations. Medical devices under Regulation (EU) 2017/745 are outside the CRA (Article 2(2)(a)), and their manufacturers handle device cybersecurity under that Regulation.

What are the CRA obligations for legacy clinical software still in use at hospitals?+

The CRA requirements apply from 11 December 2027. A product placed on the market before that date is subject to them only if it is substantially modified from that date (Article 69(2)). Legacy software already licensed and deployed before 11 December 2027 is therefore not subject to retroactive CRA conformity requirements. Article 14 reporting is the exception. It applies from 11 September 2026 to all in-scope products, also to products placed on the market before 11 December 2027 (Article 69(3)). If you continue to sell new licences of the same software from 11 December 2027, those new placements must be CRA-compliant. Continued security support for legacy software deployed before that date is an important customer commitment and may be contractually required. Hospitals should discuss CRA transition timelines with their clinical software vendors as part of their NIS2 supply chain security obligations.

Guides for related sectors

Home Health Monitoring Device ManufacturersManufacturers of connected home health devices, such as blood pressure monitors, pulse oximeters, blood glucose meters and smart scales, must first check whether each device is a medical device. A medical device under Regulation (EU) 2017/745 and an in vitro diagnostic medical device under Regulation (EU) 2017/746 are outside the CRA (Article 2(2)). Connected wellness devices with no medical purpose are in CRA scope. A wellness wearable with a health monitoring purpose is Important Class I (Annex III, point 19), and other wellness devices are default class. These devices collect sensitive physiological data in consumer home environments and must meet stringent security-by-design standards. The consumer deployment context means that usability and security must be engineered together, with automatic update mechanisms and clear end-of-support policies particularly important.Connected Laboratory Instrument ManufacturersManufacturers of connected laboratory instruments - including mass spectrometers, chromatography systems, automated liquid handlers, and scientific imaging systems with network interfaces - must comply with the CRA for their EU-market products. Laboratory instruments increasingly integrate with LIMS platforms, cloud data repositories, and remote diagnostic services, creating network exposure that the CRA directly addresses. Manufacturers must establish vulnerability disclosure programmes, maintain SBOMs for complex instrument software stacks, and implement Article 14 notification procedures. An instrument that is an in vitro diagnostic medical device under Regulation (EU) 2017/746 is outside the CRA (Article 2(2)(b)). Other instruments are default class, because Annex III lists no laboratory instrument category.Medical Device ManufacturersThe Cyber Resilience Act does not apply to medical devices under Regulation (EU) 2017/745, the MDR, or to in vitro diagnostic medical devices under Regulation (EU) 2017/746, the IVDR (Article 2(2)). Software as a Medical Device (SaMD) that is a device under those Regulations is also outside the CRA. The cybersecurity of those devices follows the MDR and IVDR general safety and performance requirements and the guidance MDCG 2019-16. A medical device manufacturer still has CRA obligations for its other products with digital elements, such as wellness wearables and software that is not a device. Those products are default class unless their core functionality matches an Annex III category.Pharmaceutical Manufacturing Automation VendorsPharmaceutical manufacturing automation vendors - supplying SCADA systems, batch management software, process analytical technology (PAT) platforms, and manufacturing execution systems (MES) to EU pharmaceutical manufacturers - must comply with the CRA for their products. The intersection of CRA cybersecurity requirements and EU GMP computerised systems validation (CSV) obligations creates a dual compliance framework that demands careful coordination between security and validation activities. CRA non-compliance by automation vendors directly threatens their customers' GMP compliance status and product supply security.

This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Need a CVD policy template for Healthcare IT & Clinical Software Vendors?

Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.

Browse templates →