How to Build a Core Technical File for Multi-Country Medical Device Registration?

How to Build a Core Technical File for Multi-Country Medical Device Registration?

The key to establishing a core technical file for multi-country medical device registration is to create a reusable 'master file' and then localize it according to the regulatory requirements of each target country. Companies should first determine whether the product falls under the medical device regulatory scope of the target country (e.g., China NMPA, EU MDR, US FDA, GHWP member states in Southeast Asia), then define the registration pathway and applicant based on risk classification. Essential documentation includes product description, design drawings, material composition, risk management report, performance validation, biocompatibility, stability, clinical evaluation or clinical evidence, labeling and instructions for use (language and symbols), and quality management system (ISO 13485 or MDSAP). A common risk is overlooking country-specific differences, leading to deficiency letters—for example, Brazil ANVISA requires Portuguese labeling, Saudi FDA requires halal certification, and some Southeast Asian countries accept CB reports but mandate a local agent. Companies should prioritize building a core file comprising basic technical documentation, risk management files, and a clinical evidence repository, then add country-specific documents as required (e.g., Canada MDL requires QMS certificate, Japan PMDA requires QMS questionnaire). Local agents or authorized representatives handle change management, renewal, and adverse event reporting; control over certificates must not be relinquished. Post-market maintenance includes periodic updates, change notifications, and CE re-certification. For multi-country registration, adopt a 'compile once, adapt to many' strategy to reduce repetitive work and deficiency risks. This article is compiled from the 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's regulatory authority and product documentation.

Applicable Scenarios and Core Issues

This guide is intended for companies planning to register medical devices in multiple countries (especially GHWP member states, Southeast Asia, the Middle East, Latin America, etc.). The core issue is: how to establish a core technical file that can be reused across markets while meeting diverse regulatory requirements? Companies often face pain points such as repeated document preparation, frequent deficiency letters, and difficulty managing local agents. A well-constructed core technical file should support submissions to major markets: China NMPA, EU CE, US FDA, Japan PMDA, Korea MFDS, Brazil ANVISA, Saudi SFDA, Australia TGA, etc. The core technical file serves not only as the basis for registration applications but also for quality system audits, post-market change management, and renewal. Therefore, the file structure must be clear, the evidence chain complete, and version controlled. Companies need to design the file architecture based on product characteristics (active, passive, IVD, software, implantable, etc.) and target market combination.

Registration Assessment Logic

Step 1: Determine whether the product falls under the medical device regulatory scope of the target country. Definitions of medical devices vary by country. For example, the US FDA may classify some products as general health products, while the EU MDR includes active implantable devices. Refer to local regulations and classification rules.

Step 2: Determine the risk class and corresponding registration pathway. High-risk devices (e.g., Class III) may require PMA or pre-market approval; low- to medium-risk devices (e.g., Class I and II) may follow self-declaration or notification pathways. For instance, China NMPA: Class II requires provincial registration, Class III requires national registration; EU MDR requires notified body review; US FDA Class II requires 510(k).

Step 3: Assess the reusability of existing documentation. If you already have NMPA registration files, CE technical files, or FDA 510(k) submissions, these can serve as the basis for the core file. However, verify that they cover all necessary elements: performance validation, biocompatibility (ISO 10993), electrical safety (IEC 60601), software validation (IEC 62304), clinical evaluation (MEDDEV 2.7/1 Rev.4 or MDR Annex XIV), etc.

Step 4: Identify specific requirements of the target countries. For example, Brazil ANVISA requires INMETRO registration; Saudi SFDA requires halal certificates; Japan PMDA requires a QMS questionnaire; Canada requires an MDEL or MDL; Thailand TFDA requires a Thai local representative. These special requirements must be evaluated early and planned for in the documentation.

Step 5: Determine the local agent or authorized representative. Almost all non-domestic manufacturers need a local agent responsible for registration applications, post-market surveillance, and adverse event reporting. The authorization agreement must clearly define responsibilities, scope, validity period, and termination clauses. Control over certificates (e.g., CE certificate, FDA listing) should remain with the company to avoid dependency on the agent.

Step 6: Establish a post-market maintenance plan. This includes periodic updates to technical files (e.g., new standards, updated clinical data), change notifications (design, process, materials, manufacturing site changes), and renewal timelines. Multi-country maintenance requires coordination of each country's cycle to avoid lapses in certificate validity.

Documentation and Evidence

The core technical file should include the following basic modules:

• Product Overview: Name, model, intended use, working principle, diagrams, specifications.
• Design Description: Design inputs and outputs, design change history, list of critical components.
• Manufacturing Process: Flowchart, critical process parameters, sterilization method, packaging description.
• Material Composition: List of all materials, biocompatibility assessment (ISO 10993 series), chemical characterization.
• Risk Management: Risk analysis report per ISO 14971 (including FMEA or FTA), risk acceptance criteria.
• Performance Validation: Functional tests, accuracy, stability (e.g., aging, shipping), software validation (IEC 62304).
• Clinical Evaluation or Clinical Evidence: Demonstrate safety and efficacy through equivalence论证, literature review, or clinical trials (if needed). High-risk products may require more robust clinical data.
• Labels and Instructions for Use: Cover language requirements of each target market, noting differences in symbols, warnings, and contraindications.
• Quality System Certificate: ISO 13485 or MDSAP certificate (some countries accept specific system audits).
• Post-Market Surveillance: PMS plan, PMCF report, adverse event reporting procedures.

For multi-country registration, create a 'core file index' listing all modules and their applicability in each country. Each module can include a generic version and country-specific versions (e.g., language, cultural differences). For example, the clinical evaluation report can be written in English first, then translated into the target language. Risk analysis should consider country-specific risks (e.g., high temperature and humidity in tropical regions).

Common Mistakes

• Ignoring product classification differences and directly applying another country's class. For example, FDA Class II may be classified as Class III in the EU, leading to insufficient clinical evaluation.
• Relying on a single market file without localization, e.g., submitting NMPA registration documents directly to Brazil ANVISA without Portuguese labels and INMETRO certificates.
• Risk management file not covering all target country requirements. For instance, EU MDR requires consideration of environmental risks, while US FDA does not.
• Insufficient clinical evaluation, especially regarding specific populations (e.g., Asian ethnicity) without demonstrating equivalence.
• Neglecting the importance of a local agent or authorized representative, resulting in inability to respond to regulatory inquiries or adverse event reports in a timely manner.
• Loss of control over certificates, e.g., the agent holding the CE certificate or FDA listing, making changes dependent on them.
• Chaotic post-market change management, failing to notify each regulatory body in a timely manner, leading to suspension or revocation of registration certificates.
• Not coordinating multi-country registration timelines, causing significant differences in market launch dates and affecting market strategy.

Company Preparation Checklist

• List target countries and review their regulations and classification rules.
• Assess product risk class to determine the registration pathway (self-declaration, notification, approval).
• Collect and organize existing technical files (NMPA/CE/FDA, etc.) and identify missing modules.
• Establish a core file master version including risk management, performance validation, clinical evaluation, labels, etc.
• For each target country, create a localization checklist: language, special tests (e.g., additional biocompatibility), system certificate, agent agreement.
• Select and contract local agents or authorized representatives, clearly defining responsibilities and certificate control.
• Develop a post-market maintenance plan including change notifications, adverse event reporting, and renewal timelines.
• Engage an experienced regulatory consultant or advisory firm to assist with document preparation and communication with regulatory bodies.
• Use a professional document management system (e.g., electronic QMS) for version control to ensure traceability.
• Conduct a pre-audit or mock review to identify document deficiencies early.

AIMEILI's Perspective

The most common misjudgment companies make is assuming that 'one CE technical file can cover all countries.' In reality, countries vary greatly in clinical evaluation, risk classification, label language, and system requirements. In the early stages of a project, companies should prioritize regulatory research and gap analysis for the target countries rather than blindly translating documents. Core documents such as the risk management report, biocompatibility report, clinical evaluation report, product basic description, and performance test reports can be reused, but must be checked for compliance with local standards (e.g., ISO version, test methods). The selection of a local agent is critical; examine their past registration experience, ability to interact with regulatory bodies, and ensure the contract specifies certificate control, change notification responsibilities, and renewal service scope. The most effective strategy for multi-country registration is to build a core file, then customize supplementary documents per market, while using parallel submissions and centralized management to reduce deficiency risks. AIMEILI recommends that companies form a cross-functional team (regulatory, R&D, quality, marketing) at project initiation and engage a global regulatory consulting team.

Frequently Asked Questions

Q1: We already have a CE technical file; can we use it directly for registration in Southeast Asia?

A: Not entirely. Although some Southeast Asian countries (e.g., Thailand, Indonesia, Malaysia, Philippines, Vietnam) partially adopt the ASEAN Medical Device Directive (AMDD), they have additional requirements regarding language, local clinical data, and system certificates (e.g., ISO 13485 certificate must be issued by an accredited body). For example, Thailand TFDA requires labels in Thai; Malaysia MDA requires local clinical trials or documentation of relevance for foreign clinical data. Therefore, the CE technical file can serve as the core basis, but must be adjusted for each country: add local language labels, consider local epidemiology in risk management, provide local agent authorization letters, etc.

Q2: How can we ensure that renewal timelines do not conflict across multiple countries?

A: Establish a unified registration management schedule recording each country's registration information (certificate number, validity, renewal cycle, submission window). Use a project management system with alerts set 6–12 months in advance for renewal preparation. For countries requiring on-site audits (e.g., China NMPA, US FDA), schedule audits early with the auditing body. Design core file performance validation reports and clinical evaluation reports as updatable versions (e.g., including a periodic literature search plan) so that they can be directly updated for renewal.

Q3: If a product design change occurs, must we notify all registration countries?

A: Yes, you must determine whether the change is significant or minor according to each country's regulations. Significant changes (e.g., design principle, main raw materials, working principle, intended use) generally require prior approval; minor changes may only require notification or registration. The classification and procedures vary by country. For example, the US FDA requires a new 510(k) or supplement for changes; EU MDR requires assessment by the notified body; China NMPA requires change registration. Therefore, companies must establish a change evaluation process and notify each country in a timely manner to avoid certificate invalidation due to lack of notification.

Continue Reading

Previous: What Are the Requirements for a Risk Management File for Overseas Medical Device Registration?

Next: How to Organize a Model/Specification Matrix for Overseas Medical Device Registration?

Recommended Reading:

• How to Reuse Medical Device Registration Documents Across GHWP Member States?
• How to Select a Local Agent for Overseas Medical Device Registration?
• How to Prepare Labels and Instructions for Use for Overseas Medical Device Registration?
• How to Use ISO 13485 Certificates for Overseas Medical Device Registration?
• How to Prepare Clinical Evaluation Documents for Overseas Medical Device Registration?
• What Are the Requirements for a Risk Management File for Overseas Medical Device Registration?

Back to FAQ Center | News | Contact AIMEILI

Content Review and Applicability Disclaimer

Author: AIMEILI Regulatory Editorial Board
Professional Review: AIMEILI Medical Device International Registration Project Team
Source Principle: Priority is given to official regulatory bodies, international organizations, standards bodies, and publicly available regulatory information; industry media and project experience are used only as supplementary references.
Applicability: This article is intended for preliminary understanding, document preparation, and project planning. It does not replace the formal requirements, test conclusions, or legal opinions of the target country's regulatory authority.