Data Encryption for Medical Devices: MDR and GDPR
Encryption at rest, in transit, and for backups: what MDR Annex I and GDPR demand from medical device manufacturers, and how startups implement it.
13 in-depth guides in this cluster
Encryption at rest, in transit, and for backups: what MDR Annex I and GDPR demand from medical device manufacturers, and how startups implement it.
How medical device software updates should be signed, verified, staged, and rolled back under MDR Annex I and EN IEC 81001-5-1:2022.
How penetration testing and vulnerability assessment fit into MDR cybersecurity evidence under Annex I ยง17.4 and EN IEC 81001-5-1:2022.
How cybersecurity patch management works under MDR, including change control, significant change, and when a patch triggers notified body notification.
How an SBOM grows out of the EN 62304 configuration item list, the SPDX and CycloneDX formats, and how to track CVEs against it under MDR.
How to monitor CVEs, vendor advisories, and threat intel under MDR Articles 83 to 86 and EN IEC 81001-5-1, wired into a working PMS plan.
IVDR 2017/746 replaced the IVDD and has applied since 26 May 2022. A startup-friendly guide to the framework, scope, and first moves.
IVDR vs MDR differences for startups building diagnostic devices. Where the two regulations overlap and where they diverge in practice.
IVDR device classification uses a four-class system (A, B, C, D) driven by the diagnostic target and substances. A startup-friendly walkthrough.
IVDR technical documentation mirrors MDR structure but swaps clinical evaluation for performance evaluation. Here is what actually changes.
IVDR conformity assessment routes explained by class. Class A non-sterile self-declares, everything else needs a notified body at some level.
The IVDR notified body pool is much smaller than MDR's. Here is how IVD startups should plan for that bottleneck realistically.
A phase-by-phase IVDR compliance checklist for IVD startups in 2026, from classification through CE mark, in the Subtract to Ship style.