Skip to content

Critical risk threshold mismatch: 75 in population dashboards vs 80 in alerts #54

Description

@manjula25

Summary

"Critical" risk means 75 on the population dashboards but 80 in alerts — the two Director surfaces disagree about who needs immediate review.

Evidence

  • apps/api/src/alerts/service.ts:37CRITICAL_THRESHOLD = 80
  • apps/api/src/fhir-data/population.ts:22CRITICAL_RISK_THRESHOLD = 75, used by getPopulationSummary / bucketFor

Impact

A patient with riskScore 76-79 lands in the "critical" bucket on GET /api/population/summary and risk-distribution, but GET /api/alerts classifies them only as "high" — inconsistent triage signal on exactly the decision these dashboards exist to support.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions