Response plan

VA Medical Center — Strain & Capacity Console

operator early-warning template · decision-support, not autopilot
—

Facility strain index DEMO DATA

Composite 0–100 from unit occupancy, staffing gap, ED boarding and access pressure. A watch tool — clinical judgment decides. Replace demo values with your facility's live feeds via the operator hook (below).
—

Unit strain ranking DEMO DATA

Each unit's strain score (worst first), with occupancy and the primary driver. ⚑ = operator override active. Mirrors the St. Pete station-criticality ranking.

Emergency Dept & patient flow DEMO DATA

The usual strain epicenter: boarding (admitted patients held in the ED for want of an inpatient bed), walkouts, and diversion.

Mental-health access DEMO DATA public anchor available

A VA-specific priority. New-patient wait, same-day demand, and inpatient psych occupancy. Published facility wait times (access.va.gov) can anchor the wait metric; live in-day demand is operator-supplied.

Charge-nurse / administrator readout

Auto-written plain-language summary of current strain and the top pressures.

Staffing coverage DEMO DATA

Actual vs target RN coverage by unit; red = understaffed. Live nurse-staffing/float data is internal — wire via the hook.

Surge scenario sandbox

Pressure-test the response plan: pick a scenario to see how strain propagates. Clearly a drill on synthetic data — never live.

Operator hook — wire your live feeds

How to make this real (no code edits to panels)

Real-time strain (census, ED boarding, RN staffing) is internal to VHA and not public, so this console ships with clearly-labeled DEMO data. To make it live, push your facility's numbers into the global override object from your own scheduled job / dashboard backend — no edits to the panels needed:

STATUS_OVERRIDE['ICU'] = {census:18, cap:16, rnAct:7, rnTgt:8, tier:'alert'};
STATUS_OVERRIDE['ED'] = {board:22, lwbs:6.0, divert:true}; then call render().

Keys are the unit IDs shown in the ranking (ED, ICU, 3W, 4E, MH, CLC, OR). Any field you supply overrides the demo value; fields you omit keep the demo. A tier:'alert'|'watch' flag forces that unit's escalation. Public anchors (VA Access-to-Care wait times, facility list/quality via api.va.gov Facilities API — note: that API needs a free key) are lagged and best baked as the baseline, with the operator hook carrying the live tail.

Data health

What's live vs demo vs operator-supplied. A single feed failure never blanks the console.