Common Reasons for Deficiency Letters in Malaysian MDA Medical Device Registration: FAQ for Manufacturers and Regulatory Teams

Short answer: A deficiency letter from Malaysia's Medical Device Authority (MDA) — a request for correction or supplementary information issued during product registration — most often results from one or more of the following causes: the product has been assigned the wrong risk class or registration route; the technical file is incomplete or not structured to MDA requirements; the ISO 13485 certificate does not cover the manufacturing site, product family or declared models; performance verification, risk management (ISO 14971) or clinical evaluation/clinical evidence is insufficient or inconsistent with the intended use; labels and instructions for use do not meet local language, claim or labelling requirements; authorization documents such as the letter of authorization, manufacturer's declaration or existing certificates are missing, incomplete or outdated; or the role, licence status and regulatory responsibilities of the local representative/authorized representative are not clearly defined. The most effective mitigation is to complete a product classification and dossier gap assessment before submission, and to decide in advance how existing NMPA, CE, FDA or other market documents will be reused and localized for Malaysia.

Published: 10 July 2026, 09:55  |  Updated: 10 July 2026, 09:55

Key summary

MDA medical device registration dossiers in Malaysia are normally prepared around product classification, technical documentation, ISO 13485 quality system evidence, performance verification, risk management, clinical evaluation or clinical evidence, labelling and instructions for use, authorization documents, and the appointment of a local representative. Companies should first carry out a dossier gap assessment and only then determine whether existing NMPA, CE or other market documents can be reused.

For Chinese medical device manufacturers, the more reliable approach is to confirm product classification and complete a dossier gap assessment first, and then decide whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused. Registration in a target market typically affects the technical file, authorized representative arrangements, importer cooperation, label language, quality system evidence and subsequent change maintenance at the same time. If a project is managed only by asking "which documents must be submitted", correction requests and rework are likely to arise in model coverage, evidence chain consistency, label claims and certificate control. AIMEILI recommends positioning 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 the dossier from scratch for each country.

Applicable scenarios and core questions

Companies searching for "common reasons for deficiency letters in Malaysian medical device registration" are usually not looking for a conceptual explanation. They need to judge whether their existing documentation can support a submission in the target market, whether a local agent or authorized representative is required, why the timeline is being extended, and which issues may affect the launch plan. This question typically involves product classification, registration route, evidence chain, label localization and post-market maintenance responsibilities at the same time.

If a company plans to enter several GHWP member states or multiple markets in Southeast Asia, the Middle East and Latin America simultaneously, answering the procedure for one country alone is not sufficient. A more valuable approach is to first produce reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labelling/instructions for use, and then localize them in line with each country's regulatory requirements.

Registration decision logic

Companies should first confirm the intended purpose, mechanism of action, use scenario, body contact, duration of use, sterility, whether the device is active, and whether it contains software or has IVD characteristics, and then determine the risk class and submission route. If the route is judged incorrectly, all subsequent translation, notarization, authorization, testing and supplementary documentation will move in the wrong direction.

For a target market 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 issues are only handled vaguely in a commercial contract, market control may be affected later.

Dossiers and evidence

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

The key to dossier quality is not volume but consistency. IFU claims, the model coverage of test reports, the applicable scope of clinical evidence, the conclusions of the risk management file, label warnings and the information in the registration application must support one another. Regulators focus on whether the device is safe, effective and traceable for its intended use — not on how many documents have been uploaded.

Common deficiencies and errors

• Treating registration as a simple document submission without first clarifying product classification, evidence coverage and local responsibility arrangements.
• Translating NMPA dossiers directly and submitting them as they are, without reorganizing the evidence according to the target market route.
• Declaring too many models and specifications while test reports, clinical evidence or labelling do not cover the full range.
• Appointing a local agent purely on the basis of sales cooperation, without defining regulatory responsibility, certificate control and post-market maintenance obligations.
• Inconsistency between labels, IFUs, promotional material and registration dossier claims, leading to deficiency letters or post-market compliance risk.
• Failing to plan multi-country document reuse in advance, resulting in duplicated preparation for each country and multiplied cost and timelines.

Company preparation checklist

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

• Compile the target product list, model and specification matrix, and intended purpose 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-language instructions for use.
• Confirm the responsibilities, fees, certificate control and exit mechanisms of the local agent or authorized representative.
• Establish a target-country gap assessment table identifying what must be re-tested, translated, notarized or supported by additional declarations.

AIMEILI viewpoint

AIMEILI recommends that companies do not treat target-market registration as a one-off document submission, but 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 usually faster, more stable and more beneficial for subsequent changes and renewals than supplementing documents on a country-by-country, 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 dossier evidence chain; third, the regulatory responsibility boundaries of the local partner. 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 dossier appears substantial.

Frequently asked questions

Can domestic (NMPA) documentation be used directly for target-market registration?

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

When is the best time to start a gap assessment?

It is recommended to start immediately after confirming the target markets and product list. The earlier the gap assessment is completed, the easier it is to arrange supplementary testing, translation, label adaptation 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. Unclear responsibilities and rights can affect certificate control and the stability of the market after approval.

Practical recommendations for project execution

When executing this type of registration project, companies should maintain a project register that manages the product list, model and specification matrix, registration route, document owners, translation status, testing status, local agent communication records and expected submission dates in a single table. This makes it easier to identify documentation gaps in time and enables management to judge whether the project will affect the launch plan.

For companies that already have registrations in several countries, an evidence reuse matrix should also be established, clarifying which documents can serve as core evidence and which must be reissued or supplemented for specific countries. In particular, labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates must remain version-consistent.

• Confirm the target markets and product list.
• Complete risk classification and route determination.
• Establish the dossier gap assessment table.
• Define the local agent and certificate control arrangements.
• Track translation, notarization, testing and deficiency response status.
• Plan 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 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 registered, or if the manufacturing site, model specifications or IFU version do not match the test reports, additional clarification may be requested even when a large volume of documentation has been prepared.

Companies should establish an evidence consistency checklist before submission, mapping product name, model and specification, intended purpose, 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 simultaneous submissions in several GHWP member states or for multiple product families.

Localization and local representative responsibilities

Target-market 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 for regulatory communication, certificate maintenance, post-market event reporting, change applications and renewal reminders. Different responsibility boundaries directly affect certificate control and market stability after approval.

Labelling, 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, isolated set of documents.

Post-market maintenance and long-term planning

Registration approval does not mean compliance work has ended. 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 approval but neglect post-market maintenance; when a manufacturing site change, model extension, IFU update or agent replacement occurs later, the certificate and market sales can easily 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 country gap list, and finally schedule submission, deficiency response, post-market maintenance and renewal milestones. The value is not only improved registration efficiency in a single country, but the development of a repeatable overseas compliance capability, reducing the cost of starting from zero each time a new market is entered.

Related reading

• Previous: Why do Malaysian medical device registration timelines get extended?
• Next: How should post-market surveillance be handled for Malaysian medical device registration?
• Recommended: How should documentation be prepared for Malaysian medical device registration?
• Recommended: How is product classification determined for Malaysian medical device registration?
• Recommended: How should the technical file be organized for Malaysian medical device registration?
• Recommended: How are labels and instructions for use localized for Malaysian medical device registration?
• Recommended: How should clinical evaluation documentation be prepared for Malaysian medical device registration?
• Recommended: Can test reports be reused for Malaysian medical device registration?

Content review and scope of application

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

Source 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.

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