Artifact GuideEU

EU MDR Clinical Evidence

under Regulation (EU) 2017/745 is the and clinical evaluation result that allows a qualified assessment that a device is safe and achieves its intended clinical benefit when used as intended.

This page helps structure the clinical evaluation file, equivalence rationale, clinical investigation decision, plan, GSPR linkage, and notified-body review package.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Overview

EU MDR work should connect the device's intended purpose, claims, risk profile, , , and technical documentation. Create a traceable clinical evaluation record that supports the relevant General Safety and Performance Requirements (GSPRs), explains any remaining uncertainty, and is ready for notified-body assessment where a notified body is involved.

Section 1

Build the clinical evaluation around the MDR evidence question

Start with Article 61 and Annex XIV: identify the GSPRs that need , specify the device's intended purpose and target groups, define measurable clinical benefits and safety endpoints, and justify the level of needed for the device's characteristics, classification, intended purpose, and risks.

The clinical evaluation should then show the route used to reach the conclusion: available for the device, clinical data for an equivalent device where equivalence is demonstrated, clinical data from similar devices where it informs state of the art or study design, and any new clinical investigation data needed to close evidence gaps.

Keep the terms separate in the working file. are the safety or performance information generated from a device's use, clinical investigations, or qualifying published experience. is the clinical data plus the clinical evaluation results that are sufficient, in amount and quality, to support conformity. Relevance, appraisal quality, and traceability to the intended purpose and GSPRs determine whether a large literature set supports sufficient clinical evidence.

  • Define the device version, Basic UDI-DI where relevant, intended users, patient population, indications, contraindications, claims, accessories, and configurations covered by the evaluation.
  • Map each clinical claim and relevant GSPR to the data source that supports it, including literature searches, clinical investigation reports, PMS and data, registries, user feedback, complaints, vigilance information, and risk-management outputs.
  • Include both favourable and unfavourable data, then explain how data quality, relevance, bias, follow-up, sample size, and transferability affect the clinical conclusion.
  • Document the clinical evaluation report as part of the technical documentation, together with the , non-clinical evidence, risk-management links, and any unresolved questions for .
Section 2

Decide when clinical investigations or other clinical data are enough

For implantable and class III devices, Article 61(4) starts from a clinical-investigation requirement, then provides defined exceptions. The CER should identify the exact route: modification of a device already marketed by the same manufacturer with demonstrated equivalence and notified-body endorsement; reliance on another manufacturer's MDR device under the Article 61(5) contract and conditions; or one of the Article 61(6) device categories where sufficient and any applicable common specification support the exception. The exception does not remove the duty to conduct and update the clinical evaluation.

Where a clinical investigation is needed, Annex XV expects a scientifically sound investigation plan aligned with the clinical evaluation plan and designed to confirm or refute the manufacturer's claims on safety, performance, clinical benefits, and benefit-risk. The investigation report should critically evaluate all collected data, including negative findings.

  • For clinical investigation reliance, keep the approved clinical investigation plan, endpoint rationale, statistical justification, monitoring records, investigator access to technical and , training evidence, and final clinical investigation report.
  • For literature or other existing , keep the search protocol, search report, selection criteria, appraisal method, full references, excluded-data rationale, and analysis showing relevance to the device and intended purpose.
  • For any decision not to perform a clinical investigation, identify the exact Article 61 paragraph, document sufficient , record any notified-body endorsement or contract required by that route, address applicable common specifications, and assign remaining questions to PMS or .
  • For Article 61(10) arguments based on non-clinical methods, keep the risk-management basis, the interaction-with-the-body analysis, intended clinical performance, manufacturer claims, and the technical-documentation justification; do not use that route for class III or implantable devices.
Section 3

Use equivalence only when the MDR criteria and data access are documented

Equivalence is not a shortcut to avoid evidence. Annex XIV requires technical, biological, and clinical characteristics to be considered, and MDCG 2020-5 emphasizes that differences must be fully identified, assessed, and scientifically justified so they do not create clinically significant differences in safety or clinical performance.

For each presumed equivalent device, keep a separate equivalence table and do not assemble equivalence from different devices for different features. Sufficient access to the data supporting equivalence is required under Annex XIV. The additional Article 61(5) contract for full, ongoing access to another manufacturer's technical documentation applies when an implantable or class III device uses that specific route to avoid a new clinical investigation; it should not be described as a universal contract requirement for every equivalence analysis.

  • Compare clinical characteristics: same clinical condition or purpose, similar severity and disease stage, same body site, similar population, same kind of user, and similar relevant critical performance for the expected clinical effect.
  • Compare technical characteristics: design, specifications, properties, deployment method, principles of operation, critical performance requirements, software algorithms, and other characteristics relevant to safety or performance.
  • Compare biological characteristics: materials or substances in contact with the same tissues or body fluids, duration of contact, release characteristics, processing effects, and biological-safety implications.
  • Document the data-access source, version or generation of the equivalent device, regulatory status, identified differences, scientific justification, and why the data remain relevant to the device under evaluation.
Section 4

Tie PMCF, benefit-risk, and technical documentation together

is a continuous process that updates the clinical evaluation after CE marking. The PMCF plan should state why each activity is needed, which residual clinical uncertainties it addresses, what data quality and quantity are expected, how bias and missing data will be controlled, and when data will be analysed and reported.

The evaluation report should feed back into the clinical evaluation report, the risk-management file, the benefit-risk conclusion, IFU and labelling decisions, SSCP where applicable, PMS outputs, and corrective or preventive action decisions. For class III and implantable devices, Article 61 requires at least annual updates of the PMCF evaluation report and, if indicated, the SSCP; other devices still need lifecycle updates when new evidence or risk information changes the evaluation.

  • Use to confirm safety and performance over the expected lifetime, monitor known side effects and contraindications, identify unknown side effects, analyse emerging risks, check continued benefit-risk acceptability, and detect systematic misuse or off-label use.
  • Reference the clinical evaluation report and risk-management file sections that will monitor; if no relevant section exists, state that explicitly and justify it.
  • Select methods that match the device risk and uncertainty: literature screening, user or patient surveys, registry analysis, real-world evidence, extended follow-up, PMCF studies, or new post-market clinical investigations.
  • Keep the plan, PMCF activity rationale, data-quality assumptions, endpoints, timelines, PMCF evaluation report, and resulting updates inside the technical documentation.
Recommended next step

Turn MDR clinical evidence into a review-ready file

Use Sorena to connect clinical claims, GSPR support, equivalence rationale, PMCF, risk management, and notified-body questions in one cited evidence workflow.

Section 5

Prepare for notified-body review of clinical evidence

Where a notified body reviews the device, expect scrutiny of the clinical evaluation as part of the technical documentation assessment and surveillance. The MDR requires notified bodies to examine clinical evaluation planning, literature methodology, clinical investigations, equivalence, PMS and , clinical evaluation reports, and justifications for not performing clinical investigations or PMCF.

For higher-risk devices subject to clinical evaluation consultation, the notified body's clinical evaluation assessment report can be reviewed by an expert panel. The package should therefore make the benefit-risk conclusion, consistency with intended purpose and medical indications, plan, and residual evidence gaps easy to follow.

  • Provide a reviewer-ready index from each clinical claim to its supporting , GSPR, risk-control record, IFU or SSCP statement, and follow-up item.
  • Flag any unresolved clinical uncertainty, non-conformity, limitation in equivalent-device data access, missing follow-up, or dependency before the notified body has to infer it.
  • Show how is reflected in the information supplied with the device, including warnings, contraindications, user training, intended purpose, claims, and SSCP where applicable.
  • Keep the notified-body questions, deficiency responses, clinical evaluation assessment report conclusions, milestones, certification conditions, and post-certification surveillance actions with the technical file.
Primary sources

References and citations

eur-lex.europa.eu6 citations
Referenced sections
  • Primary MDR source for Article 61 clinical evaluation, clinical investigation rules, Annex XIV clinical evaluation and PMCF, Annex XV clinical investigations, technical documentation, GSPR support, and notified-body review.
  • Article 61 and Annex XIV ground the clinical evaluation process, the need to justify the level of clinical evidence, the GSPR link, and the technical-documentation linkage.
  • Article 61 and Annex XV support the clinical-investigation decision, exceptions, clinical investigation plan content, and clinical investigation report expectations.
Show 3 more
  • Article 61 and Annex XIV ground the legal role of equivalence, the implantable and class III rules, and the requirement that clinical evidence support the GSPRs.
  • Annex XIV Part B grounds PMCF as a continuous process, the PMCF plan contents, the PMCF evaluation report, and the link to clinical evaluation, risk management, and technical documentation.
  • Annex VII and Annex IX ground notified-body assessment of clinical evaluation, clinical evidence, PMCF, benefit-risk, CEAR conclusions, and expert-panel consultation for certain devices.
"clinical data providing sufficient clinical evidence"
More quoted passages
"clinical investigations shall be performed"
"equivalent to the device"
"PMCF shall be understood to be a continuous process"
"review the clinical evidence presented"
health.ec.europa.eu4 citations
Referenced sections
  • MDCG guidance for sufficient clinical evidence, lifecycle clinical evaluation, legacy-device evidence, clinical-data appraisal, and GSPR support.
  • MDCG guidance used for the meaning of sufficient clinical evidence, clinical-data quality and quantity, legacy-device evidence, GSPR support, and continuous clinical evaluation.
  • MDCG 2020-6 grounds how sufficient clinical data can support legacy-device conformity and when evidence gaps need new clinical data or PMCF follow-up.
Show 1 more
  • MDCG 2020-6 supports lifecycle clinical evaluation and the expectation that clinical data continue to demonstrate safety, performance, and benefit-risk acceptability.
"sufficient clinical evidence necessary to demonstrate conformity"
More quoted passages
"quantity and quality of clinical data"
"clinical evaluation is a process"
health.ec.europa.eu2 citations
Referenced sections
  • Commission source for the role of notified bodies in assessing conformity for certain products before placing on the market.
  • Commission overview used only for the role and designation context of notified bodies that assess conformity before certain devices are placed on the market.
"assess the conformity of certain products"
health.ec.europa.eu2 citations
Referenced sections
  • MDCG guidance for using clinical data from an equivalent device, including technical, biological, and clinical criteria, scientific justification, device-by-device comparison, and data-access limits.
  • MDCG equivalence guidance used for technical, biological, and clinical comparison criteria, the need for scientific justification, device-by-device equivalence, and access-to-data constraints.
"proper scientific justification"
Show all related guides (46)

EU MDR classification workflow

A concrete EU MDR classification workflow for intended purpose, device or accessory qualification, Annex VIII rule selection, Rule 11 software review, class outcome, and notified body impact.

EU MDR Clinical Evaluation Overview

EU MDR clinical evaluation overview covering Article 61, Annex XIV, clinical data sources, equivalence, PMCF, CER evidence, notified body review, GSPR, and benefit-risk support.

EU MDR Clinical Evaluation Report Template

A cited EU MDR clinical evaluation report template covering intended purpose, GSPR linkage, clinical data appraisal, equivalence limits, PMCF, conclusions, and reviewer signoff.

EU MDR compliance obligations

EU MDR compliance guide for device qualification, classification, conformity assessment, QMS, technical documentation, UDI, EUDAMED, PMS, vigilance, and legacy transition controls.

EU MDR conformity route workflow

EU MDR workflow for classifying a device, choosing the conformity assessment route, preparing technical and QMS evidence, and reaching certificate, DoC, UDI, EUDAMED, and CE outputs.

EU MDR deadlines and compliance calendar

EU MDR calendar for application, conditional legacy-device transition, UDI carrier dates, mandatory EUDAMED modules, and recurring compliance reviews.

EU MDR Device Classification Guide

Classify an EU MDR medical device by intended purpose, Annex VIII duration, invasiveness, active-device and software rules, then document the conformity route impact.

EU MDR EUDAMED and UDI registration

MDR guide to Basic UDI-DI, UDI-DI, EUDAMED device registration, actor roles, labels, technical documentation, and UDI data governance.

EU MDR FAQ: qualification, evidence, UDI, and transition

Concise EU MDR FAQ covering device qualification, software classification, accessories, custom-made devices, clinical evidence, UDI, EUDAMED, notified bodies, significant changes, and legacy transition.

EU MDR Legacy Device Transition

EU MDR legacy-device guide to Article 120 eligibility, class-based end dates, certificate validity, significant changes, surveillance, and evidence.

EU MDR notified body route selection

Choose an EU MDR conformity assessment route by device class, Article 52 option, notified body designation scope, QMS readiness, technical documentation, clinical evidence, and certificate evidence.

EU MDR penalties and enforcement risk

EU MDR guide to Article 113 national penalties, authority measures, recalls, certificate action, and the evidence needed for a country-specific assessment.

EU MDR PMS and Vigilance Guide

EU MDR guide to post-market surveillance, PMCF updates, PMS reports, PSURs, serious incident reporting, FSCA/FSN handling, trend reporting, and evidence records.

EU MDR PMS and vigilance records

Cited EU MDR guide to PMS plans, PMS reports, PSURs, PMCF updates, serious incident and FSCA reporting, trend reporting, and EUDAMED evidence handling.

EU MDR PMS Plan Template for Medical Devices

A cited EU MDR post-market surveillance plan template covering device scope, PMS data sources, PMCF linkage, vigilance, trend reporting, PMSR or PSUR outputs, roles, cadence, and evidence records.

EU MDR QMS and technical file evidence map

Map EU MDR Article 10 QMS duties to Annex II and Annex III technical documentation, PMS, vigilance, UDI records, and notified-body review evidence.

EU MDR QMS requirements under Article 10

EU MDR QMS guide for Article 10 manufacturer controls covering regulatory strategy, design, risk, clinical evaluation, PMS, vigilance, UDI, suppliers, CAPA, and conformity records.

EU MDR qualification and borderline products

EU MDR qualification guide for medical purpose claims, accessories, software, Annex XVI products, and borderline routes to classification and conformity assessment.

EU MDR qualification workflow

A concrete EU MDR workflow for deciding whether a product is a medical device, accessory, Annex XVI product, IVD interface, medicinal-product interface, or non-MDR product before classification and conformity assessment.

EU MDR requirements checklist

Concrete EU MDR requirements for medical-device scope, classification, GSPR, conformity assessment, technical documentation, QMS, clinical evidence, UDI, EUDAMED, PMS, vigilance, and economic-operator records.

EU MDR Rule 11 software classification

Classify MDR medical device software under Rule 11 using intended purpose, diagnosis or therapy decision impact, physiological monitoring, conformity route, clinical evidence, and software-change records.

EU MDR transition timeline and end dates

EU MDR chronology for 2021 application, 2023 amendments, 2024 eligibility milestones, and conditional 2026, 2027, and 2028 transition endpoints.

EU MDR UDI and EUDAMED registration guide

EU MDR guide to Basic UDI-DI, UDI-DI, UDI carriers, EUDAMED actor and device registration, change impacts, and evidence governance.

EU MDR vigilance reporting workflow

Concrete EU MDR vigilance workflow for incident intake, serious incident assessment, FSCA and FSN handling, trend reporting, EUDAMED caveats, CAPA, PMS, clinical evaluation updates, and records.

MDR vs AI Act for medical-device software

Compare MDR and AI Act scope, high-risk classification, conformity assessment, evidence, monitoring, and timing for AI-enabled medical devices.

MDR vs EU Product Liability Directive

Compare MDR compliance evidence with EU product-liability claims, responsible parties, disclosure, presumptions, damage, and the December 2026 transition.

MDR vs GPSR: medical-device boundary checks

Compare MDR medical-device scope with general product-safety fallback questions for borderline, non-medical, and Annex XVI products.

MDR vs IVDR: medical devices and IVDs compared

Compare EU MDR and IVDR scope, classification, conformity routes, technical documentation, clinical or performance evidence, UDI, EUDAMED, PMS, and vigilance.

Custom-made medical devices under the EU MDR | EU MDR FAQ

Concise EU MDR FAQ on custom-made device definition, mass-produced exclusions, Annex XIII statements, documentation, conformity assessment, PMS, vigilance, and records to retain.

EU MDR significant changes FAQ: legacy-device transition and notified-body review

FAQ on MDR significant changes for legacy devices, including intended-purpose, design, software, material, sterilisation, clinical, QMS, notified-body, and evidence impacts.

EU MDR SSCP: Devices and Requirements

Decide whether an EU medical device needs an SSCP, see worked class IIa, IIb, and III examples, and check the required content, evidence, publication, and update controls.

How should Basic UDI-DI and UDI-DI be assigned under the EU MDR? | EU MDR FAQ

EU MDR FAQ on Basic UDI-DI grouping, device and package UDI-DIs, UDI carriers, EUDAMED registration, change triggers, and required records.

What should an EU MDR PMCF plan and report cover? | EU MDR FAQ

Under the EU MDR, PMCF is part of PMS and clinical evaluation. See what the plan, activities, report, updates, and retained evidence should cover.

What should manufacturers do when an EU MDR classification changes? | EU MDR FAQ

Concise EU MDR FAQ on classification changes, intended purpose, software, notified-body route impact, certificates, technical documentation, and retained evidence.

When can clinical equivalence be used under the EU MDR?

EU MDR FAQ on clinical equivalence, including technical, biological, and clinical characteristics, access to equivalent-device data, class III and implantable-device limits, clinical evaluation, PMCF, and retained evidence.

When do software or products make medical purpose claims under the EU MDR? | EU MDR FAQ

EU MDR FAQ on medical purpose claims, intended purpose evidence, software qualification, Annex XVI contrasts, and records to keep.

When is a PSUR required under the EU MDR and what should it contain? | EU MDR FAQ

EU MDR FAQ on PSUR scope, content, update cadence, PMS and PMCF links, notified-body handling, EUDAMED submission, and evidence to retain.

When is an accessory regulated under the EU MDR? | EU MDR FAQ

EU MDR FAQ on when an article is a medical device accessory, how intended purpose affects classification, and what evidence to keep.

When is software a medical device under the EU MDR?

EU MDR FAQ on medical device software qualification, Rule 11 and other classification rules, modules, evidence, software changes, UDI, and EUDAMED.

Which EUDAMED modules matter under the EU MDR? | EU MDR FAQ

EU MDR FAQ mapping EUDAMED modules to actor registration, UDI/device data, certificates, clinical investigations, vigilance/PMS, market surveillance, and practical records.