Market Withdrawal vs. Recall: What Your CER Must Address

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

I see this confusion repeatedly during technical documentation reviews. Manufacturers treat market withdrawal and recall as interchangeable terms. They write incident sections in the CER that cover “post-market actions” generically, without distinguishing what triggers each path and what clinical documentation is required for each.

The MDR does not use the term “market withdrawal” explicitly in the way manufacturers commonly use it. Article 10(9) and Article 95 describe obligations when a device presents an unacceptable risk or when a corrective action is needed. Vigilance under Article 87 to 92 establishes the framework for serious incidents and field safety corrective actions, which often result in recall.

But market withdrawal happens in practice. It happens when a manufacturer decides to stop selling a device for commercial, strategic, or quality reasons that do not involve immediate safety risk. The regulatory question is: what must the clinical evaluation say about both scenarios?

What Defines a Recall Under MDR

A recall is a field safety corrective action. It is triggered when a device on the market presents a risk that requires action to prevent harm or mitigate harm already occurring. This is governed by Article 89 MDR, which requires manufacturers to report serious incidents and implement corrective actions.

The recall may involve return of the device, modification, destruction, or specific instructions to users. The key element is that it stems from a safety concern identified post-market.

Clinically, this means the CER must contain an analysis framework that can accommodate new safety data. The clinical evaluation is not a static document. It is a living assessment. When a recall occurs, the clinical evaluation must be updated to reflect the nature of the incident, the root cause, the clinical impact, and whether the benefit-risk profile remains acceptable after corrective action.

During audits, Notified Bodies and competent authorities look for this integration. They want to see that the CER structure anticipates the possibility of significant post-market findings. They check whether the benefit-risk methodology can absorb new serious incident data without collapsing into vague reassurances.

What Defines a Market Withdrawal

Market withdrawal, in the practical regulatory sense, refers to the manufacturer’s decision to stop making a device available. This may be for reasons unrelated to immediate safety risk: discontinuation of a product line, business restructuring, inability to meet updated standards, or strategic exit from a market segment.

The MDR does not require a Field Safety Notice or a Competent Authority report for a simple commercial withdrawal. But—and this is where manufacturers stumble—the clinical evaluation must still address why the device is being withdrawn and whether any clinical or safety consideration contributed to that decision.

If the withdrawal is purely commercial, the CER update should state that explicitly and confirm that no new clinical data or post-market surveillance findings prompted the action. If there were borderline safety signals, quality trends, or complaint patterns that influenced the decision, those must be documented and analyzed clinically.

What I see in practice: manufacturers withdraw a device quietly, update the technical file with a note that says “product discontinued,” and leave the clinical evaluation untouched. Two years later, during a surveillance audit or when launching a similar device, the Notified Body asks: was there a clinical reason for withdrawal? The manufacturer has no documented answer. The gap creates doubt.

Clinical Evaluation Requirements for Recall

When a recall occurs, the CER must be updated under Article 10(4) and Annex XIV, Section 1. The update must address the following:

Nature and clinical significance of the incident: What happened? Was it a design flaw, a manufacturing deviation, a labeling issue, or a user error pattern? The clinical evaluation must interpret the incident in clinical terms, not just technical terms.

Root cause and relevance to benefit-risk: Does the root cause indicate a broader issue with the device’s clinical performance? Does it affect the conclusions drawn in the original CER about safety and effectiveness?

Effectiveness of the corrective action: After the recall and corrective action, does the device still meet its intended clinical performance? Is the benefit-risk balance still favorable? This requires clinical judgment, not just a statement that the technical issue was corrected.

Impact on equivalence or clinical data validity: If the CER relies on equivalence to another device, does the recall break that equivalence? If clinical investigations were conducted, does the incident suggest that the study population or follow-up duration was insufficient to detect the failure mode?

These are not checkbox items. They require analysis. I have reviewed CER updates after recalls where the manufacturer added two sentences: “A recall was conducted. The issue is resolved.” That does not satisfy Annex XIV. The clinical evaluation must show that the manufacturer understands the clinical implications and has re-confirmed acceptability.

Timeline and Documentation

The recall triggers immediate vigilance reporting under Article 87. The CER update does not need to happen within the same 15-day window, but it must happen without undue delay, typically as part of the next periodic safety update report (PSUR) cycle or sooner if the benefit-risk conclusion changes.

The CER update must reference the Field Safety Notice, the corrective action report, and any Competent Authority feedback. It should also reference updated post-market surveillance data that shows whether the corrective action was effective.

If the recall was significant enough to require Notified Body notification under Article 89(5), the Notified Body will review the CER update as part of their assessment of whether the certificate remains valid.

Clinical Evaluation Requirements for Market Withdrawal

For a market withdrawal that is not a recall, the CER update requirement is less prescriptive but still necessary. The update should:

Confirm the reason for withdrawal: State clearly that the withdrawal was a business decision, a strategic choice, or a response to regulatory change (such as reclassification or new standards). If quality or complaint trends influenced the decision, describe them.

Summarize final post-market data: Present the final snapshot of post-market surveillance data up to the point of withdrawal. This ensures that the clinical evaluation closes with a complete record, not an open question.

Address any unresolved clinical questions: If the device was withdrawn before completing a planned PMCF study, explain what was completed, what was learned, and why continuation was not feasible or necessary.

Impact on related devices: If the withdrawn device shares design, materials, or clinical data with other devices in the manufacturer’s portfolio, state whether the withdrawal affects the clinical evaluation of those devices.

This documentation prevents future ambiguity. It also supports transparency if the manufacturer later seeks to reintroduce a similar device or if a competent authority questions the withdrawal during a market surveillance inspection.

How Notified Bodies and Competent Authorities Review This

During technical documentation reviews, I see how Notified Bodies approach this topic. They ask: is there a pattern of withdrawals? Are there devices that were quietly removed from the market after complaint spikes? Is the CER update consistent with vigilance records?

They cross-check. They compare the clinical evaluation narrative with the vigilance database, the PSUR, and the quality management system records. If the CER says “no clinical issues” but the complaint log shows a rising trend before withdrawal, they will ask for clarification.

Competent authorities conducting post-market surveillance inspections ask similar questions. They want to ensure that withdrawals are not being used to avoid recall obligations. They check whether the manufacturer’s internal decision-making process included a clinical evaluation review before deciding that a withdrawal was sufficient.

The key is traceability. The CER must show that clinical considerations were part of the decision process, even if the final decision was commercial.

Practical Implications for Your CER

Build a section in your CER template that addresses post-market corrective actions and withdrawals. This section should be structured to accommodate updates without requiring a full rewrite of the document.

In your PMCF plan, define triggers for CER updates. Include not only serious incidents but also withdrawal scenarios. Clarify who is responsible for initiating the CER update and what data sources must be consulted.

Train your clinical affairs and regulatory affairs teams to recognize when a withdrawal decision requires clinical evaluation input. The decision should not be made in isolation by the commercial or quality team.

When updating the CER after a recall or withdrawal, include a clear conclusion statement. Do not leave the analysis open-ended. State explicitly whether the benefit-risk profile remains acceptable or whether the device should no longer be placed on the market.

What Happens When This Is Done Poorly

I have seen manufacturers lose their certificates because they could not demonstrate clinical oversight of post-market actions. The Notified Body concluded that the manufacturer did not have adequate control over clinical evaluation updates.

I have seen competent authorities issue corrective action requests because the CER did not reflect known recalls, creating the appearance that the manufacturer was hiding safety data.

I have seen manufacturers struggle to launch new devices because the clinical evaluation for a withdrawn predecessor device was incomplete, and the Notified Body questioned whether the same issues would reappear.

These are not theoretical risks. They are real outcomes of insufficient documentation discipline.

Final Thought

The clinical evaluation is not just a pre-market document. It is the clinical record of your device throughout its lifecycle. Whether you recall a device or withdraw it for business reasons, that record must remain complete and defensible.

The difference between recall and withdrawal is clinically significant. One responds to identified risk. The other may be strategic. But both require documentation that shows clinical judgment was applied, data was reviewed, and the decision was traceable.

When your CER treats these scenarios clearly, it becomes a tool for regulatory confidence, not a source of audit findings.

Next time you face a withdrawal or recall decision, ask: what does the clinical evaluation need to say about this? Answer that question in writing, and you will have what the Notified Body expects to see.

Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.