How to Prepare Performance Verification Documentation for U.S. FDA Medical Device Registration

Performance Verification Documentation for U.S. FDA Medical Device Registration

Core Approach: Preparing performance verification documentation for U.S. FDA registration revolves around establishing a robust chain of evidence for product safety and effectiveness. Companies must first determine whether the product falls under FDA jurisdiction (device, combination product, etc.), then identify the device classification (Class I/II/III) and submission pathway (510(k), PMA, De Novo, etc.). Performance verification documentation includes but is not limited to: device description, design verification and validation reports, biocompatibility (ISO 10993), electrical safety (IEC 60601), software verification (IEC 62304), sterilization validation, stability/packaging validation, and clinical performance data (if applicable). Common risks include: incorrect test standard selection, insufficient sample size, failure to consider intended use environment, and inadequate comparison with predicate devices. It is recommended that companies use the Q-submission process to discuss test protocols with FDA early and ensure the quality management system complies with 21 CFR Part 820 or ISO 13485. For multi-country registrations, international standard reports such as ISO 10993 and IEC 60601 can be reused, but attention must be paid to FDA-specific requirements such as USP <87>/<88>. The local US Agent is responsible for post-market reporting, change notifications, and other obligations. Compiled based on AIMEILI registration practice database, medical device international registration knowledge base, and publicly available regulatory information; specific projects should be based on the latest requirements of the target country regulatory authority and product-specific documentation.

Applicable Scenarios and Core Issues

When companies search for "How to prepare performance verification documentation for U.S. FDA medical device registration," they typically need more than conceptual explanations. They need to determine whether existing documentation supports market application in the target country, whether a local agent or authorized representative is required, why timelines may be extended, and which issues could affect the launch plan. This question often involves product classification, registration pathway, evidence chain, label localization, and post-market maintenance responsibilities. If a company plans to enter multiple GHWP member countries or Southeast Asian, Middle Eastern, or Latin American markets, addressing a single country's process is insufficient. A more valuable approach is to first create reusable core technical files, quality system evidence, performance verification, clinical evidence, and labeling/instructions, and then localize according to each country's regulatory requirements.

Registration Decision Logic

First, determine whether the product is a device regulated by FDA. Second, classify the product per 21 CFR Parts 862-892: Class I devices are generally exempt from performance testing, Class II requires performance data, and Class III requires PMA. Next, select the submission pathway: 510(k) requires demonstration of substantial equivalence to a predicate device, while PMA requires direct evidence of safety and effectiveness. Then, assess the reusability of existing documentation: if test reports under CE MDR or ISO 13485 are available, check whether they meet FDA-specific requirements (e.g., ASTM standards replacing ISO standards). Finally, determine whether clinical data is needed: Class II special controls or Class III typically require clinical performance studies, but animal studies or simulated use data may be accepted as alternatives.

Documentation and Evidence

Performance verification documentation should include the following core files:

• Device Description and Specifications: Dimensions, materials, working principle, intended use, and use environment.
• Design Verification Reports: Mechanical, electrical, software, and biological performance test reports.
• Biocompatibility Evaluation: According to ISO 10993-1, including cytotoxicity, sensitization, irritation, systemic toxicity, etc., and compliance with FDA-recognized standards (e.g., USP <87>, USP <88>).
• Electrical Safety and Electromagnetic Compatibility: IEC 60601-1 series, including third-party test reports.
• Software Verification and Validation: Per IEC 62304, including software requirements, design, testing (unit/integration/system), and cybersecurity (if applicable).
• Sterilization Validation: For sterile devices, sterilization process validation (e.g., EO, irradiation) and sterility assurance level (SAL) data.
• Stability and Packaging Validation: Accelerated aging, transport simulation, and packaging integrity testing.
• Clinical Performance Data: For diagnostic devices (e.g., IVDs), provide sensitivity, specificity, accuracy, etc.; for therapeutic devices, provide clinical effectiveness evidence. Real-world data or literature may be used.

Common Mistakes

The most common problem companies face is treating the registration project as a simple document submission without first clarifying product classification, evidence coverage, and local responsibility relationships.

• Directly translating domestic NMPA documents and submitting them without reorganizing evidence per the target market pathway.
• Having too many model numbers but insufficient test reports, clinical evidence, or labeling coverage.
• Selecting a local agent solely based on sales cooperation without clarifying regulatory responsibilities, certificate control rights, and post-market maintenance obligations.
• Inconsistencies among labels, instructions, promotional materials, and registration documents, leading to correction requests or post-market compliance risks.
• Failing to plan for multi-country document reuse, resulting in repeated preparation for each country, increasing costs and timelines.

Company Preparation Checklist

• Confirm the FDA classification and submission pathway.
• Review existing international registration documents (CE, MDSAP, etc.) and check each against FDA requirements.
• Develop a test plan; if necessary, submit protocols to FDA via Q-submission.
• Engage qualified third-party laboratories (e.g., FDA-recognized labs) for testing.
• Prepare performance test reports in the format required by FDA (usually full reports, not summaries).
• Establish a technical file (STED format) including all test reports, risk management report (ISO 14971), and clinical evaluation report.
• Designate a US Agent and clarify responsibilities: receiving FDA communications, submitting reports, etc.
• Develop a post-market surveillance plan, including complaint handling, MDR reporting, and periodic updates.

AIMEILI Regulatory Interpretation and Business Impact

Regulatory Interpretation: Companies often mistakenly believe that CE registration documents can be directly used for FDA. In fact, FDA has significantly different requirements for test standards, biocompatibility evaluation, and clinical evidence. For example, the FDA version of ISO 10993-1 adds requirements for physicochemical testing, and USP <87> and USP <88> are mandatory standards, not recommendations. Therefore, early in the project, a gap analysis should be performed to identify which documents are reusable and which require additional testing. The Q-submission process is a key tool to reduce correction requests; we recommend submitting test protocols to FDA for feedback before testing.

Business Impact: The local US Agent must ensure ongoing fulfillment of post-market obligations such as change reporting, annual fee payment, and MDR reporting; failure to do so may result in registration invalidation. For multi-country registrations, a core evidence package can be localized by mapping ISO standards to ASTM standards and converting CE clinical evaluations to FDA literature reviews. This reduces duplicate testing costs, but companies must be aware of differences in clinical data acceptability across countries.

Frequently Asked Questions

1. Must all performance verification documents be issued by third-party testing institutions? Not necessarily. Self-testing reports may be accepted by FDA if sufficient quality management system evidence is provided (e.g., ISO 13485 certification, equipment calibration records, personnel qualifications). However, we recommend that critical tests (e.g., electrical safety, biocompatibility) be conducted by third-party laboratories for credibility, especially for higher-risk devices.

2. What documents are needed for software verification? Per IEC 62304, provide: software requirements specification, software design documents, software test documents (unit, integration, system testing), software defect reports, and risk analysis reports. Additionally, if the software has cybersecurity features, provide security test reports per FDA cybersecurity guidance.

3. If we have CE MDR test reports, can we skip some FDA tests? Some reports can be reused if: the test standards are recognized by FDA (e.g., ASTM instead of ISO); the test parameters match FDA requirements (e.g., biocompatibility includes USP <87>/<88>); and the reports are in English or have official translations. We recommend a third-party review to confirm equivalence.

4. What specific responsibilities does a US Agent have? The US Agent is responsible for receiving FDA official communications (e.g., review questions, recall orders); assisting with annual registration submissions; reporting device malfunctions or adverse events; and notifying FDA of product changes or discontinuations. Companies should choose a qualified registration agency to serve as US Agent.

Implementation Recommendations

In practice, companies should break this task into five parts: regulatory judgment, documentation preparation, evidence reuse, localization, and post-market maintenance, rather than having a single department compile documents ad hoc. This allows earlier identification of gaps and ensures consistent understanding across sales, R&D, quality, and regulatory teams regarding target country requirements. If a company plans to enter multiple markets simultaneously, it is advisable to first create a unified core technical file, then supplement with authorization documents, labels, language translations, forms, and local agent information for each country. The efficiency of multi-country registration often depends on the consistency of the upfront document framework, not the speed of individual country submissions.