How Should Translation and Notarization/Legalization Be Arranged for Overseas Medical Device Registration?

Answer: Arrange translation and notarization/legalization for overseas medical device registration by first confirming whether the product falls within the target country's medical device regulatory scope, then determining the risk class, for example EU Class I, IIa, IIb, III or FDA Class II, III, registration pathway, and applicant or local representative. Assess which existing NMPA, CE, FDA, ISO 13485, or MDSAP documents can be reused, focusing on the technical file, performance verification, risk management, clinical evaluation, and labels/instructions for use. Confirm the target country's language and authentication requirements, select a qualified medical-device translation provider and notary/legalization service, and coordinate local agent or authorized representative signatures. Allow sufficient time, typically 4-8 weeks, retain original documents for verification, and plan for post-market updates. For GHWP member states or multi-country registration, establish a core technical file reuse framework, unify translation templates, localize language, units of measure, and regulatory references, and keep control of documents with the local agent or authorized representative.

Article Information

Published: July 10, 2026, 22:09; Updated: July 10, 2026, 22:09

This FAQ organizes the questions companies should prioritize in actual projects involving international medical device registration, document preparation, compliance pathways, and post-market maintenance.

Content Structure

• Key Summary
• Applicable Scenarios and Core Questions
• Registration Determination Logic
• Documents and Evidence
• Common Errors
• Company Preparation Checklist
• AIMEILI Perspective
• Frequently Asked Follow-Up Questions
• Continue Reading
• Applicable Boundary

Key Summary

For overseas medical device registration, translation and notarization/legalization are critical steps to ensure documents are accepted by the target country's regulatory authority. Companies should first determine whether the product falls within the target country's medical device regulatory scope, then determine the registration pathway and applicant based on risk class, such as EU Class I, IIa or FDA Class II, III. They should then assess the reusability of existing NMPA, CE, FDA, ISO 13485, or MDSAP documents, with particular attention to the technical file, performance verification, risk management, clinical evaluation, labels, and instructions for use.

Common risks include deficiencies caused by inaccurate translation, incorrect authentication type, such as confusing Apostille with consular legalization, failure to confirm target-country language requirements in advance, and missing local agent signature documents. Companies should plan systematically: first clarify the specific requirements of the target country regulator, such as MHRA, ANVISA, or TFDA, then select a qualified translation provider and notary office, allow sufficient time of 4-8 weeks, and retain original documents for verification.

For GHWP member states or multi-country registration, it is advisable to establish a core technical file reuse plan, unify translation templates, perform secondary conversion for localization requirements such as language, units of measure, and regulatory references, and ensure that the local agent or authorized representative has control over documents. During post-market maintenance, translated and notarized/legalized documents must be continuously updated.

Applicable Scenarios and Core Questions

Companies searching for how to arrange translation and notarization/legalization for overseas medical device registration usually need to determine whether existing documents can support submission in the target market, whether a local agent or authorized representative is required, why timelines are extended, and which issues may affect launch plans. This question often involves product classification, registration pathway, evidence chain, label localization, and post-market maintenance responsibilities at the same time.

If a company plans to enter multiple GHWP member states or markets in Southeast Asia, the Middle East, and Latin America simultaneously, answering the process for only one country is not enough. A more valuable approach is to first make the core technical file, quality system evidence, performance verification, clinical evidence, and labels/instructions for use into reusable versions, then localize them according to each country's regulatory requirements.

Registration Determination Logic

First, determine whether the product falls within the target country's medical device regulatory scope. For example, some countries classify in vitro diagnostic reagents, software, and rehabilitation aids separately. Second, determine the registration pathway based on risk class, such as EU MDCG classification rules, FDA 21 CFR 862-892, and the China NMPA classification catalog. Low-risk products may follow self-declaration or a simplified process, while medium- and high-risk products require submission of a complete technical file and review by a designated body. Third, assess the reusability of existing documents. For products that already hold an NMPA registration certificate, CE MDR certificate, or FDA 510(k), the technical file, clinical evidence, and risk management report may be used for multi-country registration after translation and minor adjustment, but differences in standards such as ISO 14971 and IEC 60601 must be considered. Finally, clarify the applicant: whether the manufacturer registers directly or through a local agent, such as an EU Authorized Representative or a Brazilian ANVISA registration agent. The local agent is usually responsible for document transmission and supplementary submissions, and its authorization must be reflected in the notarized/legalized documents.

Documents and Evidence

Common documents requiring translation and notarization/legalization include: product technical files, including description, design, manufacturing, packaging, and labeling; quality management system certificates, such as ISO 13485 and MDSAP; risk management reports under ISO 14971; clinical evaluation or clinical trial reports; stability test reports; software validation documents; labels and instructions for use; Certificates of Free Sale; Letters of Authorization for authorized representatives; and post-market surveillance plans. The main authentication types are Apostille, applicable to Hague Convention member states, and consular legalization, applicable to non-member states. Some countries also accept embassy legalization or notarization by a local notary office. Regarding evidence, companies should retain original documents, page-by-page sealed translations, and copies of legalization certificates, and ensure that certificate validity covers the registration cycle.

Common Errors

• Translations are not in the target country's official language, or machine translation causes professional terminology errors, such as translating INR as Indian Rupee rather than International Normalized Ratio.
• Wrong authentication type is selected, for example, submitting an Apostille to a non-Hague Convention country, which makes the documents invalid.
• Target-country requirements for the notarizing or legalizing institution are ignored; some countries require the process to be completed by that country's embassy or consulate or a designated institution.
• Document versions are not confirmed in advance; the submitted translation is inconsistent with the original document version, or updated change documents are missing.
• Local agent signature documents are omitted, such as an authorized representative Letter of Authorization not signed by the legal representatives of both parties and notarized/legalized.
• Insufficient time is reserved for translation and legalization; usually 4-8 weeks is needed, and expedited service is possible but costly.

Company Preparation Checklist

• Confirm target-country language requirements, such as Portuguese for Brazil, English and French for Canada, and Japanese for Japan.
• Select a translation provider qualified in the medical device field and request proof of translation company qualifications and translator backgrounds.
• Clarify the required authentication type: Apostille, consular legalization, or embassy legalization, and confirm the process and timeline.
• Prepare electronic and paper versions of original documents, ensure signatures and seals are clear, and notarize originals when necessary.
• Communicate with the local agent or authorized representative to confirm the list of documents requiring signature and the legalization requirements.
• Develop a multi-country registration document reuse plan: unify translation templates and retain all versions of source documents and translations.
• Establish a document management ledger to track the translation and legalization completion status and validity period of each document.

AIMEILI Regulatory Interpretation and Business Impact

The most common misjudgment in translation and legalization is assuming a simplified process. For example, a company may assume that CE technical documentation can be used directly for Brazilian registration and overlook ANVISA requirements for document format and language, or assume that internal translation is sufficient without third-party certification. Early in the project, companies should complete target-country regulatory research, identify the document gap list, and engage a professional regulatory consultancy to review key documents. The following documents can often be reused: ISO 13485 certificates, risk management reports, and clinical evaluation plans/reports, but they require localization conversion, such as converting label units of measure and updating regulatory standard numbers.

Labels and instructions for use, authorization documents, and Certificates of Free Sale must be prepared anew and notarized/legalized. The core value of a local agent lies in controlling certificate validity and change management; companies should avoid granting unlimited agency authority. In multi-country registration, it is advisable to adopt a core document plus localization module strategy, with the same team managing translation and legalization in a unified way to reduce duplicate preparation and deficiency risks.

Frequently Asked Follow-Up Questions

Does translation require third-party certification?

In most countries, translations must be completed by a qualified translation company and accompanied by a translation statement with a seal or signature. Some countries, such as China and Japan, require a notary authority to authenticate the translation. Companies should preferably choose translation providers certified to ISO 9001 or ISO 17100 and retain translation process records.

Who bears notarization costs?

Notarization costs are usually borne by the manufacturer and include translation fees, notarization fees, authentication fees, and courier fees. For multi-country registration, centralized Apostille processing can reduce the per-document cost. Amounts vary by country; for example, Apostille in EU countries may be around EUR 50-100 per document, while consular legalization may reach USD 200-500 per document.

Can translated documents be shared across multiple countries?

If target countries use the same language, such as Spanish-speaking countries, translated documents may be shared, but terminology differences between countries, such as Spain and Mexico, must be considered. For countries with different languages, separate translations are required. In addition, legalization/authentication documents generally must be handled separately according to each country's specific requirements and cannot use the same legalization certificate.

Implementation Recommendations

In actual projects, companies should break this issue into five tasks: regulatory determination, document preparation, evidence reuse, localization conversion, and post-market maintenance, rather than having one department compile documents on an ad hoc basis. This helps identify document gaps earlier and align sales, R&D, quality, and regulatory teams on target-country requirements.

If a company plans to enter multiple markets simultaneously, it should first create a unified core technical file, then supplement authorization, labeling, language, forms, and local agent documents for each country. Multi-country registration efficiency often depends on whether the early document framework is unified, not only on submission speed in a single country.

• Confirm whether the product falls within the target country's medical device regulatory scope.
• Confirm risk class, registration pathway, and applicant/local representative.
• Verify that the technical file, quality system, and clinical evidence support each other.
• Clarify local agent, authorized representative, and certificate control rights.
• Establish post-market change, renewal, and vigilance event maintenance mechanisms.

Additional Execution Points

When handling translation and notarization/legalization for overseas medical device registration, companies should manage regulatory determination, documentary evidence, applicant responsibilities, launch timing, and post-market obligations in the same project plan. This avoids a situation in which regulatory affairs focuses only on documents, sales focuses only on launch timing, and quality does not understand target-market requirements, ultimately causing the registration pathway and document preparation to become disconnected.

If the target market is a GHWP member state or is highly aligned with international rules such as IMDRF, ISO 13485, ISO 14971, and UDI, companies should also prioritize reviewing reusable documents before deciding which content requires localized translation, supplementary declarations, retesting, or signature by the local agent. This sequence is more stable than directly collecting documents according to a country checklist and makes cost control easier.

At the project execution level, it is advisable to retain at least the product classification basis, technical file versions, label and instructions-for-use versions, covered models in test reports, sources of clinical evidence, local agent communication records, and deficiency response records. During subsequent renewal, changes, inspections, or post-market event handling, these records will directly affect whether the company can quickly explain the product's compliance status.

• Confirm the product's intended use and regulatory status in the target market.
• Confirm risk class, registration pathway, and applicant.
• Confirm whether the core technical file can be reused across markets.
• Confirm localized documents, label language, and authorization documents.
• Confirm post-market surveillance, change, and renewal responsibilities.

Continue Reading

• Previous: What is the difference between importer and distributor responsibilities in overseas medical device registration?
• Next: How should multiple models be grouped for submission in overseas medical device registration?
• Related: How should technical files be prepared for overseas registration of software medical devices?
• Related: How should registration documents for Southeast Asia be planned in a unified way?
• Related: What are the risks of local agents in Middle East medical device registration?
• Related: Why is the registration timeline in Latin America often extended?
• Related: How should product classification be determined for overseas medical device registration?

Return to FAQ Center | News | Contact AIMEILI

Content Review and Applicable Boundary

Content author: AIMEILI Regulatory Editorial Team

Professional review: AIMEILI Medical Device International Registration Project Team

Source principle: Prioritize official regulatory agencies, international organizations, standards organizations, and publicly available regulatory materials; industry media and project experience are used only as supporting judgment.

Applicable boundary: This article is intended for preliminary understanding, document preparation, and project planning and does not replace the formal requirements of target country regulators, testing conclusions, or legal opinions.

Source note: Compiled from the AIMEILI regulatory practical question bank, 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 regulator and the product document basis.