iCanHeal

The system

iCanHeal is a patient-facing healthcare product. Healthcare means the boring constraints are the important ones: identity has to be exact, permissions have to be provably correct, and nothing can silently drop a record.

I designed and own the backend end to end.

What I built

API layer. Django + DRF, versioned, with a permission model that resolves per-resource rather than per-endpoint — so a new endpoint inherits the right access rules instead of re-deriving them and getting them subtly wrong.

Auth. Token lifecycle, refresh, device sessions, and role boundaries between patient, practitioner and admin surfaces.

Background work. Celery + Redis for anything that must not block a request: notifications, document processing, scheduled jobs, retries with backoff.

Data layer. Postgres schema design and ORM optimisation — killing N+1s, adding the indexes the query planner actually wanted, and moving aggregate work into the database where it belongs.

Production. AWS, Nginx, Gunicorn, deployment pipeline, monitoring. I run it, which means I find out first when it breaks.

AI features. LLM integrations and agent workflows for assistive features, increasingly built on MCP tooling.

Leading

I lead a team of 10 across backend, mobile and QA. The part that took real effort wasn’t the architecture — it was making the interfaces between those three groups boring enough that they could move independently.

I make product calls too. I care whether the feature is right, not just whether it compiles.