MedTech Terms
    The authoritative reference
    All terms
    Post-MarketPost-Market & SafetyGlobal Markets

    Field Action vs Recall

    Distinction between corrective field actions taken on devices in the field and FDA-defined recall events.

    Reviewed by Christian Espinosa, Founder, Blue Goat CyberLast reviewed September 19, 2026

    Definition

    Field action is a broad operational term for an action involving distributed devices; it is not a single FDA legal classification. Under 21 CFR 7.3(g), a recall is a firm's removal or correction of a marketed product FDA considers violative and against which it would initiate legal action. Market withdrawal and stock recovery are excluded from that definition. Recall classification and reporting under 21 CFR part 806 are separate questions. Part 806 covers specified manufacturer and importer corrections or removals to reduce a risk to health or remedy a violation that may present a risk to health. It includes exemptions and recordkeeping provisions; calling an action 'not a recall' does not settle the reporting analysis.
    What the regulation says
    21 CFR 7.3(g), (j) and (k) distinguish recalls, market withdrawals and stock recoveries. A software update or labeling correction can be a recall when the facts meet the definition; the action's name or technical form does not decide its status. Under 21 CFR 806.10, reportable corrections or removals must be reported within 10 working days of initiation. Section 806.1(b) excludes specified performance improvements without the relevant risk or violation, market withdrawals, routine servicing and stock recoveries. Section 806.10(f) addresses information already reported under specified provisions. Section 806.20 separately addresses records for nonreportable corrections or removals within its scope.

    What this means in practice

    Separate three decisions: what practical action is needed, whether the action meets FDA's recall definition, and whether a correction or removal must be reported under part 806. The company's internal label does not answer the other two questions. A customer notification, labeling change or software update can have different implications depending on the facts. An illustrative assessment records the affected devices and distribution, the observed problem, risk-to-health analysis, any violation and proposed remedy. Apply the recall definition and then the part 806 reporting criteria and exemptions separately. Preserve the rationale and assess applicable recordkeeping even if the correction or removal is not reportable. FDA assigns recall classifications based on health hazard, not merely the technical form of the remedy. Coordinate quality, regulatory, clinical and service teams so the evidence, communication and effectiveness checks describe the same action. For EU devices, separately assess field safety corrective action and vigilance requirements under the applicable framework; FDA recall terminology is not a one-to-one legal crosswalk. This workflow is illustrative and cannot determine the status of a particular action.

    Field action vs recall: one operational remedy, separate regulatory decisions

    Calling an action a patch, service visit or customer notice tells you what the team plans to do. It does not settle whether it is a recall, whether part 806 reporting applies or which records must be retained.

    Field action vs recall: one operational remedy, separate regulatory decisions comparison
    DecisionWhat it addressesWhat does not decide it
    Operational field actionThe remedy for distributed devicesThe company's preferred action name
    FDA recall statusThe definition in 21 CFR 7.3 and the actual factsWhether the remedy is software or hardware
    Part 806 reportabilityReporting criteria and applicable exemptionsAn internal conclusion that it is 'not a recall'
    RecordsApplicable nonreportable correction/removal record requirementsAbsence of a reporting obligation alone
    EU assessmentApplicable FSCA and vigilance requirementsA one-to-one translation of FDA terminology

    Worked review: a software patch is a remedy, not a classification

    Suppose a manufacturer discovers a software problem in distributed devices and proposes a remote update. The first question is what the problem does in use, which devices are affected and whether it creates a risk to health or remedies a relevant violation. 'Remote update' only describes the delivery mechanism. This scenario is hypothetical, not a reported recall.

    Document the problem and proposed correction, then evaluate the recall definition and part 806 reporting separately. A safety-related software correction is not exempt merely because no device is physically returned. Conversely, not every software improvement is a recall or reportable correction. The criteria, exemptions and facts determine the analysis.

    Why 'not reportable' is not the end of the file

    Part 806 distinguishes reporting from recordkeeping. Section 806.20 addresses records for nonreportable corrections and removals within its scope. A documented assessment should explain why the reporting criteria do or do not apply and identify the relevant exemption or other basis, instead of recording only 'not a recall.'

    For reportable actions under 806.10, the deadline is 10 working days after initiation. Do not replace that with calendar days or assume that waiting for a recall classification pauses the reporting analysis. Use the actual rule for the required information and applicable provisions.

    Keep customer communication aligned with the assessment

    An action file is easier to evaluate when its affected population, risk rationale, proposed remedy and customer communication describe the same issue. A harmless-sounding internal label should not conceal the clinical consequences evaluated by the team. Service, quality, clinical and regulatory participants should resolve inconsistent descriptions before communication is finalized.

    For devices also supplied in the EU, make a separate assessment under the applicable FSCA and vigilance framework. The linked FSCA page supplies that context; this FDA comparison does not establish an EU notification conclusion or make the two legal systems interchangeable.

    Evidence and editorial limits

    21 CFR 7.3: recall, market withdrawal and stock recovery

    Supports the distinctions in FDA recall terminology.

    21 CFR part 806: corrections and removals

    Supports separate reporting, exemptions, deadlines and recordkeeping analyses.

    Educational decision analysis, not classification of a particular field action, a recall plan or legal advice. Device-specific reporting and records questions require qualified review.

    Examples

    • Illustrative example: a regularly scheduled battery replacement at normal life expectancy may be routine servicing; unexpected premature replacements need a different analysis.
    • Illustrative example: a software correction addressing a safety-related violation may require both recall assessment and a part 806 reporting decision. A software format does not make it exempt.

    Use cases

    1 scenario
    1

    Assessing a distributed software correction

    Quality and regulatory teams

    A team identifies a software problem in distributed devices. It records the affected population and health risk, assesses the recall definition, then separately evaluates part 806 reporting and records before finalizing the remedy and communication.

    OutcomeSeparate, documented regulatory decisions rather than an exemption assumed from the word 'patch.'
    Common pitfalls
    • •Calling a software patch 'maintenance' without assessing the problem it remedies.
    • •Treating recall classification and part 806 reporting as one decision.
    • •Assuming a nonreportable action needs no records.
    • •Using a company's field-action label as a regulatory conclusion.
    • •Applying EU field safety corrective action terminology as if it were identical to FDA recall rules.

    Frequently asked questions

    No. Apply the recall definition in 21 CFR 7.3 to the actual correction or removal. A market withdrawal or stock recovery is excluded, but a software update can meet the recall definition.

    Related terms

    Grouped by theme
    Cited by

    Where this term appears across MedTech Terms.

    Latest in MedTech

    Sources

    4 sources

    Sources support the definition or relevant regulatory context, not necessarily every claim on this page. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.

    Official-source claim check:

    Recall classification and part 806 reporting are separate decisions; not every correction or removal is reportable.

    Partial review: verified corrections are applied, but this is not a full accuracy certification. The last full review date is unchanged.

    Remaining verification limits
    • Verified definitions and reporting exemptions, not a legal determination for any particular field action.
    Tier 1Binding law and standards· 2Tier 2Regulator guidance and consensus· 2
    Link health: 3 verified 1 unchecked· last checked 2026-06-20
    eCFR·1FDA·1European Commission·1US official source·1
    1. 1
      21 CFR 806
      Tier 1 Verified
      eCFRecfr.gov
    2. 2
      FDA Recalls - Medical Devices
      Tier 2 Verified
      FDAfda.gov
    3. 3
      EUDAMED Public Site
      Tier 2 Verified
      European Commissionec.europa.eu
    4. 4
      21 CFR 7.3, recall definitions
      Tier 1 Unchecked
      US official sourceecfr.gov

    Inline markers like [1] jump to the matching reference above.