Every MedTech deployment failure has an official story: poor adoption, clinician resistance, regulatory friction, edge cases. The structural explanation is usually different — a system built for one kind of problem sits inside a context governed by a different kind of necessity.
MedTech deployments produce a specific class of structural contradiction: a system optimized for documentation, efficiency, or cost sits inside a context governed by care, safety, and the irreversibility of decisions about living bodies. The two logics are not compatible and the gap between them cannot be closed at the implementation level.
The contradiction is not in the technology. It is in what the technology is asked to hold simultaneously — accuracy and authorization, documentation and attention, innovation and classification. This series documents where that gap migrates when no one has explicitly designed for it.
Three structural zones where MedTech contradictions concentrate.
The system was designed to capture, optimize, or authorize. The clinical context requires presence, judgment, and the ability to act on what is not yet recorded. The contradiction migrates into workarounds — which are not failures, but the system's actual operating state.
A product is classified as wellness — then reclassified as a medical device. Or the inverse. The boundary moves while the product stays the same. The absent layer is classification architecture that can hold an unstable boundary without making the product illegal by the time it is deployed.
The tool is deployed to improve one outcome. Its incentive structure is aligned to a different outcome. Over time the tool reflects what it is paid to do — not what it was announced to do. This is not misuse; it is the structural result of an unexamined design choice.
Each case is a documented structural contradiction — not a critique of healthcare technology, but an architectural analysis of what made the tension structurally predictable.
Structural patterns that recur across MedTech cases — each a specific way the contradiction migrates when the absent layer has no owner.
A system built to capture everything produces so many signals that practitioners stop reading them. The contradiction: completeness and attention are requirements in direct conflict. Workarounds — ignoring alerts, copy-pasting notes, parallel charting — are not non-compliance. They are the system adapting to survive its own information architecture.
A product is built against a regulatory classification that changes before or shortly after launch. The boundary between wellness and medical device, between monitoring and diagnosis, is not stable — but the product architecture assumes it is. The absent layer is classification resilience: the ability to hold an unstable boundary without requiring a full re-architecture.
A system deployed to improve one outcome is structurally incentivized to optimize another. The divergence between the announced goal and the operational incentive is not a corruption — it is a design outcome. Over time, the system reflects what it is paid to do. The contradiction migrates into the gap between the public rationale and the operational logic.
When practitioners consistently route around a system, the workaround is not the problem — it is the diagnosis. The workaround reveals where the system's logic and the care logic are structurally incompatible. Eliminating the workaround without addressing the structural tension removes the only visible signal that the tension exists.
The absent layer is the boundary between system logic and care logic. No one was asked to design it.
In each case, the structural contradiction moves to the next available layer — the one nobody explicitly designed. In EHR deployments it is the information architecture that must hold both completeness and clinical attention simultaneously. In regulatory navigation it is the classification layer that must remain stable while the boundary moves. In AI authorization it is the incentive architecture that must hold both cost optimization and care delivery. The layer is absent not by accident, but because the deployment asked the technology to hold what only an explicit architectural decision can hold.
Diagnostic rule: when workarounds persist after retraining, and resistance continues after redesign, look for the boundary between system logic and care logic — and ask who was assigned to design it.
If the situation looks familiar — and the same contradiction keeps returning after retraining programs or system updates — the next step is not another implementation cycle. It is finding the boundary that was never designed.
Describe your situation →