a rehab centre's whole back office, in one role-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.

View live demo TIMELINE2025 – 2026

STACK: (Next.js 16) · (React 19) · (Firestore) · (Bunny CDN)

▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚

How it has made the client benefited?

BEFORE — 2024

Paper patient files

Ad-hoc spreadsheets

WhatsApp threads

Hand-written receipts

No audit trail

→

AFTER — 2025

One console. Every admission, payment, stage change and document — recorded against a named user.

SINGLE SOURCE OF TRUTH

▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚

System Architecture :

Six-layer architecture diagram — Client, Edge, Application, API, Data, Infrastructure

Every arrow is a real handoff: the client proves identity, the edge verifies the app JWT, the application queries Firestore, the API enforces five guards, and the data layer keeps two admissions from minting the same ID.

Clinical Assessment Engine :

Hand-drawn clinical assessment flow — patient background, substance use, motivation and admission stages

Patient background, drug-use history, and the Prochaska stage-of-change — captured in one structured clinical form that feeds the rest of the patient record.

Request flow :

Firebase proves who you are; an app-minted HS256 JWT (httpOnly, 8 hours) decides what you can do; every API route re-verifies permission before touching data.

▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚▚

the console

Fera login screen — Firebase Auth proves identity; an httpOnly HS256 JWT decides what you can do.

Fera dashboard with KPI cards and charts — One server query, every KPI — each with a delta against last month.

Fera patient list with status pills — FERA-2026-00010 — IDs minted inside a transaction, so two admissions can't collide.

Fera documents folder grid — CDN-backed file manager — 200 MB max, enforced at the API layer.

Fera payments ledger with receipt rows — Nine fee categories, one receipt. The full ledger, printable per row.

Fera reports and analytics charts — Any time window, re-rendered — donut, stacked bar, and a 12-month trend.

Fera roles and permission matrix — Two roles, one 20-string permission matrix — per-user overrides on top.

Fera activity logs audit table — Every mutation writes a row. Even the purge leaves a trail.

Clinic profile

Clinic identity plus the default permission set every new staff account inherits.

Fera settings — activity log retention card — 180-day default retention. Purge is gated and itself audited.

Fera CMS patient history PDF viewer — Clinical assessment as a printable PDF, built from the patient record.

Fera payment receipt PDF — Signed receipt on demand — counter-minted number, amount-in-words computed live.

Looking for a production-ready admin console or architecture?

Get in touch