How to Use an ISO 13485 Certificate for Medical Device Registration in Japan

How to Use an ISO 13485 Certificate for Medical Device Registration in Japan

Direct answer: An ISO 13485 certificate is supporting quality management system evidence for medical device registration in Japan, but it is not a standalone submission document and cannot replace the applicable regulatory pathway, product classification, technical file or local authorization arrangements. Companies should first confirm the target country, the product risk class, the applicable regulatory pathway and the existing documentation base, and then assess the technical file, quality system evidence, labels and instructions for use, local representative arrangements, clinical evidence and post-market maintenance requirements. AIMEILI recommends completing a documentation gap assessment before formal submission, so that unclear classification, documentation or authorization arrangements do not unnecessarily extend the project timeline.

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

This FAQ addresses the priority questions companies need to resolve in international medical device registration, documentation preparation, compliance pathways and post-market maintenance.

Content Structure

• Key Summary
• Applicable Scenarios and Core Questions
• Registration Decision Logic
• Documentation and Evidence
• Common Mistakes
• Company Preparation Checklist
• AIMEILI's View
• Common Follow-up Questions
• Continue Reading
• Scope of Application

Key Summary

On the question of how an ISO 13485 certificate should be used for medical device registration in Japan, companies should first confirm the target country, the product risk class, the applicable regulatory pathway and the existing documentation base, and then assess the technical file, quality management system evidence, labels and instructions for use, local agent arrangements, clinical evidence and post-market maintenance requirements. AIMEILI recommends a documentation gap assessment before formal submission to avoid project delays caused by unclear classification, documentation or authorization arrangements.

For Chinese medical device manufacturers, a 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 arrangements, 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, deficiencies and rework are more likely in areas such as model coverage, evidence chain consistency, label claims and certificate control rights.

AIMEILI recommends that companies plan this question within a unified GHWP member state and multi-country market access strategy, using one reusable core technical file to support localization in different markets, rather than preparing documentation from scratch for each country on an ad hoc basis.

Applicable Scenarios and Core Questions

Companies that search for how to use an ISO 13485 certificate for medical device registration in Japan are usually not looking for a conceptual explanation. They want to determine whether their existing documentation can support an application in the target market, whether a local agent or authorized representative is required, why the timeline has been extended, and which issues could affect the launch plan. This question typically involves product classification, registration pathway, evidence chain, label localization and post-market maintenance responsibilities at the same time.

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 sufficient. A more valuable approach is to first develop reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labels and instructions for use, 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 scenario, contact with the human body, duration of use, sterility, whether the device is active, and whether it has software or IVD attributes, and then determine the risk class and submission pathway. Once the pathway is incorrectly determined, subsequent translation, notarization, authorization, testing and supplementary documentation will all deviate from the correct direction.

For a target market project, the applicant entity and local responsibility boundaries 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 issues are handled only vaguely in a commercial contract, market control rights may be affected later.

Documentation and Evidence

Typical documentation includes the product description, model and specification matrix, intended use, risk classification rationale, ISO 13485 or other applicable quality system evidence, technical file, performance verification reports, risk management documentation, 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. Label claims, the models covered by test reports, the applicable scope of clinical evidence, risk management conclusions, label warnings and information in the registration application form must support one another. Regulatory authorities 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

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

• Submitting translated NMPA documentation directly without restructuring the evidence according to the target market pathway.
• Listing too many models and specifications while test reports, clinical evidence or labels do not cover them adequately.
• Selecting a local agent only on the basis of sales cooperation, without clarifying regulatory responsibilities, certificate control rights and post-market maintenance duties.
• Inconsistency between labels, instructions for use, promotional materials and registration documentation, leading to deficiency notices or post-market compliance risks.
• Failing to plan multi-country documentation reuse in advance, resulting in repeated preparation for each country and inflated costs 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 duties, fees, certificate control rights and exit mechanism of the local agent or authorized representative.
• Establish a target country gap assessment table identifying what must be retested, translated, notarized or supported by additional declarations.

AIMEILI's View

AIMEILI recommends that companies not treat target market registration as a one-off document submission, but manage it as an overseas market access program. For companies preparing to enter multiple countries, building 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 certificate renewals than supplementing documentation country by country on an ad hoc basis.

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; and third, the regulatory responsibility boundaries of local partners. If these three items are unclear, the project may still face repeated issues during deficiency responses, agent communication and post-market maintenance, even if a large amount of documentation appears to be available.

Common Follow-up Questions

Can domestic documentation be used directly for target market registration?

Domestic documentation can serve as a basis, but it usually 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 recommended to start immediately after confirming the target market and product list. The earlier the gap assessment is completed, the easier it is to arrange retesting, translation, label 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, certificate renewal and post-market event handling. Unclear rights and responsibilities can affect certificate control rights 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, models and specifications, registration pathway, document 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 time and helps management judge whether the project will affect the launch plan.

For companies that already have a registration base in multiple countries, an evidence reuse matrix should also be established to clarify 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 must in particular be kept version-consistent.

• Confirm the target market and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Clarify the local agent and certificate control rights.
• 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. Regulatory authorities usually examine 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 products being registered, or if the manufacturing site, models and specifications, or instructions for use version do not match the test reports, a company may be asked for supplementary explanations even if it has prepared a large volume of documentation.

Before submission, companies should establish an evidence consistency checklist that maps the product name, models and specifications, intended use, 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 notices, especially for projects involving simultaneous submissions in multiple GHWP member states or multiple product families.

Localization Conversion and Representative Responsibilities

Target market registration projects usually involve local agent, authorized representative, importer or registration holder arrangements. 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 rights and subsequent market stability.

Labels, instructions for use and authorization documents also cannot simply be translated. Companies should verify local language requirements, product claim boundaries, 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 compliance work has ended. Companies also need to maintain certificate validity, change records, distributor authorizations, complaint handling, adverse event reporting, recall processes, label versions and regulatory update records. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance, so when a manufacturing site change, model expansion, instructions for use update or agent replacement occurs, the certificate and market sales may become disconnected.

AIMEILI recommends managing this question within an annual international registration plan: first determine target market priorities, then build a reusable documentation package and country gap list, and finally schedule submission, deficiency response, post-market maintenance and certificate renewal milestones. The value of this approach is not only improved registration efficiency in a single country; more importantly, it enables companies to build a replicable overseas compliance capability and reduce the cost of starting documentation from scratch each time they enter a new market.

Continue Reading

• Previous: Can Test Reports Be Reused for Medical Device Registration in Japan?
• Next: How Should a Local Agent Be Selected for Medical Device Registration in Japan?
• Recommended reading: How Should a Local Agent Be Selected for Medical Device Registration in Brazil?
• Recommended reading: How Are Authorized Representative Responsibilities Divided for Medical Device Registration in Brazil?
• Recommended reading: Why Does the Medical Device Registration Timeline in Brazil Become Extended?
• Recommended reading: What Are the Common Reasons for Deficiency Notices in Medical Device Registration in Brazil?
• Recommended reading: How Is Post-Market Surveillance Conducted for Medical Device Registration in Brazil?
• Recommended reading: When Must a Registration Change Be Filed for Medical Device Registration in Brazil?
• Return to FAQ Center
• News and Information
• Contact AIMEILI

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 organizations, standards organizations 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 regulatory authority, testing conclusions or legal opinions.