How to Prepare Technical Documentation for Overseas Registration of IVD Products

The key to organizing technical documentation for overseas registration of IVD products is to first determine whether the product falls under the target country's medical device regulatory scope, then identify the risk classification and registration pathway, evaluate the reusability of existing NMPA, CE, FDA, ISO 13485, or MDSAP documentation, and finally fill any gaps with locally required documents. Critical documents include product description, intended use, performance evaluation reports, risk management documentation (ISO 14971), clinical or performance studies, labels and instructions for use (in the local language), quality management system certificates, and local agent or authorized representative agreements.

Core Organizational Logic

Before compiling the technical file, manufacturers must follow a logical decision path:

• Confirm regulatory scope and risk class: Determine whether the product qualifies as an in vitro diagnostic (IVD) medical device in the target country and assign the proper risk class (e.g., A–D or I–III). Classification errors can invalidate all subsequent documents.
• Identify the registration pathway: Decide whether the route is self-declaration (e.g., low-risk CE IVDR Class A), notified body review, or competent authority approval. The pathway determines the depth and scope of documentation.
• Assess existing documentation: Evaluate whether NMPA registration, CE IVDD/IVDR certificates, FDA 510(k)/PMA, ISO 13485, or MDSAP audit reports can serve as core evidence. These documents must be translated and reformatted to match target-country requirements.
• Confirm local representation: Most countries require a local entity or authorized representative. Prepare a power of attorney and agency agreement.
• Define clinical evidence needs: High-risk IVDs may require clinical trials or performance studies; low-risk products may only need performance evaluation reports and literature data.
• Plan post-market maintenance: Registration is not the end. Prepare for change notifications, annual reports, and adverse event reporting.

Key Documents and Evidence

A comprehensive technical file typically includes the following core modules:

• Product description and intended use (including test principle, analyte, and applicable sample types)
• Design and manufacturing information
• Performance evaluation reports: analytical performance (sensitivity, specificity, precision) and clinical performance (positive/negative agreement)
• Stability studies: shelf-life, transport, and in-use stability
• Risk management documentation per ISO 14971
• Software verification and validation documentation (if applicable)
• Labels and instructions for use in the target country's language
• Quality management system certificates (e.g., ISO 13485 or MDSAP)
• Clinical evidence: trial reports, literature reviews, or clinical performance studies
• Electrical safety and electromagnetic compatibility reports (for instrument-type IVDs)

For multiple target countries, manufacturers should structure the documentation following the IMDRF STED framework and then localise for each country: translate IFUs, add local agent information, and adjust performance statement wording. Evidence completeness is critical—under EU IVDR, for example, every performance claim must be supported with specific data; stating only “conforms to requirements” is not acceptable.

Common Risks and Mistakes

• Incorrect product classification, which leads to the wrong registration pathway and misdirected documentation.
• Directly copying domestic or CE files without localisation, such as failing to translate labels and IFUs or not reformatting risk management reports to the target country.
• Insufficient or unacceptable clinical evidence, such as using non-target populations, incomplete literature searches, or lacking sample size calculations.
• Ignoring software validation requirements, especially for IVDs with software or AI algorithms.
• Failing to designate a local agent or authorized representative, causing application rejection.
• Incomplete stability data, such as providing only accelerated stability without real-time or transport simulation data.
• Non-compliant labels and IFUs, including missing warning statements, storage conditions, or symbols not aligned with ISO 15223.

Recommended Preparation Checklist

• Determine target countries and product risk classifications.
• Collect all existing product documentation: R&D reports, test reports, QMS certificates, and existing CE/FDA/NMPA certificates.
• Create a document requirements list based on each target country's regulations or STED template.
• Compile product description and intended use documents with clear clinical purpose and target population.
• Organize performance evaluation reports ensuring complete data and compliance with local sample size and statistical requirements.
• Complete risk management documentation, including risk analysis, evaluation, control measures, and residual risk acceptability.
• Prepare software verification reports (if applicable), including requirements specifications, testing, and cybersecurity.
• Draft labels and IFUs and use professional localisation services for translation.
• Engage local agents or authorized representatives and sign agreements with authorization letters.
• Verify the validity and scope of QMS certificates.
• Prepare a post-market surveillance (PMS) plan and adverse event reporting process.
• Conduct an internal review or invite a third-party pre-assessment to check completeness and consistency.

AIMEILI Interpretation and Business Impact

One of the most common misjudgements is assuming that holding a CE or FDA certificate allows direct registration in another country. In reality, each country has an independent document review system. For high-risk IVDs (Classes B/C/D or equivalent), the depth and format of technical documentation must fully comply with local requirements. A gap analysis comparing existing documentation against target-country regulations is the most critical early step. It identifies missing or insufficient content and prevents repeated corrections and delays.

Reusable documentation includes product descriptions, design files, risk management frameworks, QMS certificates, and certain performance data—especially analytical performance. Localisation is essential for clinical evaluation data (population-specific data, epidemiological background, reference intervals), label and IFU language, and local agent information. In certain countries, such as Brazil and Thailand, IFUs must be in a specific language and contain specific warning content; direct translation of CE files may not pass.

Business impact: For multi-country registrations, AIMEILI recommends building a “core file set” based on the STED framework and then creating a “differential file set” for each market. This approach significantly reduces redundant documentation work and the risk of rejection or deficiency letters. The selection of a local agent is strategically important—they are not just an authorized representative; they handle changes, renewals, and adverse event communications. An ineffective agent can lead to loss of control over certificates. Companies should sign clear service agreements specifying response times and intellectual property ownership.

Common Follow-Up Questions

Which IVD products require clinical trial data?

Most countries require clinical trial data or rigorous clinical performance studies for high-risk IVDs, such as blood screening reagents, tumor markers, and genetic testing products. Low-risk products, such as HbA1c tests or routine biochemical reagents, may be supported by literature data and comparative studies. Specific requirements vary by country; refer to the latest national guidance or consult the regulatory authority. For example, the US FDA typically requires an IDE-approved clinical trial for Class III IVDs, while the EU IVDR requires performance studies based on prospective samples for Class D products.

Do technical documents need notarization or certification?

Some countries require notarized copies or certified translations. For example, Saudi Arabia's SFDA requires all documents to be submitted via a local agent, and some documents must be authenticated by a chamber of commerce or notary. Thailand's TFDA generally accepts company-stamped documents, but IFUs must be signed by the authorized representative. Always confirm document authentication requirements with your local agent before submission to avoid rejection due to formality issues.

How should document versions be managed for multiple country registrations?

Use a document management system or numbering rule, with each document clearly versioned and dated. Create a master document list and a country-to-document mapping table. When a product changes, assess the impact on each country's registration and update relevant files. Where files are reused across markets, ensure that the version retained in each country matches the one approved. Conduct regular document reviews to maintain ongoing compliance with newly issued local regulations.