MDR vs Product Liability Directive Evidence comparison
The MDR is a market-access and lifecycle compliance regime for medical devices: qualification, classification, conformity assessment, technical documentation, clinical evidence, PMS, vigilance, UDI, and EUDAMED records.
Directive (EU) 2024/2853 applies to products placed on the market or put into service after 9 December 2026. The earlier Directive 85/374/EEC continues to govern products placed on the market before that date.
Keep two connected files. The MDR file determines whether a medical device can be placed and kept on the EU market. The liability file examines whether there was a , whether compensable damage occurred, and whether the defect caused that damage. MDR conformity can supply important evidence, but it neither guarantees a defence nor proves liability.
Side-by-side comparison
MDR vs Product Liability Directive: evidence comparison
A cited-source comparison for medical-device teams that need to keep MDR market-access compliance evidence separate from Product Liability Directive exposure analysis.
MDR controls market access and lifecycle compliance for medical devices through scope, roles, classification, conformity assessment, technical documentation, clinical evidence, PMS, vigilance, UDI, EUDAMED, and financial-coverage duties.
Second framework
Product Liability Directive
The liability side is a civil claim and evidence workstream. The applicable directive depends on when the product was placed on the market; the 2024 Directive expands coverage to software and adds rules on disclosure and rebuttable presumptions.
MDR vs Product Liability Directive: evidence comparison
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Product liability analysis asks whether a caused covered damage. Under the 2024 Directive, covered damage includes death or personal injury, including medically recognised psychological harm, specified private-property damage, and destruction or corruption of non-professional data.
Articles 2, 4 to 10, 21, and 22 support the temporal routing and the 2024 Directive's rules on defect, covered damage, causation, liable economic operators, disclosure, and rebuttable presumptions.
MDR records should identify the manufacturer, authorised representative, importer, distributor, PRRC, notified body where applicable, and the owner of each compliance artifact.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
The 2024 Directive starts with the manufacturer of the or component. Depending on the conditions, an importer, authorised representative, fulfilment service provider, distributor, or online platform may also be a defendant. These roles do not map one-to-one to MDR responsibility.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Primary MDR source for market placement, conformity assessment, technical documentation, PMS, vigilance, UDI, EUDAMED, financial coverage, and authorised-representative liability provisions.
placing on the market, making available on the market or putting into service
Liability review starts from an allegation or scenario involving defect, damage, and causal relationship, including complaints, incidents, field actions, or injured-person claims.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Commission source for voluntary harmonised standards, OJEU references, and their role in demonstrating compliance with EU legal requirements.
The use of these standards remains voluntary.
The liability file can use the same documentation to reconstruct design choices, known risks, warnings, testing, changes, and what evidence existed at relevant points in time.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Keep version history and change-control links intact; a liability investigation often depends on the exact record that existed when the device was supplied or used.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
MDR evidence includes classification rationale, conformity assessment route, certificates, declarations, Annex II and III technical documentation, clinical evaluation, PMS or PMCF, vigilance, UDI, EUDAMED, IFU, and labelling records.
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Liability-risk evidence should assemble alleged defect facts, harm facts, causal-link facts, product history, warnings, IFU versions, PMS findings, complaints, field actions, and technical-change records.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Directive (EU) 2024/2853 applies to products placed on the market or put into service after 9 December 2026. Directive 85/374/EEC continues to apply to products placed before 9 December 2026. Limitation and long-stop periods then depend on the applicable directive, national implementation, and case facts.
Articles 2, 18, 21, and 22 establish the temporal scope, limitation framework, repeal, and transition from Directive 85/374/EEC.
Record the product placement or putting-into-service date, injury date, device and software version, and Member State before calculating any claim deadline.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
The MDR output is a market-access or lifecycle decision: proceed, remediate, escalate to notified body or competent authority, update documentation, report, or stop supply.
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
The liability output is an investigation and exposure view: what is alleged, what evidence exists, what gaps remain, who owns follow-up, and what legal or insurance review is needed.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Treat MDR conformity as evidence in the investigation. Compliance does not guarantee a liability defence, and non-compliance alone does not prove every element of a liability claim.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
MDR compliance may rely on harmonised standards or other technical solutions to demonstrate requirements, with OJEU-referenced standards supporting presumption-of-conformity analysis where applicable.
Commission source for voluntary harmonised standards, OJEU references, and their role in demonstrating compliance with EU legal requirements.
The use of these standards remains voluntary.
For liability review, standards evidence can help explain the technical baseline considered, but the Product Liability Directive question still turns on defect, damage, and causal relationship.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Select Directive 85/374/EEC or Directive (EU) 2024/2853 by the product's placement date, then assess defect, covered damage, causation, responsible economic operators, disclosure, and any applicable presumptions.
Articles 2, 4 to 10, 21, and 22 support the temporal routing and the 2024 Directive's rules on defect, covered damage, causation, liable economic operators, disclosure, and rebuttable presumptions.
Run MDR readiness and liability-risk review as linked but separate workstreams, with separate conclusions and source tags.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Scope boundary
MDR
MDR is a pre-market and post-market compliance regime for devices placed on, made available on, or put into service in the EU.
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Product Liability Directive
Product liability analysis asks whether a caused covered damage. Under the 2024 Directive, covered damage includes death or personal injury, including medically recognised psychological harm, specified private-property damage, and destruction or corruption of non-professional data.
Articles 2, 4 to 10, 21, and 22 support the temporal routing and the 2024 Directive's rules on defect, covered damage, causation, liable economic operators, disclosure, and rebuttable presumptions.
Covered actors
MDR
MDR records should identify the manufacturer, authorised representative, importer, distributor, PRRC, notified body where applicable, and the owner of each compliance artifact.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Product Liability Directive
The 2024 Directive starts with the manufacturer of the or component. Depending on the conditions, an importer, authorised representative, fulfilment service provider, distributor, or online platform may also be a defendant. These roles do not map one-to-one to MDR responsibility.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Trigger
MDR
MDR work starts with intended purpose, medical-device qualification, classification, role, conformity route, market placement, and lifecycle changes.
Primary MDR source for market placement, conformity assessment, technical documentation, PMS, vigilance, UDI, EUDAMED, financial coverage, and authorised-representative liability provisions.
placing on the market, making available on the market or putting into service
Product Liability Directive
Liability review starts from an allegation or scenario involving defect, damage, and causal relationship, including complaints, incidents, field actions, or injured-person claims.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Core obligations
MDR
MDR technical documentation supports conformity by documenting the device description, design, manufacture, GSPR evidence, benefit-risk rationale, verification, validation, clinical evidence, PMS plan, and updates.
Commission source for voluntary harmonised standards, OJEU references, and their role in demonstrating compliance with EU legal requirements.
The use of these standards remains voluntary.
Product Liability Directive
The liability file can use the same documentation to reconstruct design choices, known risks, warnings, testing, changes, and what evidence existed at relevant points in time.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Operational implication
Keep version history and change-control links intact; a liability investigation often depends on the exact record that existed when the device was supplied or used.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Evidence record
MDR
MDR evidence includes classification rationale, conformity assessment route, certificates, declarations, Annex II and III technical documentation, clinical evaluation, PMS or PMCF, vigilance, UDI, EUDAMED, IFU, and labelling records.
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Product Liability Directive
Liability-risk evidence should assemble alleged defect facts, harm facts, causal-link facts, product history, warnings, IFU versions, PMS findings, complaints, field actions, and technical-change records.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
The Basic UDI-DI is the main key in the database
Timing and deadlines
MDR
MDR requires post-market surveillance and vigilance processes that document complaints, incidents, serious-incident reportability, field safety corrective actions, PMCF outputs, and risk updates.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Product Liability Directive
Directive (EU) 2024/2853 applies to products placed on the market or put into service after 9 December 2026. Directive 85/374/EEC continues to apply to products placed before 9 December 2026. Limitation and long-stop periods then depend on the applicable directive, national implementation, and case facts.
Articles 2, 18, 21, and 22 establish the temporal scope, limitation framework, repeal, and transition from Directive 85/374/EEC.
Operational implication
Record the product placement or putting-into-service date, injury date, device and software version, and Member State before calculating any claim deadline.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Enforcement
MDR
The MDR output is a market-access or lifecycle decision: proceed, remediate, escalate to notified body or competent authority, update documentation, report, or stop supply.
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Product Liability Directive
The liability output is an investigation and exposure view: what is alleged, what evidence exists, what gaps remain, who owns follow-up, and what legal or insurance review is needed.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Operational implication
Treat MDR conformity as evidence in the investigation. Compliance does not guarantee a liability defence, and non-compliance alone does not prove every element of a liability claim.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Overlap and reuse
MDR
MDR compliance may rely on harmonised standards or other technical solutions to demonstrate requirements, with OJEU-referenced standards supporting presumption-of-conformity analysis where applicable.
Commission source for voluntary harmonised standards, OJEU references, and their role in demonstrating compliance with EU legal requirements.
The use of these standards remains voluntary.
Product Liability Directive
For liability review, standards evidence can help explain the technical baseline considered, but the Product Liability Directive question still turns on defect, damage, and causal relationship.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Product Liability Directive
Select Directive 85/374/EEC or Directive (EU) 2024/2853 by the product's placement date, then assess defect, covered damage, causation, responsible economic operators, disclosure, and any applicable presumptions.
Articles 2, 4 to 10, 21, and 22 support the temporal routing and the 2024 Directive's rules on defect, covered damage, causation, liable economic operators, disclosure, and rebuttable presumptions.
Operational implication
Run MDR readiness and liability-risk review as linked but separate workstreams, with separate conclusions and source tags.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Practical decision rule
How should teams use this comparison?
Start with an MDR fact sheet: device, intended purpose, risk class, role, conformity route, certificate or declaration status, UDI identifiers, technical documentation version, PMS owner, and vigilance status.
Open a liability-risk file to record: alleged defect, alleged damage, causal-link facts, responsible actors, and the MDR records that can support or challenge those facts.
Escalate legal conclusions separately; the operational record should say what evidence exists and what remains unresolved, not decide civil liability outcomes.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
1
Section 1
Separate the MDR compliance file from the liability-risk file
The MDR side asks whether the product is a medical device or accessory, which role the company plays, which classification and conformity route applies, and which technical, clinical, PMS, vigilance, UDI, and EUDAMED records must exist before and after market placement.
Product-liability analysis does not decide market access. Directive (EU) 2024/2853 creates no-fault liability for defective products, so an injured person does not have to prove the defendant's fault. It applies to products placed on the market or put into service after 9 December 2026. Directive 85/374/EEC continues to apply to products placed before 9 December 2026, so record the placement date before selecting the legal framework.
Under the 2024 Directive, a product includes software, including AI systems, as well as digital manufacturing files and components. The liable economic operator depends on the supply chain and facts: the manufacturer of the or component is the starting point, with possible routes involving an importer, authorised representative, fulfilment service provider, distributor, or online platform when the Directive's conditions are met.
A person that substantially modifies a product outside the original manufacturer's control and then makes it available or puts it into service can be treated as the manufacturer of the modified product. For connected medical devices, preserve who controlled software updates, cybersecurity fixes, learning behaviour, and related digital services after placement; those facts can affect both the defect analysis and the responsible-operator route.
Create one MDR index for classification, conformity assessment, technical documentation, clinical evaluation, PMS or PMCF, vigilance decisions, UDI data, EUDAMED submissions, certificates, declarations, IFU, labelling, and field actions.
Create a separate liability-risk index for complaint facts, alleged harm, device history, design or manufacturing changes, warnings and IFU versions, PMS findings, vigilance assessments, corrective actions, and causation questions.
Use MDR evidence to reconstruct what was known, controlled, monitored, and communicated; do not state that the MDR file proves or disproves liability without a separate legal assessment.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Articles 2, 4, 8, 21, and 22 support the application-date split, expanded product definition, and potentially liable economic operators.
2
Section 2
Use MDR evidence to support investigations without overclaiming it
MDR technical documentation and clinical evidence show the intended purpose, design choices, benefit-risk rationale, standards or common specifications used, and the data behind safety and performance claims.
Post-market records add what happened after release: complaints, non-serious incidents kept in the QMS, serious-incident reportability decisions, field safety corrective actions, PMCF outputs, trend signals, and updates to risk management or clinical evaluation. Those records can support a defect investigation, but they remain evidence inputs rather than automatic liability conclusions.
The 2024 Directive's defect assessment considers all circumstances, including product presentation, reasonably foreseeable use and misuse, the product's ability to learn after deployment, relevant product-safety requirements, recalls or regulatory intervention, and the safety a person is entitled to expect. A claimant must generally prove defect, damage, and causation, but courts can order disclosure and apply rebuttable presumptions under the Directive's conditions.
Tie each complaint or incident to device identifiers, Basic UDI-DI or UDI-DI where relevant, batch or serial data, IFU and labelling version, software version, certificate scope, and market where the event occurred.
Link the investigation file to the MDR source record that supports the fact: technical documentation, clinical evaluation report, PMS plan, PMCF plan or report, vigilance assessment, field safety notice, EUDAMED entry, or harmonised-standard rationale.
Record unresolved issues separately, such as missing samples, incomplete use conditions, uncertain causation, supplier gaps, or whether a changed device still matches the certified configuration.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
Articles 6, 9, and 10 support the defect factors, disclosure mechanism, burden of proof, and rebuttable presumptions.
Recommended next step
Review MDR evidence before liability-risk discussions
Build a cited evidence map that separates MDR compliance records from defect, damage, and causation questions, then reuse the map for investigations, authority responses, and customer assurance.
Reopen the comparison when the MDR evidence baseline changes or when a liability allegation depends on facts not already covered by the technical and PMS file. For the 2024 Directive, also preserve evidence about software versions, updates, upgrade paths, cybersecurity controls, learning behaviour, and related digital services that affect product safety. The output is an evidence map, not a merged legal opinion.
Product change: new intended purpose, claims, software logic, materials, supplier, manufacturing process, accessories, packaging, or IFU wording.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
the damage, the defect and the causal relationship
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
EUDAMED is the IT system developed by the European Commission
Articles 4 and 6 support preserving software, update, related-service, cybersecurity, and learning-function evidence where relevant to the product and defect assessment.
Binding source for products placed on the market or put into service after 9 December 2026, including product and damage definitions, defect factors, liable operators, disclosure, and evidentiary presumptions.
Articles 2, 4, 8, 21, and 22 support the application-date split, expanded product definition, and potentially liable economic operators.
Articles 6, 9, and 10 support the defect factors, disclosure mechanism, burden of proof, and rebuttable presumptions.
Show 6 more
Articles 4 and 6 support preserving software, update, related-service, cybersecurity, and learning-function evidence where relevant to the product and defect assessment.
Articles 5 and 4 define the right to compensation and covered damage for products within the Directive's temporal scope.
Articles 2, 4 to 10, 21, and 22 support the temporal routing and the 2024 Directive's rules on defect, covered damage, causation, liable economic operators, disclosure, and rebuttable presumptions.
Article 8 identifies the economic operators that can be liable and the conditions for secondary routes.
Articles 2, 4-10, 21, and 22 support the temporal routing and the 2024 Directive's liability analysis.
Articles 2, 18, 21, and 22 establish the temporal scope, limitation framework, repeal, and transition from Directive 85/374/EEC.
Commission product-law guidance used for the official source Product Liability Directive comparison, including strict liability, defect, damage, and causal-link framing.
"the damage, the defect and the causal relationship"
Commission source for EUDAMED as the IT system implementing MDR and IVDR modules, including actor, UDI/device, certificates, and vigilance-related records.
"EUDAMED is the IT system developed by the European Commission"
MDCG guidance used for Basic UDI-DI, UDI traceability, and links between UDI data, technical documentation, certificates, declarations, and SSCP records.
"The Basic UDI-DI is the main key in the database"