Key Summary

After obtaining FDA registration, manufacturers must report changes that could significantly affect product safety or effectiveness. This FAQ outlines when a change submission is required, based on 21 CFR 807.81 and FDA guidance, covering 510(k) and PMA products, common errors, and preparation checklists.

After a medical device obtains U.S. FDA registration, any change that may significantly affect the device's safety or effectiveness must be reported to the FDA in a timely manner. The triggering conditions for change reporting are primarily based on 21 CFR 807.81 and related FDA guidance. Companies need to determine whether a change is a "significant modification," such as: new intended use, design or material changes, major manufacturing process changes, key label modifications, sterilization method changes, or software updates that affect functionality. For 510(k) devices, such changes may require a new 510(k) submission; for PMA devices, a PMA supplement (e.g., Normal Supplement, Real-Time Supplement, or CBE/CP) may be needed. Companies should establish a change control system to evaluate the impact of changes on their registration. Common risks include product being considered unapproved and halted from sale, or being cited as a serious non-compliance during post-market inspections. It is recommended that companies refer to FDA's guidance "Deciding When to Submit a 510(k) for a Change to an Existing Device" and integrate quality system change evaluation processes, consulting a regulatory affairs specialist when necessary. Preparing validation data, risk analysis, and clinical evaluation evidence in advance can prevent post-market disruptions.

Core Content

Applicable Scenarios and Core Questions

Companies searching for this question typically need more than a conceptual explanation—they need to determine if existing documentation supports the target market submission, whether a local agent or authorized representative is required, why timelines may be extended, and which issues could affect launch plans. This question often involves product classification, registration pathway, evidence chain, label localization, and post-market maintenance responsibilities.

Registration Evaluation Logic

The evaluation follows three steps: First, confirm the product still falls under FDA jurisdiction. Second, determine the risk level based on the change's potential impact on safety and effectiveness. Third, identify the appropriate registration pathway. For 510(k) devices, if the change could significantly affect safety or effectiveness, or alter intended use, a new 510(k) is typically required. For PMA devices, significant changes require a PMA supplement (e.g., PMA Supplement or PMA CBE/CP). Companies should refer to FDA's guidance documents: "Deciding When to Submit a 510(k) for a Change to an Existing Device" and "Modifications to Devices Subject to Premarket Approval (PMA)." Also consider whether special controls or performance standard changes are involved.

Documentation and Evidence

Common documentation includes: product description, model/specification matrix, intended use, risk classification basis, ISO 13485 or applicable quality system certificate, technical files, performance validation reports, risk management files, clinical evaluation or clinical evidence, labels and instructions, authorization documents, existing registration certificates, manufacturer declarations, and post-market surveillance records. Key is consistency across documents: claims in labeling must align with test reports, clinical evidence scope, risk management conclusions, warnings, and registration application information. Regulators focus on whether the product is safe, effective, and traceable for its intended use, not on the volume of documents submitted.

Common Mistakes

  • Misjudging a significant modification as a minor change, leading to unsubmitted reports and regulatory non-compliance.
  • Evaluating changes only from a technical perspective while neglecting regulatory submission requirements.
  • Failing to collect sufficient validation data, resulting in FDA deficiency letters and approval delays.
  • Using change reports from other markets (e.g., CE) without local adaptation for FDA requirements.
  • Overlooking label changes (e.g., warnings, contraindications) and failing to update and report them.
  • Underestimating software changes, not distinguishing between "function-affecting" and "insignificant" updates.
  • Implementing changes before realizing the need for submission, leading to post-market recall risks.
  • Not maintaining change history records, making it impossible to provide evidence during FDA inspections.

Company Preparation Checklist

  • Establish a product change control SOP that includes a regulatory evaluation checkpoint.
  • Train R&D, quality, and regulatory personnel on FDA change guidance.
  • Use a "Change Regulatory Impact Assessment Form" to determine submission necessity at the start of each change.
  • Prepare technical documents (performance, clinical, risk, etc.) required for the change in advance.
  • Associate changes with FDA application files (e.g., 510(k) number, PMA number) and maintain change history.
  • Retain communication records with local agents or authorized representatives (if applicable).
  • Periodically audit the compliance of the change control system, via internal or third-party audits.

AIMEILI Regulatory Interpretation and Business Impact

The most common misjudgment in FDA registration changes is the boundary between "minor" and "significant" modifications, especially for compound changes or cumulative effects. AIMEILI recommends establishing a complete change control process early and conducting internal classification tests using FDA guidance. Technical files from CE or NMPA may be reusable but must be localized for FDA requirements (e.g., specific clinical data, U.S. clinical practice, standard differences). The local agent (U.S. agent) is not merely a mail recipient but should assist with regulatory change submissions.

For multi-country registrations, a unified change management platform is advisable to avoid redundant testing, but note that deficiency requests vary by country. Regarding certificate control, ensure that FDA registration, listing, and certificate information are synchronized after changes to avoid denial during renewal due to unreported changes. Proactive planning can reduce deficiency risks by over 30%.

Source and Language Notice

View Chinese original page

Related Reading

Need a registration pathway assessment?

Send product type, intended use, target countries and existing certificates. AIMEILI can help evaluate registration pathway, documentation gaps and compliance risks.

Contact AIMEILI