Clinician-built healthcare technology

Healthcare AI should not simply be delivered to clinicians. It should be shaped by them.

Surgeon-led tools, built around real pathway friction — locally adaptable, tightly governed and accountable by design.

Explore
01Clinician-led
02Bounded
03Validated
04Auditable
05Useful

Built from inside the pathway

The people closest to the work should define the tools that change it.

Generic platforms begin with what technology can do. We begin with the missed action, the fragmented handover and the real clinical constraint.

Local ownership means faster learning and more useful tools. Strong governance means every role, output and limit stays explicit as those tools evolve.

AI can assist, coordinate, summarise and automate bounded tasks. Accountability does not move.
Local pace
Clinical control

Three tools. One philosophy.

Built for the friction that teams actually feel.

01Prototype · pathway support

My Foot Care

Close the loop around the diabetic foot pathway.

  • Patient photo check-in
  • Four fixed-rule questions
  • Patient & clinician views
  • Stage-by-stage governance
Governance position

Research/demo only. A bounded photo-usability check is non-clinical; any urgency band or routing used in care would require Tier 3 governance and validation.

Open demonstration
02Research planning software

CT Splicer

CT Orthopaedic Surgical Planner

A surgeon-facing way to see, link and plan from DICOM.

  • DICOM-based workflow
  • Linked multiplanar CT + 3D
  • Surgeon-facing planning
  • Research / planning status
Governance position

Not validated for patient care. If used to inform clinical planning, it would require Tier 3 governance.

Open demonstration
+

An extensible portfolio

More clinician-built tools will follow.

New tools start with a named pathway problem, a bounded purpose and a governance position — not a technology looking for somewhere to land.

Not bolted on later

The level of assurance follows what the tool does — not what it is called.

A simple interface can carry clinical consequence. A sophisticated model can remain low risk when its authority is tightly bounded and every output is reviewed.

Tier 1

Human-reviewed

No deep systems integration. Every output is reviewed by a person before use.

Typical assuranceStandard IG review · Trust AI-use policy
Tier 2

Operationally integrated

Connects with EPR, booking, theatre or diagnostic systems to coordinate bounded workflow tasks.

Typical assuranceDPIA / IG per data flow · DCB0160 where outputs enter the record · Integration engineering
Tier 3

Clinically influential

Any function that informs a clinical decision, regardless of how simple the interface appears.

Typical assuranceDCB0129 / 0160 · Named CSO · Shadow-mode validation · DPIA / Caldicott · DTAC · MHRA SaMD assessment where applicable
Important

App-level classification is function-specific. One product may contain Tier 1, Tier 2 and Tier 3 functions; each function should be governed according to its data flows, integration and clinical influence.

Local iteration, controlled release

Change quickly. Know exactly what changed.

01

Define the friction

02

Bound the task

03

Validate in shadow mode

04

Release with approval

05

Monitor, learn, version

Bespoke does not mean uncontrolled. Every iteration can have a clear owner, intended use, evidence threshold, audit trail and route to stop.

That is how local ownership and rapid learning coexist with strong clinical safety.

For clinical teams and hospital leaders

Bring us the pathway problem.

We will start with the people doing the work, define the smallest useful tool, and build the governance alongside it.

Contact details will be added before public go-live.