本頁閱讀時間3分鐘
概述
The analysis depends on the function, intended user, and ability of a health professional to independently review the basis for recommendations. These distinctions require function-specific review, not assumptions based on a product’s “CDS” label.
深入探討
Clinical decision support software provides information or recommendations to support healthcare decisions. FDA’s guidance explains how the agency assesses software functions under the applicable statutory criteria. Some functions may be excluded from the device definition when they meet specific conditions, including that a health professional can independently review the basis for recommendations. Other functions, including certain patient-specific analyses or device functions, may remain subject to oversight. The assessment is about what a particular software function does, its intended user, and how the output is used. A product can contain multiple functions with different regulatory status. A tool that presents evidence for a clinician to review is not automatically treated the same as software that directs diagnosis or treatment. FDA guidance also notes that functions intended for patients or caregivers may be assessed differently from clinician-facing support. Manufacturers should define each function and provide information that supports independent review where relevant. Clinicians should understand what inputs and evidence support a recommendation, the intended population, and limitations. A generated explanation is not itself proof of the underlying basis. Check current FDA guidance and product labeling for the specific function. This guide summarizes concepts and does not determine regulatory status for a product. Preserve examples of intended use and evidence that support the analysis, and revisit it when users, claims, or outputs change. Keep patient-facing and clinician-facing functions distinct in requirements and documentation.
戰略影響
風險與安全
災難性和日常的人工智慧危害都取決於誰了解風險以及誰能夠採取行動。
更明確的決策
民眾和專業素養決定強而有力的安全政策在政治上是否可行。
突破炒作
清晰的解釋可以減少炒作、實驗室公關和模糊道德劇場的影響。
The Future of FDA Clinical Decision Support Software Guidance
Decision-support products increasingly use machine learning and generative models, creating new questions about explainability and how clinicians review evidence. FDA guidance is updated as laws and technology change. Developers should monitor current agency materials and preserve a function-level analysis. Care teams need training to interpret outputs and should retain clinical judgment even when a tool is authorized. Developers should design interfaces that make the evidence and limitations easy to inspect, not merely generate a plausible explanation. Monitor outcomes and user feedback.
現實世界的實施
A clinician reviews sources and rationale behind a recommendation before acting.
A software team separates administrative reminders from patient-specific treatment recommendations.
A hospital confirms whether a function is intended for health professionals or patients.
A developer maps the product’s intended use to the criteria in current FDA guidance.
風險與防護欄
將存在風險視為科幻小說,同時能力複合。
混淆了表面產品安全與高度自治下的對準。
只給非英語和非專業觀眾留下低品質的資源。
實施路線圖
單獨的產品危害、誤用和失控/失調風險。
詢問哪些證據會改變您對時間表和嚴重性的看法。
比起行銷主張,更喜歡主要來源和具體評估。
確定一條行動路徑:職業、政策、資金或技能——而不僅僅是意識。
不斷探索
Free newsletter
Get the daily AI briefing
Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.
One email each weekday. Unsubscribe in one click. We never sell or share your address.
Test yourself
Take the FDA Clinical Decision Support Software Guidance quiz
Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.
Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation
常見問題
What is FDA Clinical Decision Support Software Guidance?
FDA’s Clinical Decision Support Software guidance explains when software functions may be regulated as medical devices and when a non-device CDS exclusion may apply. The analysis depends on the function, intended user, and ability of a health professional to independently review the basis for recommendations. These distinctions require function-specific review, not assumptions based on a product’s “CDS” label.
What does FDA evaluate in clinical decision-support software?
Regulatory analysis depends on the function and how it is used.
Why analyze a product function by function?
Regulatory assessment is not necessarily product-wide and uniform.
What should developers document for a function?
Function-specific documentation supports assessment and use.
What should clinicians do with a CDS recommendation?
CDS supports decisions and does not replace professional review.
繼續學習
相關指南
為此主題精選的更多指南