Before anything is built, we need to understand what actually happens.
What we inspect is not the pathway in the abstract. It is the exchange: the moment where responsibility, evidence, clinical intent, and obligation actually move between people, teams, or organisations. That is where risk becomes real, and where clinicians are already compensating for what the formal system fails to hold.
Pathways describe sequence. Risk lives in exchanges.
A urology pathway looks sequential on a diagram: GP assessment, drug trial, diagnostics, surgical decision, post-operative care, community follow-up. But diagrams describe sequence. They do not describe the exchange conditions at each transition, where responsibility state, evidence completeness, consent scope, and alert obligation are tested and frequently found wanting.
- Defined roles at each stage
- System integrations documented
- Referral and discharge protocols in place
- Alert obligations nominally assigned
- Sequential, predictable flow
- Responsibility state undefined during pending acceptance
- Evidence arriving with no designated action owner
- Clinical intent shifting without consent confirmation
- Obligation continuity broken at discharge
- Alert responsibility ambiguous between concurrent holders
The assessment inspects exchange points, not pathway steps.
Within a defined pathway slice, we examine every micro-boundary where the formal pathway stops explaining what clinicians are actually doing. Not the system-to-system integrations. The moments where responsibility transfers without bilateral confirmation, where evidence arrives without a clear action owner, where clinical intent shifts without documented consent, where alert obligation falls between two holders and neither knows it.
These are the exchange conditions the assessment surfaces. Each one is a question the formal system never answered.
Responsibility without a holder
Referral sent, not yet acknowledged. The GP's obligation has not formally ended. The hospital's has not formally begun. The patient exists in a governed gap.
Result without action ownership
A dip test result arrives outside a scheduled appointment. It sits in a system. No clinician is expecting it. No obligation to act on it has been assigned.
Investigation becomes intervention
Clinical intent moves from diagnostic to surgical. The patient's consent scope may not extend to it. The transition is real but undocumented in governance terms.
Discharge without obligation transfer
The surgical team releases the patient. What evidence travels with that release, what stays in the hospital record, and what the GP is expected to act on without having seen.
Overlapping responsibility
Post-operative consultant and GP both holding some version of responsibility. Neither has a clear alert obligation if the patient deteriorates between appointments.
Deterioration after the last handover
Complications at home, weeks after the formal pathway ended. No designed exchange exists for this moment. The patient's safety depends on informal action.
The assessment maps all of it. Including the exchange conditions nobody has written down.
Workarounds reveal what the system structurally fails to encode.
Spreadsheets tracking referrals the system does not follow. Personal notes covering handoffs that are not recorded. Text messages between colleagues to cover what the alert system does not catch. These are not local messiness. They are evidence of stable, recurring truths about exchange conditions the formal system has never encoded.
Pending acceptance. Unowned result action. Undocumented transfer of intent. Overlapping alert obligations. Informal continuity practices. The same exchange failures appear wherever responsibility crosses organisational lines. Clinicians compensate for them because the system does not.
Those recurring truths are what infrastructure must hold. That is what the assessment discovers.
Applications sit on top of workflows. They assume the workflow is correct and the handover is clean. Infrastructure has to hold when responsibility shifts, evidence is incomplete, and the formal pathway no longer explains what clinicians are actually doing.
The assessment does not produce requirements for an application. It discovers the exchange conditions that infrastructure must govern. That is the distinction.
Three outputs. Each one a build input.
The assessment does not recommend technology or propose a system architecture. It produces the specification that infrastructure is built against: the exchange landscape, the governance priorities, and the boundary that gets implemented first.
Exchange map
Every point where responsibility, evidence, and obligation move between people, roles, and organisations. The current state of each exchange documented honestly, including where no clear answer exists.
Defines the exchange landscapeRisk analysis
Where responsibility state is undefined, where alert obligations are unassigned, where evidence arrives without action ownership. Grounded in what clinicians reported and what the exchange map revealed.
Prioritises where governance must holdLighthouse specification
One boundary, precisely scoped, where exchange conditions are demonstrably ungoverned, clinical motivation is present, and scope is narrow enough to implement as governed infrastructure.
Defines one buildable governed boundaryThe right candidate has a specific exchange problem, not a general one.
You know where the exchange breaks
- A specific handover is causing demonstrable difficulty
- Clinicians can describe the compensation they perform
- Responsibility, evidence, or obligation is unclear at a defined boundary
- The organisation is motivated to govern what is currently informal
- You want to understand the exchange before committing to a solution
These are different engagements
- Broad digital transformation without a defined boundary
- System procurement or vendor selection
- Compliance audit or regulatory assessment
- Organisation-wide process mapping
- Application development for a clean workflow
Eight weeks. Exchange discovery to buildable specification.
The engagement produces outputs, not recommendations. It ends with a specification that is either built against or not. That decision remains with the organisation.
Boundary scoping
Define the pathway slice. Identify the exchange points. Agree what is in scope and what is not.
▶Exchange inspection
Inspect every micro-boundary. Capture workarounds. Document the exchange conditions clinicians are compensating for.
▶Risk prioritisation
Where is responsibility state undefined, where are alert obligations unassigned, where has harm occurred or nearly occurred at an exchange.
▶Specification
One boundary. Precisely scoped. The exchange conditions that must be governed, defined as a buildable implementation brief.
The specification becomes the lighthouse scope.
Organisations that proceed from assessment to lighthouse implementation carry the specification with them. The exchange conditions the assessment discovered become the governance requirements the lighthouse implements.
The lighthouse governs one boundary. Responsibility transfer becomes bilateral. Evidence state becomes verifiable. Alert obligation becomes assigned. The exchange conditions that clinicians were compensating for become the exchange conditions that infrastructure holds.
When that boundary is evidenced, the next one is additive.
If you know where the exchange breaks, we should talk.
The assessment begins with a conversation about your specific boundary. No proposal until we understand the exchange conditions.
Talk to us Learn about the lighthouse →