How Should Post-Market Surveillance Be Handled After Medical Device Registration in Thailand?

Post-market surveillance (PMS) for a medical device registered in Thailand should be planned before submission, not after approval. In practice, manufacturers first need to confirm the product classification and the applicable TFDA registration pathway, then prepare technical documentation, labels and instructions for use (IFU), quality system evidence, authorization documents and local representative information. Existing NMPA files can serve as a starting point, but they generally have to be adapted for language, format, labelling and evidence-chain requirements set by the Thai Food and Drug Administration (TFDA). The most reliable approach is to complete a product classification and documentation gap assessment first, and only then decide whether NMPA, CE, FDA, ISO 13485 or other market files can be reused. Thailand registration typically affects the technical file, authorized representative arrangements, importer cooperation, label language, quality system evidence and subsequent change control at the same time; if a company proceeds only on the basis of "which documents must be submitted," deficiency letters and rework are likely to arise in model coverage, evidence-chain consistency, label claims and certificate control.

Published: 10 July 2026, 12:51  |  Updated: 10 July 2026, 12:51

This article reviews the questions that companies should assess first in real international registration projects relating to medical device registration, documentation preparation, compliance pathways and post-market maintenance.

Key Takeaways

Medical device registration in Thailand usually requires confirming the product classification and applicable pathway first, followed by preparation of the technical file, labels and IFU, quality system evidence, authorization documents and local representative information. Existing NMPA documentation may be used as a basis, but it generally needs to be adapted for language, format, labelling and evidence-chain requirements under the TFDA. For manufacturers, the more prudent approach is to complete a product classification and documentation gap assessment first, and then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.

Thai registration commonly affects the technical file, authorized representative, importer cooperation, label language, quality system evidence and subsequent change maintenance simultaneously. If the project is driven only by a document checklist, corrections and rework can easily arise in model coverage, evidence-chain consistency, label claims and certificate control. AIMEILI recommends placing 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 an ad hoc basis for each country.

Companies should also make project-level judgments based on the latest requirements of the target regulatory authority, the existing technical file base, the product risk class and the launch plan, instead of preparing mechanically against a document list.

Applicable Scenarios and Core Questions

Companies searching for guidance on post-market surveillance for Thai medical device registration are usually not looking for a conceptual explanation. They want to determine whether their existing documentation can support a Thai submission, whether a local agent or authorized representative is required, why timelines are being extended, and which issues may affect their launch plan. Behind this question there are typically several interconnected matters: product classification, registration pathway, evidence chain, label localization and post-market maintenance responsibilities.

If a company intends to enter several GHWP member states at the same time, or markets in Southeast Asia, the Middle East and Latin America, answering the procedure for a single country is not sufficient. A more valuable approach is to first develop reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labels/IFU, and then localize them according to 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 involves software or IVD characteristics. Only then can the risk class and submission pathway be determined. Once the pathway judgment is wrong, all subsequent translation, notarization, authorization, testing and supplementary documentation will move in the wrong direction.

For a Thai project, the applicant entity and the boundaries of local responsibility must also be confirmed: 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 matters are left vague in a commercial contract, market control can be affected later on.

Documentation and Evidence

Typical documentation includes the product description, model and specification matrix, intended use, risk classification rationale, 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 documentation.

The key to documentation quality is not volume but consistency. IFU claims, the models covered by test reports, the scope of clinical evidence, risk management conclusions, 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 its intended use, not on the quantity of documents uploaded.

Common Pitfalls

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

• Translating domestic NMPA documents directly and submitting them without restructuring the evidence according to the Thai pathway.
• Too many model or specification variants, while test reports, clinical evidence or labelling coverage are insufficient.
• Selecting a local agent purely on the basis of sales cooperation, without defining regulatory responsibility, certificate control and post-market maintenance obligations.
• Inconsistency between labels, IFU, promotional materials and registration claims, leading to deficiency letters or post-market compliance risk.
• Failure to plan multi-country documentation reuse in advance, so that each country requires separate preparation and both cost and timelines are inflated.

Company Preparation Checklist

Before starting a project, companies should use an internal checklist to confirm the documentation base, 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 registrations can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management documentation, clinical evaluation and English-language IFU.
• Confirm the responsibilities, fees, certificate control and exit mechanism of the local agent or authorized representative.
• Establish a country-specific gap assessment table that identifies what additional testing, translation, notarization or supplementary declarations are required.

AIMEILI Perspective

AIMEILI recommends that companies not view Thai registration as a one-off document submission, but manage it as an overseas market access project. For companies preparing to enter multiple countries, establishing a clear core technical file and evidence matrix first, and then converting it to meet national requirements, is generally faster, more stable and more conducive to later changes and certificate renewals than patching documentation country by country.

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

Frequently Asked Questions

Can domestic documentation be used directly for Thai registration?

Domestic documentation can be used as a basis, but it generally cannot be submitted as-is. Companies need to adjust the document structure, language, labels, authorization documents and evidence chain in accordance with local regulatory requirements.

When is the best time to start a gap assessment?

A gap assessment should be started as soon as the target markets and product list are confirmed. The earlier it 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?

A local agent is typically involved in registration communication, changes, certificate renewal 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 documentation is not an isolated certificate. Regulators usually examine whether the manufacturer name, manufacturing site, 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 product being registered, or if the manufacturing site, model specifications, IFU version and test reports are inconsistent, the company may be asked for supplementary explanations even if a large volume of documentation has been prepared.

Before submission, companies should establish an evidence consistency checklist that maps the product name, model and specification, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label and IFU version, and quality system certificate item by item. This step appears basic, but it can significantly reduce the probability of deficiency letters, particularly for projects involving multiple GHWP member states or multiple product families submitted at the same time.

Localization and Authorized Representative Responsibilities

Thai registration projects usually involve arrangements with a local agent, authorized representative, importer or registration holder. Companies should 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, IFU 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

Completion of registration does not mean that compliance work has ended. Companies must also maintain certificate validity periods, change records, distributor authorizations, complaint handling, adverse event reporting, recall procedures, label versions and regulatory update records. Many companies invest substantial effort in obtaining the certificate but neglect post-market maintenance; subsequently, when a manufacturing site change, model expansion, IFU update or agent replacement occurs, the certificate can become disconnected from market sales.

AIMEILI recommends integrating this question into annual international registration planning: 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 higher registration efficiency in a single country; more importantly, it enables companies to build a replicable overseas compliance capability and reduce the cost of starting from scratch each time they enter a new market.

Further Reading

• Previous: What Are the Common Reasons for Deficiency Letters in Thai Medical Device Registration?
• Next: When Must a Registration Change Be Filed for Thai Medical Device Registration?
• Recommended: How Should Documentation Be Prepared for Medical Device Registration in Malaysia?
• Recommended: How Should Product Classification Be Determined for Medical Device Registration in Malaysia?
• Recommended: How Should the Technical File Be Organized for Medical Device Registration in Malaysia?
• Recommended: How Should Labels and IFU Be Localized for Medical Device Registration in Malaysia?
• Recommended: How Should Clinical Evaluation Documentation Be Prepared for Medical Device Registration in Malaysia?
• Recommended: Can Test Reports Be Reused for Medical Device Registration in Malaysia?

Content Review and Scope of Application

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team.

Source principles: 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 judgment.

Scope of application: This article is intended for preliminary understanding, documentation preparation and project planning. It does not replace the formal requirements of the target country's regulatory authority, testing conclusions or legal advice.