FDA Updates Clinical Decision Support Software FAQ: Device Scope and Real-World Use Review

FDA Updates Clinical Decision Support Software FAQ

Clear answer: FDA's updated FAQ explains which clinical decision support software functions may not be regulated as medical devices and which software functions may remain subject to FDA medical device oversight. The determination generally turns on intended use, outputs, independent user review, influence on diagnosis or treatment decisions, and patient risk.

Source: FDA. Original date: June 29, 2026. Site publication time: June 29, 2026, 09:00. Original link: https://www.fda.gov/medical-devices/software-medical-device-samd/clinical-decision-support-software-frequently-asked-questions-faqs

Full Translation of Core Content

The FDA page addresses common questions about clinical decision support software, with particular focus on which CDS software functions may fall outside medical device regulation and which software functions may remain subject to FDA medical device oversight.

Whether CDS software is regulated usually depends on the software's intended use, the content of its outputs, whether users can independently review the basis for recommendations, whether the software directly drives or influences diagnosis and treatment decisions, and the degree of impact on patient risk. FDA's regulatory determination for this type of software focuses on function and clinical role, not the software's name.

For Chinese software medical device companies, before entering the U.S. market, companies should first determine whether the product constitutes medical device software or SaMD, and then plan the depth of evidence, labeling claims, clinical validation, cybersecurity, and postmarket update strategy.

Business Impact

The update may affect a company's assessment of regulatory pathways, technical file preparation, labeling and instructions for use, quality management system records, and postmarket maintenance arrangements. Companies should conduct an internal assessment against target markets, product risk class, existing certificates, and sales plans, rather than treating regulatory news as general information only.

AIMEILI Regulatory Interpretation

AIMEILI Regulatory Affairs Department considers that updates related to software, algorithms, and human factors together indicate a trend: regulators are moving medical device software review from function description review toward real-world use scenario review. Companies cannot only demonstrate that software runs, algorithms have high accuracy, or the interface appears clear; they must also demonstrate that the product can be used safely, stably, and explainably by the intended users, in the intended scenarios, and at the intended risk level.

For SaMD, algorithm-assisted diagnosis, clinical decision support, remote monitoring, and products with complex user interfaces, registration dossiers should cover intended use, inputs and outputs, user roles, algorithm boundaries, data representativeness, performance validation, clinical evidence, cybersecurity, software lifecycle, human factors validation, and postmarket version management. For algorithmic products in particular, regulatory focus often centers on data bias, applicable populations, clinical scenarios, model changes, and result interpretation, rather than the level of sophistication described in promotional materials.

AIMEILI recommends that companies establish a software medical device evidence package that places algorithm description, data governance, performance validation, human factors engineering, cybersecurity, risk management, clinical evaluation, and version control in a single document system. This enables faster conversion across different regulatory frameworks when entering markets such as FDA, PMDA, MFDS, HSA, and EU MDR, rather than preparing materials ad hoc for each country.

Business Impact and Compliance Actions

Companies should confirm whether the update affects existing regulatory pathways, certificate maintenance, or postmarket obligations; verify technical files, labeling and instructions for use, quality management system arrangements, and local responsible party arrangements in target countries; establish change impact assessments and regulatory update tracking records for marketed products; and, where necessary, archive official source texts, translated interpretations, and internal action items for later audits and project reviews.

Related Updates Listed in the Source

• July 7, 2026: FDA announces public meeting on medical device user fee reauthorization.
• July 6, 2026: FDA publishes recall information for Abiomed Impella CP with SmartAssist heart pump.
• July 6, 2026: FDA publishes recall information for Hologic BioZorb 3D bioabsorbable implant marker.
• July 6, 2026: FDA publishes recall information for Insulet Omnipod Pods insulin pump.
• July 6, 2026: FDA publishes correction information for North American Rescue first aid kit TRUE METRIX device.
• July 6, 2026: FDA updates the TAP full lifecycle consultation program.

Adjacent Updates

Previous: July 1, 2026 — Australia TGA medical device UDI requirements formally implemented in phases. Next: June 26, 2026 — FDA updates the eMDR electronic medical device reporting system enhancement plan.

Content Review and Applicable Boundaries

Content author: AIMEILI Regulatory Editorial Department. Professional review: AIMEILI Medical Device International Registration Project Team. Source principle: Priority is given to official regulatory agencies, international organizations, standards bodies, and public regulatory materials; industry media and project experience are used only as supporting judgment. Applicable boundaries: This article is intended for preliminary understanding, document preparation, and project planning and does not replace the formal requirements, testing conclusions, or legal opinions of target-country regulatory authorities.