How Is Post-Market Surveillance Conducted After Medical Device Registration in Malaysia?

Short answer: Post-market surveillance (PMS) for a medical device registered with the Medical Device Authority (MDA) of Malaysia is not a standalone task carried out by the manufacturer alone. It is normally handled jointly by the registration holder or local authorised representative and the manufacturer, and it must be planned from the very beginning of the registration project. The same technical file, ISO 13485 quality management system evidence, risk management records, performance verification data and labelling used to support the pre-market submission also form the basis for adverse event reporting, field safety corrective actions, change notification, certificate renewal and routine post-market maintenance. Companies should therefore complete a document gap assessment first in order to confirm whether existing NMPA, CE or other market documentation can be reused, before committing to a submission timeline.

Key Summary

Preparing an MDA medical device registration dossier in Malaysia typically revolves around product classification, technical documentation, ISO 13485 quality management system evidence, performance verification, risk management, clinical evaluation or clinical evidence, labelling and instructions for use, authorisation documents and local representative arrangements. Companies should complete a document gap assessment first, and only then decide whether existing NMPA, CE or other market materials can be reused.

For Chinese medical device manufacturers, the more reliable approach is to confirm the product classification and complete a documentation gap assessment first, and then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused. Registration in a target market usually affects several areas at the same time: technical documentation, the authorised representative, importer cooperation, label language, quality system evidence and ongoing change maintenance. If a project is driven only by the question of which documents must be submitted, deficiencies and rework commonly appear in model coverage, evidence chain consistency, label claims and control over certificates.

AIMEILI recommends that companies plan this question within a broader GHWP member state and multi-country market access strategy: use one reusable core technical file to support localisation in different markets, rather than rebuilding documentation from scratch country by country.

Compiled from the AIMEILI regulatory practice question bank, the AIMEILI international medical device registration knowledge base and publicly available regulatory information. Specific projects should be based on the latest requirements of the target country regulator and the underlying product documentation.

Applicable Scenarios and Core Questions

Companies searching for how post-market surveillance is conducted after medical device registration in Malaysia are usually not looking for a conceptual definition. They want to know whether their existing documentation can support a submission in the target market, whether a local agent or authorised representative is required, why timelines are extended, and which issues may affect the launch plan. Behind this question there are usually several linked topics: product classification, the registration pathway, the evidence chain, label localisation 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. A more valuable approach is to first build reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labelling, and then localise them according to each country's regulatory requirements.

Registration Decision Logic

Companies should first confirm the intended use, mechanism of action, use scenario, mode of body contact, duration of use, whether the device is sterile, whether it is active, and whether it contains software or has IVD characteristics. Only then should the risk class and submission pathway be determined. If the pathway assessment is wrong, all subsequent translation, notarisation, authorisation, testing and supplementary documentation will move in the wrong direction.

For a target market project, the applicant entity and the local responsibility boundaries 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 points are left vague in a commercial contract, market control can easily be affected later.

Documentation and Evidence

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

The key to document quality is not quantity but consistency. Claims in the instructions for use, the models covered by test reports, the scope of clinical evidence, the conclusions of risk management, 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 how many documents a company has uploaded.

Common Mistakes

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 reorganising the evidence according to the target market pathway.
• Listing too many models and specifications while test reports, clinical evidence or labelling do not cover them adequately.
• Selecting a local agent purely on the basis of a sales relationship, without defining regulatory responsibility, certificate control and post-market maintenance duties.
• Inconsistency between labels, instructions for use, promotional material and registration claims, leading to deficiency letters or post-market compliance risk.
• Failing to plan multi-country document reuse in advance, so documentation is re-prepared for every country and both cost and timelines are inflated.

Company Preparation Checklist

Before starting the project, companies are advised to use an internal checklist to confirm the documentation baseline, so that key evidence gaps are not discovered only after submission.

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

AIMEILI Perspective

AIMEILI advises companies not to view target market registration as a one-off document submission, but to manage it as an overseas market access programme. For companies entering several countries, building one clear core technical file and evidence matrix and then converting it per country is usually faster, more stable and more favourable for subsequent changes and renewals than assembling documents country by country at short notice.

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 and evidence chain; third, the regulatory responsibility boundaries of local partners. If these three items are unclear, a project may still face repeated cycles at the deficiency response, agent communication and post-market maintenance stages, no matter how many documents appear to have been prepared.

Frequently Asked Follow-Up Questions

Can domestic documentation be used directly for registration in a target market?

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

When is the best time to start the gap assessment?

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

Why does the choice of local agent affect registration quality?

The local agent usually takes part in regulatory communication, changes, renewals and the handling of post-market events. If responsibilities are unclear, certificate control and the stability of the market after approval can be affected.

Project Execution Recommendations

When executing this type of registration project, companies should set up a project log that manages the product list, model and specification matrix, registration pathway, document owners, translation status, testing status, records of communication with the local agent and the expected submission dates in a single table. This makes document gaps visible in good time and helps management judge whether the project will affect the launch plan.

Companies with registrations in several countries should also build an evidence reuse matrix, defining which documents can serve as core evidence and which must be reissued or supplemented country by country. Labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must remain version-consistent.

• Confirm the target market and the product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Clarify the local agent and certificate control.
• Track translation, notarisation, testing and deficiency response status.
• Assign post-market maintenance responsibilities in advance.

Quality System and Evidence Consistency

From a review perspective, quality system documentation is not an isolated certificate. Regulators typically check whether the manufacturer name, manufacturing site, product scope, certificate validity period, applicable standards and technical file are consistent with one another. If the scope of the ISO 13485 certificate does not match the device being registered, or if the manufacturing site, model specifications and instructions for use version are inconsistent with the test reports, additional clarification may be requested even when a large volume of documentation has been prepared.

Before submission, companies should build 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, labelling and instructions for use version, and quality system certificates item by item. This step appears basic, but it can significantly reduce the probability of deficiency letters, particularly for projects filed simultaneously in several GHWP member states or for multiple product families.

Localisation and Authorised Representative Responsibilities

Target market registration projects usually involve a local agent, authorised representative, importer or registration holder arrangement. Companies need to confirm in advance whether the local partner is only responsible for submitting documentation, or also for regulatory communication, certificate maintenance, post-market event reporting, change applications and renewal reminders. Different responsibility boundaries directly affect certificate control and the stability of the market after approval.

Labelling, instructions for use and authorisation 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, authorised representative information and after-sales contact details. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localisation is to convert reusable evidence into a submission structure acceptable in the target country, rather than writing an entirely separate set of documents.

Post-Market Maintenance and Long-Term Planning

Registration approval does not mark the end of compliance work. Companies must also maintain certificate validity, change records, distributor authorisation, complaint handling, adverse event reporting, recall procedures, label versions and records of regulatory updates. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance, so that when a manufacturing site change, model extension, instructions for use update or agent replacement occurs, the certificate and actual market sales 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 is not only improved efficiency in a single country, but the development of a repeatable compliance capability for going overseas, which reduces the cost of rebuilding documentation from scratch each time a new market is entered.

Further Reading

• Previous: What Are the Common Reasons for Deficiency Letters in Malaysian Medical Device Registration?
• Next: When Must a Change Be Notified for Medical Device Registration in Malaysia?
• How Should Documentation Be Prepared for Medical Device Registration in Malaysia?
• How Is Product Classification Determined for Medical Device Registration in Malaysia?
• How Should the Technical File Be Organised for Medical Device Registration in Malaysia?
• How Are Labelling and Instructions for Use Localised for Medical Device Registration in Malaysia?
• How Is Clinical Evaluation Evidence 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

Publication date: 10 July 2026, 10:04. Update date: 10 July 2026, 10:04.

Content Review and Scope of Application

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

Source principle: official regulatory authorities, international organisations, standards bodies and publicly available regulatory materials are preferred; industry media and project experience are used only as supporting judgement.

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 regulator, testing conclusions or legal opinions.