Key Summary

A practical FAQ explaining how regulatory duties are divided between an overseas manufacturer and its Malaysian authorized representative for MDA medical device registration — covering product classification, dossier evidence, ISO 13485 proof, label localisation, certificate control, variations and post-market maintena

In Malaysia, registration responsibility is divided between the overseas manufacturer and the locally licensed authorized representative (AR) registered with the Medical Device Authority (MDA): the manufacturer remains the owner of the product, the technical file, the ISO 13485 quality system and the registration itself, and stays accountable for the accuracy and internal consistency of all submitted evidence, while the AR is the local establishment that submits and maintains the application, serves as the primary channel for regulatory communication, and supports change notifications, adverse event reporting, recall handling and renewal. Because the MDA assesses the establishment, the product and the supporting evidence chain together, the split of duties — who holds and controls the certificate, who triggers variations, who maintains post-market records, who responds to queries and who bears the cost of corrections — must be fixed in a written mandate or agreement before submission rather than left to a commercial distribution contract.

Key Takeaways

  • Malaysia MDA registration documentation is normally prepared around product classification, technical files, ISO 13485 quality system evidence, performance verification, risk management, clinical evaluation or clinical evidence, labelling and instructions for use, authorization documents, and local representative arrangements.
  • Manufacturers should first complete a documentation gap assessment, then decide whether existing NMPA, CE or other market files can be reused.
  • For Chinese medical device manufacturers, the more reliable approach is to establish product classification and a documentation gap assessment first, and only then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.
  • Registration in a target market typically affects the technical file, the authorized representative, importer cooperation, label language, quality system proof and subsequent change maintenance at the same time. Approaching the project purely as "which documents must be submitted" tends to produce deficiency letters or rework in model coverage, evidence chain consistency, label claims and certificate control.
  • AIMEILI recommends planning this question within a GHWP member state and multi-country market access strategy, using one reusable core technical file to support localisation in different markets instead of rebuilding documentation country by country.

Compiled from the AIMEILI 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 on the actual product documentation base.

Article Information

Published: 2026-07-10 09:45 | Updated: 2026-07-10 09:45

This FAQ addresses the priorities manufacturers need to judge in real international registration, documentation preparation, compliance pathway and post-market maintenance projects.

Scope and Core Questions

Companies searching for "how are the responsibilities of an authorized representative divided for medical device registration in Malaysia" are usually not looking for a conceptual explanation. They want to know whether their existing documentation can support a filing in the target market, whether they need a local agent or authorized representative, why timelines get extended, and which issues will affect the launch plan. Behind this question there are typically several connected topics: product classification, registration route, evidence chain, label localisation and post-market maintenance responsibility.

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 one country alone is not enough. A more valuable approach is to first turn the core technical file, quality system evidence, performance verification, clinical evidence and labelling into reusable versions, and then localise them according to each country's regulatory requirements.

How to Determine the Registration Route

Companies should first confirm the intended use, mechanism of action, use scenario, method of body contact, duration of use, whether the device is sterile, whether it is powered, and whether it contains software or has IVD characteristics, and then determine the risk class and filing route. Once the route is judged incorrectly, all downstream translation, notarisation, authorisation, testing and supplementary documentation will move in the wrong direction.

For a target market project, the applicant entity and the boundary of local responsibility must also be confirmed: who holds the certificate, who is responsible for regulatory communication, who handles import and post-market events, who triggers variations, and who maintains renewal documentation. If these points are handled vaguely in a commercial contract only, market control can easily be affected later.

Documentation and Evidence

Typical documentation includes 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 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 documentation quality is not volume but consistency. Instructions-for-use claims, the models covered by test reports, the scope of application 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 product is safe, effective and traceable for its intended use, not on how many documents a company has uploaded.

Common Mistakes

  • Treating registration as a simple document submission without first clarifying product classification, evidence coverage and local responsibility relationships.
  • Translating domestic NMPA documentation and submitting it directly, without reorganising the evidence according to the target market route.
  • Listing too many models and specifications while test reports, clinical evidence or labels do not cover them adequately.
  • Selecting a local agent purely on the basis of sales cooperation, without defining regulatory responsibility, certificate control and post-market maintenance duties.
  • Inconsistency between labels, instructions for use, promotional materials and registration claims, leading to deficiency letters or post-market compliance risk.
  • Failing to plan multi-country documentation reuse in advance, so that each country requires separate preparation and both cost and timelines are multiplied.

Preparation Checklist for Manufacturers

Before starting a project, companies are advised to confirm their documentation base using an internal checklist, so that critical evidence gaps are not discovered only after filing.

  • Compile the target product list, model and specification matrix, and intended use statements.
  • Check 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 instructions for use.
  • Confirm the duties, fees, certificate control and exit mechanism of the local agent or authorized representative.
  • Build a target-country gap assessment table identifying what needs additional testing, translation, notarisation or supplementary declarations.

AIMEILI View

AIMEILI advises manufacturers not to treat target market 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 per country is usually faster, more stable and more conducive to later variations and renewals than filling documentation gaps country by country on an ad hoc basis.

From a project management perspective, three things should be controlled in advance: first, product classification and route determination; second, consistency of the documentation evidence chain; third, the regulatory responsibility boundary of the local partner. If these three points are unclear, the project may still go back and forth during deficiency responses, agent communication and post-market maintenance, no matter how extensive the documentation appears.

Frequently Asked Questions

Can domestic documentation be used directly for target market registration?

Domestic documentation can serve as a starting point, but it usually cannot be submitted as is. Companies need to adjust the documentation structure, language, labelling, authorisation documents and evidence chain according to local regulatory requirements.

When is the best time to start a gap assessment?

It should start as soon as the target markets and product list are confirmed. 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, variations, renewals and post-market event handling. Unclear responsibilities affect certificate control and the stability of the market afterwards.

Project Execution Recommendations

When executing this type of registration project, companies should keep a project register that manages the product list, model and specification details, registration route, document owners, translation status, testing status, local agent communication records and estimated submission dates in a single table. This makes documentation gaps visible early and helps management judge whether the project will affect the launch plan.

Companies that already have registrations in multiple countries should also build an evidence reuse matrix defining which documents can serve as core evidence and which must be reissued or supplemented with explanations for specific countries. Labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must be kept at consistent versions.

  • Confirm target markets and product list.
  • Complete risk classification and route determination.
  • Build a documentation gap assessment table.
  • Define the local agent arrangement 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 registration review perspective, quality system documentation is not an isolated certificate. Regulators generally 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 products being filed, or if the manufacturing site, model and specification details or instructions-for-use version do not align with the test reports, additional explanations may be requested even when a large volume of documents has been prepared.

Before filing, companies should prepare an evidence consistency checklist that maps product name, model and specification, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label and instructions-for-use version, and quality system certificates item by item. This looks like a basic step, but it noticeably reduces the probability of deficiency letters, particularly for projects filed simultaneously in several GHWP member states or covering multiple product families.

Localisation and Authorized Representative Responsibilities

Target market registration projects usually involve local agent, authorized representative, importer or registration holder arrangements. 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, variation applications and renewal reminders. Different responsibility boundaries directly affect certificate control and the subsequent stability of the market.

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 localisation is converting reusable evidence into a filing structure acceptable to the target country, not writing a separate set of isolated documents.

Post-Market Maintenance and Long-Term Planning

Completing registration does not mark the end of compliance work. Companies also need to maintain certificate validity periods, change records, distributor authorisations, complaint handling, adverse event reporting, recall processes, label versions and regulatory update records. Many companies invest heavily in the approval stage but neglect post-market maintenance, so once a manufacturing site change, model extension, instructions-for-use update or agent replacement occurs, certificates can easily fall out of step with actual market sales.

AIMEILI recommends managing this question within an annual international registration plan: first set 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 doing this is not only higher registration efficiency in a single country; more importantly, it lets a company build a repeatable compliance capability for going global and reduces the cost of starting documentation from scratch each time it enters a new market.

Related Reading

  • Previous: How Should a Local Agent for Medical Device Registration in Malaysia Be Selected?
  • Next: Why Does the Medical Device Registration Timeline in Malaysia Get Extended?
  • How Should Documentation for Medical Device Registration in Malaysia Be Prepared?
  • How Is Product Classification Determined for Medical Device Registration in Malaysia?
  • How Should the Technical File for Medical Device Registration in Malaysia Be Organised?
  • How Should Labels and Instructions for Use Be Localised for Medical Device Registration in Malaysia?
  • How Should Clinical Evaluation Documentation for Medical Device Registration in Malaysia Be Prepared?
  • Can Test Reports Be Reused for Medical Device Registration in Malaysia?
  • Return to the FAQ Centre
  • News and Insights
  • Contact AIMEILI

Content Review and Scope

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 organisations, standards bodies and publicly available regulatory materials; industry media and project experience are used only as supporting references.

Scope: this article supports preliminary understanding, documentation preparation and project planning. It does not replace the formal requirements of the target country's regulatory authority, test conclusions or legal advice.

Source and Language Notice

View Chinese original page

Related Reading

Need a registration pathway assessment?

Send product type, intended use, target countries and existing certificates. AIMEILI can help evaluate registration pathway, documentation gaps and compliance risks.

Contact AIMEILI