Skip to content
Clinloop docs

Overview

Clinloop is a B2B healthcare shift staffing platform for Ontario. Facilities post shifts, verified workers accept them via a two-tier booking engine (preferred agency pool → open marketplace).

This site is the internal reference for the team building it. It is the single index for:

  • repo orientation and local-dev setup
  • the architecture of the booking engine and adjacent systems
  • the live API contract (auto-generated from the OpenAPI spec)
  • the data model (auto-generated from the Drizzle schema)
  • runbooks for common operational tasks
  • the audit-log catalog and PHIPA-aligned compliance notes
  • the design system shared across web apps and mobile

Audience

You are an engineer or compliance reviewer with access to the staging environment. Customer-facing marketing copy lives at clinloop.ca; operational dashboards live in the admin portal at admin.clinloop.ca.

Where to start

Local development Get the stack running on your machine — Docker, Postgres, Redis, all five apps.
Repo orientation What lives where in the monorepo, and why.
API reference The live OpenAPI spec, rendered.
Audit overview How PHIPA accountability is enforced in code.

Conventions used in these docs

  • Code blocks are real. If you see a make target or pnpm script, you can run it verbatim.
  • File paths are absolute from the repo root.
  • Asides call out things you can break:
    • note — context, no action needed
    • tip — a shortcut
    • caution — read this before doing the thing
    • danger — destructive operation; double-check