Cybersecurity Is Patient Safety
Healthcare security failures cannot be evaluated only as confidentiality incidents. Their consequences are measured in delayed care.
Applied Horizons
Beyond the immediate horizon.
Emerging technologies change more than what is possible. They change what follows.
The first effect is rarely the last.
The immediate consequence of a new capability, decision, or intervention is usually the easiest thing to see. The harder questions arrive later, and quietly.
What dependencies does it create? What assumptions does it invalidate? What becomes vulnerable that was not before? Who adapts around it? What becomes harder to reverse? What obligations eventually attach to it?
These questions are usually considered separately — by engineers, security teams, clinicians, counsel, policy staff, operators — and often only after the decision that made them urgent.
Applied Horizons considers them together, and earlier.
From capability to consequence.
Capability is only the beginning. Once applied, it creates dependencies, exposures, responses, and obligations that can matter more than the original change. Each stage is a question asked of the one before.
- Capability
What has become possible?
- Application
Where is it actually being used?
- Dependency
What now relies on it working?
- Exposure
What became vulnerable as a result?
- Response
Who reacts, and how quickly?
- Governance
What must now be demonstrated?
- Consequence
What is permanently different?
Most analysis stops at the second step. The consequences that matter usually appear after the fourth — and rarely in a straight line.
Areas of exploration.
The subject changes. The method does not. These are areas we return to often, not the boundaries of what we will look at.
- 01
Artificial Intelligence
Intelligence is becoming infrastructure. Emerging architectures, agentic systems, model security, evaluation, and the operational consequences of software that increasingly decides. - 02
Cyber & Resilience
New capability creates new exposure. Adversarial behaviour, systemic dependency, emerging attack surface, and the difference between a system that resists failure and one that survives it. - 03
Quantum Technologies
Some technologies change the assumptions beneath the system. Computing, communication, sensing, and timing — four capabilities maturing at different rates, each altering something a great deal of infrastructure quietly assumes. - 04
Autonomous Systems
When software begins to act. Perception, decision, and action in increasingly independent systems — and the question of who remains accountable for the outcome. - 05
Governance & Assurance
Capability alone does not establish trust. Oversight, standards, evaluation, controls, and the mechanisms by which a system earns the confidence already placed in it. - 06
Law, Policy & Institutions
Technology moves. Institutions respond. The evolving rules, obligations, and institutional structures that form around a technology once it becomes consequential. - 07
Health & Human Systems
Where technical capability becomes human consequence. Clinical systems, medical devices, health data, human performance, and the interfaces where a person and a machine share a decision. - 08
Applied Research
Ideas become more useful when tested. Experiments, prototypes, tooling, and technical investigation — the work of finding out rather than assuming.
Selected writing.
Analysis of what changes, what follows, and what is easy to miss.
-
The Intelligence Layer
What changes when machine intelligence stops being an application and becomes something other systems are built on. -
When the Model Is Right and the System Is Wrong
Technical accuracy does not guarantee safe clinical implementation. Most of the difficulty arrives after the model is correct. -
Agents Change the Threat Model
Autonomy expands capability and attack surface at the same rate, and the second expansion is the one that goes unbudgeted. -
The Cryptographic Horizon
Post-quantum migration is an asset discovery and lifecycle problem wearing a cryptography costume.
The horizon is rarely the end of the problem.
We work from the problem outward. If you are trying to understand something that does not sit neatly inside one field, tell us what you are looking at.