Clinical Decision Supporter
When to activate
When building or refining CDS rules in an EHR, designing clinical alerts, implementing order sets, or when alert fatigue is reported and rules need optimization. Use for drug-drug interactions, sepsis screening, VTE prophylaxis, and preventive care reminders.
When NOT to use
Skip for simple reference lookups (lab ranges, drug dosing tables), administrative reminders without clinical impact, or when the CDS rule already exists and is functioning within acceptable parameters.
Instructions
Clinical trigger: What patient data element or event activates the CDS rule?
- Lab value thresholds, vital sign patterns, medication orders, diagnosis codes
- Time-based triggers (e.g., 48h post-op without ambulation)
Evidence grading: What is the evidence level for this recommendation?
- Level A: Multiple RCTs or meta-analyses
- Level B: Single RCT or large observational studies
- Level C: Expert consensus or small studies
Alert specification:
- Severity: CRITICAL (must acknowledge before continuing), WARNING (can dismiss with reason), INFO (passive display)
- Timing: On order entry, on result review, on admission, on discharge
- Display: Concise clinical question + recommended action + evidence level
Alert fatigue mitigation:
- Override rate monitoring (target <50%)
- Specificity optimization (minimize false positives)
- Tiered alerting (only interrupt for high-severity, high-confidence)
- Context-aware suppression (don't alert if action already taken)
Outcome measurement: How will CDS effectiveness be measured?
Output Format
CDS RULE: [Name]
TRIGGER: [Condition] | TIMING: [When]
EVIDENCE: Level [A/B/C] — [Source]
ALERT:
Severity: [CRITICAL/WARNING/INFO]
Display: "[Clinical message]"
Recommended action: [Specific action]
Dismissal requires: [Reason / Nothing / Acknowledgment]
SUPPRESSION LOGIC:
- [Condition under which alert should NOT fire]
- [...]
METRICS:
Sensitivity target: [X]% | Specificity target: [X]%
Override rate target: <[X]%
Outcome: [Clinical metric to track]
SAFETY REVIEW:
Patient safety impact: [Positive/Negative/Neutral]
False positive consequence: [Clinical burden]
False negative consequence: [Risk]
Example
CDS RULE: Sepsis Early Warning
TRIGGER: SIRS criteria ≥2 + organ dysfunction marker | TIMING: On vital sign entry + lab result
EVIDENCE: Level A — Surviving Sepsis Campaign 2021, qSOFA validation studies
ALERT:
Severity: CRITICAL
Display: "SEPSIS ALERT: Patient meets ≥2 SIRS criteria + lactate 3.2 mmol/L.
Recommend: blood cultures ×2, broad-spectrum antibiotics within 1h, fluid bolus 30mL/kg."
Recommended action: Initiate sepsis bundle order set
Dismissal requires: Documented clinical reason (dropdown + free text)
SUPPRESSION LOGIC:
- Sepsis bundle already ordered within last 2h
- Patient already in ICU with active sepsis protocol
- Palliative care / comfort measures only order active
METRICS:
Sensitivity target: 85% | Specificity target: 70%
Override rate target: <40%
Outcome: Time to first antibiotic, in-hospital mortality
SAFETY REVIEW:
Patient safety impact: Positive — early detection saves lives
False positive consequence: Unnecessary labs, antibiotic exposure
False negative consequence: Delayed treatment, increased mortality
1---2name: clinical-decision-supporter3description: Designs clinical decision support (CDS) rules and alert logic for EHR systems. Outputs structured CDS specifications with trigger conditions, evidence grading, alert severity, and alert fatigue mitigation strategies.4allowed-tools: Read, Write, WebSearch5effort: high6metadata:7 source: https://skillmd.com/skills/uitbreidenos/clinical-decision-supporter8---910# Clinical Decision Supporter1112## When to activate13When building or refining CDS rules in an EHR, designing clinical alerts, implementing order sets, or when alert fatigue is reported and rules need optimization. Use for drug-drug interactions, sepsis screening, VTE prophylaxis, and preventive care reminders.1415## When NOT to use16Skip for simple reference lookups (lab ranges, drug dosing tables), administrative reminders without clinical impact, or when the CDS rule already exists and is functioning within acceptable parameters.1718## Instructions19201. **Clinical trigger:** What patient data element or event activates the CDS rule?21 - Lab value thresholds, vital sign patterns, medication orders, diagnosis codes22 - Time-based triggers (e.g., 48h post-op without ambulation)23242. **Evidence grading:** What is the evidence level for this recommendation?25 - Level A: Multiple RCTs or meta-analyses26 - Level B: Single RCT or large observational studies27 - Level C: Expert consensus or small studies28293. **Alert specification:**30 - **Severity:** CRITICAL (must acknowledge before continuing), WARNING (can dismiss with reason), INFO (passive display)31 - **Timing:** On order entry, on result review, on admission, on discharge32 - **Display:** Concise clinical question + recommended action + evidence level33344. **Alert fatigue mitigation:**35 - Override rate monitoring (target <50%)36 - Specificity optimization (minimize false positives)37 - Tiered alerting (only interrupt for high-severity, high-confidence)38 - Context-aware suppression (don't alert if action already taken)39405. **Outcome measurement:** How will CDS effectiveness be measured?4142## Output Format4344```45CDS RULE: [Name]46TRIGGER: [Condition] | TIMING: [When]47EVIDENCE: Level [A/B/C] — [Source]4849ALERT:50 Severity: [CRITICAL/WARNING/INFO]51 Display: "[Clinical message]"52 Recommended action: [Specific action]53 Dismissal requires: [Reason / Nothing / Acknowledgment]5455SUPPRESSION LOGIC:56 - [Condition under which alert should NOT fire]57 - [...]5859METRICS:60 Sensitivity target: [X]% | Specificity target: [X]%61 Override rate target: <[X]%62 Outcome: [Clinical metric to track]6364SAFETY REVIEW:65 Patient safety impact: [Positive/Negative/Neutral]66 False positive consequence: [Clinical burden]67 False negative consequence: [Risk]68```6970## Example7172```73CDS RULE: Sepsis Early Warning74TRIGGER: SIRS criteria ≥2 + organ dysfunction marker | TIMING: On vital sign entry + lab result75EVIDENCE: Level A — Surviving Sepsis Campaign 2021, qSOFA validation studies7677ALERT:78 Severity: CRITICAL79 Display: "SEPSIS ALERT: Patient meets ≥2 SIRS criteria + lactate 3.2 mmol/L.80 Recommend: blood cultures ×2, broad-spectrum antibiotics within 1h, fluid bolus 30mL/kg."81 Recommended action: Initiate sepsis bundle order set82 Dismissal requires: Documented clinical reason (dropdown + free text)8384SUPPRESSION LOGIC:85 - Sepsis bundle already ordered within last 2h86 - Patient already in ICU with active sepsis protocol87 - Palliative care / comfort measures only order active8889METRICS:90 Sensitivity target: 85% | Specificity target: 70%91 Override rate target: <40%92 Outcome: Time to first antibiotic, in-hospital mortality9394SAFETY REVIEW:95 Patient safety impact: Positive — early detection saves lives96 False positive consequence: Unnecessary labs, antibiotic exposure97 False negative consequence: Delayed treatment, increased mortality98```