Benchmark Hospital
A comparable view of every hospital site against a benchmark hospital, so hospital directors see the real need before a decision about a site's role is made. Prototype with illustrative demo data.
Stack: Next.js 16 (App Router), React 19, Tailwind 4, Recharts, Supabase (Postgres).
Set up
- Supabase: create a project, open SQL Editor and run, in this order,
supabase/migrations/20261026000000_init.sql (schema) and supabase/seed.sql (synthetic data: 18 sites × 12 quarters plus departments, monthly activity, operating rooms, cost split and patient catchment). Both are safe to re-run; seed.sql resets the data to the demo set.
- Keys: Project Settings → API → copy the project URL and the
service_role key into .env.local (see .env.example): SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY. The key is server-only; row level security is on with no policies, so the public anon key can read nothing.
- Run:
npm install
npm run dev # http://localhost:3000
npm test # domain logic + dataset consistency tests
Deploy on Vercel
Import the repo at vercel.com/new, then add the Supabase integration (Storage → Supabase) or set SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY under Settings → Environment Variables. Redeploy. Data lives in Supabase, so saved sites persist.
Data
npm run db:sql regenerates supabase/seed.sql from lib/demo/generate.ts (deterministic; edit the site profiles there to change the demo network).npm run db:seed loads the same data through the API instead (needs the keys in .env.local).- Detail tables reconcile with the quarterly snapshot: department beds add up to the site's beds, monthly bed-days to the quarter's occupancy, cost categories to facility cost × floor area.
Loading real data
- Fill
data/import-template.csv — one row per site and quarter.
npm run db:import -- yourfile.csv --replace (--replace removes the demo sites and their detail data).- Edit benchmark values and decision thresholds in the
benchmark_values and settings tables (Supabase Table Editor).
Pages
The app is a director view of one hospital, with a navigation bar on every page:
/ — opening page: My hospital, What if scenarios (under construction), Log in as demo hospital (all data filled in)/hospital — pressure overview (beds, staff, cost, energy → links), action plan, graphs over time/patients, /wards, /staff, /energy — detail pages; wards and staff include a map of other hospitals (public, anonymous)/compare — the hospital's wards against each other, ward capacity of other hospitals, ranking at the bottom/scenarios — what-if scenarios (under construction); holds the ward closure dashboard/benchmark — the benchmark as a theoretical hospital on paper/upload — one place to upload data: pick dataset → empty template → CSV → preview → plain-word check/profile — hospital profiles (each hospital has its own)
Director data lives in lib/hospital/: one department list (departments.ts), one 12-month period (period.ts), the upload datasets and checks (datasets.ts), the derived view every page reads (derive.ts — a number is uploaded once and only displayed elsewhere), the demo hospital (demo.ts) and anonymous other hospitals (others.ts). Profiles and uploads are kept in the browser (store.ts) in this prototype. Benchmark values and decision rules still come from Supabase; without Supabase keys the built-in placeholder values are used, so the director pages also run locally without a database.
The old /data URL redirects to /upload and /sites/* to /hospital. npm run build:closure-preview writes a self-contained public/closure-preview.html of the closure dashboard. The "build a hospital" forms (components/flow/BuilderForm.tsx, BuildSizing.tsx) are kept for a separate page later.
JSON endpoints: /api/sites, /api/sites/[slug], /api/sites/[slug]/stats, /api/benchmark.
Layout
lib/domain/ — pure scoring, scenarios and recommendation logic (shared by server and browser)lib/db/ — Supabase client and repository; lib/demo/ — synthetic dataset generator; supabase/ — schema and seed SQLapp/ — pages and API routes; components/ — UI and chartsscripts/ — seed, SQL generation and CSV import; tests/ — unit tests
Next.js 16 has breaking changes vs. older versions (async params/searchParams, request-time rendering rules); see AGENTS.md.
