Back to Explorer

Policy for Device Software Functions and Mobile Medical Applications: Guidance for Industry and Food and Drug Administration Staff

FinalCenter for Devices and Radiological Health Center for Biologics Evaluation and Research09/28/2022

Description

FDA is issuing this guidance to communicate how the Agency intends to apply its regulatory oversight to certain software, including device software functions and mobile medical applications (MMAs) intended for use on mobile platforms or on general-purpose computing platforms. FDA intends to apply its regulatory oversight to those device software functions that meet the definition of a medical device and whose functionality could pose a risk to a patient’s safety if the device were not to function as intended. This guidance describes FDA’s policy for device software functions and MMAs that meet the device definition, including some that are the focus of FDA’s regulatory oversight and some for which FDA does not intend to enforce requirements under the Federal Food, Drug, and Cosmetic Act. This guidance also provides information on some software functions that do not meet the device definition, and as such, are software functions that are not subject to applicable FDA regulatory requirements.

Scope & Applicability

Product Classes

10
Software as a Medical Device (SaMD)

Software performing medical purposes without being part of hardware

In vitro diagnostic products

Subject to 21 CFR Part 809

Cochlear implant

Implantable device calibrated by software

Infusion pump

Intended for use in a health care facility to pump fluids and medications.

Non-Device-MDDS

Software functions solely intended to transfer, store, convert formats, and display medical device data; software functions that meet the definition of Non-Device-MDDS

Class III devices

Subject to General Controls and Premarket Approval

Class II devices

Proposed classification for NGS-based tests for germline diseases.

Class I devices

Subject to General Controls

Software in a Medical Device (SiMD)

Software functions within the control of a hardware device

Mobile Medical App

Software function meeting device definition deployed on a mobile platform; Software that meets the definition of a device; software functions that may be subject to reporting or exemptions

Stakeholders

7
Mobile Medical App Manufacturer

Entity responsible for manufacturing mobile medical applications; Entity that initiates specifications, designs, or labels a mobile medical app

importer

Person responsible for establishing FSVP; Person in the United States who owns or has purchased the food at time of entry; entity responsible for FSVP compliance; Entity responsible for FSVP compliance; Entity responsible for conducting hazard analysis; Subject of FSVP requirements for food for humans and animals.; The entity responsible for FSVP compliance and supplier approval.; entity responsible for foreign supplier verification; entity responsible for developing FSVP; entity responsible for

Institutional Review Board

Governs top dose in clinical studies

health care professionals

Users of medical software functions

Health Care Professional

Intended users such as nurses in a nonemergency setting

manufacturer

Entity required to conduct postmarket surveillance; entity responsible for submitting postmarket surveillance plans; Entity holding the approved PMA, HDE, or cleared 510(k); The entity responsible for conducting postmarket surveillance and submitting reports.; Entity that can use the checklist as a reference for submissions.

licensed practitioners

Physicians, dentists, and optometrists manufacturing apps for professional practice

Regulatory Context

Attributes

4
Commercial Off-The-Shelf (COTS)

Type of software components or platforms used in mobile apps

lower risk

FDA intends to exercise enforcement discretion because they pose lower risk

intended for use in the diagnosis of disease

Criteria used to determine if software is a medical device

intended use

Specifications that are directly associated with the intended use of the device.

Identified Hazards

Hazards

3
Patient Safety Risk

Risk posed if a device software function fails to perform as intended

risk to health

threshold for requiring a report of correction or removal

Risk to Patient Safety

Potential risk if software applications do not function as intended

Related CFR Sections (20)

Related Warning Letters (10)

  • CGMP/QSR/Medical Devices/Adulterated

    Envoy Medical Inc.

    2025-12-09
  • CGMP/QSR/Medical Devices/Adulterated

    Hong Qiangxing Shenzhen Electronics Limited

    2025-11-25
  • CGMP/QSR/Medical Devices/Adulterated

    Contec Medical Systems Co., Ltd.

    2025-10-28
  • CGMP/QSR/Medical Devices/Adulterated/Misbranded

    Royal Philips

    2025-10-28
  • CGMP/QSR/Medical Devices/Adulterated/Misbranded

    Qianjiang Kingphar Medical Material Co Ltd.

    2025-10-28
  • CGMP/QSR/Medical Devices/Adulterated

    LEVO AG

    2025-10-21
  • CGMP/QSR/Medical Devices/Adulterated

    Technological Medical Advancements LLC

    2025-10-07
  • Medical Device Reporting/Misbranded

    Insung Medical Co. Ltd.

    2025-09-30
  • Medical Device/Adulterated/Misbranded/Lacks PMA and/or 510(k)

    The Richline Group, Inc.

    2025-09-23
  • Investigational Device Exemptions (IDE)/Premarket Approval Application (PMA) Adulterated Device

    SeniorLife Technologies, Inc.

    2025-09-16

See Also (8)