Alerts Use Cases (ALR)

UC-ALR-001: Evaluate Critical Lab Alerts

Purpose: Implement MVP-required rule-based alerts for critical labs.

Property	Value
Actor	Alert Engine
Trigger	New lab result ingested
Priority	P0

Main Success Scenario:

1. Read incoming lab Observation
2. Check LIS "critical" flag OR compare value against configured critical ranges
3. If critical → create `alert{type: "critical_lab", value, test, timestamp}`
4. Store alert in bundle `alerts[]`
5. Mark alert as "informational, non-CDS" as per MVP constraint

Acceptance Criteria: 1. [ ] Zero silent failures — every lab must be evaluated 2. [ ] Critical alerts visible on patient Summary + Timeline 3. [ ] Rules must be configurable per site

---

UC-ALR-002: Detect Rapid Weight Loss

Purpose: Implement MVP-required alert for rapid weight loss.

Property	Value
Actor	Alert Engine
Trigger	New weight/vitals observation
Priority	P1

Main Success Scenario:

1. Retrieve last N weight values (e.g., 30 days)
2. Compute Δ% weight change
3. If Δ% exceeds configured threshold (e.g., >5% in <30 days):
   - Create alert {"type": "rapid_weight_loss"}
   - Attach to patient bundle
   - Sync to alerts panel and UI Summary

Acceptance Criteria: 1. [ ] Alert applies only when at least 2 data points exist 2. [ ] Threshold configurable per hospital 3. [ ] Must not override past alerts; all alerts timestamped