Decos Healthtech | Blog

SOFTWARE AS A MEDICAL DEVICE (SAMD) IN US FDA AND ITS SUBMISSION PROCESS.

Written by Sonali Hinge | 11/19/2026

SOFTWARE AS A MEDICAL DEVICE (SAMD) IN US FDA AND ITS SUBMISSION PROCESS.

The United States Food and Drug Administration (FDA) is a key regulatory authority for medical devices. Medical device manufacturers must meet the requirements applicable to their devices and the relevant marketing pathway, which may involve FDA clearance, approval, De Novo authorization, or an exemption. They must also maintain an appropriate quality management system.
 
In December 2019, the FDA recognized ISO 14971:2019, the revised international risk management standard for medical devices, alongside numerous other consensus standards. Manufacturers should check the FDA’s current database of recognized consensus standards to determine the applicable edition and any transition or extent-of-recognition details for a submission.
The earlier ISO 14971:2007 edition should not be assumed to remain an accepted basis for a new declaration of conformity. Manufacturers should apply the relevant currently recognized edition and assess how software changes affect device risk. Changes that may warrant additional regulatory evaluation can be categorized as follows:
A change that introduces a new risk or modifies an existing risk that could result in significant harm
A change to risk controls to prevent significant harm and
A change that significantly affects the clinical functionality or performance specifications of the device.
For software changes, whether a new premarket submission is required depends on the device’s regulatory pathway and the impact of the change on safety, effectiveness, intended use, and other factors described in FDA guidance. For a PMA-approved device, changes affecting safety or effectiveness may require an appropriate PMA supplement rather than an “auxiliary application,” including certain changes to indications, clinical effects, or performance characteristics.
Premarket approval (PMA) is the regulatory review process conducted by the FDA to evaluate the safety and effectiveness of Class III medical devices. These devices are of substantial importance in preventing impairment of human health or present a potential, unreasonable risk of illness or injury. [2]
FDA Guidance
The FDA has issued medical device software guidance over many years. As of February 2, 2026, the Quality Management System Regulation (QMSR) is effective under 21 CFR Part 820, incorporating ISO 13485:2016 by reference. The previous standalone design controls citation in 21 CFR 820.30 should therefore not be presented as the current governing requirement. Applicable design and development controls remain part of the QMS framework.
The FDA’s guidance explains how regulatory expectations apply to different aspects of software. Its June 2023 guidance, “Content of Premarket Submissions for Device Software Functions,” addresses recommended software documentation for premarket submissions and replaced the 2005 software submission guidance. Other FDA and IMDRF guidance addresses clinical evaluation of Software as a Medical Device. [3]
Software as a Medical Device must support clinical vocabulary for its use; this has to do with proper instruction and design in the interface.
It should address clinical evaluation methods and clinical evidence relevant to the use of the SaMD software.
It should have various recommendations attached to the software for analytical purposes and those manufacturers should outline potential adverse consequences.
Submission to FDA
Companies planning to market SaMD in the United States must determine whether FDA marketing authorization is required and which pathway applies, such as 510(k), De Novo, or PMA. Certain devices are exempt from premarket notification. Software changes to an existing cleared device should be evaluated under FDA guidance, “Deciding When to Submit a 510(k) for a Software Change to an Existing Device.” Some changes do not require a new 510(k), while others—including changes to algorithms, architecture, or data handling—may require additional review depending on their effect on safety and effectiveness. [1]
The types of principles fall into two broad categories: 
Pre-Market:
Data to establish the evidence on SaMD:
Scope and intended use/environment of use.
Safety and Effectiveness
Specificity/Sensitivity
Reliability/Limitations/accuracy
Post-Market: Continue to collect and evaluate real-world data on:

  • Performance

  • Complaints

  • Safety

  • Effectiveness

 

The Pre-Market process of the 510(k) application includes the following steps :

  1. Confirm your FDA product code, regulation number, and predicate devices.

  2. Identify all testing, FDA guidance, consensus standards, and clinical data requirements.

  3. Prepare a detailed gap analysis report to provide a clear pathway for 510(k) submission.

  4. Compile all the data and submit the application and address the post-submission questions.

PMA is a stringent premarket review pathway generally used for Class III devices that require FDA approval. Applicants must receive PMA approval before marketing a device subject to PMA requirements. FDA approval depends on valid scientific evidence providing reasonable assurance that the device is safe and effective for its intended use or uses.

Post-approval studies can provide additional evidence about the safety and effectiveness of approved medical devices using data from patients, healthcare professionals, manufacturers, and other stakeholders. The FDA may require post-approval studies as a condition of certain PMA approvals and may impose appropriate postmarket requirements under other applicable authorization pathways.

In summary, the applicable FDA submission and postmarket processes support the development and continued use of safe and effective SaMD. Manufacturers should define performance objectives, document software and algorithm changes, validate modifications, and monitor real-world performance. For AI-enabled device software functions, the FDA’s August 2025 guidance on predetermined change control plans describes how specified future modifications may be planned and reviewed as part of a marketing submission, subject to the plan and applicable requirements.