From December 2026, software is liable like any other product
The new EU Product Liability Directive applies to all products placed on the market after 9 December 2026. It makes clear that software is a product, even when it is supplied as a cloud service. For medical software, three things change: updates become a question of liability, the burden of proof shifts for complex products, and the MDR obligation to provide financial coverage for liability will in future refer to the new law. This article sets out what applies and what you can prepare now.
Work on medical software usually centres on approval: the MDR, the risk class and the notified body. The question of who pays when the software causes harm tends to come second. From 9 December 2026, EU law answers that question anew, for all software placed on the market after that date.
The basis: a new directive with a fixed cut-off date
Directive (EU) 2024/2853 on liability for defective products replaces the Product Liability Directive of 1985. The old directive is repealed with effect from 9 December 2026, but continues to apply to products placed on the market or put into service before that date (Article 21). The new one applies to everything placed on the market after it (Article 2(1)). Member States must transpose it into national law by the same date (Article 22). As a rule, national provisions may be neither stricter nor more lenient (Article 3).
The core remains: the manufacturer is liable without fault. An injured person must prove the defect, the damage and the causal link between them, but not fault. Compensation covers death and personal injury, expressly including medically recognised damage to psychological health, as well as damage to property not used exclusively for professional purposes and the destruction or corruption of data not used for professional purposes (Article 6). Liability may not be limited or excluded by contract or by national law (Article 15), including by financial ceilings (Recital 56).
Software is a product, however it is supplied
Article 4(1) expressly includes software among products. Recital 13 makes clear that the mode of supply does not matter: stored on a device, accessed over a network or through the cloud, or offered as software-as-a-service. A developer of software is treated as a manufacturer, including providers of AI systems. Mere information, such as the content of digital files, and the mere source code of software are not products.
Two terms reach into the supply chain. A component is any item integrated into, or inter-connected with, a product, including a related service: a digital service without which the product could not perform one or more of its functions (Article 4(3) and (4)). The manufacturer of a defective component is liable alongside the manufacturer of the product (Article 8(1)). Anyone who substantially modifies a product outside the manufacturer's control and then makes it available is considered a manufacturer (Article 8(2)). Free and open-source software developed or supplied outside the course of a commercial activity is excluded (Article 2(2)).
What matters most for medical software
Updates become a question of liability. Under the 1985 directive, a manufacturer could already escape liability by showing that the defect probably came into being after the product was put into circulation (Article 7 there). The new directive retains this defence (Article 11(1)(c)), but under Article 11(2) it no longer applies where the defect is due to software, including updates or upgrades, to a lack of updates necessary to maintain safety, to a related service or to a substantial modification, provided that this is within the manufacturer's control. A manufacturer has such control simply by being able to supply updates, itself or through a third party (Article 4(5)). The assessment of defectiveness takes into account, among other things, a product's ability to continue to learn after it has been placed on the market and safety-relevant cybersecurity requirements (Article 7(2)). Recital 51 refers expressly to manufacturers' lifecycle responsibilities under the MDR.
The burden of proof shifts. On request, the defendant must disclose relevant evidence once the claimant has made the claim plausible (Article 9). If the defendant fails to do so, defectiveness is presumed; the same applies where the product breaches mandatory safety requirements or obviously malfunctions (Article 10(2)). Where proof is excessively difficult because of technical or scientific complexity, the court presumes defectiveness or causation as soon as they are likely (Article 10(4)). Recital 48 expressly cites an innovative medical device and machine learning as examples of such complexity. All presumptions are rebuttable, and trade secrets remain protected (Article 9(4) and (5), Article 10(5)).
The MDR points to liability. Under Article 10(16) MDR, manufacturers must have measures in place to provide sufficient financial coverage for their potential liability under the 1985 directive, proportionate to the risk class, type of device and size of the enterprise. Under Article 21 of the new directive, references to the old one are to be construed as references to the new one. The coverage therefore relates to a liability regime that expressly includes software.
An example
Consider software certified as a medical device under the MDR that calculates doses. Version 3 is released in January 2027. A later update introduces a calculation error, or a known security vulnerability remains unpatched, and a patient is harmed. The manufacturer can no longer argue that the defect arose only after delivery: both the update and the missing fix are within its control. If the patient did not install an update that had been made available, Recital 51 does not foresee this liability. After a substantial modification, the ten-year expiry period starts again from the date on which the modified product is made available (Article 17).
How to proceed
- Record which products and versions will be placed on the market after 9 December 2026, including cloud elements that may count as a related service.
- Run the update process as a safety process: how quickly safety-relevant updates are available, how their provision is documented and how users learn about them.
- Keep the technical documentation in a form that can be disclosed in the event of a dispute. In our assessment, documentation on lifecycle, risk management, verification and validation kept in accordance with Annex I Section 17.2 MDR is the best basis for this.
- Review the supply chain: libraries, AI models and cloud services from other manufacturers can be components. For software supplied by micro or small enterprises, the right of recourse can be waived by contract (Article 12(2)).
- Check the financial coverage under Article 10(16) MDR against the new scope of liability.
Where this does not apply
The directive does not create an obligation of its own to supply updates (Recital 51). Such obligations come from the MDR and other product legislation; the directive governs only the consequences where they are missing. It does not cover damage to property used exclusively for professional purposes or to data used for professional purposes; in our assessment, damage to a hospital's IT will therefore generally fall outside it. Contractual claims and data protection law are unaffected (Article 2(4)).
Conformity with the MDR does not automatically protect against liability. A manufacturer is exempt only where the defect is due precisely to the product's compliance with legal requirements (Article 11(1)(d)). The defence that the defect could not be discovered according to the state of scientific and technical knowledge is retained in principle (Article 11(1)(e)), but Member States may depart from it within narrow limits (Article 18).
Two uncertainties remain. In an individual case, what counts is the national transposing law, not the directive itself. And how courts will interpret, for example, a substantial modification of software or excessive difficulty of proof is open, as there is no case law yet. This article is not legal advice.
Conclusion
The new directive makes clear that software is a product. For medical software, the main consequence is this: whoever controls the updates is also liable for their absence. Aligning the update process, documentation and supply chain with this before 9 December 2026 provides the best basis should it ever be needed.
Sources: Directive (EU) 2024/2853 on liability for defective products, OJ L of 18 November 2024 — Articles 2, 3, Article 4 points (1), (3) to (5) and (18), Articles 6 to 12, 15, 17, 18, 21 and 22, Recitals 13, 48, 51 and 56. Council Directive 85/374/EEC concerning liability for defective products, 1985, Article 7. Regulation (EU) 2017/745 (Medical Device Regulation, MDR), Article 10(16) and Annex I Section 17.2.
We begin with a process analysis and show, with evidence, what is possible.
Arrange a conversation