a rehab centre's wholeback office, in onerole-aware console
Paper files, spreadsheets, and WhatsApp ran a treatment centre in Bangladesh. Now one console does — and every action has a name on it.
How has the business benefited after the software ?
2025
2026
SINGLE SOURCE OF TRUTH
One console. Every admission, payment, stage change and document — recorded against a named user.
six layers, each a real handoff
Every arrow is a place the request changes hands. The Edge is one proxy.ts; Data-layer transactions keep two admissions from minting the same ID.
clinical assessment engine
From intake to discharge, every clinical stage is tracked against the patient record — assessments, diagnoses, treatment plans, and progress notes live in one place.
request flow
A single patient lookup travels six layers before it renders. Each layer has one job, one guard, and zero shared state.
Appendix · Roadmap
what ships next
Firestore listeners
Live data for two staff on one record — the cache and limiter are already sized to absorb it.
Multi-clinic tenancy
A clinicId on every document plus a tenant-aware proxy check — one deployment, several centres.
E-sign intake
Sign the CMS admission form on a lobby tablet — the PDF and storage path already exist.
Auditable on day one. Extensible on day one hundred.
Built end to end for a real clinic — architecture, backend, frontend, infra, docs.