Clinical Decision Support
Software providing healthcare professionals with knowledge and patient-specific information.
Definition
Clinical Decision Support (CDS) software analyzes data within EHRs or directly from devices to help providers make clinical decisions. Some CDS functions are excluded from FDA device regulation under Section 3060 of the Cures Act when criteria are met.What this means in practice
Whether a CDS function is a regulated device depends on transparency of the basis for recommendations and time-criticality of the underlying condition.Examples
- A CDS function analyzing patient data to suggest potential drug interactions, but allowing the physician to review the evidence and make the final prescribing decision, exemplifies an excluded function under the Cures Act.
- Software that provides guidance on appropriate diagnostic tests based on a patient's symptoms, where the physician can independently evaluate the rationale, is an example of an excluded CDS.
- A CDS system providing real-time alerts for critical vital sign changes in an ICU setting, where immediate action is required, likely falls under FDA regulation due to time-criticality.
- •A common pitfall is assuming all CDS software is exempt from regulation; only specific functions meeting the Cures Act criteria are excluded.
- •Misinterpreting "transparency" can lead to non-compliance, as the basis for recommendations must be clearly understandable by a healthcare professional.
- •Failing to consider the time-criticality of the clinical situation for which the CDS is intended can result in incorrect regulatory classification.
- •Neglecting to update regulatory assessments when CDS functionalities change can lead to non-conforming products.
- •Assuming EU MDR classification is identical to FDA Cures Act exemptions will lead to non-compliance in the EU market.
Frequently asked questions
Related terms
Grouped by themeEditor's picks
· Hand-selected related conceptsSaMD & AI/ML Devices
· From this learning pathFDA mechanism to pre-authorize specific modifications to AI/ML-enabled devices.
Software not developed for medical device use, or lacking adequate development records, incorporated into a device.
Software embedded in or required to operate a hardware medical device.
IEC 62304 classes A, B, C reflecting potential harm from software failure.
Software Team Onboarding
· From this learning pathLifecycle requirements for medical device software.
The federal statute that gives FDA explicit premarket authority over cybersecurity for cyber devices.
Confirming design outputs meet inputs (V) and that devices meet user needs (V).
A documented, risk-based set of processes that build cybersecurity into a medical device across its full lifecycle.
Where this term appears across MedTech Terms.
- SaMD & AI/ML DevicesLesson 6 of 9
- Software Team OnboardingLesson 7 of 12
Primary references
3 sources- 1FDA CDS GuidanceVerifiedFDAfda.gov
- 2IMDRF - Software as a Medical DeviceVerifiedIMDRFimdrf.org
- 3MDCG Software GuidanceVerifiedMDCGhealth.ec.europa.eu
Inline markers like [1] jump to the matching reference above.