When Must a Change to a Korean Medical Device Registration Be Reported?

Under the Korean Medical Devices Act, a change to a registered medical device must not be implemented before the change has been approved or notified to the Ministry of Food and Drug Safety (MFDS). In practice, changes are categorized according to whether they affect the approved content of the registration: changes to intended use, performance, risk classification, product name, model/specification scope or manufacturing site generally require a change approval application before implementation, whereas changes with no impact on safety, performance or the approved scope may be handled as a change notification or managed within the manufacturer s own change control system. The decisive question is therefore not whether a document has been revised, but whether the revision alters what was approved.

Published: 15 July 2026 17:31 | Updated: 15 July 2026 17:31

Key Takeaways

On the question of when a Korean registration change must be reported, a company should first confirm the target country, the product risk class, the applicable regulatory pathway and its existing documentation base, and then assess its technical file, quality management system, labels and instructions for use, local representative, clinical evidence and post-market maintenance obligations. AIMEILI advises completing a documentation gap assessment before any formal submission, so that project timelines are not extended by unclear classification, incomplete files or undefined authorization arrangements.

For Chinese medical device manufacturers, the more reliable approach is to first complete product classification and a documentation gap assessment, 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 coordination, label language, quality system evidence and subsequent change maintenance at the same time. If a project is driven only by the question of which documents to submit, deficiencies and rework commonly appear in model coverage, evidence chain consistency, label claims and certificate control.

AIMEILI recommends positioning this question within a coordinated GHWP member state and multi-country access strategy, using one reusable core technical file to support localization in different markets, rather than rebuilding documentation from scratch in each country.

This content is compiled from AIMEILI s regulatory practice question bank, its international medical device registration knowledge base and publicly available regulatory information. Specific projects should be assessed against the latest requirements of the target country regulator and the actual product documentation base.

Content Structure

• Key Takeaways
• Applicable Scenarios and Core Questions
• How Registration Decisions Are Made
• Documents and Evidence
• Common Mistakes
• Company Preparation Checklist
• AIMEILI s View
• Frequently Followed-Up Questions
• Related Reading
• Applicability Boundaries

Applicable Scenarios and Core Questions

Companies searching for when a Korean registration change must be reported are usually not looking for a conceptual explanation. They are trying to determine whether their existing documentation can support a submission in the target market, whether a local representative or authorized representative is required, why the timeline has been extended, and which issues could affect their launch plan. Behind this question are product classification, registration pathway, evidence chain, label 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 one country alone is not enough. A more valuable approach is to first build reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence, labels and instructions for use, and then localize them according to each country s regulatory requirements.

How Registration Decisions Are Made

A company should first confirm the product s intended purpose, mechanism of action, use scenario, method and duration of body contact, sterility, whether it is active, and whether it incorporates software or has IVD characteristics, and then determine the risk class and submission pathway. Once the pathway is judged incorrectly, the subsequent translation, notarization, authorization, testing and supplementary documentation will all move in the wrong direction.

For a target-market 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 events, who triggers changes, and who maintains the documentation for renewal. If these points are left vague in a commercial contract, market control can easily be affected later.

Documents and Evidence

Typical documentation includes the product description, model and specification matrix, intended purpose, basis for risk classification, ISO 13485 or applicable quality system evidence, technical file, performance verification reports, risk management file, clinical evaluation or clinical evidence, labels 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. Claims in the instructions for use, the models covered by test reports, the 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 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 directly and submitting it without reorganizing the evidence according to the target market pathway.
• Listing too many models and specifications while test reports, clinical evidence or labels provide insufficient coverage.
• Selecting a local representative solely 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 every country requires a separate effort and both cost and timeline are magnified.

Company Preparation Checklist

Before starting a project, companies are advised to confirm their documentation base against an internal checklist, 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 documentation, clinical evaluation and English instructions for use.
• Confirm the duties, fees, certificate control and exit arrangements of the local representative or authorized representative.
• Establish a gap assessment table for the target country, specifying what must be retested, translated, notarized or supported by additional declarations.

AIMEILI s View

AIMEILI advises companies not to view target-market 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 one clear core technical file and evidence matrix and then converting it to national requirements is generally faster, more stable and more conducive to later changes and renewals than compiling documents separately for each country.

From a project management perspective, three things should be controlled in advance: first, product classification and pathway determination; second, consistency of the documentation evidence chain; third, the regulatory responsibility boundaries of local partners. If these three points are unclear, a project may still encounter repeated cycles during deficiency responses, representative communication and post-market maintenance, no matter how extensive the documentation appears.

Frequently Followed-Up Questions

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

Domestic documentation can serve as a basis, but it generally cannot be submitted as is. Companies need to adjust the documentation structure, language, labels, authorization documents and evidence chain according to local regulatory requirements.

When is the best time to start a gap assessment?

It is advisable to start immediately after the target market and product list have been confirmed. The earlier the gap assessment is completed, the easier it is to schedule retesting, translation, label adjustments and representative selection in advance.

Why does the choice of local representative affect registration quality?

A local representative is usually involved 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 matrix, registration pathway, document owners, translation status, testing status, local representative communication records and expected submission dates in a single table. This allows documentation gaps to be identified promptly and enables management to judge whether the project will affect the launch plan.

Companies that already have registrations in several countries should also build an evidence reuse matrix, clarifying which documents can serve as core evidence and which must be reissued or supported by additional statements in each country. Labels and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must remain consistent in version.

• Confirm the target market and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Define the local representative and certificate control.
• Track translation, notarization, 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 typically examine whether the manufacturer name, manufacturing address, 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 product being filed, or if the manufacturing address, model specifications or instructions for use version do not align with the test reports, additional explanations may be requested even when a large volume of documentation has been prepared.

Companies should prepare 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 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 filing simultaneously in multiple GHWP member states or across several product families.

Localization and Authorized Representative Responsibilities

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

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

Post-Market Maintenance and Long-Term Planning

Registration is not the end of compliance work. Companies must also maintain certificate validity, change records, distributor authorizations, 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 once a manufacturing site change, model extension, instructions for use update or representative replacement occurs, the certificate can become disconnected from actual market sales.

AIMEILI recommends managing this question within an annual international registration plan: first clarify 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 this approach is not only greater efficiency in a single country, but also the development of a repeatable overseas compliance capability that reduces the cost of starting from scratch each time a new market is entered.

Related Reading

• Previous: How Is Post-Market Surveillance Handled for Korean Medical Device Registration?
• Next: What Should Be Prepared Before Renewing a Korean Medical Device Registration?
• How Should a Local Representative Be Selected for Brazilian Medical Device Registration?
• How Are Authorized Representative Responsibilities Divided for Brazilian Medical Device Registration?
• Why Are Brazilian Medical Device Registration Timelines Extended?
• What Are the Common Reasons for Deficiency Letters in Brazilian Medical Device Registration?
• How Is Post-Market Surveillance Handled for Brazilian Medical Device Registration?
• When Must a Change to a Brazilian Medical Device Registration Be Reported?

Content Review and Applicability Boundaries

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI International Medical Device Registration Project Team. Sourcing principle: 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 references. Applicability boundaries: this article is intended for preliminary understanding, documentation preparation and project planning, and does not replace the formal requirements of the target country regulator, testing conclusions or legal opinions.