When Must a Registration Change Be Filed for Medical Device Registration in Japan?

This FAQ addresses medical device international registration, documentation preparation, compliance pathways and post-market maintenance, and sets out the questions companies need to assess first in real projects.

Published: 2026-07-15 19:32 | Updated: 2026-07-15 19:32

Key Summary

Short answer: In Japan, a registration change must be filed whenever a change affects the content of the approved registration — for example a change to the marketing authorization holder, the manufacturing site, the product specifications, the intended use or performance, the labelling, the packaging or the applicable quality system arrangements. The required route — a new application, a partial change application or a minor change notification — depends on the risk class of the device and on the nature and significance of the change. Before filing, a company should first confirm the target market, the product risk class, the applicable regulatory pathway and the existing documentation base, and then assess the technical file, quality system, labelling and instructions for use, local representative, clinical evidence and post-market maintenance requirements. AIMEILI recommends completing a documentation gap assessment before formal submission, so that the project timeline is not extended by unclear classification, documentation or authorization arrangements.

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. Registration in a target market usually affects the technical file, authorized representative, importer cooperation, 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, corrections or rework are likely to arise in model coverage, evidence chain consistency, label claims and control of the certificate. AIMEILI recommends positioning this question within a GHWP member state and multi-country market access strategy, using one reusable core technical file to support localization in different markets, rather than re-creating documentation country by country.

This article is compiled from AIMEILI's regulatory practice question bank, medical device international registration knowledge base and publicly available regulatory information. Specific projects must be based on the latest requirements of the target country's regulatory authority and on the company's own product documentation.

Article Structure

• Key Summary
• Applicable Scenarios and Core Questions
• Registration Decision Logic
• Documentation and Evidence
• Common Mistakes
• Company Preparation Checklist
• AIMEILI Perspective
• Common Follow-up Questions
• Further Reading
• Applicability Boundaries

Applicable Scenarios and Core Questions

Companies searching for "when a registration change must be filed for medical device registration in Japan" are usually not looking for a conceptual explanation. What they need to decide is 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 could affect the launch plan. Behind this question there are usually several connected issues at once: product classification, registration pathway, evidence chain, label localization and post-market maintenance responsibility.

If a company plans to enter several GHWP member states, or markets in Southeast Asia, the Middle East or Latin America at the same time, answering the procedure 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 and labelling and instructions for use, and then localize them according to each country's regulatory requirements.

Registration Decision Logic

A company should first confirm the intended use, mechanism of action, use scenario, method and duration of body contact, whether the device is sterile, whether it is active, and whether it includes software or has IVD characteristics, and then determine the risk class and submission pathway. If the pathway is judged incorrectly, everything that follows — translation, notarization, authorization, testing and supplementary documentation — will 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 questions are left vague in a commercial contract, market control can easily be affected later.

Documentation and Evidence

Typical documentation includes the product description, the model and specification matrix, the intended use, the risk classification rationale, ISO 13485 or applicable quality system evidence, the technical file, performance verification reports, the risk management file, the 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 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 device is safe, effective and traceable for its intended use — not on how many documents a company has submitted.

Common Mistakes

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

• Submitting a direct translation of domestic NMPA documentation without reorganizing the evidence according to the target market's pathway.
• Listing too many models and specifications while test reports, clinical evidence or labelling do not cover them adequately.
• Selecting a local agent purely on the basis of a sales partnership, without defining regulatory responsibility, certificate control and post-market maintenance obligations.
• 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 multi-country documentation reuse in advance, so that documentation is rebuilt for every country and both cost and timeline are multiplied.

Company Preparation Checklist

Before starting a project, companies are advised to use an internal checklist to confirm the 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 statements.
• Check 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 instructions for use.
• Confirm the responsibilities, 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 Perspective

AIMEILI advises companies not to regard registration in a target market as a one-off document submission, but to manage it as an overseas market access programme. For companies preparing to enter several countries, building a clear core technical file and evidence matrix first and then converting it to each country's requirements is usually faster and more stable than assembling documentation country by country, and it also supports subsequent changes and renewals more effectively.

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

Common Follow-up Questions

Can domestic documentation be used directly for registration in a target market?

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

When is the best time to start a gap assessment?

Immediately after the target markets and the product list are confirmed. The earlier the gap assessment is completed, the easier it is to arrange re-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 registration communication, changes, renewal and post-market event handling. Unclear responsibilities affect certificate control and the stability of the market afterwards.

Project Execution Recommendations

When executing this type of registration project, companies should establish a project register that manages the product list, model and specification matrix, registration pathway, documentation owners, translation status, testing status, records of communication with the local agent and the expected submission date in a single table. This makes documentation gaps visible early and helps management judge whether the project will affect the launch plan.

Companies that already hold registrations in several countries should also build an evidence reuse matrix, defining which documents can serve as core evidence and which must be re-issued or supported by additional statements according to national requirements. In particular, labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates must be kept at consistent versions.

• Confirm the target market and the product list.
• Complete risk classification and pathway determination.
• Build a documentation gap assessment table.
• Define the local agent and certificate control.
• Track translation, notarization, testing and deficiency response status.
• Plan 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 usually examine whether the manufacturer name, manufacturing address, product scope, certificate validity period, applicable standards and technical file are mutually consistent. If the scope of the ISO 13485 certificate does not match the device being submitted, or if the manufacturing address, model specifications, instructions for use version and test report are inconsistent, a company may be asked for additional explanation even when it has prepared a large volume of documents.

Companies should establish an evidence consistency checklist before submission, matching 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 appears basic, but it significantly reduces the probability of deficiency letters, particularly for projects submitted simultaneously to several GHWP member states or for multiple product families.

Localization Conversion and Agent Responsibility

Target market registration projects usually involve arrangements with a local agent, authorized representative, importer or registration holder. Companies must confirm in advance whether the local partner is only responsible for submitting documents or also handles regulatory communication, certificate maintenance, post-market event reporting, change applications and renewal reminders. Different responsibility boundaries directly affect certificate control and the stability of the market afterwards.

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 details and after-sales contact information. 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 in the target country, rather than to write a separate set of isolated documents.

Post-Market Maintenance and Long-Term Planning

Registration does not mean that compliance work is finished. 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 agent replacement occurs, the certificate and the marketed product can 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 a country gap list, and finally schedule submission, deficiency response, post-market maintenance and renewal milestones. The value of this approach is not only higher efficiency in individual countries, but also the development of a repeatable overseas compliance capability that reduces the cost of starting documentation from scratch every time a new market is entered.

Further Reading

• Previous: How Is Post-Market Surveillance Handled for Medical Device Registration in Japan?
• Next: What Should Be Prepared Before Renewing a Medical Device Registration in Japan?
• Recommended: How Should a Local Agent Be Selected for Medical Device Registration in Brazil?
• Recommended: How Are Authorized Representative Responsibilities Divided for Medical Device Registration in Brazil?
• Recommended: Why Do Medical Device Registration Timelines in Brazil Become Extended?
• Recommended: What Are the Common Reasons for Deficiency Letters in Medical Device Registration in Brazil?
• Recommended: How Is Post-Market Surveillance Handled for Medical Device Registration in Brazil?
• Recommended: When Must a Registration Change Be Filed for Medical Device Registration in Brazil?

Content Review and Applicability Boundaries

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 organizations, standards organizations and publicly available regulatory materials; industry media and project experience are used only as supporting judgement.

Applicability boundary: 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, test conclusions or legal advice.