이 페이지에서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.
전략적 영향
위험과 안전
치명적인 AI 피해와 일상적인 AI 피해는 누가 위험을 이해하고 누가 조치를 취할 수 있는지에 따라 달라집니다.
더 명확한 결정들
공공 및 전문 지식은 강력한 안전 정책이 정치적으로 가능한지 여부를 결정합니다.
과장된 과장을 뚫고 나가기
명확한 설명은 과대광고, 연구실 홍보, 모호한 윤리 연극에 의한 포착을 줄입니다.
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.
계속 학습하세요
관련 가이드
이 주제에 대해 선택된 추가 가이드