Skip to main content

​
Configuration

All CL-35 configuration is stored in cl_module_settings.custom_fields under the population_health key, scoped per organization.

​
Care gap thresholds

Jurisdiction note (PF-96): These thresholds are clinical defaults, not state-Medicaid mandates. If a state defines stricter timeliness requirements, the values are overridden via the org’s PF-96 jurisdiction profile (useJurisdictionProfile(siteId) on the frontend; pf_resolve_jurisdiction_profile() in edge functions). Arizona AHCCCS is the default profile, not a universal default.

​
Risk stratification weights

Weights MUST sum to 1.00. The risk engine validates and rejects configurations that violate this constraint. When MOUD is excluded (no consent or no MOUD enrollment), its weight is redistributed proportionally across the remaining components.

​
Risk tier thresholds

A patient with a composite score ≥ high is “critical”; ≥ medium is “high”; ≥ low is “medium”; otherwise “low”.

​
Feature Flags

Configured in pf_feature_flags:

​
Cron / Scheduled Jobs

All cron functions are deployed via Supabase Edge Functions and use createCronHandler from _shared/cron-handler.ts.

​
HEDIS / MA STARS Measure Definitions

Measure definitions live as versioned JSON under supabase/seeds/cl_hedis_measure_definitions/. Each annual NCQA spec update is added as a new variant rather than overwriting prior years to maintain auditability. FUH/FUM are consumed from CL-29-EN-65 and not re-implemented in CL-35. To add a new measure year:
  1. Update the relevant JSON file with a new effective_year variant.
  2. Re-deploy cl-hedis-calculator (no schema migration needed).
  3. Re-run the calculator for any year requiring re-computation.

​
Permissions

CL-35 ships these permission keys (registered in PF-30):
  • cl.care-gaps.view
  • cl.care-gaps.close
  • cl.risk-stratifications.view
  • cl.population-dashboard.view
  • cl.quality-measures.view
  • cl.quality-measures.export
Assign to roles via Settings → Permissions.

​
Compliance Controls (built-in)

See REGULATORY_COMPLIANCE_TRACKER.md for current status.