MDRC logo
Explore
← Knowledge centre

MDR Article 61 · Annex XIV · Class I

Class I does not mean clinical evidence is optional

The evidence package may be proportionate. The reasoning still has to be rigorous.

A simple device can have a concise clinical evaluation, but not an empty one. The manufacturer must connect the intended purpose, clinical claims, risks, available data and post-market plan into a defensible clinical story.

Updated 10 February 2025 11-minute guide Current MDR framework
Start with the device route ↓

The rule in one sentence

Risk class changes the depth of the evaluation, not the obligation to perform it

01The manufacturer must specify and justify the clinical evidence level appropriate to the device and its intended purpose.

02The evaluation must be planned, methodologically sound, documented in a CER and updated throughout the device lifecycle.

First question

Which Class I route actually applies?

All four routes require technical documentation and clinical evaluation. What changes is whether a notified body has a limited role in the conformity assessment.

I

Manufacturer self-declaration

Technical documentation comes before the declaration

The manufacturer draws up the Annex II and III technical documentation, completes the clinical evaluation and issues the EU declaration of conformity. Self-declaration is not evidence exemption.

  • No notified body for the ordinary Class I route
  • Clinical Evaluation Plan and Clinical Evaluation Report required
  • Class I PMS report under MDR Article 85

The evidence workflow

Build the CER from claims outward

Starting with a literature search is tempting. Starting with the intended purpose and the claims prevents a beautifully documented search from answering the wrong questions.

01Scope

Lock the intended purpose

Define users, patient population, indications, contraindications, anatomical site, duration, operating principle and product variants.

02Claims

Translate claims into outcomes

State what the device is expected to achieve clinically and identify the safety, performance and benefit-risk questions to be answered.

03Level

Justify the evidence depth

Consider novelty, contact with the body, clinical claims, known risks, state of the art, product history and uncertainty.

04Data

Identify and appraise evidence

Search systematically, include favourable and unfavourable data, assess relevance and quality, and expose the gaps.

05Gaps

Generate what is missing

Use the right method for each gap. That may be bench testing, preclinical work, usability data, PMCF or a clinical investigation.

06Lifecycle

Conclude, monitor and update

Align the CER with risk management, GSPR evidence, labelling, PMS and PMCF, then define when new information triggers review.

Proportionate does not mean superficial

A Class I evidence package is usually mixed

Clinical evidence rarely comes from one perfect source. The CER should explain what each source contributes and where it cannot carry the argument.

Important boundary

Bench, biocompatibility and usability testing are not automatically clinical data. They can still be essential non-clinical evidence supporting safety, performance and the justification of the clinical evidence level.

01

Direct device data

Clinical investigations, published experience, complaints, vigilance, PMCF and real-world use relating to the evaluated device.

Highest direct relevance
02

Equivalent-device data

Clinical data may support conformity only when technical, biological and clinical equivalence is demonstrated and data access is sufficient.

Requires full equivalence
03

Similar devices and state of the art

Useful for clinical background, benchmark outcomes, known risks and alternative options, but not automatically proof for the subject device.

Context and benchmarks
04

Non-clinical verification

Performance, biological safety, usability, packaging, sterilisation, reprocessing and shelf-life data close specific technical questions.

Supports defined gaps
05

Post-market evidence

Sales exposure, complaints, trend data, literature, user feedback, incidents and PMCF test whether the pre-market conclusions remain true.

Lifecycle confirmation

The equivalence trap

“Similar” is a search term. “Equivalent” is a conclusion.

Decades of use by comparable products can be valuable. It does not remove the need to show why their data apply to your device.

Technical

Does the device work in materially the same way?

Compare design, specifications, physicochemical properties, conditions of use, deployment, operating principle and critical performance.

Biological

Does the body encounter the same materials?

Compare materials and substances, contact tissues and fluids, contact type and duration, and release characteristics including degradation products and leachables.

Clinical

Is the clinical context genuinely comparable?

Compare purpose, condition, severity, body site, population, intended user, critical performance and the expected clinical effect.

Gate 01No clinically significant difference in safety or clinical performance
+
Gate 02Proper scientific justification across all relevant characteristics
+
Gate 03Sufficient access to the data needed to support the equivalence claim

Do you need a clinical investigation?

Class I is not the answer. Evidence sufficiency is.

MDR does not automatically require a pre-market clinical investigation for every Class I device. Annex XIV does require new clinical data when the available evidence leaves relevant questions unresolved.

01

Are the intended purpose and claims conventional?

Novel claims can raise the evidence requirement even when the hardware appears simple.

02

Is the available evidence directly relevant?

General literature about a product category may not support a specific performance or benefit claim.

03

Can every material gap be closed without human data?

Article 61(10) requires a device-specific justification when non-clinical methods alone are considered adequate.

04

What uncertainty remains after risk controls?

If a clinically important question remains open, a focused investigation or PMCF activity may be the shortest defensible route.

Evidence sufficient

Document why the combined clinical and non-clinical evidence supports each claim and relevant GSPR. Define proportionate post-market confirmation.

or
Material gap remains

Generate targeted data. Do not disguise an unresolved clinical question as a generic “low-risk device” justification.

Two worked scenarios

The intended purpose changes the evidence story

Product names do not determine classification. The claims, contact, mode of action and conditions of use do.

Scenario 01 Potential route · Class I

Non-sterile adhesive dressing for a superficial injury

Assume the intended purpose is limited to acting as a mechanical barrier and absorbing exudate from a minor superficial injury.

Why Class I may apply

MDR Rule 4 places wound-contact devices in Class I when they are intended as a mechanical barrier, for compression or for absorption of exudates.

Likely evidence package

State-of-the-art literature, material and biocompatibility data, adhesive and absorption performance, skin-reaction risks, usability, comparable market experience and PMS.

Classification boundary

A dressing intended to manage the wound micro-environment is generally Class IIa. A product principally intended for certain deeper wounds healing by secondary intent can be Class IIb.

Scenario 02 Route · Class Ir

Reusable scalpel handle without an active-device connection

Assume the instrument is intended for surgical cutting, is reused after validated reprocessing and meets the MDR definition of a reusable surgical instrument.

Why Class Ir applies

Rule 6 places reusable surgical instruments in Class I, while Article 52(7) requires limited notified-body involvement for the reuse-related aspects.

Likely evidence package

Clinical and state-of-the-art literature, functional and material evidence, usability and handling, validated cleaning and sterilisation, reuse-cycle testing, degradation limits, risk management and PMS.

Evidence boundary

Reprocessing validation does not replace clinical evaluation. It answers an essential reuse question within the wider safety and performance case.

After CE marking

The CER becomes a loop, not an archive

Article 61 requires the clinical evaluation and its documentation to be updated throughout the device lifecycle using PMCF and PMS information.

Class I reporting

Manufacturers prepare a PMS report under Article 85 rather than the PSUR required for Classes IIa, IIb and III. The report is updated when necessary.

Clinical
evaluation
Current conclusion
01PMS and PMCF
02Risk review
03Claims and labelling
04CER update

What weak Class I CERs get wrong

Seven shortcuts that create longer reviews later

The recurring problem is not a short report. It is a report whose conclusions cannot be traced back to the device, the claims and the data.

  1. 01

    Using “Class I” as the justification for a low evidence level instead of analysing device characteristics, intended purpose, claims and risks.

  2. 02

    Calling competitor products equivalent without a technical, biological and clinical comparison or sufficient access to the underlying data.

  3. 03

    Presenting bench or biocompatibility testing as clinical data instead of explaining its proper role in the overall evidence package.

  4. 04

    Searching only for favourable publications and omitting known adverse effects, recalls, safety notices or alternative treatments.

  5. 05

    Writing a literature summary without defining acceptance criteria, appraising study quality or mapping evidence to claims and GSPRs.

  6. 06

    Waiving PMCF with a generic sentence rather than a device-specific justification supported by the CER, risk management and PMS strategy.

  7. 07

    Allowing the CER, risk file, IFU, marketing claims and post-market plan to describe slightly different products.

Practical questions

Class I clinical evaluation FAQ

The shortest reliable answer is usually conditional. Open each question for the boundary that matters.

Does every Class I medical device need a Clinical Evaluation Report?+

Yes. MDR Article 61 and Annex XIV require the clinical evaluation, its results and the clinical evidence to be documented in a CER that forms part of the technical documentation.

Does every Class I device need a clinical investigation?+

No. The need depends on whether the available clinical and non-clinical evidence is sufficient for the intended purpose, claims, risks and relevant GSPRs. New clinical data are needed when material clinical gaps remain.

Can literature about competitor devices support the CER?+

Yes, but its role must be clear. Similar-device literature can establish the state of the art and known risks. Reliance on another device's clinical data as evidence for conformity requires a defensible equivalence demonstration.

Can PMCF be considered not applicable for a simple Class I device?+

Potentially, but the technical documentation must contain a device-specific justification. The manufacturer must still maintain PMS, review new clinical information and update the clinical evaluation throughout the lifecycle.

Does a notified body approve the full CER for Class Is, Im or Ir?+

Article 52(7) limits the notified body's mandated involvement to sterility, metrological or reuse-related aspects, as applicable. The manufacturer remains responsible for the complete clinical evaluation and technical documentation.

Primary regulatory sources

Go back to the rule when the answer feels too easy

MDCG documents are guidance and do not replace the Regulation. They help translate the legal requirements into a reviewable evidence process.

From “low risk” to defensible evidence

Need a Class I clinical evaluation that is proportionate without being fragile?

MDRC can review the classification, define the clinical evidence strategy, identify avoidable gaps and prepare or update the CEP and CER.

Discuss your device ↗
↑

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.