MDRC logo
Explore
← Knowledge centre

MDR Articles 61–82 · Annexes XIV and XV

A clinical investigation is not the clinical evaluation

One asks what the complete evidence means. The other generates human data when the answer is still missing.

Confusing the two creates opposite errors: commissioning a study before defining the evidence gap, or trying to write around a gap that only new clinical data can close. The better route begins with the claims and ends with a study only when the logic requires one.

Updated 10 February 2025 13-minute guide Current MDR framework
Separate the two concepts ↓

The rule in one sentence

Evaluate first, investigate when a material clinical question remains unanswered

01The clinical evaluation defines the evidence needed, identifies what already exists and tests whether it is sufficient.

02A clinical investigation should be designed around a specific unresolved question, not used as a substitute for an evidence strategy.

Two connected processes

Same evidence system, different jobs

The MDR definitions make the boundary clear. The clinical evaluation is continuous and comprehensive. A clinical investigation is a defined investigation involving human subjects.

Article 2(44)CE

The decision framework

Clinical evaluation

A systematic and planned process that continuously generates, collects, analyses and assesses clinical data to verify safety, performance and clinical benefit when the device is used as intended.

  • Required for every medical device under the MDR
  • Covers all relevant favourable and unfavourable data
  • Connects evidence to claims, GSPRs and benefit-risk
  • Is documented in the Clinical Evaluation Report
  • Continues throughout the device lifecycle
Output

A justified conclusion on whether the clinical evidence is sufficient

Article 2(45)CI

The data-generation method

Clinical investigation

A systematic investigation involving one or more human subjects, undertaken to assess the safety or performance of a device.

  • Required when the legal route or evidence gap demands it
  • Answers pre-specified safety, performance or benefit questions
  • Requires a sponsor, CIP, ethical review and regulatory pathway
  • Produces data that must still be critically appraised
  • May occur before or after CE marking
Output

A clinical investigation report and data for the wider clinical evaluation

Terminology check

The MDR uses “clinical investigation” for medical devices. “Clinical trial” is commonly associated with medicinal products and should not be used as the default device term.

The investigation decision

Start with the device situation, then test evidence sufficiency

Select a situation to see the governing logic. A device can move between these situations when its intended purpose, design, claims or evidence base changes.

61.4

Investigation is the starting expectation

Check the Article 61 exemption routes precisely

For implantable and Class III devices, Article 61(4) states that clinical investigations shall be performed. The exceptions in Article 61(4), (5) and (6) have distinct conditions. MDCG 2023-7 explains that these routes are independent unless the Regulation explicitly links them.

  • Do not merge conditions from different exemption cases
  • Demonstrate equivalence under Annex XIV where relied upon
  • Show sufficient access to data when the selected route requires it
  • Document the justification in the CER and PMCF strategy

The evidence chain

Do not begin with a protocol

A well-designed investigation can still be strategically useless if it measures endpoints that do not support the intended purpose, claims or unresolved GSPRs.

  1. 01Scope

    Fix the intended purpose

    Define patients, users, indications, contraindications, setting, operating principle, variants and duration of use.

  2. 02Claims

    Convert claims into questions

    State the clinical performance, benefit and safety outcomes that the evidence must demonstrate.

  3. 03Existing evidence

    Inventory every relevant source

    Include own-device data, literature, equivalent-device data, PMS, PMCF and relevant alternatives.

  4. 04Appraisal

    Test relevance and quality

    Examine population, device version, design, bias, endpoints, follow-up, statistics and access to underlying data.

  5. 05Gap

    Name the unresolved uncertainty

    Write the gap as an answerable question and explain why existing evidence cannot close it.

  6. 06Generation

    Choose the right method

    Use a clinical investigation only when the unresolved question requires data from human use.

  7. 07Integration

    Return results to the CER

    Appraise the study, update benefit-risk, GSPR mapping, labelling, risk controls and residual gaps.

What counts as clinical data

The MDR recognises several routes into the evidence base

Article 2(48) identifies clinical data generated through use of the device. Each source can be valuable, but none becomes sufficient merely because it is labelled “clinical”.

Important boundary

Bench testing, software verification, biocompatibility testing and animal data are important evidence, but they are not clinical data. They answer different questions within the overall conformity case.

01
Direct

Investigations of the device concerned

The closest source to the actual design, intended purpose and population, provided the investigation is methodologically sound and relevant.

Own device
02
Transferred

Investigations or studies of an equivalent device

Usable for conformity only when technical, biological and clinical equivalence is demonstrated and the data are adequately accessible.

Equivalent device
03
Published

Peer-reviewed reports of clinical experience

Literature may support the device or an equivalent device, while similar-device data can also help define state of the art and known risks.

Literature
04
Lifecycle

Clinically relevant PMS and PMCF information

Complaints, registries, PMCF studies, vigilance and real-world use can confirm conclusions or reveal that the evidence strategy must change.

Post-market

Gap triage

Not every evidence gap belongs in a clinical investigation

The fastest way to overspend is to ask human subjects to answer a question that should have been resolved by engineering, laboratory or usability work.

Technical01

Does the device perform as designed?

Accuracy, strength, reliability, interoperability, cybersecurity, software verification, transport or shelf-life questions normally require technical evidence.

Likely method

Bench, analytical or software verification and validation

Biological02

Is the biological interaction acceptable?

Material characterisation, toxicology, biocompatibility and preclinical questions should be addressed within the biological evaluation strategy.

Likely method

Biological evaluation and justified preclinical testing

Use-related03

Can intended users operate it safely?

Interface comprehension, critical tasks, training and foreseeable use error often require usability engineering rather than a clinical investigation.

Likely method

Formative and summative usability evaluation

Clinical04

Does it achieve the intended clinical result safely?

Unresolved questions about clinical performance, clinical benefit, undesirable side-effects or benefit-risk may require new data from human use.

Likely method

Clinical investigation or another justified clinical-data route

Choose the regulatory route

“Clinical investigation” is not one administrative pathway

The device status, study purpose, intended use and additional procedures determine the applicable MDR article. National requirements remain relevant.

62

Conformity assessment

Pre-market or pre-expansion evidence generation

Article 62 applies where an investigation is carried out as part of the clinical evaluation for conformity assessment purposes to establish or verify intended performance, clinical benefit or clinical safety.

  • Authorisation and ethical review apply
  • Annex XV governs planning and conduct
  • The device may be pre-CE or used outside its certified scope
74

Post-market clinical follow-up

Further assessment within the CE-marked intended purpose

Article 74 addresses PMCF investigations of CE-marked devices used within their intended purpose. Article 74(1) provides a specific notification route where subjects undergo additional invasive or burdensome procedures.

  • The investigation must align with the certified intended purpose
  • Additional procedures affect the regulatory route
  • National notification requirements must be checked
82

Other clinical investigations

Investigations outside the Article 62 purposes

Article 82 sets minimum MDR protections for other investigations involving devices. Member States may impose additional requirements, so the national pathway must be established before submission.

  • Scientific and ethical safeguards still apply
  • The study purpose must be classified correctly
  • National provisions can differ between Member States
Do not classify by timing alone

A study conducted after CE marking is not automatically a PMCF investigation under Article 74. Its purpose, device use, intended-purpose boundary and study procedures still need to be assessed.

Design backwards from the claim

A compliant study can still produce unusable evidence

Authorisation is not proof that the design will answer the CER question. The CIP should make the connection between intended purpose, clinical claims, risks, objectives, endpoints and analysis visible before the first subject is enrolled.

Practical test

If the primary endpoint is met, which exact clinical claim or GSPR conclusion becomes supportable? If that cannot be answered, the design is not finished.

  1. 01

    Representative population

    Match the intended patients, relevant subgroups, users and use environment.

  2. 02

    Meaningful endpoints

    Measure outcomes linked to performance, benefit, safety and the state of the art.

  3. 03

    Defensible comparator

    Use the current clinical alternative or justify why another design answers the question.

  4. 04

    Adequate follow-up

    Capture the timing of benefits, foreseeable side-effects and relevant device failures.

  5. 05

    Sample-size logic

    Base assumptions on clinically meaningful effects and realistic event rates.

  6. 06

    Bias control

    Plan randomisation, blinding, adjudication or other controls where feasible and relevant.

  7. 07

    Missing-data strategy

    Predefine handling of withdrawals, protocol deviations and incomplete follow-up.

  8. 08

    Safety visibility

    Define events, reporting, monitoring, stopping rules and the analysis population.

After the database is locked

A study result does not enter the CER by copy and paste

The clinical investigation report is a source. The clinical evaluation must still decide how much weight that source deserves and what it changes.

01Verify conduct

Compare actual conduct with the approved CIP and account for deviations.

→
02Appraise validity

Assess bias, precision, completeness, relevance and statistical uncertainty.

→
03Interpret clinically

Distinguish statistical findings from clinically meaningful benefit and risk.

→
04Update the system

Revise CER conclusions, risk controls, GSPRs, labelling, PMS and PMCF.

Positive result

Support only what was actually demonstrated

A successful primary endpoint does not automatically support every population, indication, duration, variant or promotional claim.

Negative result

Do not make unfavourable evidence disappear

Analyse the cause, affected claims, benefit-risk impact, corrective actions and whether the intended purpose remains defensible.

Inconclusive result

Uncertainty is itself a regulatory finding

Decide whether the limitation can be resolved through analysis, further investigation, restricted claims, added controls or withdrawal of the claim.

Three evidence stories

The device name does not decide whether a study is needed

The answer changes with intended purpose, novelty, risk, claims, available data and residual uncertainty.

Scenario 01Investigation may not be needed

Established reusable surgical instrument

Assume a conventional instrument with a narrow intended purpose, mature technology, well-characterised risks and no novel clinical claim.

Evidence logic

Relevant literature, state of the art, verification, reprocessing validation, usability, risk management and market experience may provide a sufficient package.

Decision point

A clinical investigation is not added merely to make the file look stronger. The manufacturer documents why the available evidence is sufficient.

Scenario 02Own clinical data may be needed

Software with a new clinical recommendation

Assume an algorithm changes from displaying information to recommending a patient-specific clinical action in a new population.

Evidence logic

Software verification can confirm implementation, but it may not demonstrate clinical performance, generalisability, benefit or new use-related risks.

Decision point

If existing clinical data do not represent the new intended use, a prospective investigation or another justified human-data strategy may be necessary.

Scenario 03Investigation expected

Novel Class III implant

Assume a new implant design and material combination with long-term performance claims and limited relevant human experience.

Evidence logic

Article 61(4) starts from the requirement to perform clinical investigations, while novelty and long-term uncertainty also make transferable evidence difficult.

Decision point

The development programme should generate device-specific evidence and plan post-market follow-up for residual long-term questions.

Where evidence programmes fail

Seven expensive shortcuts

Most failures begin before study start or after study completion, at the points where strategy and evidence should connect.

  1. 01

    Writing the CIP before defining the exact CER gap, intended claims and decision the study must support.

  2. 02

    Assuming every piece of human-use information is relevant, reliable and sufficient clinical evidence.

  3. 03

    Using “similar” and “equivalent” as interchangeable terms without completing the Annex XIV equivalence analysis.

  4. 04

    Trying to solve technical, biological or use-related questions through a costly clinical investigation.

  5. 05

    Selecting convenient endpoints that cannot substantiate the intended clinical performance or benefit claim.

  6. 06

    Treating PMCF as a future repair plan for evidence that should have been available before conformity assessment.

  7. 07

    Summarising the final report in the CER without updating benefit-risk, GSPRs, risk management, labelling and residual gaps.

Practical questions

Clinical investigation and evaluation FAQ

Open each question for the distinction that usually changes the regulatory answer.

Does every medical device need a clinical investigation?+

No. Every device needs a clinical evaluation, but a new investigation is not automatically required for every device. For implantable and Class III devices, Article 61(4) starts from a mandatory investigation requirement subject to defined exceptions. For other devices, the need follows from the clinical evaluation objectives and the sufficiency of existing clinical evidence.

Can literature replace a clinical investigation?+

Sometimes existing literature contributes enough evidence, but only when it is relevant, methodologically sound and appropriately linked to the device. Reliance on another device's data for conformity requires a defensible equivalence demonstration. Similar-device literature can still inform the state of the art without proving conformity for the device under evaluation.

Is a PMCF study always a clinical investigation?+

No. PMCF includes different methods, from literature and registry analyses to surveys and formal investigations. When a PMCF activity meets the MDR definition of a clinical investigation, the applicable investigation requirements must be followed.

Can bench testing support a clinical evaluation?+

Yes. Non-clinical evidence is part of the overall conformity case and can support clinical conclusions when it answers the relevant technical or biological question. It should not be relabelled as clinical data, and it cannot replace human data where the unresolved question is inherently clinical.

Does a successful investigation guarantee a positive CER conclusion?+

No. The study must be appraised for relevance, quality, bias, precision and consistency with the complete evidence base. A positive result may support a narrow claim while leaving other safety, population, duration or lifecycle questions unresolved.

Can one investigation support several device variants?+

Potentially, if the variants are sufficiently represented or a scientifically justified bridge shows that the differences do not affect clinical safety, performance or benefit. The CER should make the applicability boundary explicit rather than treating a product family as automatically homogeneous.

Primary regulatory sources

Build the decision on the Regulation, then use guidance to test the reasoning

MDCG documents support a common application of the MDR but are not legally binding. Device-specific facts and applicable national requirements still control the final route.

From evidence gap to usable data

Need to decide whether your device requires a clinical investigation?

MDRC can review the clinical evidence strategy, define the unresolved questions, select the regulatory route and align the CIP, endpoints and analysis with the intended CER conclusions.

Discuss your evidence strategy ↗
↑

Discuss your regulatory pathway

Whether you are developing medical software, an AI-enabled healthcare solution, a digital health platform or a software-driven medical device, we can help define the regulatory strategy, evidence requirements and next steps.

→

Where companies need support

Regulatory strategy
Technical documentation
Clinical and performance evidence
Software lifecycle and cybersecurity
Notified Body readiness

Start a discussion

 

Regulatory support for software medical devices, AI health technologies and digital healthcare solutions.


©2026 MDRC - Medical Devices Regulatory Compliance

Useful information

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

How to obtain CE marking for medical software under the EU MDR or IVDR?

Technical documentation for Medical Device Software in the EU

Read more >>


Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.

Send us an email:
info@mdrc-services.com

Or use the contact form below

 

Solutions

EU Authorised Representative (EC REP)

EU PRRC

Technical documentation

Risk management

Clinical evaluation

Notified Bodies

Quality management system

Post-market surveillance

Resources

Medical Device Regulation (MDR) - basics

CE-marking process for medical devices

CE-marking process for in vitro diagnostic medical devices

MDR technical documentation checklist

IVDR technical documentation checklist

Technical documentation checklist for medical device software (MDSW)

MDR-compliant quality system documentation checklist

MDR-compliant quality system documentation checklist for medical device software

Clinical Evaluation Plan checklist

Clinical Evaluation Report checklist

PRRC under MDR or IVDR

Articles

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

More articles >>

Devices

General medical devices and equipment

In vitro diagnostics (IVD)

Medical software

Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.