Nimbli clinic software

Nimbli is practice software for counselling clinics: scheduling, charting, telehealth, invoicing and counsellor pay in one system, hosted in Canada. I built it from staff requests to production.

Product
Nimbli, my own product
First client
A Vancouver counselling clinic
My role
Lead developer, end to end
Timeline
2024 to now

Visit nimbli.ca

The problem

A counselling clinic needed one system for bookings, clinical notes, insurer billing and counsellor pay, that staff could trust with records and with money.

Every handoff between separate tools is a place where a session, a bill or a paycheque can go missing. Health records also had to stay in Canada, under BC and federal privacy law.

The product had to serve more than one clinic without ever mixing their records.

What it does

  • Scheduling with two-way Google and Outlook calendar sync
  • Charting with row-level security
  • Telehealth video with a consent gate
  • Insurer and victim-services invoicing
  • Stripe Connect payments
  • Counsellor pay and reconciliation

My role

I lead the product end to end: the client conversations, the data model, the back end, the front end, the AWS hosting and every release.

About 1,800 of the project’s 1,900 commits are mine. I direct an AI-agent workflow for much of the typing, and I own the design, review and testing.

Decisions

  • One database for each clinic

    Each clinic gets its own Postgres database, created automatically in a Canadian region. Each clinic can be backed up, restored or removed on its own.

    The cost is running every migration on many databases, so each deploy takes a backup first.

  • Let the database enforce who sees what

    Postgres row-level security decides which rows a user can read or write, even if the application code has a bug. A 13-case cross-tenant test suite checks it, and it found and closed a real write leak.

    Reports must respect the same rules, so they take more care to write and to test.

  • Bill each session exactly once

    I reproduced a duplicate-billing race in a three-thread test. The fix: the invoice scheduler takes a Postgres advisory lock to elect one leader, and a unique partial index refuses a second bill.

    A skipped run must be safe to retry, so the job can run again without side effects.

    Insurer invoice run 0 duplicates
    02:00:00 worker-a  advisory lock acquired
    02:00:00 worker-b  lock held, run skipped
    02:00:03 worker-a  18 invoices written
    02:00:03 worker-a  unique (session, payer) ok
    02:00:04 worker-a  lock released
  • Consent before every video session

    Telehealth video opens only after the client gives consent, and the consent is recorded with the session.

    A small extra step for clients, in exchange for a clear record.

Results

  • 337sessions where counsellor pay had been missed, found across 51 counsellors by a reconciliation report
  • 1×each session is billed once, enforced by a lock and a unique index
  • 4,714automated tests pass on the onboarding module alone: 4,079 back end and 635 front end
  • 73of 120 screens fixed for WCAG AA contrast, with a 137-token design system

Tech

Back end
Python, FastAPI, SQLAlchemy, Strawberry GraphQL, Redis
Data
PostgreSQL with row-level security, about 55 tables
Front end
React 19, Vite, TypeScript, a 24-component design system
Cloud
AWS EC2, S3, SES, ECR and Route 53, GitLab CI
Services
Stripe Connect, Daily.co video, Google and Microsoft calendars

Next case study

Radiology report screen

The report screen of a medical-imaging product on the FDA 510(k) path, built as the sole front-end developer.

Read the case study

Hiring for a remote role in Canada? Tell me about it.

This opens your email app with your note, addressed to me.

Email
ekamxjot@gmail.com
Resume
Full-stack engineer resume (PDF)
Elsewhere
LinkedIn · GitHub