Correction, Removal, or Recall? How to Navigate 21 CFR 806 When Your Device Has a Field Problem

Executive Takeaway

• What is misunderstood: “Recall” is an FDA classification, not a manufacturer action. Manufacturers initiate corrections or removals; FDA classifies the action as Class I, II, or III recall based on a health hazard evaluation.
• Why it matters: Failure to report a correction or removal under 21 CFR 806 within 10 working days can result in FDA enforcement action — even if the health risk is low. Over 68,000 recall records are tracked in the FDA database.
• What to do next: Map your field action decision tree before a problem occurs. Know the difference between correction (fix in the field), removal (return to manufacturer), and market withdrawal (not a recall). Document the health hazard evaluation.

When the Phone Rings: A Real-World Scenario

It starts with a Jira ticket flagged “urgent.” A field service engineer reports that a Class II patient monitor intermittently displays incorrect heart rate values — off by 15–20 bpm for 3–5 seconds before self-correcting. The software team reproduces the bug: a race condition in the data-rendering thread triggered under specific alarm configurations. Quality convenes an emergency meeting. Marketing argues the issue is rare and self-correcting — “don’t overreact.” The RA manager pulls up 21 CFR 806 and points out the 10-working-day reporting clock that starts the moment you determine a correction or removal is necessary. Nobody has performed a health hazard evaluation. The CEO walks in and asks the one question everyone dreads: “Is this a recall?” The honest answer is: “It depends — and we need to make that determination today.”

What the Regulation Requires

The medical device recall framework spans multiple regulations and guidance documents. Understanding which applies — and when — is critical for timely and compliant field actions.

21 CFR 806 — Reports of Corrections and Removals

Manufacturers and importers must report corrections and removals to FDA within 10 working days of initiating the action, unless the correction or removal was not undertaken to reduce a risk to health posed by the device or to remedy a violation of the FD&C Act (21 CFR 806.10). The report must include a description of the event, an evaluation of the risk, the total number of affected units, and the corrective action plan.

21 CFR 7 — FDA Enforcement Policy and Recall Classification

FDA classifies manufacturer-initiated corrections and removals into three recall classes:

• Class I: Reasonable probability that use of or exposure to the product will cause serious adverse health consequences or death.
• Class II: Use of or exposure may cause temporary or medically reversible adverse health consequences, or the probability of serious consequences is remote.
• Class III: Use of or exposure is not likely to cause adverse health consequences.

FDA Guidance: Distinguishing Recalls from Enhancements

FDA has issued guidance clarifying when a change to a device constitutes a reportable correction versus a product enhancement. A change that reduces a risk to health is a correction — even if it also adds features. Mislabeling an enhancement as a routine update to avoid reporting is a compliance risk.

Health Canada — Mandatory Problem Reporting (SOR/98-282)

Under the Medical Devices Regulations, manufacturers must report incidents involving a device that has led or could lead to serious injury or death. Recall actions must be reported to Health Canada, which maintains its own recall database and classification system.

EU MDR 2017/745 — Field Safety Corrective Actions

Article 83 requires manufacturers to report serious incidents. Article 87 mandates Field Safety Corrective Actions (FSCAs) and Field Safety Notices (FSNs) when a device poses an unacceptable risk. The competent authority must be notified, and the manufacturer must track the effectiveness of the corrective action.

Seven Common Failure Modes in Recall Management

1. Confusing “recall” with “removal”: A recall is FDA’s classification of your action. You initiate a correction or a removal. Many teams use the word “recall” internally and create confusion about their regulatory obligations.
2. Not reporting corrections because “it’s just a software update”: If the software update reduces a risk to health, it is a correction under 21 CFR 806 and must be reported. The delivery mechanism does not change the reporting obligation.
3. Missing the 10-working-day reporting window: The clock counts working days, not calendar days. Teams that count calendar days may file late — or teams that assume weekends and holidays count may file unnecessarily early, creating internal confusion about actual deadlines.
4. Health hazard evaluation performed by the wrong people: Marketing or sales should never drive the health hazard evaluation. This assessment requires clinical and engineering expertise to evaluate the probability and severity of harm. Bias toward minimizing the action is a documented audit finding.
5. No recall effectiveness check plan: FDA requires manufacturers to verify that the recall has reached all affected units. Without a documented effectiveness check plan — specifying audit methods, sample sizes, and success criteria — the recall is incomplete from a regulatory perspective.
6. Treating a market withdrawal as exempt from reporting: A market withdrawal involves removing a product from the market for reasons that do not involve a defect or violation. If the withdrawal actually addresses a health risk, it meets the definition of a correction or removal and requires 21 CFR 806 reporting.
7. Not linking field actions back to CAPA and risk files: A field action that does not trigger a CAPA investigation and risk file update creates a gap in your quality system. Auditors expect traceability from field problem detection through corrective action to risk re-evaluation.

Audit-Proof Evidence Checklist

The Correct Workflow: 10 Steps from Detection to Closure

1. Detect the problem. Sources include customer complaints, internal testing, adverse event reports, field service observations, or post-market surveillance data.
2. Assess immediate patient safety risk. Determine whether urgent communication (e.g., urgent field safety notice) is needed before completing the full evaluation.
3. Perform the Health Hazard Evaluation (HHE). Clinical and engineering teams assess the probability that the device will cause harm and the severity of that harm. This drives every subsequent decision.
4. Classify the action. Correction: the device is fixed in the field (e.g., software update, relabeling). Removal: the device is returned to the manufacturer or destroyed. Market withdrawal: the product is removed for reasons unrelated to a defect or health risk.
5. Determine the 21 CFR 806 reporting obligation. If the correction or removal is undertaken to reduce a risk to health or remedy a violation, it must be reported.
6. Submit the FDA 806 report within 10 working days of initiating the correction or removal. Use the FDA FURLS (FDA Unified Registration and Listing System) portal.
7. Develop the recall strategy. Define scope (lot numbers, serial numbers, date ranges), depth (user level, distributor level, retail level), and communication method (letter, email, phone).
8. Execute customer notification and track responses. Maintain a log of all notifications sent, responses received, and units accounted for.
9. Conduct recall effectiveness checks. Audit that affected units were actually corrected or returned. FDA expects documented evidence with defined success criteria.
10. Close the loop. Update the CAPA record, risk management file, and PMS documentation. Ensure the root cause is addressed and preventive actions are verified.

Practical Example: Software Bug in a Patient Monitor

Your device is a Class II patient monitor. Engineering discovers a software bug that causes intermittent incorrect heart rate display — values off by 15–20 bpm for 3–5 seconds before auto-correcting. Here is how to walk the decision tree:

The fix is a software update deployed remotely to all affected units. The device does not need to be returned. This makes the action a correction, not a removal. Does it meet 21 CFR 806 criteria? The software update reduces a risk to health — a clinician could make a treatment decision based on an incorrect vital sign — so the answer is yes, report it. The health hazard evaluation determines the severity: the incorrect reading is temporary and medically reversible if a clinician acts on a single erroneous reading. Expected FDA classification: Class II recall. You have 10 working days from the date you determined the correction was necessary to submit the report via FDA FURLS.

Ask Our Regulatory Intelligence Tool

TrueMedDevice tracks over 68,000 FDA recall records and 38,000 enforcement actions. Use our Regulatory Intelligence tool to search real regulatory data and get cited answers to recall-related questions.

Try these queries:

• “What Class I recalls have been issued for patient monitors in the last 3 years?”
• “Show me FDA recall classification criteria for software-related field actions”
• “What are the 21 CFR 806 reporting requirements for corrections vs removals?”

Ask a Recall Question →

Post-Market Surveillance for Recalls

Recalls are a critical PMS output. TrueMedDevice connects field actions to your product profile so you can monitor, document, and respond with audit-ready traceability.

• Monitor competitor recalls matching your device profile in real time — know when a similar device has a field problem before your auditor asks.
• Build a recall decision log with health hazard evaluation traceability — every field action linked to the evidence that drove the decision.
• Generate audit-ready field action reports linked to CAPA records and risk files — close the loop from detection to closure with documented evidence.

Take the Free PMS Gap Assessment →

Conclusion

Field problems are inevitable in medical device manufacturing. Software bugs, component failures, labeling errors — every manufacturer will face a field action decision at some point. What separates a compliant organization from an enforcement target is not whether problems occur, but how they are handled. Map your field action decision tree before you need it. Train your team on the difference between correction, removal, and market withdrawal. Ensure your health hazard evaluation process involves clinical and engineering expertise, not wishful thinking. The 10-working-day clock waits for no one.

TrueMedDevice tracks over 68,000 FDA recall records and thousands of enforcement actions. Search the database to see how similar devices have been handled — and build your response plan on real regulatory evidence.