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.
The Product Liability Directive comparison is narrower here: MDR evidence can inform defect, damage, and causal-link investigations, but this page does not claim that MDR compliance decides civil liability.
Structured answer sets in this page tree.
Cited legal and guidance references.
Use this comparison when the same medical-device facts must be handled in two different files: an MDR compliance file for placing and keeping a device on the EU market, and a liability-risk file that tests whether a defect, damage, and causal link may be alleged. Keep the records connected, but do not collapse the two legal questions into one conclusion.
A grounded 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.
The liability side is an exposure and investigation workstream. Grounded here, it focuses on defect, damage, causal relationship, and the MDR provisions that require liability coverage or can identify responsible actors.
| Dimension | MDR | Product Liability Directive | Operational implication |
|---|---|---|---|
| Scope boundary | MDR is a pre-market and post-market compliance regime for devices placed on, made available on, or put into service in the EU. | Product liability analysis asks whether a defective product caused compensable damage; it is not the route for CE marking or market placement. | Run MDR readiness and liability-risk review as linked but separate workstreams, with separate conclusions and source tags. |
| Covered actors | MDR records should identify the manufacturer, authorised representative, importer, distributor, PRRC, notified body where applicable, and the owner of each compliance artifact. | The liability file should identify parties tied to the alleged defect and harm; MDR grounding also flags manufacturer financial coverage and authorised-representative liability where the non-EU manufacturer has not met Article 10 obligations. | Do not let the regulatory-affairs owner silently absorb legal, insurance, supplier, customer, or litigation-response ownership. |
| Trigger | MDR work starts with intended purpose, medical-device qualification, classification, role, conformity route, market placement, and lifecycle changes. | Liability review starts from an allegation or scenario involving defect, damage, and causal relationship, including complaints, incidents, field actions, or injured-person claims. | Use intake questions that route a matter to MDR compliance, liability-risk review, or both; the same complaint may need two files. |
| Core obligations | 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. | 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. | 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. |
| Evidence record | 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. | 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. | Reuse MDR evidence as an indexed fact base, but mark which documents support MDR compliance and which are being used only as investigation evidence. |
| Timing and deadlines | MDR requires post-market surveillance and vigilance processes that document complaints, incidents, serious-incident reportability, field safety corrective actions, PMCF outputs, and risk updates. | Those records can show notice, trend signals, corrective action history, and follow-up facts relevant to defect and causation questions, without deciding the liability result. | Route every complaint or incident through MDR reportability and through the separate liability evidence map when harm or defect allegations are present. |
| Enforcement | 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. | 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. | Keep wording precise: MDR compliance evidence may support the investigation, but the page should not state that compliance guarantees a liability defence or that non-compliance proves liability. |
| Overlap and reuse | 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. | 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. | Do not convert a standards matrix into a liability conclusion; keep it as evidence for what design and verification baseline was used. |
| Practical decision rule | MDR is a pre-market and post-market compliance regime for devices placed on, made available on, or put into service in the EU. | Product liability analysis asks whether a defective product caused compensable damage; it is not the route for CE marking or market placement. | Run MDR readiness and liability-risk review as linked but separate workstreams, with separate conclusions and source tags. |
MDR is a pre-market and post-market compliance regime for devices placed on, made available on, or put into service in the EU.
Product liability analysis asks whether a defective product caused compensable damage; it is not the route for CE marking or market placement.
Run MDR readiness and liability-risk review as linked but separate workstreams, with separate conclusions and source tags.
MDR records should identify the manufacturer, authorised representative, importer, distributor, PRRC, notified body where applicable, and the owner of each compliance artifact.
The liability file should identify parties tied to the alleged defect and harm; MDR grounding also flags manufacturer financial coverage and authorised-representative liability where the non-EU manufacturer has not met Article 10 obligations.
Do not let the regulatory-affairs owner silently absorb legal, insurance, supplier, customer, or litigation-response ownership.
MDR work starts with intended purpose, medical-device qualification, classification, role, conformity route, market placement, and lifecycle changes.
Liability review starts from an allegation or scenario involving defect, damage, and causal relationship, including complaints, incidents, field actions, or injured-person claims.
Use intake questions that route a matter to MDR compliance, liability-risk review, or both; the same complaint may need two files.
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.
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.
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.
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.
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.
Reuse MDR evidence as an indexed fact base, but mark which documents support MDR compliance and which are being used only as investigation evidence.
MDR requires post-market surveillance and vigilance processes that document complaints, incidents, serious-incident reportability, field safety corrective actions, PMCF outputs, and risk updates.
Those records can show notice, trend signals, corrective action history, and follow-up facts relevant to defect and causation questions, without deciding the liability result.
Route every complaint or incident through MDR reportability and through the separate liability evidence map when harm or defect allegations are present.
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.
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.
Keep wording precise: MDR compliance evidence may support the investigation, but the page should not state that compliance guarantees a liability defence or that non-compliance proves liability.
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.
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.
Do not convert a standards matrix into a liability conclusion; keep it as evidence for what design and verification baseline was used.
MDR is a pre-market and post-market compliance regime for devices placed on, made available on, or put into service in the EU.
Product liability analysis asks whether a defective product caused compensable damage; it is not the route for CE marking or market placement.
Run MDR readiness and liability-risk review as linked but separate workstreams, with separate conclusions and source tags.
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.
The Product Liability Directive side is not a market-access checklist. Based on the MDR grounding available here, keep it to the grounded product-liability frame: a defective product claim turns on defect, damage, and a causal relationship, while MDR and national-law liability provisions may affect who must be in the investigation file.
MDR evidence is useful because it is structured around the device lifecycle. 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.
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 new liability allegation depends on facts not already covered by the technical and PMS file. The useful output is an evidence map, not a merged legal opinion.
"the damage, the defect and the causal relationship"
"EUDAMED is the IT system developed by the European Commission"
"The use of these standards remains voluntary."
"The Basic UDI-DI is the main key in the database"
"placing on the market, making available on the market or putting into service"