EU Cyber Resilience Act Guide for Telemedicine & Remote Patient Monitoring Vendors
Outside the CRA for medical devices under Regulation (EU) 2017/745 and in vitro diagnostic devices under Regulation (EU) 2017/746 (Article 2(2)). In-scope products are default class, except a personal wearable with a health monitoring purpose outside those Regulations, which is Important Class I (Annex III, point 19)
The CRA does not apply to products to which Regulation (EU) 2017/745 (MDR) or Regulation (EU) 2017/746 (IVDR) applies (Article 2(2)). A telemedicine or remote patient monitoring (RPM) product that is a medical device is regulated for cybersecurity under the MDR. Vendors must determine precisely which products are medical devices under the MDR and which are software or connectivity products outside it. Those other products are in CRA scope and are classified by core functionality (Article 7(1)). Security failures in RPM devices - which transmit real-time physiological data from patients' homes - carry both patient safety and data protection consequences, making robust security engineering a clinical as well as regulatory obligation.
Last updated 26 October 2026
CRA Scope and Interaction with the Medical Device Regulation
The CRA does not apply to products with digital elements to which Regulation (EU) 2017/745 (MDR) or Regulation (EU) 2017/746 (IVDR) applies (Article 2(2)). A telemedicine device or a piece of software that is a medical device under the MDR, including Software as a Medical Device (SaMD), is therefore outside the CRA. Annex I to Regulation (EU) 2017/745 already sets cybersecurity requirements for these devices, including minimum IT security measures and protection against unauthorised access. The MDR conformity assessment covers them.
Products that the MDR and the IVDR do not cover are in CRA scope. Examples are telemedicine software without a medical intended purpose, video consultation software, practice administration software and wellness devices. Classification follows core functionality (Article 7(1)). Most of these products are default class. A personal wearable with a health monitoring purpose to which Regulation (EU) 2017/745 or (EU) 2017/746 does not apply is Important Class I (Annex III, point 19). Commission Implementing Regulation (EU) 2025/2392 names fitness trackers, smartwatches, smart jewellery and smart clothing that sense health-relevant information. A wearable intended for use by children under 14 is also Important Class I. Vendors must document for each product whether the MDR applies and, if it does not, its CRA class.
Technical Security Obligations for Remote Patient Monitoring
RPM devices transmitting patient physiological data from home environments present a challenging security profile: they must be simple enough for non-technical patients to operate, while securing sensitive health data in transit and at rest. Annex I requirements for RPM vendors include: encrypting all patient data transmissions using current TLS versions; implementing authentication that is accessible to elderly or technically inexperienced patients while preventing unauthorised access; ensuring device firmware updates are automatically available without requiring patient action; eliminating default credentials; implementing data minimisation - collecting only the physiological parameters required for clinical purpose; and providing documented procedures for data erasure when a device is returned or repurposed. The SBOM must cover firmware components in patient-side devices and server-side processing platforms. Vendors must also ensure cloud back-ends have appropriate access controls preventing data aggregation beyond clinical necessity. These Annex I requirements apply to RPM products in CRA scope. An RPM device that is a medical device under Regulation (EU) 2017/745 is outside the CRA and follows the general safety and performance requirements in Annex I to that Regulation (Article 2(2)).
CVD Policy Under Article 13 for Healthcare Technology
Article 13 requires a published CVD policy. For telemedicine vendors, the CVD policy for in-scope products must operate alongside the requirement under GDPR to report personal data breaches within 72 hours of discovery. It must also operate alongside MDR post-market surveillance for any medical devices in the same portfolio. The CVD policy should specify: a dedicated security reporting contact; coordination procedures with the relevant competent authority (e.g. national medical device authority) for vulnerabilities with patient safety implications; how vulnerability information is shared with healthcare provider customers using the platform; and how security updates are communicated to patients using home-based devices. Because RPM devices process special category health data under GDPR Article 9, the CVD policy should address the privacy implications of vulnerability reports and researcher access to test environments. Separate from the CVD policy, the vendor's post-market surveillance plan under MDR must incorporate cybersecurity monitoring.
Article 14 Incident Reporting and Patient Safety Coordination
Article 14 requires notification to the relevant national CSIRT within 24 hours of confirmed active exploitation. For an RPM product in CRA scope, exploitation scenarios can also require GDPR data breach notification to the data protection authority within 72 hours. Examples are unauthorised access to patient vitals data, manipulation of device readings that could affect clinical decisions and denial-of-service attacks that disrupt monitoring. Article 14 does not apply to a medical device (Article 2(2)). For a medical device, Regulation (EU) 2017/745 Article 87 serious incident reporting to the competent authority applies instead, within 15 days for serious incidents or 2 days for a serious public health threat. Vendors must design their incident response plan to trigger all applicable notification streams simultaneously. Where one incident affects both a medical device and an in-scope product, for example through a shared back end, the CRA notification, the GDPR breach notification and the MDR serious incident report must be consistent and cross-referenced. Legal counsel should be engaged in drafting incident response playbooks to ensure multi-regulatory compliance.
Conformity Assessment for MDR Devices and CRA Products
A medical device under Regulation (EU) 2017/745 follows the MDR conformity assessment only, because the CRA does not apply to it (Article 2(2)). The MDR assessment covers its cybersecurity under Annex I to that Regulation. There is no CRA conformity assessment for that device.
An in-scope telemedicine product that is default class can use Module A internal control (Article 32(1)). A personal health-monitoring wearable outside the MDR and the IVDR is Important Class I (Annex III, point 19). It can use Module A only when it fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level substantial or higher (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so such a wearable needs a notified body for now (Module B plus Module C, or Module H). The CRA technical file must cover the SBOM, the CVD policy documentation, the Article 14 notification procedures and post-market vulnerability monitoring. A vendor with both medical devices and in-scope products must assess the scope of each product under each Regulation independently. The cybersecurity evidence compiled for MDR devices can support the CRA technical file of a related in-scope product.
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
Our RPM platform is a Class IIa medical device under MDR with notified body certification. Do we still need a separate CRA assessment?+
No. The CRA does not apply to products to which Regulation (EU) 2017/745 applies (Article 2(2)). Your Class IIa RPM platform is outside the CRA, and the MDR notified body certification covers its cybersecurity under Annex I to that Regulation. The CRA applies to the other products you place on the market that are not medical devices, such as a wellness app or a wellness wearable. For those products, the cybersecurity evidence compiled for the MDR, such as the security architecture, the risk assessment and the post-market surveillance, can support the CRA technical file.
Our wearable RPM device connects to a patient's smartphone app. Who is responsible for CRA compliance - us or the smartphone manufacturer?+
First check whether the MDR applies. A wearable RPM device that is a medical device under Regulation (EU) 2017/745 is outside the CRA (Article 2(2)), and so is a companion app that is itself a medical device or an accessory to one under that Regulation. When the CRA applies, you are responsible for CRA compliance for your RPM device and the companion app you distribute. A personal wearable with a health monitoring purpose outside the MDR is Important Class I (Annex III, point 19). The smartphone itself is the responsibility of the smartphone manufacturer. A companion app outside the MDR, when distributed commercially to EU patients or healthcare providers, is in scope as a product with digital elements. The app's interactions with your device - including the Bluetooth or Wi-Fi interface - must be covered by your Annex I security assessment. You should document assumptions about smartphone security in your threat model and include guidance on minimum OS version requirements in patient-facing documentation.
How do we handle security updates for patients who are elderly or have limited technical literacy?+
Annex I requires security updates to be made available without undue delay and that devices support an automatic update mechanism where technically feasible. For consumer-facing RPM devices used by elderly or non-technical patients, automatic updates are both the technically appropriate solution and the patient safety imperative. Updates should be configured to install automatically during off-peak hours with minimal patient interaction required. Where patients can disable automatic updates, the device should prominently alert them when critical security updates are pending. Your patient-facing documentation should explain the importance of allowing automatic updates using plain, accessible language.
Compliance checklists for your products
Key CRA articles for Telemedicine & Remote Patient Monitoring Vendors
Guides for related sectors
Free CRA tools
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 Telemedicine & Remote Patient Monitoring Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.