Clinical Decision Support
Conceptual Explanation
CDS Intervention Types
CDS is not a single technology; it encompasses a spectrum of intervention types that vary in their timing, intrusiveness, and required clinical action:
| Intervention Type | Timing | Intrusiveness | Example |
|---|---|---|---|
| Alerting / Notification | Real-time, workflow-blocking | High | Drug allergy alert at order sign |
| Advisory | Real-time, non-blocking | Medium | Sepsis score display on patient chart |
| Order facilitation | Triggered, non-blocking | Low | Pre-populated order sets |
| Relevant information | On-demand | None | Knowledge retrieval (clinical RAG) |
| Expert systems | Asynchronous, proactive | None | Care gap identification |
The Alert Fatigue Problem
Alert fatigue is the state in which clinicians systematically dismiss CDS alerts without reading them because past experience has taught them that most alerts are not actionable for their specific patient and situation. It is a conditioned behavior, not a character flaw — it is the rational response to a high-noise, low-signal alert environment.
Alert fatigue has two components:
- Notification fatigue: Too many alerts interrupt clinical workflow
- Relevance fatigue: Too many alerts are not relevant to the specific patient's situation
The engineering solutions address both:
- Threshold calibration: Raise alert thresholds to fire only for interactions/situations above a clinical significance threshold
- Context enrichment: Add patient context to the alert logic (renal function, existing medications, indication) to filter out alerts that are non-actionable given the patient's situation
- Severity stratification: Distinguish truly dangerous alerts (which warrant workflow interruption) from informational alerts (which can be asynchronous)
- Actionability design: Every alert must offer a specific action the clinician can take; alerts without an actionable response are noise
Core Architecture
Common Mistakes
Building Blocking Alerts for Non-Critical Situations. Workflow-blocking alerts that require acknowledgment before the clinician can proceed are justified only for genuinely dangerous situations. Organizations that implement blocking alerts for "warning" level interactions produce exactly the dismissal behavior that causes alert fatigue — and train clinicians to acknowledge-without-reading as fast as possible.
No Alert Review Process. CDS alert libraries that are never reviewed accumulate obsolete alerts, miscalibrated thresholds, and retired rules that continue to fire. Establish an annual alert review process that evaluates every active alert for current clinical evidence, override rate, and action rate.
Delivering All Alerts Through One Channel. An alert that requires a decision must be delivered at the point of decision (order sign, discharge); an informational observation does not need to interrupt the workflow. Mixing all alert severity levels into the same workflow interruption channel produces the signal-to-noise ratio that causes fatigue.
Best Practices
- Restrict blocking alerts to genuinely dangerous situations; use non-blocking cards for warnings
- Capture structured override reasons — they are the primary calibration signal for alert improvement
- Monitor override rate and action rate continuously; investigate deviations from targets promptly
- Review the full alert catalog annually; retire alerts that have consistently high override rates and low action rates
- Use LLM reasoning for nuanced context assessment only when rule-based checks have found something worth reasoning about — not as the first-line check for every order
- Govern every new CDS alert through a clinical review process before deployment
Trade-offs
| CDS Design | Alert Specificity | Alert Volume | Implementation Complexity | Alert Fatigue Risk |
|---|---|---|---|---|
| Rule-based only | Low-Medium | High | Low | High |
| Rule + context filtering | Medium | Medium | Medium | Medium |
| Rule + ML severity scoring | High | Low-Medium | Medium-High | Low |
| Rule + ML + LLM nuance | Highest | Lowest | High | Lowest |
Interview Questions
Q: A hospital's CMO tells you that clinicians are overriding 85% of drug-drug interaction alerts in the EHR. What is your diagnosis and what would you recommend?
Category: System Design / Clinical Informatics Difficulty: Senior Role: AI Architect / FDE
Answer Framework:
An 85% override rate is a textbook alert fatigue indicator. The alerts are firing but not being read — clinicians have learned that most alerts for their specific patient population are non-actionable, so the rational response is to dismiss them quickly and continue the workflow.
The diagnosis has three possible root causes, each with different remedies:
Root cause 1 — Threshold too low: The alert fires for drug interactions that are clinically significant in theory but rarely clinically significant in practice given the hospital's patient population. Remedy: analyze the override data — what reason do clinicians select when they override? If the dominant reason is "not clinically significant for this patient," the threshold needs calibration against the actual patient population.
Root cause 2 — Missing patient context: The alert fires without considering patient context (renal function, dose, indication, current monitoring). A drug interaction that requires dose adjustment in renal impairment should not fire the same alert for a patient with normal renal function. Remedy: add patient-context filters to the rule logic before the alert fires.
Root cause 3 — Alert catalog too broad: The alert catalog contains too many interaction pairs, including low-severity interactions that trained clinicians would manage without an alert. Remedy: audit the alert catalog against override rates by alert type; retire alerts with > 80% override rate and limited evidence of clinical consequence.
The recommendation: run a 90-day alert performance analysis with structured override reason capture (if not already in place), then prioritize root cause remediation based on the override reason distribution. Do not add new alerts until the existing catalog is calibrated.
Key Points to Hit:
- 85% override = alert fatigue, not clinical disagreement with legitimate alerts
- Three root causes: threshold, context, catalog breadth
- Override reason capture is the diagnostic tool — without structured reasons, calibration is guesswork
- Retire before adding — the catalog is already over-alerting
Key Takeaways
- CDS spans a spectrum from deterministic rule-based alerts to nuanced LLM reasoning — use the simplest appropriate mechanism for each alert type
- Alert fatigue is the primary failure mode of clinical CDS; it is caused by low specificity (alerts fire when non-actionable) not by high volume per se
- Severity stratification is the most important CDS design decision: blocking alerts must be rare, reserved for genuinely dangerous situations
- Override reason capture is the primary calibration signal; alert review should be a continuous process, not a one-time deployment activity
- LLMs add value to CDS at the nuance layer — reasoning about whether a rule-triggered alert is clinically significant given the specific patient's context