The EU Clinical Investigation Exemption Still Needs a Clinical Evidence File

The easiest way to misread a regulatory exemption is to focus on the work it removes and ignore the evidence it leaves behind.

That risk is especially real for manufacturers affected by Commission Delegated Regulation (EU) 2026/1451. Published in the Official Journal on June 29, 2026, the regulation expanded the list of implantable and class III device technologies that may be exempt from the obligation to perform a clinical investigation under Article 61(6)(b) of the Medical Device Regulation. It entered into force 20 days after publication.

The expanded list is substantial. It includes technologies ranging from introducers, dilators, ventricular drains, feeding tubes, bone substitutes, dental implants, and reusable surgical instruments to guidewires, pacing leads, embolisation coils, and shunts.

That is meaningful regulatory relief for eligible devices. It is not an exemption from clinical evaluation, and it is not a conclusion that can be copied from the regulation into a technical file without device-specific analysis.

The list changed, but the evidence obligation did not disappear

The regulation is explicit on the point manufacturers cannot afford to miss: devices on the expanded list remain subject to the requirement to plan, conduct, and document a clinical evaluation under Article 61.

The exemption addresses whether a clinical investigation must be performed. It does not remove the need to demonstrate that the clinical evaluation is based on sufficient clinical data. Where a relevant common specification exists, the evaluation must also comply with it.

For a regulatory team, this changes the central question. The question is no longer simply, "Is our technology named on the list?" It becomes, "Can we show that this particular device, for this intended purpose and configuration, belongs within the scope of the listed technology and has sufficient clinical evidence?"

That distinction matters because the regulation names technology types, not every possible variant, material, feature, indication, anatomical location, or patient population. A familiar product family can still contain a device whose design, intended purpose, or risk profile stretches beyond the evidence supporting the well-established technology.

Start with device-specific eligibility

Create a controlled eligibility record before revising the clinical development plan. The record should identify the exact technology entry, the device and variants being assessed, intended purpose, classification, implantable status, materials, design features, patient population, and the clinical claims that need support.

Then document where the device matches the well-established technology and where it differs. Differences deserve attention even when they appear modest. A coating, delivery method, new anatomical site, altered duration of use, or expanded indication may affect whether existing clinical data remain sufficient.

This is also where regulatory, clinical, risk, and design owners need to work from the same product definition. If the clinical team evaluates one configuration while the design file, labeling, and notified-body submission describe another, the exemption decision becomes difficult to defend.

The strongest eligibility record does not try to prove that every difference is immaterial. It identifies the differences and explains, with evidence, why they do or do not change the conclusion.

Rebuild the clinical evaluation plan around the exemption

Once eligibility is established, update the clinical evaluation plan. Do not simply remove the planned investigation and leave the rest of the document untouched.

The plan should explain the evidence sources that will support safety, performance, and clinical benefit; the methods used to identify and appraise those sources; the relationship between each clinical claim and its supporting data; and how post-market clinical follow-up will address residual uncertainty.

Sufficient clinical data still has to be shown

"Sufficient" is not a fixed number of papers, years on the market, or units sold. It is a conclusion about whether the available evidence is adequate for the device, intended purpose, and risks being assessed.

Build a claim-to-evidence matrix. For each clinical claim, identify the relevant clinical data, product relationship, limitations, and any remaining evidence gap. Link that matrix to the risk management file so the clinical evidence addresses the safety and performance questions that matter for the actual device.

If the evidence is broad but the new claim is narrow and novel, volume alone will not close the gap. The evaluation must still explain why the evidence is applicable.

Equivalence cannot become a shortcut

Manufacturers may use data from equivalent devices when the MDR conditions for equivalence and access to data are met. The new list does not relax those conditions.

Treat equivalence as its own controlled assessment. Compare technical, biological, and clinical characteristics. Identify the source of the data and the level of access available. Record who reviewed the conclusion and what new information would trigger reassessment.

If the equivalence case depends on assumptions that cannot be verified, the exemption does not repair that weakness. The team needs another evidence path.

Put the exemption through change control

The regulation may affect clinical plans, regulatory submissions, technical documentation, contracts with clinical vendors, budgets, timelines, and post-market commitments. That makes it a change-control event, not merely a regulatory-news item.

Open one cross-functional assessment for each affected product family. Map the downstream documents and decisions. A revised investigation strategy may require updates to the clinical evaluation plan and report, risk management documentation, general safety and performance requirements checklist, post-market clinical follow-up plan, regulatory strategy, and notified-body communication plan.

Assign an owner and approval path for each change. Preserve the prior strategy and the reason it changed. If a planned clinical investigation is paused or cancelled, document how commitments, vendor work, ethics submissions, and data already collected will be handled.

This is where connected compliance infrastructure changes the operating model. A product classification decision can be linked directly to the clinical evaluation, device variants, risk controls, design changes, regulatory correspondence, and post-market evidence. Teams no longer have to reconstruct the reason for the decision from separate trackers after the technical file has moved on.

IntelaSolve's medical-device compliance platform is designed around that lifecycle relationship, connecting design controls and risk management with clinical, regulatory, quality, and post-market work. It does not decide whether a device qualifies for the exemption. It gives the qualified team a controlled place to document the decision and keep its consequences traceable.

Five actions for affected manufacturers

1. Screen the device portfolio against the expanded Article 61(6)(b) list, including variants and intended purposes.
2. Create a device-specific eligibility record instead of relying on a technology name alone.
3. Update the clinical evaluation plan and claim-to-evidence map, including the rationale for sufficiency.
4. Route the strategy change through design, risk, regulatory, and post-market owners before cancelling or revising clinical work.
5. Confirm the evidence and communication expectations with the notified body where the interpretation could materially affect the conformity-assessment plan.

The broader global markets view also matters for manufacturers selling the same product outside the EU. An EU investigation exemption does not automatically change evidence expectations in another jurisdiction. Keep the market-specific decision attached to the global product record so one region's strategy is not silently applied to another.

Regulatory relief is strongest when the evidence trail is clear

The 2026 regulation can reduce unnecessary clinical-investigation burden for genuinely well-established technologies. The benefit is real. So is the responsibility to show why the exemption applies and why the remaining clinical data are sufficient.

The practical test is simple: could a reviewer move from the listed technology to the exact device, intended purpose, clinical claims, supporting data, risk controls, and post-market plan without guessing? If the answer is yes, the exemption is being used as intended. If the answer is no, the file needs more work before the clinical program changes course.

Related reading: living clinical evidence system.