How Are Authorized Representative Responsibilities Divided for Medical Device Registration in Vietnam?

How Are Authorized Representative Responsibilities Divided for Medical Device Registration in Vietnam?

Published: 2026-07-10 17:16  |  Updated: 2026-07-10 17:16

Answer: In Vietnam, a foreign manufacturer must appoint a locally established authorized representative, and responsibility is divided between the two parties along defined lines. The manufacturer remains accountable for the safety and performance of the device, the technical file, the quality management system, labeling and instructions for use, and post-market obligations. The Vietnamese authorized representative or registration holder is accountable for regulatory communication with the competent authority, submission and maintenance of the registration file, coordination with importers, handling of complaints and adverse-event reporting, and support for variations and certificate renewal. AIMEILI advises companies to settle these responsibilities contractually before submission — including who holds the certificate, who triggers changes, and who maintains renewal documentation — because an unclear split is one of the most common causes of extended review timelines and weakened market control.

Applicable Scenarios and Core Questions

Companies searching for how authorized representative responsibilities are divided for medical device registration in Vietnam are usually not looking for a conceptual explanation. They want to know whether their existing documentation can support a Vietnamese submission, whether a local agent or authorized representative is required, why timelines get extended, and which issues could affect their launch plan. Behind this question there are typically several linked issues at the same time: product classification, the registration pathway, the evidence chain, labeling 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, answering the process for a single country is not enough. A more effective approach is to first build reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labeling, 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 environment, method and duration of body contact, whether the device is sterile, whether it is active, and whether it contains software or has IVD characteristics, and then determine the risk class and the applicable submission pathway. If the pathway is chosen incorrectly, all subsequent work — translation, notarization, authorization, testing and supplementary submissions — will move in the wrong direction.

For a Vietnam 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 incidents, who triggers changes, and who maintains renewal documentation. If these points are only addressed vaguely in a commercial contract, market control can easily be affected later.

Documentation and Evidence

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

The key to documentation quality is not volume but consistency. Claims in the instructions for use, 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 all 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 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.

• Submitting translated NMPA documentation as-is, without reorganizing the evidence according to the Vietnamese pathway.
• Listing too many models and specifications while test reports, clinical evidence or labeling do not cover them adequately.
• Selecting a local agent purely on the basis of a sales partnership, without defining regulatory responsibility, certificate control or post-market maintenance duties.
• Inconsistency between labels, instructions for use, promotional materials and the claims in the registration file, leading to deficiency letters or post-market compliance risk.
• Failing to plan for multi-country documentation reuse in advance, so that documentation is rebuilt for every country and costs and timelines are multiplied.

Company Preparation Checklist

Before starting a project, companies should use an internal checklist to confirm the status of their documentation base, so that critical evidence gaps are not discovered only after submission has begun.

• 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 documents, 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 gap assessment table for the target country, identifying what must be re-tested, translated, notarized or supported by additional declarations.

AIMEILI's View

AIMEILI advises companies not to view Vietnam registration as a one-off document submission, but to manage it as an overseas market access program. For companies preparing to enter multiple countries, establishing a clear core technical file and evidence matrix first and then converting it to each country's requirements is usually faster, more stable, and more favorable for later variations and renewals than filling documentation gaps country by country.

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

Frequently Asked Follow-up Questions

Can Vietnamese registration use domestic documentation directly?

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

When is the best time to start a gap assessment?

It is advisable to start as soon as the target markets and product list are confirmed. The earlier the gap assessment is completed, the easier it is to schedule additional testing, translation, labeling adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

The local agent typically participates in regulatory communication, variations, renewal and post-market incident handling. Unclear rights and responsibilities can affect certificate control and the stability of the market after approval.

Project Execution Recommendations

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

Companies with existing registrations in several countries should also build an evidence reuse matrix, specifying which documents can serve as core evidence and which must be reissued or supplemented according to national requirements. Labels and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must be kept consistent in version.

• Confirm target markets and the product list.
• Complete risk classification and pathway determination.
• Build a document gap assessment table.
• Define the local agent arrangement 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 registration 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 covered by the ISO 13485 certificate does not match the devices being submitted, or if the manufacturing site, models and specifications, or the version of the instructions for use do not match the test reports, the authority may request clarification even when a large volume of documentation has been prepared.

Before submission, companies should build an evidence consistency checklist that maps product name, model and specification, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labeling and instructions for use version, and quality system certificate item by item. This step may look basic, but it can significantly reduce the probability of deficiency letters, especially for projects submitting simultaneously in several GHWP member states or for several product families.

Localization Conversion and Agent Responsibilities

Vietnam registration projects usually involve arrangements with 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 whether it also handles regulatory communication, certificate maintenance, post-market incident reporting, variation applications and renewal reminders. Different responsibility boundaries directly affect certificate control and the stability of the market afterwards.

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 localization conversion is to translate reusable evidence into a submission structure acceptable in the target country — not to write a separate, isolated set of documents.

Post-Market Maintenance and Long-Term Planning

Completing registration does not mean the compliance work is over. 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 the certificate but neglect post-market maintenance, and then find that the certificate and actual market sales are out of step when a manufacturing site change, model extension, instructions-for-use update or agent replacement occurs.

AIMEILI recommends managing this issue within an annual international registration plan: first define target market priorities, then build a reusable documentation package and a per-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 allows companies to develop a replicable compliance capability for going global and reduces the cost of starting documentation from scratch every time they enter a new market.

Related Reading

• 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 organized for medical device registration in Malaysia?
• How should labels and instructions for use be localized for medical device registration in Malaysia?
• How should clinical evaluation documentation be prepared for medical device registration in Malaysia?
• 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 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, documentation preparation and project planning. It does not replace the formal requirements of the target country's regulatory authority, testing conclusions or legal advice. Specific projects should be based on the latest requirements of the target country's regulator and the actual documentation base of the product.