Updated 21 October 2026.
The most powerful position in healthcare AI may not belong to the company with the highest-scoring model. It may belong to the service through which clinicians reach the patient record, obtain context, request evidence and complete an action. If that interface becomes difficult to replace, control over the workflow could matter more than ownership of the underlying intelligence.
This is a strategic hypothesis, not a finding that Tandem or any named supplier holds a monopoly or has breached competition law. It asks where bargaining power could accumulate as clinical AI moves from separate tools towards integrated platforms.
The model and the route to the clinician are different assets
A model supplies capabilities such as language generation, extraction or reasoning. A clinical application decides how those capabilities are used, which information they receive and what outputs the user sees. The surrounding workflow determines whether an answer becomes a draft, a suggestion or a completed action.
A supplier can sometimes change the model beneath its interface while retaining its customer relationship. The clinician may continue using the same application because the integration, permissions, templates and support arrangements remain useful. That possibility gives the application layer strategic importance without making model quality irrelevant.
The reverse is also possible: a model provider could offer capabilities directly or enable competitors. The eventual balance depends on how replaceable each layer becomes. It should not be assumed that either foundation models or clinical applications will capture all the value permanently.
Tandem illustrates the move towards a broader interface
Tandem's published integration catalogue and clinic-operating-system ambition show a strategy extending beyond a standalone text-generation feature. Its clinical evidence offering adds another reason for a clinician to remain within the same environment.
That combination creates a plausible distribution advantage. A supplier serving documentation may be well placed to offer evidence questions, coding or other adjacent tasks. However, proximity is not the same as proficiency, and a proposed operating-system role should not be treated as a completed replacement for every clinical system.
For buyers, the significant question is whether the convenience of one interface leaves meaningful choice over individual functions. A platform can be useful precisely because it coordinates work, while still deserving scrutiny over how easily another service can complement or replace part of it.
Switching costs are not automatically network effects
These terms are often used interchangeably, but they describe different mechanisms. Switching costs arise when changing supplier requires migration, training, reconfiguration or new assurance work. Network effects arise when the service becomes more valuable because additional participants use it.
A clinical platform can have substantial switching costs without demonstrating a strong network effect. Templates and integrations can make departure inconvenient even when another customer joining the platform does not directly improve the original customer's experience.
The distinction matters because the remedies differ. Portability, clear configuration exports and reusable assurance can reduce switching costs. Interoperability may help customers benefit from participation across services. A vague claim that a platform has "network effects" should not prevent buyers from asking which mechanism actually makes it difficult to replace.
The established record system remains an important participant
A new AI interface does not necessarily displace the system that stores the clinical record or manages access to it. Record-system suppliers may retain control over interfaces, permissions and commercial terms. Clinical organisations also remain responsible for deciding how their systems are connected.
An AI company can therefore become an important intermediary without controlling the entire stack. Its bargaining position may depend on partners that can change their own products, access arrangements or strategy. The market could develop competing layers of influence rather than a single new gatekeeper.
This is why procurement should examine dependencies beyond the visible brand. A change in an upstream model, cloud service or record-system connection can affect the end service. The organisation should understand who can resolve a failure and what happens when a commercial relationship changes.
Bundling can improve value and weaken visibility
A combined service can reduce contracting effort, simplify the interface and spread support costs across useful functions. Those are legitimate advantages. It becomes harder to assess value when the bundle obscures which modules are used, how they perform and what would happen if one were replaced.
A buyer should be able to distinguish the cost and benefit of the overall service from those of its components. This does not require every contract to price every feature separately. It requires enough information to understand whether the platform is useful because its parts work well together or because alternatives have become inconvenient to access.
The more consequential functions also need their own evidence. A successful documentation module should not automatically secure acceptance for a new decision-support or operational feature merely because the additional function appears to be free.
Open interfaces need practical, not decorative, meaning
Interoperability is valuable when it allows information and functions to be used safely across services under clear permissions. An API reference on a website is not sufficient evidence that a customer can easily connect a competing product or retrieve what it needs to leave.
Practical questions concern access terms, authentication, data formats, documentation, testing support and limits on use. Organisations should also understand whether configuration, templates and relevant audit information are portable, not merely whether a final note can be downloaded.
The NHS guidance on digital assurance for APIs and services demonstrates that connectivity has assurance requirements of its own. Greater openness should not mean abandoning security or clinical safety. The objective is dependable substitutability and collaboration, not unrestricted access to sensitive systems.
Independent reference and learning can preserve a different relationship
This article is published by iatroX. An independent clinical reference service can maintain a direct relationship with the clinician that is not entirely mediated by the organisation's workflow supplier. Learning activities may also extend across employers, placements and stages of training.
That independence is useful only when the product earns it through value. It does not guarantee a different underlying model, eliminate privacy obligations or establish better clinical accuracy. Nor does it imply that clinicians should avoid integrated services that genuinely improve their work.
The procurement principle is broader than any one company: keep enough transparency and practical flexibility that useful functions can be evaluated on their merits. The danger is not integration itself. It is allowing the convenience of integration to make the evidence, costs and alternatives increasingly difficult to see.
If healthcare AI develops a dominant bottleneck, the workflow is a plausible candidate. Buyers can influence that outcome now through portable information, clear responsibilities and contracts that preserve meaningful choice as the technology changes.
Frequently asked questions
Is Tandem described here as an actual monopoly?
No. The article analyses a possible source of future market power. It does not establish dominance, unlawful conduct or a competition-law conclusion about Tandem or another supplier.
Are switching costs always bad?
No. Some arise from valuable configuration and integration. The concern is whether the costs are understood, proportionate and manageable, rather than discovered only when a customer needs to change provider.
Can integrated platforms and independent tools coexist?
Yes. A platform can coordinate clinical work while separate tools provide reference, specialist functions or learning. Practical interoperability and clear governance determine how well that combination operates.
Keep a direct route to clinical knowledge
Explore Ask-iatroX as a dedicated reference environment alongside the workflow platforms used in your clinical setting.