After 16+ years in software engineering, including 14 years building healthcare and medical device platforms, one thing is clear: MedTech architecture is entering a new phase.
Two developments in a single week said it all. A large-scale device management event exposed the risks of centralized, fleet-wide control. And Microsoft introduced Copilot Health, unifying medical records, wearables and lab data through a single AI layer for millions of patients.
Both point to the same question: are we building the architecture these platforms deserve?
Here is my framework.
Sovereign Systems, Not Silent Fleets
Humans must retain authority over high-impact decisions. Human-in-the-loop isn't a limitation. It builds trust at scale.
The Blast Radius Principle
Clinical operations must be architecturally isolated from corporate IT. No single disruption should cascade across the entire system.
Designing for the "Dark Day"
Systems must continue operating safely when cloud dependencies become unavailable. Resilience is a care continuity requirement, not just a technical one.
Intentional Modernization
Resilience gets built in while a legacy system is modernized, not bolted on afterwards.
Efficiency, innovation and resilience aren't competing goals. When we architect intentionally, we can achieve all three.
The next few posts take each principle in turn.
Seen this differently?
Questions, corrections and counterexamples are welcome.