How to Prepare Performance Verification Documentation for Overseas Registration of Active Medical Devices?

Key Summary

To prepare performance verification documentation for overseas registration of active medical devices, manufacturers must first clarify the regulatory framework and product classification of the target country. Companies should assess the product risk class and applicable pathway based on registration requirements in GHWP member countries and markets in Southeast Asia, the Middle East, and Latin America. Performance verification documentation is not a standalone document but a comprehensive reflection of technical and quality systems. It typically includes risk management reports, safety and EMC test reports, environmental testing, software verification, usability evaluation, and clinical evaluation or literature evidence.

At an early stage, manufacturers should prioritize reviewing existing documentation from NMPA, CE, FDA, ISO 13485, MDSAP, and other systems to evaluate the potential for reuse and localization conversion. Key risks include differences in test standards, sample sizes, and test conditions that do not meet local requirements, as well as delays in communication with regulators due to the lack of a local authorized representative. Companies should establish a complete technical file index, confirm the validity of quality system certificates, prepare localized labels and instructions for use, and maintain post-market responsibilities such as updates, change notifications, and renewal obligations.

It is recommended that a gap analysis be completed with a regulatory consulting firm before project initiation to avoid duplicate testing and correction delays.

Applicable Scenarios and Core Questions

For active medical devices, performance verification documentation is a core component of the technical file during overseas registration and directly influences regulators' assessment of product safety and effectiveness. Applicable scenarios include markets under GHWP member countries and regions in Southeast Asia, the Middle East, and Latin America, each with different review logic.

The core question is not simply collecting reports according to a checklist, but how to use one evidence system to satisfy multiple market requirements. Manufacturers should first determine whether the product falls within the medical device regulatory scope of the target country, and then confirm classification, registration pathway, and applicant entity.

Many companies interpret performance verification as only conducting safety and EMC testing. In practice, additional active-device-specific requirements such as environmental testing, software validation, usability assessment, cybersecurity, and software lifecycle must also be considered.

Registration Judgment Logic

The first step is to determine the product boundary. Some active devices may be classified as IVDs, medical device accessories, or combination products, each with a different registration pathway.

The second step is to determine the risk classification in the target country. GHWP member countries generally adopt risk-based classification, but classification rules may differ and must be verified country by country.

The third step is to assess the reusability of existing documentation. NMPA registration files, CE technical documentation, FDA 510(k) or PMA files, and ISO 13485 and MDSAP certificates can all serve as a foundation, but the applicable test standard versions and local differences must be confirmed.

The fourth step is to confirm the complete scope of performance verification projects. In addition to safety and essential performance, additional items such as temperature, humidity, vibration, power fluctuations, software versions, and alarm thresholds should be considered.

The final step is to form a registration strategy: determine which countries accept the same test report, and which countries require local testing or additional data.

Documentation and Evidence

Performance verification documentation generally includes the following categories:

• Risk management reports and documentation — compliant with ISO 14971 and covering intended use and foreseeable misuse.
• Safety test reports — such as the IEC 60601-1 series, with confirmation of the standard version and differences accepted by the target country.
• EMC test reports — including complete records for radiated emissions, conducted emissions, electrostatic discharge, radiated immunity, electrical fast transients, and surge.
• Environmental test reports — covering temperature, humidity, vibration, shock, transport, and storage conditions.
• Software verification and validation documentation — including software requirements specification, test records, defect tracking, and version release information.
• Usability engineering documentation — formative and summative evaluations completed according to IEC 62366.
• Cybersecurity verification materials — for products with network connectivity, covering security updates, abnormal input response, and vulnerability assessment.
• Clinical evaluation or clinical evidence — including literature searches, clinical data assessment, or clinical trial summaries required by the target country.

Each piece of evidence must maintain traceability. The product model, software version, accessory list, and label information in reports must be consistent with descriptions in the technical file.

Common Mistakes

• Directly using test reports prepared for other markets without verifying the accepted versions, standards, and test conditions in the target country, leading to requests for additional information.
• Ignoring rules requiring re-verification after product changes. When hardware, software, or critical components change, performance verification documentation is not updated accordingly.
• Confusing risk management with performance verification. The risk management report is not an appendix to a test report; it should drive the selection of test items and justification for exemptions.
• Unclear responsibilities of the local authorized representative. Without a qualified local agent, regulators cannot complete communication, and the correction and approval process is significantly delayed.
• Translating labels and instructions for use rather than localizing them according to target country language, units of measurement, warning symbols, and safety requirements.
• Failing to establish a performance verification document list and version control mechanism, leading to repeated recompilation and omissions during multi-country registration.

Company Preparation Checklist

• Establish a target country registration directory, clarifying product classification, registration pathway, applicant identity, and fees for each country.
• Set up a joint working group involving internal regulatory affairs, R&D, quality, clinical, and testing teams, and designate a project leader.
• Collect existing registration files, including NMPA registration certificates, CE certificates, FDA approval letters, ISO 13485 certificates, MDSAP certificates, and all test reports.
• Conduct a gap analysis to confirm differences in test standards, technical specifications, and document formats item by item.
• Confirm the capability scope of testing laboratories and arrange long-term testing projects early to avoid queues and report delivery delays.
• Prepare risk management reports, clinical evaluation plans, and evidence of effectiveness that may be required by agencies such as ANVISA or MHRA.
• Sign agreements with local authorized representatives or agents in target countries, clarifying responsibilities for change notifications, adverse event reporting, and renewal obligations.
• Develop a post-market performance tracking plan, including periodic reviews, customer complaint evaluation, and update testing.

AIMEILI Regulatory Interpretation and Business Impact

The most common misjudgment made by manufacturers is assuming that piecing together reports will pass regulatory review. In reality, regulators focus on the completeness, consistency, and risk analysis logic of the evidence chain.

At the beginning of a project, a gap analysis should be completed rather than starting testing immediately. A test matrix can clearly show which data can be reused and which must be supplemented. This assessment can significantly save budget and time.

Reusable documentation typically includes basic standard test reports, a general risk management framework, and quality system certificates. Localization is required for labels and instructions for use, clinical evaluation approaches, warning symbols, and additional documents required by local regulations.

A local authorized representative is not merely a mailing address but an extension of the registration affairs team. Control of certificates, change applications, renewal reminders, and recall communications all require the agent to have clear compliance capabilities and accountability.

For multi-country registration, it is recommended to establish a model of “core technical files plus country-specific difference files.” Prepare only the difference portion for each country to avoid recompiling a complete set of performance verification documentation. This approach reduces the risk of deficiencies and accelerates submission in subsequent countries.

Common Questions and Answers

Do all active devices require the same level of performance verification?

No. Devices with lower risk or simple structure may be exempt from certain EMC or environmental test items, but a risk-based justification must be provided. Companies should refer to target country guidelines or consult local agents rather than automatically applying the highest standard.

Can NMPA test reports be directly used for overseas registration?

Direct use is not possible, but they can serve as a reference. The target country may require the testing laboratory to be qualified or require supplementary testing based on local differences. In particular, EMC test conditions, power frequency magnetic fields, and electrostatic discharge levels may differ.

How can performance verification documentation avoid repeated deficiencies in multi-country registration?

The key method is to verify the “common review questions” of each country in advance. Regulators typically review along the path of risk analysis, standard compliance, software lifecycle, and clinical evidence. It is recommended that companies create an “evidence mapping table” that links each risk control measure to the corresponding test report.

Quality System and Evidence Consistency

From a registration review perspective, quality system documentation is not simply an isolated certificate. Regulators often check whether the manufacturer name, production address, product scope, certificate validity, applicable standards, and technical documentation are consistent. If the scope of an ISO 13485 certificate does not match the declared product, or if the production address, model specifications, or instruction manual version differ from test reports, additional explanations may be requested even when extensive documentation has been prepared.

Before submission, companies should create an evidence consistency checklist that maps product name, model specifications, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label and instruction manual versions, and quality system certificates. This may seem basic, but it can significantly reduce the likelihood of deficiencies, especially for registrations across multiple GHWP member countries or multiple product lines.

Localization Conversion and Authorized Representative Responsibilities

Overseas registration projects typically involve local agents, authorized representatives, importers, or registration holders. Companies must confirm whether the local partner is responsible only for submitting documents or also for regulatory communication, certificate maintenance, post-market event reporting, change applications, and renewal reminders. Different responsibility boundaries directly affect certificate control and long-term market stability.

Labels, instructions for use, and authorization documents cannot be simply translated. Companies should verify local language requirements, product claim boundaries, warning statements, storage and transport conditions, UDI or traceability requirements, importer information, authorized representative details, and after-sales contact information. For companies that already have CE, FDA, NMPA, or other market documentation, the focus of localization conversion is to transform reusable evidence into an accepted submission structure for the target country, rather than writing a completely new set of isolated documents.

Post-Market Maintenance and Long-Term Planning

Registration completion does not mean the end of compliance work. Companies still need to maintain certificate validity, change records, distributor authorizations, complaint handling, adverse event reporting, recall procedures, label versions, and regulatory update records. Many companies invest substantial effort during the certificate acquisition phase but neglect post-market obligations. When production address changes, model expansions, instruction manual updates, or agent replacements occur, the certificate may become disconnected from market operations.

AIMEILI recommends incorporating this issue into an annual international registration plan: first define target market priorities, then establish a reusable documentation package and country-specific gap list, and finally schedule submissions, corrections, post-market maintenance, and renewal milestones. The value goes beyond improving registration efficiency in a single country; it enables companies to build a replicable compliance capability for overseas expansion and reduce the cost of starting from scratch each time they enter a new market.

This article is compiled based on the AIMEILI registration practice database, the medical device international registration knowledge base, and publicly available regulatory information. Specific projects should be based on the latest requirements of the target country’s regulatory authorities and the product documentation basis.