PMDA Updates English SaMD Page on July 6, 2026, Signaling Continued Focus on Innovative Software Medical Devices

PMDA Updates English SaMD Page on July 6, 2026

The PMDA English website indicates that its Software as a Medical Device (SaMD) page was updated on July 6, 2026, reflecting Japan’s continued efforts to consolidate review information for innovative SaMD products.

Source

• Source organization: PMDA
• Original date: July 6, 2026
• Site publication time: July 8, 2026, 09:00
• Original link: https://www.pmda.go.jp/english/review-services/reviews/0009.html

Full Translation of Core Content

The PMDA English website shows that the page related to Software as a Medical Device (SaMD) was updated on July 6, 2026. The page consolidates information on Japan’s SaMD review support, consultation services and related information entry points, with the aim of helping innovative software medical devices enter practical use more smoothly.

SaMD generally refers to software products with a medical purpose that can operate independently or in combination with hardware. In Japan, regulatory focus includes whether the software has a medical purpose; whether its intended use is clear; whether algorithm outputs affect diagnostic or treatment decisions; whether performance validation is sufficient; whether clinical evidence supports claims; and whether cybersecurity and software lifecycle management are adequate.

For companies, the PMDA update to the SaMD page indicates that Japanese regulators continue to treat software medical devices as a priority area for information integration and review support. Products planned for the Japanese market—including software, artificial-intelligence-assisted diagnosis, remote monitoring, health management or clinical decision support—should confirm regulatory classification and evidence depth in advance. An ordinary software manual cannot replace medical device registration materials.

Business Impact

Companies planning to enter the Japanese market with software medical devices should first determine whether the software has a medical purpose, whether it qualifies as standalone software as a medical device, and the degree of its impact on clinical decisions. For artificial-intelligence-assisted, diagnostic-support, sleep, monitoring, remote-management and treatment-recommendation software, particular attention should be paid to clinical evidence, algorithm changes, cybersecurity, user interfaces and real-world use scenarios.

AIMEILI Regulatory Interpretation

AIMEILI Regulatory Department believes that the updates related to software, artificial intelligence and human factors together indicate a trend: regulators are moving medical device software review from “function-description review” to “real-world use scenario review.” Companies cannot merely demonstrate that software runs, that algorithm accuracy is high or that the interface appears clear; they must also demonstrate that the product can be used safely, stably and explainably by the target users, in the target scenarios and at the target risk level.

For SaMD, artificial-intelligence-assisted diagnosis, clinical decision support, remote monitoring and products with complex user interfaces, registration materials should cover intended use, inputs and outputs, user roles, algorithm boundaries, data representativeness, performance validation, clinical evidence, cybersecurity, software lifecycle, human factors validation and post-market version management. For artificial-intelligence-related products in particular, regulatory attention often focuses on data bias, applicable populations, clinical scenarios, model changes and interpretation of results—not on the degree of “intelligence” emphasized in company promotional materials.

AIMEILI recommends that companies establish a “software medical device evidence package” that places algorithm descriptions, data governance, performance validation, human factors engineering, cybersecurity, risk management, clinical evaluation and version control within a single document system. This enables rapid conversion to different regulatory requirements when entering markets such as FDA, PMDA, MFDS, HSA and EU MDR, rather than preparing additional materials on an ad hoc basis for each country.

Compliance Actions for Companies

• Confirm whether the update affects existing registration pathways, certificate maintenance or post-market obligations.
• Verify technical documentation, labels and instructions for use, quality system and local responsible entity arrangements for target countries.
• Establish change impact assessments and regulatory update tracking records for marketed products.
• Where necessary, archive official original pages, translated interpretations and action items for future audits and project reviews.

Content Review and Applicability

• Content author: AIMEILI Regulatory Editorial Department
• Professional review: AIMEILI Medical Device International Registration Project Team
• Source principles: Official regulatory authorities, international organizations, standards organizations and public regulatory materials are preferred; industry media and project experience are used only as supporting judgment.
• Applicability boundary: This article is intended for preliminary understanding, document preparation and project planning and does not replace formal requirements of target-country regulators, testing conclusions or legal advice.