MedDeviceGuideMedDeviceGuide
Back
Post-Market SurveillanceRegulatoryPolicy & LegislationUSEUBrazilThailandGlobal

Recall vs FSCA Compared: FDA 21 CFR 806, EU MDR, Brazil & Thailand

Side-by-side legal-text comparison of medical device field actions: FDA 21 CFR Part 806, EU MDR FSCA/FSN, Brazil RDC 551/2021, and Thailand recall guidance — triggers, timelines, filing objects.

Ran Chen
Ran Chen
Global MedTech Expert | 10× MedTech Global Access
Published 2026-06-16Last reviewed 2026-06-1610 min read

Two Terms, Four Legal Frameworks — Pick the Wrong One and Miss a Deadline

When a device already on the market has to be retrieved or corrected, four legal texts decide what you file, with whom, and how fast: the FDA's corrections-and-removals rule (21 CFR Part 806), the EU MDR's Field Safety Corrective Action (FSCA) regime (Articles 87, 89 and Article 2(68)), Brazil's field-action resolution (ANVISA RDC 551/2021), and Thailand's recall/field-safety guidance (Thai FDA, MoPH Notification B.E. 2563/2020). They look interchangeable — every one of them is about getting a risky device off the field — but the filing object, the trigger, and the clock are different in each, and the word "recall" itself means different things.

This is a regulatory-research comparison for compliance planning, not legal advice for a specific product. Verify every hook against the official text listed at the end.

Side-by-Side: Filing Object, Trigger, and Clock

Dimension FDA (US) EU MDR Brazil (ANVISA) Thailand (Thai FDA)
Legal text 21 CFR Part 806 (reporting) + Part 7 (recall framework) Regulation (EU) 2017/745, Art. 2(68), 87, 89 + Annex; MDCG 2023-3 RDC 551/2021 (field actions) + RDC 67/2009 (technovigilance) MoPH Notification B.E. 2563 (2020) + Thai FDA recall & FSCA guidance
Regulated party Manufacturer or importer who initiates the action Manufacturer (or authorized representative) Registration holder (BRH) — joint responsibility along the chain Registered manufacturer/importer or market authorization holder
Concept "Correction" (no physical removal) or "Removal" (physical removal); "recall" is the Part 7 umbrella FSCA — corrective action for technical/medical reasons to reduce risk of a serious incident Ação de campo (field action) — includes recall and other corrective actions "Product recall" + FSCA (uses the same term as the EU)
Trigger Action to reduce a risk to health or remedy a violation that may present a risk to health Any action to reduce the risk of a serious incident from a device already on the market Device no longer meets essential safety/effectiveness requirements; minimize risk effectively and timely Device defect/adverse event making the product unsafe; FSCA to reduce risk
Filing object 806 report (Form FDA 3389 / eMDR ecosystem context) to the District Recall Coordinator FSCA report via EUDAMED (Art. 92) before the action, except in urgency Field-action notification to ANVISA + alert to consumers Recall/FSCA report to the Health Product Vigilance Centre (HPVC)
Clock 10 working days from initiation (§806.10(b)) In advance of the action; incident clocks of 2 / 10 / 15 calendar days Promptly per severity (RDC 67/2009 timelines); alert distributed when action taken 10 days (death/serious injury) or 30 days (potential death/serious harm) from awareness
Public notice Class I/II → public warning; FSN concept is not native Field Safety Notice (FSN) reviewed by CA (≥48 h) before distribution Alert message distributed to consumers; HPVC-style public listing HPVC publishes vigilance news and recall on its website

FDA: 21 CFR Part 806 and the "Risk to Health" Gate

The US system separates the recall (run under 21 CFR Part 7, where the FDA classifies the action as Class I/II/III by hazard under §7.3) from the report of that action (Part 806). The reporting duty is the one that creates a hard clock.

  • §806.10(a): a device manufacturer or importer must submit a written report of any correction or removal initiated (1) to reduce a risk to health posed by the device, or (2) to remedy a violation of the act that may present a risk to health.
  • §806.10(b): the report is due within 10 working days of initiating the correction or removal — "initiation" meaning the first implementing step, e.g., first notice to consignees.
  • §806.2(d)/(i): a correction is repair/modification/adjustment/relabeling/destruction/inspection without physical removal; a removal is the physical removal of the device from its point of use.
  • §806.1(b) exemptions: quality improvements that do not reduce a risk to health are exempt from reporting (but still subject to recordkeeping under §806.20).

Cross-market trap: "risk to health" in §806 tracks the Class I and II recall definitions in §7.3(m). A Class III recall (unlikely to cause adverse health consequences) is recordkeeping only — no 806 report. Firms that assume "any retrieval = reportable" over-report; firms that assume "no injury yet = not reportable" miss the clock, because the trigger is the intent of the action, not whether harm has occurred.

Recommended Reading
Adverse-Event Reporting Compared: FDA 21 CFR 803, EU MDR, Brazil, Thailand & SA
Post-Market Surveillance Regulatory2026-06-16 · 14 min read

EU MDR: FSCA Is a Pre-Action Filing, Not a Post-Action Report

The EU's FSCA concept is the structural opposite of the FDA's: it is filed before the corrective action is carried out, not after.

  • Article 2(68): an FSCA is a corrective action taken by the manufacturer for technical or medical reasons to prevent or reduce the risk of a serious incident associated with a device already made available on the market.
  • Article 89(1) + 87(1)(b): except in cases of urgency, the manufacturer reports the FSCA without undue delay and in advance of the action being undertaken, through the electronic system (EUDAMED, Art. 92).
  • Incident clocks (Art. 87(3)–(5)), in calendar days: a serious public health threat → 2 days; death or unanticipated serious deterioration → 10 days; all other serious incidents → 15 days. An initial incomplete report followed by a complete report is permitted (Art. 87(6)).
  • Field Safety Notice (FSN): the manufacturer prepares an FSN for each FSCA; competent authorities review it before distribution (minimum 48 hours under the vigilance guidance).
  • What an FSCA can comprise (per the MDR vigilance guidance): return of the device to the supplier, device modification, exchange, destruction, a retrofit (manufacturer's modification applied in the field), a software update, or advice on use — including for devices already withdrawn from the market but still implanted or in use.
  • MDCG 2023-3 (rev. 2) clarifies that "day 0" is the manufacturer's awareness date, and the reporting period runs in calendar days (including weekends/holidays).

Cross-market trap: the EU FSCA is a prospective notification ("we are about to act"), whereas the FDA Part 806 report is a reactive account ("we started acting on day X"). A manufacturer that files the EU-style pre-notification to the FDA, or the US-style 10-working-day post-report to an EU competent authority, will be using the wrong instrument for the wrong audience.

Brazil: RDC 551/2021 and the Registration-Holder Anchor

Brazil does not split "recall" from "correction" the way the US does; it uses a single field action (ação de campo) concept, anchored on the registration holder.

  • Article 1: RDC 551/2021 defines the situations in which the execution and notification of field actions by medical-device registration holders in Brazil are mandatory, and their minimum requirements.
  • Article 2 + sole paragraph: the registration holder (the entity holding the ANVISA registration/notification) is the responsible party; the registration holder and every other agent from production to use are jointly responsible for quality, safety, and effectiveness down to the end consumer.
  • Article 4: a field action is triggered when a medical device does not meet the essential safety and effectiveness requirements, and must be planned to minimize the risk to health in an effective and timely manner.
  • Alert obligation: an alert outlining the corrective action must be reported to ANVISA and distributed to consumers when the field action is taken; monitoring and final reports follow under the technovigilance regime (RDC 67/2009).

Cross-market trap: a foreign manufacturer without a Brazilian Registration Holder (BRH) cannot file a field action itself — the BRH is the only legal addressee. Adverse-event and field-action timelines live in RDC 67/2009, not 551/2021, so firms must read both side by side.

Thailand: Parallel "Recall" and "FSCA" Tracks Under One Centre

Thailand is the one jurisdiction here that formally uses both "recall" and "FSCA" as distinct instruments, governed by a single Ministerial Notification and operationalized by one vigilance centre.

  • MoPH Notification B.E. 2563 (2020): "Criteria, procedures and conditions for preparation of reports on medical device defects or adverse events occurring to consumers and reports on field safety corrective actions for medical devices" — the binding instrument.
  • Thai FDA guidance (two documents): Guidance for the Medical Device Industry: Reporting of Device Defects, Adverse Events and Field Safety Corrective Actions, and Guidance for the Medical Device Industry on Product Recalls — both issued by the Health Product Vigilance Centre (HPVC).
  • Responsible parties: registered manufacturers/importers and market authorization holders of licensed devices.
  • Clocks: report within 10 days of awareness where a death or serious injury has occurred; within 30 days where evidence indicates a recurrence could lead to death or serious harm. Reports go to the HPVC (online or in person), which then publishes vigilance news and the recall on its website.

Cross-market trap: Thailand's FSCA terminology mirrors the EU's, but its recall track and HPVC-centric public listing are local. A manufacturer assuming the EU's "file in advance via EUDAMED" model will find Thailand expects awareness-date reports to a national centre with its own 10/30-day structure.

Recommended Reading
Investigational Device Rules Compared: FDA 21 CFR 812, EU MDR, SFDA & Health Canada
Clinical Evidence Regulatory2026-06-16 · 10 min read

What to Verify in the Original Text

  • 21 CFR 806.10(a)–(b) and 806.2(d),(i): confirm the 10-working-day clock, the correction/removal definitions, and that the trigger is "risk to health" — then cross-check §7.3(m) and the Class I/II/III recall definitions that govern whether an 806 report is even required.
  • EU MDR Article 2(68), Article 87(1)(b) and (3)–(5), and Article 89(1): confirm the FSCA definition, the in-advance filing requirement, and the 2/10/15-calendar-day incident clocks; read MDCG 2023-3 (rev. 2) for the awareness-date ("day 0") rule.
  • RDC 551/2021, Articles 1, 2 (sole paragraph) and 4: confirm the registration-holder responsibility, the joint-responsibility chain, and the essential-requirements trigger — then pull RDC 67/2009 for the notification timelines and alert rules that 551/2021 relies on.
  • MoPH Notification B.E. 2563 (2020) and the two Thai FDA guidance documents: confirm the responsible parties, the 10/30-day reporting structure, and which form each track (recall vs FSCA) requires.

Practical Implications for a Global Field Action

If the same defect surfaces in all four markets, the binding constraints stack: the EU demands a pre-action FSCA filing via EUDAMED with a reviewed FSN, the US wants a post-initiation 806 report within 10 working days, Brazil requires the BRH to notify ANVISA and distribute a consumer alert, and Thailand wants an awareness-date report to the HPVC on a 10- or 30-day clock. The single biggest planning error is treating these as one global "recall" with one deadline — the EU's prospective filing and the US's reactive 10-working-day report can pull in opposite directions, and Brazil's BRH dependency can block the whole Latin-American response if the registration holder is not pre-contracted. Build a single global field-action SOP that maps each jurisdiction's filing object and clock separately, and pre-clear the BRH relationship before any incident forces it.

Sources

Related Articles

Regulatory510(k)

FDA 510(k) Clearance Trends 1995-2026: Volume Stable as Traditional Submissions Take Share

Analysis of 175,149 FDA 510(k) clearances. Volume stabilized at roughly 3,200 per year after 2007, while Traditional submissions rose from 73% to 83% as Special and Abbreviated programs declined.

2026-06-16·10 min read
RegulatoryQuality Systems

FDA Medical Device Recall Concentration: Top 50 Firms Drive Over Half of All Recalls

Analysis of 58,374 FDA recall records: recall burden is concentrated. The top 50 firms drive 52% of recalls while 42% of firms recalled only once. Zimmer Biomet, Philips, Stryker, and Medtronic lead.

2026-06-16·11 min read
RegulatoryQuality Systems

FDA Orthopedic Implant Recalls: Zimmer Biomet Leads 3,167 Hip & Knee Recall Records

FDA recall analysis: 3,167 hip, knee, and shoulder joint-replacement recalls across 70 product codes. Zimmer Biomet holds 37%, the top-10 firms 87%, and 96% are Class II 510(k) devices, not PMA.

2026-06-16·10 min read