What Are the Risk Management File Requirements for Medical Device Registration in Thailand?

Thailand medical device registration typically requires confirming the product classification and applicable registration pathway first, and only then preparing the technical file, labels and instructions for use, quality management system evidence, authorization documents and local representative information. Existing NMPA documentation can serve as a baseline, but it generally has to be adapted to Thai FDA requirements in terms of language, format, labelling and the overall evidence chain. For Chinese medical device manufacturers, the more reliable approach is to conduct a product classification and documentation gap assessment first, and then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused. Registration in Thailand usually affects the technical file, authorized representative arrangements, importer cooperation, label language, quality system evidence and ongoing change maintenance at the same time. If the project is driven only by the question of which documents to submit, deficiencies and rework are likely to arise in model coverage, evidence chain consistency, label claims and certificate control.

AIMEILI recommends that companies position this question within a broader GHWP member state and multi-country market access strategy, using one reusable core technical file to support localization in different markets rather than rebuilding documentation on a case-by-case basis for each country. Companies should also make project-level judgements based on the latest requirements of the target regulator, the existing technical file foundation, the product risk class and the launch plan, rather than mechanically preparing documents against a checklist.

Publication date: 2026-07-10 13:35; Update date: 2026-07-10 13:35. Compiled from AIMEILI's regulatory practice 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's regulatory authority and the underlying product documentation.

This article addresses the questions companies need to prioritize in practice across international medical device registration, documentation preparation, compliance pathways and post-market maintenance.

Key Takeaways

• Thailand medical device registration usually starts with product classification and pathway confirmation, followed by the technical file, labels and instructions for use, quality system evidence, authorization documents and local representative information.
• Existing NMPA documentation can be used as a foundation, but it normally needs adaptation to Thai FDA requirements for language, format, labelling and evidence chain.
• For Chinese manufacturers, the prudent approach is to complete a product classification and documentation gap assessment before deciding whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.
• Thailand registration simultaneously affects the technical file, authorized representative, importer cooperation, label language, quality system evidence and subsequent change maintenance.
• AIMEILI recommends planning this question within a GHWP member state and multi-country access strategy, using a reusable core technical file to support localization in each market.

Scope and Core Question

Companies searching for the risk management file requirements for medical device registration in Thailand are usually not looking for a conceptual explanation. What they need to determine is whether their existing documentation can support a Thai submission, whether a local agent or authorized representative is required, why timelines get extended, and which issues could affect the launch plan. Behind this question there are typically several interconnected topics: product classification, registration pathway, evidence chain, label localization and post-market maintenance responsibilities.

If a company plans to enter several GHWP member states or markets in Southeast Asia, the Middle East and Latin America at the same time, answering the process for a single country is not sufficient. The more valuable approach is to first build reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labels and instructions for use, and then localize them in line with each country's regulatory requirements.

Registration Decision Logic

Companies should first confirm the intended use, mechanism of action, use scenario, method and duration of body contact, whether the device is sterile, whether it is active, and whether it incorporates software or has IVD characteristics, and then determine the risk class and submission pathway. Once the pathway assessment is wrong, all subsequent translation, notarization, authorization, testing and supplementary documentation will move in the wrong direction.

For a Thailand project, it is also necessary to confirm the applicant entity and the boundaries of local responsibility: who holds the certificate, who is responsible for regulatory communication, who handles importation and post-market events, who triggers changes, and who maintains renewal documentation. If these points are handled vaguely in a commercial contract only, market control can be affected later on.

Documentation and Evidence

Typical documentation includes the product description, model and specification matrix, intended use, basis for risk classification, ISO 13485 or applicable quality system evidence, technical file, performance verification reports, risk management file, clinical evaluation or clinical evidence, labels and instructions for use, authorization documents, existing registration certificates, manufacturer declarations and post-market surveillance documentation.

The key to documentation quality is not volume but consistency. Claims in the instructions for use, the models covered by test reports, the applicable scope of clinical evidence, the conclusions of the risk management file, label warnings and the information in the registration application form must support one another. Regulators focus on whether the device is safe, effective and traceable for the intended use, not on whether the company uploaded a large number of documents.

Common Pitfalls

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

• Translating NMPA documentation directly and submitting it without restructuring the evidence according to the Thai pathway.
• Listing too many models and specifications while test reports, clinical evidence or labels do not provide sufficient coverage.
• Selecting a local agent purely on the basis of sales cooperation, without clarifying regulatory responsibilities, certificate control and post-market maintenance obligations.
• Inconsistency between labels, instructions for use, promotional materials and registration documentation, leading to deficiency letters or post-market compliance risk.
• Failure to plan multi-country documentation reuse in advance, resulting in duplicated preparation for each country and inflated cost and timelines.

Company Preparation Checklist

Before starting a project, companies should use an internal checklist to confirm the documentation foundation, so that critical evidence gaps are not discovered only after submission.

• Compile the target product list, model and specification matrix and intended use statements.
• Verify whether existing NMPA, CE, FDA or other market registration documentation can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management file, clinical evaluation and English instructions for use.
• Confirm the responsibilities, fees, certificate control and exit mechanism of the local agent or authorized representative.
• Establish a target-country gap assessment table specifying what needs additional testing, translation, notarization or supplementary declarations.

AIMEILI Perspective

AIMEILI advises companies not to view Thailand registration as a one-off document submission, but to manage it as an overseas market access programme. For companies preparing to enter multiple countries, establishing a clear core technical file and evidence matrix first and then converting it to national requirements is generally faster, more stable and more conducive to subsequent changes and renewals than supplementing documentation country by country on an ad hoc basis.

From a project management perspective, three things should be controlled as early as possible: first, product classification and pathway determination; second, consistency of the documentation evidence chain; and third, the regulatory responsibility boundaries of local partners. If these three items are unclear, the project may still encounter repeated issues during deficiency responses, agent communication and post-market maintenance, even if the documentation appears extensive.

Frequently Asked Follow-up Questions

Can domestic documentation be used directly for Thailand registration?

Domestic documentation can serve as a foundation, but it usually cannot be submitted as is. Companies need to adjust the documentation structure, language, labelling, authorization documents and evidence chain in accordance with local regulatory requirements.

When is the best time to start a gap assessment?

It is advisable to start immediately after confirming the target markets and product list. The earlier the gap assessment is completed, the easier it is to arrange additional testing, translation, label adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

The local agent typically participates in registration communication, changes, renewals and post-market event handling. If responsibilities are unclear, certificate control and subsequent market stability can be affected.

Quality System and Evidence Consistency

From a registration review perspective, quality system documentation is not an isolated certificate. Regulators usually examine whether the manufacturer name, manufacturing address, product scope, certificate validity period, applicable standards and technical file are consistent with one another. If the scope covered by the ISO 13485 certificate does not match the device being registered, or if the manufacturing address, model specifications, instructions for use version and test reports are inconsistent, the company may be asked for supplementary explanations even if it has prepared a large volume of documents.

Companies should establish an evidence consistency verification table before submission, mapping the product name, model specifications, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label and instructions for use version and quality system certificate item by item. This step may appear basic, but it can significantly reduce the probability of deficiency letters, particularly for projects involving simultaneous submissions in several GHWP member states or for multiple product families.

Localization and Agent Responsibilities

Thailand registration projects typically involve arrangements with a local agent, authorized representative, importer or registration holder. Companies need to confirm in advance whether the local partner is only responsible for submitting documents, or whether it also handles regulatory communication, certificate maintenance, post-market event reporting, change applications and renewal reminders. Different responsibility boundaries directly affect certificate control and subsequent market stability.

Labels, instructions for use and authorization documents also cannot simply be translated. Companies should verify local language requirements, the boundaries of product claims, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorized representative information and after-sales contact details. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localization is to convert reusable evidence into a submission structure acceptable to the target country, rather than writing a separate set of isolated documents.

Post-Market Maintenance and Long-Term Planning

Completing registration does not mean the compliance work is over. Companies must also maintain certificate validity, change records, distributor authorizations, complaint handling, adverse event reporting, recall procedures, label versions and regulatory update records. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance, and later, when a manufacturing address change, model extension, instructions for use update or agent replacement occurs, the certificate and actual market distribution can become disconnected.

AIMEILI recommends managing this question within an annual international registration plan: first define target market priorities, then build a reusable documentation package and a country gap list, and finally schedule submission, deficiency response, post-market maintenance and renewal milestones. The value of this approach is not only greater efficiency in a single country, but also the development of repeatable overseas compliance capability, reducing the cost of starting from scratch each time a new market is entered.

Further Reading

Previous

• How should multiple models be grouped for medical device registration in Thailand?

Next

• How should performance verification documentation be prepared for medical device registration in Thailand?

Recommended Reading

• How should registration documentation be prepared for medical device registration in Malaysia?
• How should product classification be determined for medical device registration in Malaysia?
• How should the technical file be organized for medical device registration in Malaysia?
• How should labels and instructions for use be localized for medical device registration in Malaysia?
• How should clinical evaluation documentation be prepared for medical device registration in Malaysia?
• Can test reports be reused for medical device registration in Malaysia?

Back to the FAQ Centre

• News and Insights
• Contact AIMEILI

Content Review and Applicability Boundaries

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team. Sourcing principle: priority is given to official regulatory authorities, international organizations, standards bodies and publicly available regulatory materials; industry media and project experience are used only as supporting references. Applicability boundary: this article is intended for preliminary understanding, documentation preparation and project planning, and does not replace the formal requirements of the target country's regulatory authority, testing conclusions or legal advice.