Back to Columns
AI & DX11 min read

What Is Software as a Medical Device (SaMD)? The Regulatory Position of AI Features

August 10, 2026

What Is Software as a Medical Device (SaMD)? The Regulatory Position of AI Features
Share this article

Two regulatorily distinct kinds of AI are entering clinical settings: voice entry and document drafting in an EMR, and AI detecting lesions in images. Both get called "medical AI," but the former is generally not a medical device while the latter may constitute Software as a Medical Device (SaMD) under pharmaceutical and medical device law.

Disclaimer: This article provides general information. Medical device status is determined product by product, and regulation is subject to revision. Always verify with current primary sources (the Ministry of Health, Labour and Welfare, PMDA) and the responsible authorities.

What SaMD Is

SaMD is termed a program medical device under Japanese law: software that functions as a medical device in itself, rather than software embedded in hardware.

Under pharmaceutical and medical device law, programs meeting certain requirements fall within the definition of a medical device, bringing requirements for marketing authorization holder licensing and per-product approval, certification, or notification.

Status Is Not Determined by Developer Intent

The most important point. Whether software constitutes a medical device does not depend on whether its developer considers it one. It is determined by statutory definition.

Two perspectives govern:

  1. The degree of involvement in diagnosis, treatment, or prevention of disease
  2. The level of risk to life and health should a malfunction occur

The higher both are, the more likely the software qualifies—and the heavier the regulatory class.

Examples on Either Side

Generally not a medical device

  • Programs that merely record, display, and store data such as weight and step count without processing it
  • Programs providing general health information not based on an individual patient's condition
  • Programs supporting work processes such as documentation, booking, and claim generation

Potentially a medical device

  • Programs detecting candidate lesions in images to support diagnosis
  • Programs processing test data to indicate disease likelihood
  • Programs directly involved in determining treatment policy

The dividing line is broadly whether the software merely handles data or participates in medical judgment.

Classification of diagnostic support programs is evaluated on the significance of the diagnostic result, the risk of malfunction, and whether it supports or replaces the physician's final judgment.

Which Are EMR AI Features?

FeaturePosition
Generating chart entries from speechDocumentation support; generally workflow support
Searching and summarizing past recordsInformation organization; generally workflow support
Drafting referrals and certificatesDocument support; generally workflow support
Checking for missed billingClaims support; generally workflow support
Automating booking and receptionWorkflow support
Detecting lesions in imagesMay constitute a medical device
Indicating disease likelihood from test valuesMay constitute a medical device

Most functions an AI-native EMR provides fall under support for documentation, paperwork, claims, and booking. Where diagnostic support is placed within the same interface, that portion may fall under a different regulatory framework.

The functional scope is covered in What Can an AI-Native EMR Actually Do?.

Whether a specific product qualifies is a per-product determination. The above is a general orientation; actual determinations require confirmation with the responsible authority.

What Qualification Entails

  • Marketing authorization holder licensing
  • Per-product procedures: notification, certification, or approval depending on class
  • Quality and safety management systems, including post-market malfunction reporting
  • Advertising restrictions applicable to medical devices

Regulatory weight scales with classification—higher risk, heavier procedure.

Programs Promoting Development

DASH for SaMD. A joint package strategy from the Ministry of Health, Labour and Welfare and the Ministry of Economy, Trade and Industry. Under it, consultations on medical device status are handled centrally by the responsible ministry division. A second-phase strategy has also been published.

Two-stage approval. In November 2023, guidance established a staged approach reflecting SaMD characteristics: granting approval early once a degree of efficacy is confirmed, then advancing evaluation based on real-world use. Industry associations have published illustrative case collections.

PMDA capacity. In July 2024, PMDA's SaMD review function was reorganized from a division into a department with expanded capacity. PMDA also publishes a guide to regulatory development and approval applications for SaMD.

What Providers Should Verify

Is this function a medical device or workflow support? Ask the vendor explicitly. If a feature claims diagnostic support, confirm whether it holds approval or certification.

If approved, within what scope? Use must stay within the approved intended use, target, and conditions. Distinctions arise—usable for this examination, not contemplated for that one.

Reimbursement treatment. Holding medical device approval and being reimbursed are separate matters. If you are considering payback on cost, verify them separately.

Where responsibility for final judgment sits. Most important of all: even when using AI-based diagnostic or therapeutic support, the responsibility for final judgment rests with the physician. Adopting an AI output verbatim does not transfer responsibility to the AI.

See Where to Draw the Line on Delegating Work to AI.

The Relationship to Generative AI

Recent generative AI sits awkwardly within existing frameworks because output is probabilistic and the same input need not yield the same result.

Most generative AI currently deployed in clinical settings occupies workflow support—documentation, summarization, drafting—where the premise is that a human verifies and finalizes the output, keeping regulatory position and operational safety aligned.

Legal orientation is covered in Using Generative AI in Healthcare.

Conclusion

  • SaMD is software functioning as a medical device in itself
  • Status is set by statutory definition, not developer intent, judged on involvement in diagnosis and treatment and on malfunction risk
  • Programs that only record, display, and store, and workflow support programs, are generally out of scope
  • Lesion detection in images and disease likelihood from test values may qualify
  • Most EMR AI features are workflow support, but adding diagnostic support changes the treatment of that portion
  • Japan has DASH for SaMD, two-stage approval, and expanded PMDA review capacity as promotion measures
  • Providers should separately verify device status, approved scope, reimbursement, and responsibility
  • Even with AI support, responsibility for final judgment rests with the physician

For details on AI Karte or to request a demo, please contact us.

Share this article

Related Articles

AI & DX

Where to Draw the Line on Delegating Work to AI

The first decision when bringing AI into clinical settings is how far to delegate. Can errors be detected? How large is the impact when they occur? Who bears responsibility? What does human verification cost? We sort work along these four axes and cover how to build operating rules that treat drafts as drafts.

August 10, 2026
AI & DX

Using Generative AI in Medical Institutions: A Practitioner's Guide to Law, Vendor Selection, and Security

An in-depth guide to generative AI in medical institutions—covering Japan's APPI with article references, the three-ministry guidelines, and medical-device (SaMD) classification, plus the entrustment/third-party distinction, cross-border transfer, the shared-responsibility model, and prompt-injection defense.

July 28, 2026
AI & DX

What Can the AI in an AI-Native EMR Actually Do?

"AI chart" is a vague term—what does the AI actually do? This article walks through the concrete AI features of an AI-native EMR, following the flow of clinical practice.

July 27, 2026
AI & DX

What Is AI in Electronic Medical Records? What It Can Do, Three Types and How to Choose

What AI in an EMR can do, the different ways AI is built in, and what to check before adopting it, organized for clinic directors and office managers.

July 14, 2026
Healthcare Security

Securing Network-Connected Medical Devices: Protecting Equipment That Cannot Be Patched

Imaging systems, patient monitors, analysers. Network-connected medical devices often run an operating system that stopped receiving support years ago. This article explains why patching is structurally hard, how to defend such devices through network segmentation, and what to specify at the next procurement.

September 14, 2026
ISMS & Certification

SaMD: How ISMS Relates to QMS (ISO 13485)

Companies building Software as a Medical Device carry both a quality management system (ISO 13485) and an ISMS. One protects patients from harm, the other protects information assets. Whether to run two documentation sets or integrate them — including how design controls and ISO 14971 risk management fit in.

September 14, 2026
AI Karte

Explore AI Karte

An AI-native EHR connecting reception, documentation, accounting, claims, and analytics into one cycle.

View the product page

AI Karte as an Option

Most of the problems covered in this article are what AI Karte, our AI-native EHR for clinics, is built to handle. Start by seeing what it is.