Antelope Valley · Coordination Dashboard
What's happening in the region, right now.
Demand by city, service-type gaps, HHAP spend velocity, pending discharge handoffs, and partner-network status. One screen for county health staff, coordinating-body directors, and elected offices — populated with realistic seeded data for demonstration. Production hooks up to Bitfocus Clarity HMIS and county Sheriff / BH systems.
Antelope Valley — building our baseline
We're standing up the Antelope Valley program. Early figures here reflect the platform, not yet a full local count for the Antelope Valley. Numbers will fill in as we verify resources and build on the ground across Lancaster and Palmdale.
Active alerts
Demand by city (last 24h)
| City | Requests | Capacity | Trend |
|---|
Service-type gaps (current shift)
HHAP spend velocity (last 4 quarters)
Antelope Valley HHAP spend and earmark figures are being gathered. The load-bearing spend gap is why outcome tooling matters this quarter — HHAP-6 second-half disbursement is conditional on closing it.
Pending discharge handoffs (next 72h)
| ID | Source | Release at | Population | Bed | BH appt | MAT | Status |
|---|
Production view pulls from Sheriff release roster + Behavioral Health discharge planner + Bitfocus Clarity bed inventory.
Live activity (today)
Last 30 days
- Meal credits redeemed
- 0
- Partners onboarded
- 1
- Tier 1 users
- 0
- Tier 2 users
- 0
- Tier 3 users
- 0
- Warm handoffs completed
- 0
- Handoff success rate
- 0%
Wizard funnel (start → submit)
HMIS UDE 4.14 — Project Services. Counts of doc_submissions by status over the week window.
- Started
- 0
- Submitted
- 0
HHAP velocity (by form × month)
HMIS UDE 4.14. HHAP-eligible doc_submissions grouped by month.
No HHAP form submissions yet in this window.
CalAIM-Reentry encounter counts
HMIS UDE 4.14. CalFresh-SAWS + Medi-Cal partner-routed.
- calfresh-saws
- 0
- medi-cal
- 0
Email health
From email_log (migration 0021). Transactional sends only.
- Sends
- 0
- Bounce rate
- 0%
- Complaint rate
- 0%
Notification preferences distribution
From notification_preferences (migration 0022). Trauma-informed opt-in defaults — most categories OFF by default.
- Total users with prefs
- 0
- Email opted in
- 0
- SMS opted in
- 0
- Push opted in
- 0
- Paused all
- 0
Redemptions + earn attestations
Guardian-internal. Donation-code redemptions (personal_donation_codes used_count sum) + earn_attestations (caseload-confirmed earnings).
- Donation-code redemptions
- 0
- Earn attestations
- 0
Partner-side participation
Counts of users with partner_admin / partner_staff app_role.
- Partner admins
- 0
- Partner staff
- 0
Privacy incidents
From audit_log event_type LIKE ‘incident.%’. We publish zero or non-zero — both are signal.
- Incidents in window
- 0
Resource map clicks
Future: requires PII-stripped client-side analytics (we don't pixel).
211 + 988 cross-link rate
n/a — instrumentation pending
Demand-by-city, service-gaps, spend-velocity, pending-discharges, activity feed, and alerts go live once the upstream pipelines land (help_requests, service-gap derived view, county_finance_quarterly, discharge_intakes, activity_events, ops_alerts).
Who sees this dashboard
The view above is aggregate and de-identified: counts by city, by service type, by status. No PHI on this page. Where a specific discharge event surfaces below (the "Pending discharge handoffs" table), the IDs shown are workflow IDs, not personal identifiers — and the full per-record handoff workflow with PHI lives at /dashboard/discharge, gated by role-based access control.
This dashboard · aggregate view
HHS analysts · JPA staff · supervisor offices · partner-org leadership · the public (this is the demo URL)
County rollups · city-level demand · capacity bars · spend velocity · status counts. No PHI.
Per-record handoff workflow
Assigned case manager (full) · BH coordinator (population-scoped) · HHS Director (break-glass with reason code)
Full PHI on assigned records · row-level RLS enforces scope · every read logged
See full visibility matrix →Confidential (VAWA) records
FJC navigator + survivor only · NEVER joined into HMIS or this dashboard
Comparable Database operated by FJC under 24 CFR §578.103(b) · VAWA 34 U.S.C. §12291(b)(2) + FVPSA 42 U.S.C. §10406(c)(5) + VOCA confidentiality · separate audit log
When Guardians of the AV operates as a Business Associate to a Covered Entity (45 CFR 164.500(c)), production deployment will require a signed Business Associate Agreement with every covered entity (e.g. LA County DHS/DMH, the county Sheriff's jail-medical contractor, the regional Medi-Cal managed-care plan, Bitfocus Clarity HMIS Lead) before any PHI flows. Encryption: TLS 1.3 in transit, AES-256 at rest. Minimum-necessary enforced via Postgres Row-Level Security policies (Built, alpha). Audit log is append-only, hash-chained, and retained 6 years (HIPAA minimum, 45 CFR 164.316(b)(2)). Full HIPAA posture →