Competitor Recall: Is Your Clinical Evaluation Still Valid?

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

Recalls happen. Devices fail. Investigations reveal design flaws, manufacturing issues, or clinical risks that were not detected during the conformity assessment. When this happens to your competitor, it creates immediate implications for your technical file—especially if your clinical evaluation references that device in any capacity.

The problem is that most regulatory teams treat recalls as external events. They update their vigilance monitoring. They document the recall in their literature search. But they do not reassess the validity of their own claims. That creates a gap between what the file says and what the evidence supports. Notified Bodies notice this gap. They ask for updates. And those updates often require substantial rework.

Why Competitor Recalls Affect Your Clinical Evaluation

Clinical evaluations are built on literature, clinical investigations, and equivalence claims. When you cite a device as similar to yours, you are borrowing credibility from its clinical data and post-market history. If that device experiences a significant safety event, the credibility disappears. The evidence base changes.

This is not theoretical. MDR Article 61(5) requires manufacturers to update their clinical evaluation throughout the device lifecycle. MDCG 2020-13 clarifies that post-market data, including adverse events and recalls, must be integrated into the appraisal of clinical evidence. If a device you reference experiences a recall, your clinical evaluation is no longer current.

Most teams understand this in principle. But in practice, they underestimate the scope of the required update. They think it is enough to mention the recall in the PMCF report or add a paragraph to the next clinical evaluation update. That misses the deeper issue.

The recall signals that something was wrong with the risk-benefit assessment. If your device is similar enough to use that device in your equivalence claim, it is also similar enough to share that risk profile. You need to demonstrate that your device does not have the same flaw. That requires technical analysis, not just documentation.

What Triggers a Required Update

Not every recall demands the same response. The nature of the recall determines the scope of your update. If the recall is due to a labeling error, the impact on your clinical evaluation may be minimal. If the recall is due to a design flaw that affects safety or performance, the impact is significant.

Three factors determine whether your clinical evaluation needs substantial revision:

First: The reason for the recall. Was it a manufacturing defect specific to a single batch, or was it a design issue present in all units? If the issue is systemic, it affects the clinical evidence you relied on. That evidence now includes a known failure mode.

Second: Your claimed equivalence. Did you use this device as a reference for technical, biological, or clinical equivalence? If yes, the recall directly challenges your equivalence argument. You need to show that your device does not share the root cause of the failure.

Third: The severity and frequency of the adverse events. A recall based on isolated complaints may not change your benefit-risk conclusion. A recall based on a pattern of serious injuries does. The clinical data you used to support your device now shows unacceptable risk under real-world conditions.

If any of these factors apply, your clinical evaluation is out of date the moment the recall is announced.

The Equivalence Problem

Equivalence claims are the most common pathway to demonstrate clinical evidence under MDR. MDCG 2020-5 sets strict criteria: technical, biological, and clinical equivalence must all be demonstrated. When a device you use for equivalence is recalled, one of these equivalences is called into question.

If the recall is due to a material issue, biological equivalence is challenged. If the recall is due to a design flaw, technical equivalence is challenged. If the recall is due to unexpected clinical complications, clinical equivalence is challenged. In any case, you need to demonstrate that your device does not have the same vulnerability.

This is more than an academic exercise. Notified Bodies ask for a clear explanation of how your device differs from the recalled device in the specific aspect that caused the failure. They ask for test data, design documentation, or clinical data that proves the difference. They do not accept statements like