Healthcare Systems Engineer

Operational healthcare systems, built from inside the workflow.

I spent years on hospital and rehab floors before I wrote the software for them.

Clinical workflows · Backend systems · Applied AI

Vancouver, BC · Live · 4 VCH sites

Laptop showing the capacity_service.py code editor split with a Sites overview panel listing four Vancouver Coastal Health sites, surrounded by a capacity trend chart, a discharge workflow status card, sticky notes reading 'People first. Systems second.' and a clinical-needs-to-better-outcomes flow, a hand typing on the trackpad, and a notebook sketch of the operational flow next to a 'Built with: Python, FastAPI, PostgreSQL, Redis, React' note.

4

Hospital sites · live deployment

800+

Assets tracked in production

498

Automated tests across 5 systems

9+

Years in healthcare operations

Currently available

Vancouver, BC · Open to healthcare systems, backend, and applied AI engineering roles — remote, hybrid, or on-site

Start a conversation

Core capabilities

Built across the stack hospitals run on.

Four capability clusters — built on real clinical operations.

Clinical Operations Intelligence

  • Hospital workflow optimization
  • Rehabilitation operations
  • Equipment tracking systems
  • Operational analytics

Applied AI & Data Systems

  • SQL · Python · R
  • Prompt engineering · LLM workflows
  • Structured data extraction
  • AI-assisted automation

Analytics & Visualization

  • Tableau · Power BI
  • Time-series analytics
  • KPI & operational reporting
  • Data storytelling

Application Development

  • React · Next.js · TypeScript
  • FastAPI · PostgreSQL
  • Cloud deployment
  • Production-grade UX

Featured work

Four systems where the hard part was in the data layer: tenant isolation, encrypted-but-searchable identity, an append-only ledger, and retrieval that knows when to refuse.

View all projects
Flagship system · Live deployment
ProductionCase Study

Multi-Tenant Clinical Equipment Tracking

Running across 4 Vancouver Coastal Health sites, tracking 800+ wheelchairs and clinical assets through an 11-state lifecycle the database enforces directly — so a transition that skips a step, or a role that is not permitted to make it, simply cannot be written.

  • Live across 4 Vancouver Coastal Health sites, tracking 800+ assets
  • An 11-state request lifecycle whose transitions are gated by role in the database
  • Postgres row-level security isolating every tenant, enforced below the API
  • QR scanning driving intake, assignment, and return from the floor

React · Vite · Supabase · PostgreSQL · Row-Level Security · Edge Functions · QR workflows

Read the case study

Request lifecycle · 11 states

  1. Requested
  2. Acknowledged
  3. Searching
  4. Waiting
  5. On Hold
  6. Assigned
  7. In Use
  8. Discharged
  9. Completed
  10. Cleaning
  11. Available

Enforcement path

QR Scan
RPC
State + Audit
Tenant RLS
Dashboards

4 sites

live deployment

800+

assets tracked

11

workflow states

243

test files

AI tools

ClaudeOpenAIGeminiCursorGitHub CopilotAntigravity

Stack

SQLPythonRTableauPower BINext.jsTypeScriptFastAPIPostgreSQLPower PlatformMicrosoft ListsQR / barcode workflows

Let's build the next healthcare system.

I'm running a multi-site hospital equipment-tracking and analytics system in production, and I'm open to healthcare data, analytics, AI, and application engineering roles — remote, hybrid, or on-site. The best way in is a short conversation.

Start a conversation

Find me on