How Are Multiple Models Grouped in a Medical Device Registration Application in South Korea?

Quick Answer

For the question of how multiple models of a medical device should be grouped in a South Korean registration application, manufacturers should first confirm the target country, the product risk class, the applicable regulatory pathway and the documentation already available, and only then assess the technical file, quality system evidence, labelling and instructions for use, in-country representative arrangements, clinical evidence and post-market maintenance obligations. AIMEILI recommends completing a documentation gap assessment before formal submission, so that unclear classification, missing documentation or undefined authorisation arrangements do not extend the project timeline. For Chinese medical device manufacturers, the more reliable approach 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.

Published: 15 July 2026, 17:46 | Updated: 15 July 2026, 17:46

Key Takeaways

Registration in a target market usually affects the technical file, authorised representative arrangements, 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 must be submitted, deficiency letters and rework are likely to arise in the areas of model coverage, evidence-chain consistency, label claims and certificate control.

AIMEILI recommends that manufacturers position this question within a broader GHWP member state and multi-country market access strategy, using one reusable core technical file to support localisation in different markets, rather than re-preparing documentation from scratch country by country.

This article is compiled from the AIMEILI regulatory practice question bank, the medical device international registration knowledge base and publicly available regulatory information. Individual projects should be based on the latest requirements of the target-country regulator and the manufacturer's existing documentation base.

Applicable Scenarios and Core Questions

Companies searching for how multiple models of a medical device should be grouped in a South Korean registration application are usually not looking for a conceptual explanation. They want to know whether their existing documentation can support an application in the target market, whether a local agent or authorised representative is needed, why timelines become extended, and which issues may affect the launch plan. Behind this question there are typically several linked topics: product classification, registration pathway, evidence chain, label localisation and post-market maintenance responsibility.

If a manufacturer plans to enter several GHWP member states at the same time, or markets in Southeast Asia, the Middle East and Latin America, answering the process for a single country is not sufficient. A more valuable approach is to first prepare reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labelling and instructions for use, and then localise them according to each country's regulatory requirements.

Registration Assessment Logic

Manufacturers should first confirm the intended use, mechanism of action, use scenario, mode of body contact, duration of use, 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 submission pathway. If the pathway is misjudged, all downstream translation, notarisation, authorisation, testing and supplementary submissions will follow 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 import and post-market events, who triggers changes, and who maintains renewal documentation. If these points are left vague in a commercial contract, control over the market can be compromised at a later stage.

Documentation and Evidence

Typical documentation includes the device 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, authorisation documents, existing registration certificates, manufacturer's declarations and post-market surveillance documentation.

The key to documentation quality is not volume but consistency. IFU claims, the models covered by 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. What regulators assess is whether the device is safe, effective and traceable for its intended use, not how many documents have been uploaded.

Common Errors

• Treating registration as a simple document submission without first clarifying product classification, evidence coverage and local responsibility relationships.
• Translating NMPA documentation directly and submitting it without restructuring the evidence according to the target-market pathway.
• Listing too many models and specifications while test reports, clinical evidence or labelling do not provide adequate coverage.
• Selecting a local agent solely on the basis of sales cooperation, without defining regulatory responsibility, certificate control and post-market maintenance obligations.
• 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 preparation is repeated in every country and both cost and timelines are magnified.

Manufacturer Preparation Checklist

Before starting a project, manufacturers 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 statement.
• 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 responsibilities, fees, certificate control and exit arrangements of the local agent or authorised representative.
• Build a target-country gap assessment table specifying which items require additional testing, translation, notarisation or supplementary declarations.

AIMEILI's Perspective

AIMEILI advises manufacturers not to view 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 to national requirements is usually faster, more stable and more conducive to later changes and renewals than preparing documents country by country on an ad hoc basis.

From a project management perspective, three items should be controlled in advance: first, product classification and pathway determination; second, the consistency of the documentation evidence chain; third, the boundaries of regulatory responsibility of local partners. If these three items are unclear, a project may still face repeated requests for supplementation, agent communication issues and post-market maintenance problems, even when the documentation appears extensive.

Frequently Asked Questions

Can NMPA documentation be used directly for registration in the target market?

NMPA documentation can serve as a basis but generally cannot be submitted as it stands. Manufacturers need to adjust the document structure, language, labelling, authorisation documents and evidence chain in accordance with local regulatory requirements.

When is the best time to start a gap assessment?

Immediately after the target market and product list have been confirmed. The earlier the gap assessment is completed, the easier it is to schedule additional testing, translation, label adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

The local agent usually participates in regulatory communication, changes, renewals and post-market event handling. Unclear allocation of responsibilities and rights will affect certificate control and the stability of the market after approval.

Project Execution Recommendations

When executing this type of registration project, manufacturers should establish a project register that manages the product list, model specifications, registration pathway, document owners, translation status, testing status, records of communication with the local agent 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.

For manufacturers that already have registration bases in several countries, an evidence reuse matrix should also be established, defining which documents can serve as core evidence and which must be re-issued or supplemented according to national requirements. Labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must be kept at consistent versions.

• Confirm the target market and product list.
• Complete risk classification and pathway determination.
• Build the documentation gap assessment table.
• Define the local agent role 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 address, product scope, certificate validity period, applicable standards and technical file are consistent with one another. If the scope of the ISO 13485 certificate does not match the device being submitted, or if the manufacturing address, model specifications or IFU version are inconsistent with the test reports, the manufacturer may be asked for supplementary clarification even when a large volume of documentation has been prepared.

Before submission, manufacturers should establish an evidence consistency checklist that maps the product name, model specifications, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label and IFU version, and quality system certificate item by item. This appears basic, but it significantly reduces the likelihood of deficiency letters, particularly for projects covering several GHWP member states or several product families submitted at the same time.

Localisation and Local Representative Responsibilities

Target-market registration projects usually involve arrangements with a local agent, authorised representative, importer or registration holder. Manufacturers need to confirm in advance whether the local partner is responsible only for submitting documentation, or also for regulatory communication, certificate maintenance, post-market event reporting, change applications and renewal reminders. Different boundaries of responsibility directly affect certificate control and the stability of the market after approval.

Labelling, instructions for use and authorisation documents also cannot simply be translated. Manufacturers should verify local language requirements, the boundaries of product claims, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorised representative information and after-sales contact details. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localisation is to convert reusable evidence into an application structure acceptable in the target country, rather than to write an isolated set of new documents.

Post-Market Maintenance and Long-Term Planning

Approval does not mean that compliance work has ended. Manufacturers must also maintain certificate validity periods, change records, distributor authorisations, 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 a change of manufacturing address, extension of models, update of instructions for use or replacement of an agent can quickly create a disconnect between the certificate and actual market sales.

AIMEILI recommends managing this question within an annual international registration plan: define target market priorities first, then build a reusable documentation package and a country-specific 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 the development of a replicable overseas compliance capability that reduces the cost of rebuilding documentation from zero each time a new market is entered.

Content Review and Scope of Application

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

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

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 regulator, testing conclusions or legal advice.