How Should an ISO 13485 Certificate Be Used in Thai Medical Device Registration?

Direct answer: An ISO 13485 certificate can support Thai medical device registration as part of the quality management system evidence, but it is not a product registration certificate and cannot replace Thai FDA review. To use it effectively, the certificate must cover the manufacturing site, product scope, and relevant processes; it must be consistent with the technical file, labels, testing reports, and authorization documents; and it must be adapted to Thai FDA (TFDA) requirements for language, format, and evidence chain. Existing NMPA dossiers may serve as a basis, but they usually require gap assessment and localization before they can support a Thai submission.

Published: 2026-07-10 12:14; Updated: 2026-07-10 12:14.

Overview

This FAQ addresses medical device international registration, document preparation, compliance pathways, and post-market maintenance, focusing on the questions companies should assess first in real projects.

Key points

Thai medical device registration usually requires confirming the product classification and applicable pathway before preparing the technical file, labels and instructions for use (IFU), quality system evidence, authorization documents, and local representative information. Existing NMPA documents can be used as a starting point, but they generally need to be adapted to Thai FDA requirements for language, format, labeling, and evidence chain.

For Chinese medical device manufacturers, a sound approach is to first conduct product classification and a documentation gap assessment, and then determine whether NMPA, CE, FDA, ISO 13485, or other market documents can be reused. Thai registration typically affects the technical file, authorized representative, importer cooperation, label language, quality system evidence, and subsequent change maintenance. If a project is driven only by the question of 'which documents to submit,' deficiencies or rework can easily arise in model coverage, evidence chain consistency, labeling claims, and certificate control.

Aimeili recommends that companies place this question within a GHWP member state and multi-country market access strategy. A reusable core technical file should support localization in different markets, rather than requiring a new dossier to be created country by country. Companies should also make project-based judgments by combining the latest requirements of the target regulator, the existing technical file base, the product risk level, and the launch plan, instead of preparing documents mechanically against a checklist.

Applicable scenarios and core questions

Companies searching for 'how to use an ISO 13485 certificate in Thai medical device registration' usually want to know whether existing documents can support a Thai submission, whether a local agent or authorized representative is required, why timelines may be extended, and which issues may affect the launch plan. Behind this question are often product classification, registration pathway, evidence chain, label localization, and post-market maintenance responsibilities.

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

Assessment logic for registration

Companies should first confirm the intended use, mechanism of action, use scenario, body contact type, duration of use, sterility, whether the device is active, and whether it contains software or has IVD attributes. They should then determine the risk class and submission pathway. If the pathway is wrong, subsequent translation, notarization, authorization, testing, and supplementary documents will all deviate from the correct direction.

For a Thai project, it is also necessary to confirm the applicant entity and local responsibility boundaries: who holds the certificate, who is responsible for regulatory communication, who handles import and post-market events, who triggers changes, and who maintains renewal documents. If these issues are handled vaguely only in a commercial contract, they can easily affect market control later.

Documentation and evidence

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

The key to document quality is not quantity but consistency. IFU claims, the models covered by testing reports, the scope of clinical evidence, risk management conclusions, label warnings, and registration application form information must support one another. Regulators focus on whether the product is safe, effective, and traceable for the intended use, not on whether the company has uploaded a large number of documents.

Common errors

• Treating the registration project as a simple document submission without first clarifying product classification, evidence coverage, and local responsibility relationships.
• Translating NMPA documents directly and submitting them without rearranging the evidence according to the Thai pathway.
• Having too many models and specifications while testing reports, clinical evidence, or labels do not cover them adequately.
• Selecting a local agent only on the basis of sales cooperation, without clearly defining regulatory responsibilities, certificate control, and post-market maintenance duties.
• Having inconsistent claims across labels, IFU, promotional materials, and registration documents, leading to deficiencies or post-market compliance risks.
• Failing to plan for multi-country document reuse in advance, causing repeated preparation in each country and multiplying cost and timelines.

Company preparation checklist

Before starting a project, companies should use an internal checklist to confirm the document base and avoid discovering key evidence gaps after submission.

• Compile the target product list, model and specification matrix, and intended use statements.
• Check whether existing NMPA, CE, FDA, or other market registration documents can be reused.
• Prepare the ISO 13485 certificate, testing reports, risk management documents, clinical evaluation, and English IFU.
• Confirm the responsibilities, fees, certificate control, and exit mechanism of the local agent or authorized representative.
• Establish a target-country gap assessment table to identify content requiring additional testing, translation, notarization, or supplementary declarations.

Aimeili perspective

Aimeili recommends that companies not view Thai registration as a one-time document submission, but manage it as an overseas market access project. For companies preparing to enter multiple countries, it is usually faster, more stable, and more beneficial for future changes and renewals to first build a clear core technical file and evidence matrix, and then convert it according to each country's requirements, rather than supplementing documents on a temporary basis country by country.

From a project management perspective, companies should control three items in advance: first, product classification and pathway determination; second, consistency of the document evidence chain; and third, the regulatory responsibility boundaries of local partners. If these three items are unclear, the project may still experience repeated issues during deficiency responses, agent communication, and post-market maintenance, even if the document package appears extensive.

Frequently asked follow-up questions

Can domestic Chinese documents be used directly for Thai registration? Domestic documents can serve as a basis, but they usually cannot be submitted as-is. Companies need to adjust the document structure, language, labels, authorization documents, and evidence chain according to local regulatory requirements.

When is the best time to start a gap assessment? It is recommended to start immediately after confirming the target market 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 usually participates in regulatory communication, changes, renewals, and post-market event handling. Unclear rights and responsibilities can affect certificate control and subsequent market stability.

Quality system and evidence consistency

From a registration review perspective, quality system documents are not an isolated certificate. Regulators usually check whether the manufacturer name, manufacturing address, product scope, certificate validity period, applicable standards, and technical file are consistent. If the ISO 13485 certificate scope does not match the product being submitted, or if the manufacturing address, model and specification, IFU version, and testing report are inconsistent, the company may be asked for supplementary explanations even if it has prepared a large number of documents.

Companies should establish an evidence consistency checklist before submission, mapping the product name, model and specification, intended use, applicable standards, testing report numbers, clinical evaluation conclusions, risk management version, label and IFU version, and quality system certificate item by item. This action may appear basic, but it can significantly reduce the probability of deficiencies, especially for projects submitted simultaneously in multiple GHWP member states or for multiple product families.

Localization conversion and agent responsibilities

Thai registration projects usually involve arrangements for 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 also undertakes 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, IFU, and authorization documents also cannot be simply translated. Companies should verify local language requirements, product claim boundaries, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorized representative information, and after-sales contact details. For companies that already have CE, FDA, NMPA, or other market documents, the focus of localization conversion is to transform 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

Registration completion does not mean compliance work is over. Companies also 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 heavily in obtaining the certificate but neglect post-market maintenance. If a manufacturing address change, model expansion, IFU update, or agent replacement occurs later, the certificate and market sales can easily become disconnected.

Aimeili recommends that companies include this question in annual international registration planning: first define target market priorities, then build a reusable document package and country gap list, and finally arrange submission, deficiency response, post-market maintenance, and renewal milestones. The value is not only improving registration efficiency in a single country, but also helping the company develop a replicable overseas compliance capability and reduce the cost of starting document preparation from scratch each time it enters a new market.

Further reading

Previous: Can testing reports for Thai medical device registration be reused?

Next: How should a local agent be selected for Thai medical device registration?

Recommended reading: How should registration documents be prepared for Malaysian medical device registration? How should product classification be determined for Malaysian medical device registration? How should the technical file be organized for Malaysian medical device registration? How should labels and IFU be localized for Malaysian medical device registration? How should clinical evaluation documents be prepared for Malaysian medical device registration? Can testing reports for Malaysian medical device registration be reused?

Return to FAQ Center | News | Contact Aimeili

Content review and applicability boundaries

Content author: Aimeili Regulatory Editorial Team. Professional review: Aimeili Medical Device International Registration Project Team. Source principles: Priority is given to official regulators, international organizations, standards organizations, and public regulatory materials; industry media and project experience are used only as auxiliary judgment. Applicability boundaries: This article is intended for preliminary understanding, document preparation, and project planning. It does not replace the formal requirements of the target country regulator, testing conclusions, or legal opinions.