One engine, many clinical areas: how pathway packs work

We don't build a separate tool for every service. One reasoning engine, many pathway packs, each validated on its own.

Published

Health services share a common problem: generalist clinicians making specialist-level decisions, often in a single appointment. The details differ from one service to the next, but the shape of the work is similar. That's why we built one reasoning engine and deliver it as pathway packs.

What is a pathway pack?

A pathway pack holds what's specific to one clinical area:

  • the referral and triage criteria for that service
  • the rules that apply them
  • the clinical guidance the reasoning draws on
  • the tests we use to check it

The engine underneath stays the same. It reads the case, finds what matters, explains why and leaves the decision to the clinician.

Why build it this way?

  • Consistency. Every clinical area gets the same safeguards: citations, abstention and clinician sign-off.
  • Focus. Each pack is shaped by clinicians who work in that area, together with independent specialty advisers.
  • Room to grow. A new clinical area means a new pack, not a new product.

Validated one at a time

A shared engine doesn't mean shared approval. Each pack has its own intended purpose and is validated separately before it is released. We take areas forward one at a time, assessing need, NHS priorities, data access, safety requirements, how quickly we can produce evidence, partner commitment and equity.

See the clinical areas we're developing.

← All insights