GUIDE DE LA SOCIÉTÉ

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.

  • 3 minutes de lecture
  • Dernière mise à jour
Sur cette page3 minutes de lecture
  1. Aperçu
  2. Plongée profonde
  3. Impact stratégique
  4. The Future of FDA Clinical Decision Support Software Guidance
  5. Mise en œuvre dans le monde réel
  6. Risques et garde-fous
  7. Feuille de route de mise en œuvre
  8. Continuez à explorer
  9. Questions fréquemment posées

Aperçu

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.

Plongée profonde

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.

Impact stratégique

Risques et sécurité

Les dommages catastrophiques et quotidiens causés par l’IA dépendent tous deux de la personne qui comprend les risques et qui peut agir.

Décisions plus claires

Les connaissances du public et des professionnels déterminent si une politique de sécurité forte est politiquement possible.

Passer à travers le battage médiatique

Des explications claires réduisent la capture par le battage médiatique, les relations publiques en laboratoire et le théâtre d'éthique vague.

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.

Mise en œuvre dans le monde réel

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.

Risques et garde-fous

  • Traiter le risque existentiel comme de la science-fiction alors que les capacités s’accroissent.

  • Confondre sécurité des produits de surface et alignement sous haute autonomie.

  • Laisser le public non anglophone et non expert avec uniquement des sources de mauvaise qualité.

Feuille de route de mise en œuvre

  1. Séparez les dommages causés aux produits, leur mauvaise utilisation et les risques de perte de contrôle/désalignement.

  2. Demandez quelles preuves pourraient changer votre point de vue sur les délais et la gravité.

  3. Préférez les sources primaires et les évaluations concrètes aux allégations marketing.

  4. Identifiez une voie d’action : carrière, politique, financement ou compétences – et pas seulement la sensibilisation.

Continuez à explorer

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.

Démarrer le quiz

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

Questions fréquemment posées

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.