About us
Built so that care doesn't fall through the gaps between systems.
Most of what goes wrong in an outpatient journey happens in the handoffs — between booking and consultation, between a doctor and a laboratory, between one visit and the next. Carepath is built around those handoffs.
The problem we started from
Records that don't travel
A patient's prescription lives in one place, their laboratory result in another, and their history in a folder they carry. Every new consultation starts by reconstructing context that already exists somewhere.
Access decided informally
Where systems do share data, they often share too much. Carepath treats each access as a decision to be evaluated and recorded, rather than a door left open once someone has logged in.
What we build on
These principles decide the design when there is a trade-off to make.
Fail closed
When an external provider or an integration is not configured, the platform refuses the action rather than guessing or silently degrading.
Consent is a record
Consent is captured server-side as part of the booking, tied to the episode of care, and can be withdrawn.
Least access
Every request is checked against role, organisation, care relationship, and consent. A session grants a scope, never blanket access.
Auditable by default
Access to clinical data and changes to verification state are written to an audit trail administrators can review.
One record, many surfaces
Patient, doctor, laboratory, and administrative views read the same underlying record instead of keeping their own copies.
Tenant-aware
Organisations, locations, and laboratories are first-class, so access is scoped to the institution a user actually belongs to.
Where the platform is today
Carepath covers the full outpatient path today: one-time-code sign-in, a booking draft that captures consent, appointment and check-in states, the clinical encounter with prescriptions and investigation orders, laboratory specimen and result handling, clinician review, and follow-up booking. Role-based access, the clinician verification lifecycle, and the audit trail are in place across all four surfaces.
External integrations are enabled per deployment rather than assumed. Messaging, payment, laboratory partner, and health-record integrations are configured for each clinic, and the platform refuses to use an adapter that has not been approved for that environment. Features still being rolled out — including video consultation, counselling, and subscriptions — sit behind server-owned flags, so a clinic only ever sees what has actually been enabled for it.
Talk to us about your clinic
If you are evaluating Carepath for a practice or a laboratory, sign in to the relevant workspace to walk the flow end to end.