Clinical Rule Builder

Rule ID *

Rule Name *

Description *

Applicable Signals * Hold Ctrl/Cmd to select multiple

Tags

Clinical Category

Author *

Rule Enabled

Disabled rules are visible but won't execute when applying rules to data

💡 Tip: Define rule metadata here, then switch to SQL Editor (write WHERE clause) or Visual Builder (drag & drop) to add conditions and actions.

📊 Custom Metrics (Optional):

💡 Define calculated metrics using SQL SELECT:
• SELECT (ecg.summary.mean_heart_rate_bpm * abp.summary.mean_systolic_bp) AS cardiac_load
• SELECT (abp.summary.mean_systolic_bp - abp.summary.mean_diastolic_bp) AS pulse_pressure
• SELECT CASE WHEN ecg.summary.mean_heart_rate_bpm > 100 THEN 1 ELSE 0 END AS tachycardia_flag
• SELECT combined.pep_ms / combined.lvet_ms AS pep_lvet_ratio
Then use these custom metrics in WHERE clause below.

🔍 WHERE Clause (Conditions):

💡 SQL Syntax Examples:
• Simple: `ecg.summary.mean_heart_rate_bpm` > 100
• Combined: `ecg.summary.mean_heart_rate_bpm` > 100 AND `abp.summary.mean_systolic_bp` < 90
• Range: `abp.summary.mean_systolic_bp` BETWEEN 120 AND 140
• Complex: (`ecg.summary.mean_heart_rate_bpm` > 100 OR `abp.summary.mean_systolic_bp` > 140) AND `combined.pep_ms` < 100
• Custom metrics: `sys_roll10` > 1200 (use backticks for custom metrics defined above)
• Beat-level: Custom metrics can query beat_level_metrics table for rolling calculations
Note: Use backticks (`) around metric paths and custom metric names
Available Metrics: View All Metrics →

⚡ Actions (when rule is satisfied):

🚨 Alert

📝 Log Event 📊 Increment Score:

⚡ Conditions

Define when this rule should trigger

Condition Logic:

🎯 Actions

Define what happens when rule triggers

👁️ Preview

JSON representation of your rule

🧪 Rule Testing

Test your rule against sample data before saving. Uses VitalDB case 1, segment 74 as default test data.

🧪

No test results yet

Click "Run Test" to evaluate your rule against sample data

📋 Rule Library

⚡ Conditions

🎯 Actions

👁️ Preview

🧪 Rule Testing