Information flows
System rules
Feedback loops
Goals of the system
Delay structures
Paradigm shift

Systems thinking · CauseACTION

The system
behind the system.

Every NHS improvement tool moves numbers. Few change the system that produces them. This page explains the intellectual framework that makes CauseACTION different — and shows what becomes possible when that framework is applied to real clinical work.

Where in a system
can you intervene?

In 1999, systems thinker Donella Meadows published a hierarchy of leverage points — places in a system where a small intervention produces large change. She identified twelve, ranked from weakest to most powerful. Most improvement effort in complex systems, she observed, is spent at the weak end of the hierarchy — adjusting numbers, tweaking parameters — while the powerful levers go untouched.

Healthcare is a vivid illustration. Enormous energy is invested in dashboards, targets, and compliance frameworks — all operating at levels 12 to 10. The information structures, rules, and feedback loops that actually determine how the system behaves receive far less attention. This is not a failure of intent. It is a failure of infrastructure. Changing information flows requires knowing what information exists, where it is, and who needs it — in real time. That is precisely what CauseACTION is built to do.

The 12 leverage points — weakest to strongest
Highlighted rows show where CauseACTION operates
12
Numbers — constants and parameters
Targets, thresholds, budgets. Moving numbers rarely changes system behaviour — the feedback loops stay intact. Most NHS performance management operates here.
11
Buffer sizes
Bed capacity, staffing headroom, stock levels. Important but slow to change and expensive to alter.
10
Structure of material flows
Physical layout — theatre design, ward configuration, supply chains. Hard to change once built.
9
Lengths of delays
Referral-to-treatment gaps, handover lag, results turnaround. Delays cause oscillation and instability. CauseACTION quantifies these — reducing lag changes system dynamics.
8
Strength of negative feedback loops
Compliance loops, outcome attribution, non-conformance capture. CauseACTION strengthens these — more signal means better self-correction.
7
Gain around positive feedback loops
Learning loops that amplify good practice. CauseACTION closes the feedback gap between frontline work and organisational learning — every case feeds the next.
6
Structure of information flows
Who gets what data, when, in what form. Missing information produces wrong behaviour — no incentive compensates. This is CauseACTION's primary operating point. Perfusion data that never reaches coding. Haematology results buried in a letter. Staffing gaps invisible until the emergency call.
Primary CauseACTION lever
5
Rules of the system
Protocols, staffing standards, clinical guidelines. CauseACTION audits adherence in real time and surfaces where rules are consistently broken — the precondition for changing them.
Enabled by continuous data capture
4
Power to change system structure
Pathway redesign, service reconfiguration. The Digital Twin enables this — simulating the optimal pathway and modelling financial and clinical impact before committing to change.
Digital Twin capability
3
Goals of the system
What the system optimises for. Making quality universally measurable — in real time, without additional workload — shifts what the system treats as a goal. Variation becomes visible. The gap between planned and delivered care becomes a measure, not an assumption.
Long-term CauseACTION ambition
2
Mindset — the paradigm the system arises from
Work as done WELL. From individual blame to system design. From point-in-time audit to continuous learning.
1
Power to transcend paradigms
The capacity to question the system's own assumptions. The long-horizon ambition.
Network topology
"The most powerful leverage point in a system is not adjusting its parameters. It is changing the information flows that determine how the system sees itself." — After Donella Meadows, Thinking in Systems (2008)

Three frameworks.
One proposition.

CauseACTION is not built on a single theory. It draws on three bodies of thought that converge on the same conclusion: the problem in complex systems is rarely what people do. It is what the system allows them to see.

SEIPS 3.0

Systems Engineering Initiative for Patient Safety

SEIPS maps the work system — People, Tools, Tasks, Organisation, and Environment — and the processes that flow through it. It explains why the same protocol produces different outcomes in different hands in different contexts: the work system is never the same twice. CauseACTION uses SEIPS as both a design methodology and a classification taxonomy for non-conformance. When something goes wrong, SEIPS tells you which component of the system was the proximate cause — and that distinction determines whether the correct response is training, equipment, staffing, or process redesign. Most incident reporting systems cannot make this distinction. CauseACTION is built around it.

Weick & Sutcliffe — Managing the Unexpected

High Reliability Organisations

Five principles distinguish organisations that operate safely at extreme complexity from those that fail catastrophically despite best intentions: preoccupation with failure (near-misses as signals, not luck), reluctance to simplify (resisting reassuring narratives), sensitivity to operations (frontline situational awareness at every level), commitment to resilience (recovery capacity, not just prevention), and deference to expertise (decisions routed to the most informed, not the most senior). CauseACTION makes each operational — NCR capture is preoccupation with failure; DO2i multi-factor analysis is reluctance to simplify; live staffing visibility is sensitivity to operations; the Digital Twin is commitment to resilience; automated pathway routing is deference to expertise.

Barabási — Network Theory

Networks are only the skeleton of complexity — and phase transition changes everything

Barabási established that complex systems share a universal topology: a few highly connected hubs, many peripheral nodes, and link dynamics that determine how the network actually behaves. Healthcare has the skeleton — the policies, protocols, reporting structures. What it lacks is visibility of the dynamics along the links: what information flows, where it slows, where it disappears entirely.

But network theory offers a second, equally important insight: phase transition. Why does water freeze? Why do disordered magnetic domains suddenly align? Not because energy is added — but because it is removed. At high thermal energy, particles move too fast for weak forces to act. As temperature falls, those forces — which existed all along — finally align neighbouring nodes. Order emerges from disorder, without command.

Healthcare systems are running hot. Staff carry too much undischarged cognitive load for the weak forces of natural alignment — shared situational awareness, mutual trust, lateral collaboration — to do their work. CauseACTION aims to take the heat out: giving staff the information they need automatically, making true workload visible, reducing administrative burden. When staff are no longer reconstructing a picture that should already exist, they have time for the constructive collaboration where genuine improvement originates. Order from disorder. Not imposed — enabled.

A connected system
of care — in full.

The following scenario is not speculative. Every element draws on existing clinical practice, documented system failures, and CauseACTION's designed capability. What does not yet exist is the infrastructure that connects them. This is what that infrastructure makes possible.

The sickle cell pathway — from referral to national learning

A patient with sickle cell disease is referred for cardiac surgery. CauseACTION detects the referral and automatically surfaces the clinical history — identifying from pre-existing haematology correspondence, using NLP, that exchange transfusion will be required before bypass. Within minutes of referral receipt, every relevant stakeholder has a role-specific summary: the surgical team has the operative complexity flags, the haematology team has the transfusion timeline, NHSBT has the request for exchange blood, and the scheduling team knows that additional pre-operative time is required.

The system reviews planned staffing levels for the case date, identifies a perfusionist to conduct the operation, and surfaces the relevant sections of the national SOP for exchange transfusion in cardiac surgery — flagging that the protocol was updated eighteen months ago based on evidence from another centre that achieved superior outcomes with ultra-rapid exchange using the heart-lung machine itself, requiring fewer donor units and reducing complications. That protocol update exists because a previous CauseACTION case at that centre generated a national learning event, anonymised, shared, and incorporated into the standard.

On the morning of surgery, the assigned perfusionist reports sick. CauseACTION records the adaptation, alerts the coordinator, updates the team assignments, and ensures the replacement clinician — less experienced with this case type — is immediately directed to the relevant protocol sections and to the national outcome data that underpins them. The system does not panic. It routes information to where it is needed.

Throughout the procedure, automated sensing and minimal human input confirm adherence to best practice. The case completes without incident. The data from this case — haemodynamics, exchange transfusion volumes, bypass parameters, outcome — is pseudonymised and added to the national dataset. The next centre facing the same case has more evidence than the last. The system has learned.

This is not a vision of a different NHS. It is the same NHS — with its data connected. Every element of this scenario already exists somewhere in the system. CauseACTION is the infrastructure that joins it.

Recurring challenges.
Made visible. Made manageable.

These vignettes illustrate how CauseACTION translates the hidden complexity of daily work into visible, actionable insight. Each reflects a real pattern within cardiac services — not isolated incidents, but systemic challenges that repeat because the system has no way to see them clearly enough to address them.

Operations · Theatre flow

Coordinating theatres and critical care — replacing phone calls with live context

One of the most persistent operational challenges within cardiac services is managing critical care bed availability throughout the day. For Band 7 coordinators, this requires balancing multiple moving parts across several theatres simultaneously — conducted through a constant stream of phone calls, entirely reactive, introducing risk and contributing to theatre downtime and late finishes.

CauseACTION addresses this by applying live data from the EPR and theatre systems to automatically prioritise cases and surface real-time bed availability to all teams simultaneously. ITU update bed readiness directly. Fewer phone calls, fewer late finishes, senior nurses freed for clinical decision-making.
Learning · NLP intelligence

Revealing hidden clinical patterns — what free text knows that databases do not

Certain intraoperative challenges remain invisible to traditional reporting systems because they are described only in free text notes — never coded, never counted, never fed back into learning. A powerful example involves cases where myocardial ischaemia management deviates unexpectedly: an arrest not sustained, multiple re-arrest attempts, conversion to full bypass without conventional arrest, later found to be due to anomalous coronary drainage. The finding was previously documented — it was there in the operative notes. But written in unstructured free text, it didn't automatically surface and didn't reach the people or processes that could have learned from it.

CauseACTION applies NLP to operative notes, perfusion records, and post-case summaries — identifying and classifying similar descriptions across cases, flagging clusters of events that might indicate system weaknesses previously unrecognised. Tacit knowledge becomes explicit organisational learning.
Safety · Coordination failures

The case that nearly disappeared — process failures and communication gaps

A high-risk patient was scheduled for a complex aortic procedure. The referral arrived, an initial request for further details was sent, and nothing came back. Nine days later, contact was re-established the evening before surgery — leaving hours rather than days for essential preparation. This is a structural pattern: complex referrals that fall between systems, between people, between working weeks. The information needed to prevent the problem exists. It has no mechanism to surface itself.

CauseACTION prevents this through live referral tracking, automated escalation when responses are not received within defined windows, and shared accountability. Key risk factors and preparation tasks are visible to all stakeholders before the day of surgery — not because someone remembered to chase, but because the system made forgetting impossible.
Workforce · Complexity capture

Capturing operational complexity — the adaptations that never get recorded

Within a busy cardiac unit, countless small adaptations occur daily — staff running late, sickness cover arranged informally, theatre allocations changed at short notice. None are routinely recorded. Yet each shifts the operational picture: workload peaks, staffing ratios change, the risk profile of the list quietly increases while remaining invisible to anyone not physically present. Operational complexity can be precisely defined: the volume of change against a planned baseline. Currently that cost is absorbed silently.

CauseACTION makes complexity measurable by overlaying real-world operational data onto planned schedules — surfacing workforce pressures as they unfold, enabling proactive rebalancing, and generating a retrospective dataset that makes invisible patterns visible for the first time.
Evidence · Health Technology Assessment

Why technologies appear not to work — and how to tell the difference

Cerebral near-infrared spectroscopy (NIRS) monitors oxygen delivery to the brain during cardiac surgery. Two centres both record it as "in use." At one centre, when the NIRS signal drops, the team responds — adjusting flow, pressure, or haemoglobin. At the other, the signal is observed but rarely acted upon systematically. In both cases, the HTA dataset records the same thing: NIRS used. The analysis concludes: NIRS has no effect. But the conclusion is wrong. The technology did not fail. The implementation did.

This is one of the hardest problems in real-world evidence — what might be called implementation fidelity bias. Health Technology Assessment typically captures whether a technology was present and what the outcome was. It does not capture whether the technology was used as intended, whether the signals it generated were interpreted correctly, or whether the appropriate responses followed. Variation in implementation is systematically misread as variation in effectiveness. Technologies are dismissed. Guidance is wrong. Patients are affected.

The same failure mode runs across devices, drugs, and pathways. In every case, outcome = intervention × implementation × context. Current HTA can measure the first and the last. It cannot see the middle.

CauseACTION introduces fidelity-aware real-world evidence. For the NIRS example it would capture four layers for every case: the signal (NIRS dropped below threshold), the context (patient haemoglobin, bypass flow, pressure at that moment), the response (was action taken — and what action), and the outcome (AKI incidence, stroke, length of stay). This creates three analytically distinct groups that current HTA cannot distinguish: NIRS present and acted upon; NIRS present and not acted upon; no NIRS. The question shifts from "does NIRS work?" to "does NIRS work when used as intended?" — which is the question that actually matters, and which produces guidance that is conditional, context-aware, and clinically actionable rather than a blunt yes or no. The same principle applies to every monitoring technology, every pathway protocol, and every drug where dose, timing, and response are as important as prescription. CauseACTION does not just measure care. It can explain why interventions appear to work — or not — in the real world.

Not a better dashboard.
A different kind of system.

The vignettes above are drawn from cardiac surgery because that is where CauseACTION begins. But the architecture is not cardiac-specific. The same infrastructure that connects perfusion data to a coding team connects a medicines pathway to a pharmacist. The same NLP that surfaces a sickle cell result from a haematology letter surfaces a deteriorating renal function from a GP discharge summary. The same feedback loop that makes N+1 compliance visible nationally makes antibiotic prescribing variation visible nationally.

"When you start, the data is never as good as you would like — and that is where the courage comes in. But data only becomes good when you use it." — Professor Sir Bruce Keogh

The NHS is, as Dame Penny Dash observed, one of the most data-rich healthcare systems in the world. The challenge is not collection. It is connection. The challenge is not evidence. It is infrastructure. The challenge is not knowing what good looks like. It is making the gap between good and current practice visible — continuously, automatically, and without adding a single form to the workload of the people already keeping the system alive.

6→2
Meadows leverage levels

From restructuring information flows to shifting the paradigm. CauseACTION operates across this range — each level enabling the next.

5
HRO principles enacted

Preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, deference to expertise — each as a system feature, not a culture aspiration.

Network learning effect

Every case adds to the evidence base. Every centre benefits from every other's experience. The system improves through use — and it never forgets.

0
Additional forms

The infrastructure captures work as done — from data that already exists, through tools staff already use. No new burden. No extra clicks. Just connection.

Everywhere in healthcare there is skeleton — the policies and SOPs. What we have yet to visualise are the muscles and tendons.

CauseACTION is built to make those muscles and tendons visible — connecting the information that already exists, surfacing the patterns that are already there, and turning every routine case into evidence that makes the next one safer. The system already knows what it needs to improve. CauseACTION is the infrastructure that lets it act on that knowledge.

← Return to main site Get in touch ↗