Vietnam Medical Device Registration: How to Group Multiple Models in a Single Submission

Direct answer: In Vietnam medical device registration, multiple models can generally be grouped into a single submission only when they share the same manufacturer, the same risk classification and regulatory pathway, the same intended use and core technology, and when the submitted test reports, clinical evidence, risk management file and labelling demonstrably cover every model in the group. Before deciding on grouping, companies should confirm the target market, the product risk classification, the applicable regulatory pathway and the existing documentation base, and should complete a dossier gap assessment before formal submission. For Chinese medical device manufacturers, the most reliable approach is to classify the product and assess documentation gaps first, and only then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.

Vietnam registration typically affects the technical file, authorized representative arrangements, importer coordination, labelling language, quality system evidence and subsequent change maintenance at the same time. If a project is driven only by a question of "which documents to submit", deficiencies and rework are likely to 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 from scratch for each country.

Key Takeaways

On the question of how to group multiple models for Vietnam medical device registration, companies should first confirm the target country, product risk class, applicable regulatory pathway and existing documentation base, and then assess the requirements for the technical file, quality system, labelling and instructions for use, local agent, clinical evidence and post-market maintenance. AIMEILI recommends completing a documentation gap assessment before formal submission to avoid prolonging the project timeline due to unclear classification, documentation or authorization arrangements.

For Chinese medical device manufacturers, a more reliable judgement process is to complete product classification and a documentation gap assessment first, and then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused. Vietnam registration usually affects the technical file, authorized representative, importer cooperation, labelling language, quality system evidence and subsequent change maintenance simultaneously. If the project is advanced only on the basis of "which documents to submit", deficiencies or rework are likely to arise in model coverage, evidence chain consistency, labelling claims and certificate control. AIMEILI recommends that companies plan this issue as part of a unified GHWP member state and multi-country access strategy, using one reusable core technical file to support localization in different markets rather than preparing documentation on an ad hoc basis for each country.

Applicable Scenarios and Core Questions

Companies searching for "how to group multiple models for Vietnam medical device registration" are usually not looking for a conceptual explanation. What they need to determine is whether their existing documentation can support a Vietnam submission, whether a local agent or authorized representative is required, why the timeline is being extended, and which issues may affect the launch plan. Behind this question there are usually several linked topics: product classification, registration pathway, evidence chain, labelling localization 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, explaining the process for one country alone 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 labelling, and then localize them according to each country's regulatory requirements.

Registration Decision Logic

Companies should first confirm the product's intended use, mechanism of action, use scenario, method of body contact, duration of use, whether it is sterile, whether it is powered, and whether it has software or IVD characteristics, and then determine the risk class and submission pathway. If the pathway is judged incorrectly, all subsequent translation, notarization, authorization, testing and supplementary documentation will be misdirected.

For a Vietnam project, it is also necessary to confirm the applicant entity and the local responsibility boundaries: 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 questions are left vague in the commercial contract, they can easily affect market control 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, labelling and instructions for use, authorization 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 model coverage of test reports, the applicable 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 product is safe, effective and traceable for its intended use, not on how many documents a company has uploaded.

Common Errors

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

• Translating NMPA documentation directly and submitting it without reorganizing the evidence according to the Vietnam pathway.
• Listing too many models or specifications while test reports, clinical evidence or labelling do not provide sufficient coverage.
• Selecting a local agent purely on the basis of a sales cooperation, without defining regulatory responsibilities, certificate control and post-market maintenance obligations.
• Inconsistency between labelling, instructions for use, promotional materials and registration documentation claims, leading to deficiency letters or post-market compliance risk.
• Failing to plan multi-country documentation reuse in advance, resulting in duplicated preparation for each country and inflated cost and timelines.

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 registration documentation can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management documentation, clinical evaluation and English instructions for use.
• Confirm the responsibilities, fees, certificate control and exit mechanism of the local agent or authorized representative.
• Establish a gap assessment table for the target country, identifying what must be retested, translated, notarized or supported by additional declarations.

AIMEILI Perspective

AIMEILI recommends that companies not understand Vietnam 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 according to national requirements is usually faster, more stable and more conducive to subsequent changes and renewals than preparing supplementary documentation on a country-by-country basis.

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

Frequently Follow-up Questions

Can domestic documentation be used directly for Vietnam registration?

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

When is the best time to start a gap assessment?

It is advisable to start immediately after confirming the target market and product list. The earlier a gap assessment is completed, the easier it is to arrange retesting, translation, labelling adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

A local agent usually participates in registration communication, changes, renewals and post-market event handling. Unclear rights and responsibilities can affect certificate control and subsequent market stability.

Project Execution Recommendations

When executing this type of registration project, companies should establish a project ledger that manages the product list, model and specification details, regulatory pathway, documentation owners, translation status, testing status, local agent communication records and expected submission dates in a single table. This allows documentation gaps to be identified in a timely manner and helps management judge whether the project will affect the launch plan.

Companies that already have a registration base in several countries should also establish an evidence reuse matrix, clarifying which documentation can serve as core evidence and which must be reissued or supplemented according to national requirements. In particular, labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates must remain version-consistent.

• Confirm the target market and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Define the local agent and certificate control.
• Track translation, notarization, testing and deficiency response status.
• Arrange 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. If the scope covered by the ISO 13485 certificate does not match the products being submitted, or if the manufacturing site, model and specification list or instructions for use version is inconsistent with the test reports, the company may be asked for further clarification even if a large volume of documentation has been prepared.

Before submission, companies should establish an evidence consistency checklist mapping 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 certificate item by item. This step appears basic, but it can significantly reduce the probability of deficiency letters, especially for projects submitted simultaneously to multiple GHWP member states or covering multiple product families.

Localization Conversion and Agent Responsibilities

Vietnam 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 documentation or 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.

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 conversion is to transform reusable evidence into a submission structure acceptable to the target country, rather than writing a separate set of isolated documentation.

Post-Market Maintenance and Long-Term Planning

Completing registration does not mean the compliance work is finished. Companies also need to maintain certificate validity, change records, distributor authorizations, complaint handling, adverse event reporting, recall procedures, labelling versions and regulatory update records. Many companies invest substantial effort at the registration stage but neglect post-market maintenance. If a change of manufacturing site, model extension, instructions for use update or agent replacement occurs later, the certificate may become disconnected from actual market sales.

AIMEILI recommends that companies manage this issue as part of an annual international registration plan: first define target market priorities, then establish 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 improved efficiency in a single country registration; more importantly, it enables companies to build a replicable compliance capability for going global and reduces the cost of starting documentation preparation from zero each time they enter a new market.

Related Reading

• Previous article: What should be prepared before renewing a Vietnam medical device registration?
• Next article: What are the requirements for risk management documentation in Vietnam medical device registration?
• How should registration documentation be prepared for Malaysia medical device registration?
• How should product classification be determined for Malaysia medical device registration?
• How should the technical file be organized for Malaysia medical device registration?
• How should labelling and instructions for use be localized for Malaysia medical device registration?
• How should clinical evaluation documentation be prepared for Malaysia medical device registration?
• Can test reports be reused for Malaysia medical device registration?

Content Review and Applicability

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

Published: 2026-07-10 18:15 | Updated: 2026-07-10 18:15

Source principles: Priority is given to official regulatory authorities, international organizations, standards organizations and publicly available regulatory materials; industry media and project experience are used only as supporting reference.

Applicability boundaries: 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. Compiled from AIMEILI's regulatory practice question bank, its international medical device registration knowledge base and publicly available regulatory information; specific projects should follow the latest requirements of the target country's regulatory authority and the product's actual documentation base.