From Adapting to Emerging.
What the next phase of healthcare technology requires — and why the organisations best positioned to deliver it have not yet designed for it. We need to adapt and seek out the emerging knowledge, value and connections achieved through Ecosystem design
This post is a ten to twelve minute read: invest the time, understand the return.
No doubt something significant has been built in healthcare through technology.
Over the past decade, the leading organisations in healthcare technology have made investments that would have seemed implausible at the start of it. Diagnostic imaging data estates that encompass millions of patient encounters across dozens of geographies. Artificial intelligence portfolios with hundreds of clinically validated applications, cleared by the most demanding regulatory bodies in the world.
Investments in platform architectures designed to aggregate data from disparate systems, vendors, and care settings into a single coherent intelligence layer. Partnership networks spanning pharmaceutical companies, hospital systems, academic medical centres, AI developers, payers, and care pathway specialists — relationships built with genuine sophistication and genuine intent by many of the leading organisations* engaged in healthcare.
The financial results that have followed reflect the quality of this work. Enterprise agreements signed at a scale and duration that signal deep institutional trust. Margins expanding. Innovation pipelines strengthening. Clinical outcomes improving in measurable and documented ways. The organisations that have invested most seriously in building these capabilities have, by most reasonable measures, been rewarded for doing so.
This is not a piece that questions any of that. The investment has been real. The capability built is genuine. The results achieved are deserved.
The question this piece asks is a different one. Not whether what has been built is valuable — it is. But whether it is sufficient for what comes next.
What has characterised this period for these HealthTech companies, honestly examined, is a sustained capacity to adapt and react.
Adapt to the emergence of artificial intelligence as a clinical tool — integrating it into imaging workflows, diagnostic decision support, treatment planning, and operational management faster than most observers anticipated. React to the shift in healthcare delivery toward decentralised and home-based care — building connected monitoring infrastructure, remote diagnostic capability, and enterprise service models that follow the patient rather than waiting for the patient to arrive.
It is those willing to adapt to the expectations of hospital system partners who are no longer willing to manage dozens of bilateral vendor relationships — consolidating propositions into multi-year enterprise agreements that span modalities, services, and geographies. React to the competitive pressure of platform-native technology companies entering the sector — investing in digital architectures sophisticated enough to meet them on their own terms.
Each of these adaptations required resolute organisational capability building and genuine strategic conviction. None of them was straightforward. The organisations that executed them well deserve credit for doing so.
But adapting and reacting, even when done exceptionally well, is fundamentally a response to what is already happening. It produces better versions of what already exists. It optimises the current model rather than transcending it. It generates improvements in scale, efficiency, and capability within a defined architecture — rather than changing the architecture itself.
And the architecture that has defined this period — however sophisticated its individual components — has a shared characteristic across every leading organisation in the sector. Its primary logic is bilateral. Organisation and partner. Platform and developer. Hospital system and technology provider. Each relationship managed with increasing skill.
That is not a criticism. It is a precise description of where the sector currently sits. And it is the description that makes the next question visible.
The challenge is that each node in the network needs to be made more capable through investment and attention. But the relationships, fundamentally, running from a central point outward — and not yet flowing between the actors themselves in ways that generate value the central organisation did not direct, anticipate, or control.
Examine the leading healthcare technology organisations closely — their strategies, their architectures, their investment patterns, their partnership designs — and a consistent finding emerges across all of them.
The data is extraordinary. The intelligence built from it is genuine and growing. The platform architectures designed to host and distribute that intelligence are among the most sophisticated in any industry. The partnership networks assembled around those platforms represent years of relationship building, trust cultivation, and commercial negotiation.
And at the level of what happens between those partners — at the level of how the intelligence generated in one part of the network flows to the actors who could act on it in another part, of how a discovery made in one node compounds into value across every other node that touches it, of how the network as a whole senses what is changing at its edges and evolves its architecture in response — something is consistently absent.
Not absent through neglect. Not absent through lack of investment or capability or intention. Absent because the concept itself has not yet been fully designed for. Because the vocabulary for it exists — ecosystem, orchestration, intelligence layer, connected care — but the architectural design that makes those words real rather than aspirational has not yet been built.
The organisations closest to it have built remarkable platforms. They have created environments where third parties can participate, where data can be aggregated, where AI applications can be deployed. These are genuine achievements. But a platform where partners participate is not the same as an ecosystem where partners create value for each other.
A data layer that aggregates is not the same as an intelligence network that flows. An AI marketplace where applications are distributed is not the same as a governed architecture where what those applications learn compounds back into the knowledge of every other actor in the network.
The distinction is not semantic. It is the difference between what the current architecture can produce and what the next one makes possible.
The question that defines the next phase is this: what moves data and intelligence into knowledge and value?
Data, in the healthcare technology sector, is no longer scarce. The diagnostic imaging data estates, the clinical trial repositories, the real-world evidence platforms, the connected monitoring streams, the pharmaceutical diagnostics outputs — the volume and diversity of data available to leading organisations in this sector is without precedent in the history of medicine. The intelligence built from that data — through AI models, through clinical validation, through years of algorithmic refinement — is genuine and growing.
But intelligence held within a single organisation, however sophisticated, has a ceiling. It improves the products of that organisation. It sharpens the decisions made within its bilateral relationships. It creates better versions of what that organisation already does.
What it does not do — what it structurally cannot do within a bilateral architecture — is generate the kind of compounding knowledge that emerges when intelligence flows across a governed multi-actor network, when what is learned in one corner of the ecosystem reaches every other corner where it could create value, when the understanding built through one set of clinical relationships compounds into insight that transforms the work of every other actor the network touches.
Knowledge, in this sense, is not a larger version of intelligence. It is what intelligence becomes when it is allowed to move — across organisational boundaries, through a governed network, between actors who are not all managed bilaterally by a central node — and compound at every point of contact. It is the emergent property of an ecosystem designed for flow rather than aggregation.
And value — the kind that does not erode with the next product cycle, the next competitive entry, the next loss of exclusivity, the next platform feature that a well-funded competitor replicates within eighteen months — is what knowledge creates when it is embedded in a governance architecture that makes the network itself the source of advantage rather than any individual asset within it.
This is not a technology question. The technology to support it exists and is in use. It is not a partnership question. The relationships needed to populate such a network are already built or buildable. It is not a data question. The data estates required to feed it are already extraordinary.
It is a design question. A governance question. An architecture question. What does the structure look like that allows intelligence to flow rather than accumulate? What are the rules, the trust frameworks, the decision mechanisms, the feedback loops that turn a sophisticated collection of bilateral relationships into a self-evolving network that generates knowledge none of its individual members could produce alone? What is the function — not a technology, not a team, not a platform feature — that sits at the centre of this architecture and actively routes capability between actors, senses what is emerging at the network edges, and evolves the structure in response?
These are the questions the next phase of healthcare technology asks. They are not being asked loudly yet? But the organisations that begin designing for them now will find, when the questions become unavoidable, that they have already built the answer.
What emerges when an organisation moves from bilateral intelligence architecture to governed ecosystem knowledge network is not a marginal improvement on what existed before. It is a qualitatively different form of value creation.
The strategic moat shifts. In a product-led architecture, the moat is the product — its performance, its differentiation, its switching cost. In a platform-led architecture, the moat is the platform — its installed base, its network of developers, its data aggregation capability. Both are real and both erode over time as competitors invest, as technology evolves, and as the switching costs that once felt prohibitive become worth paying. The moat that does not erode in the same way — because it is not a product or a platform but a governed intelligence network — is the knowledge that compounds across every actor in the ecosystem with every interaction that passes through it. The more actors participate, the more intelligence flows, the more valuable the knowledge becomes for every participant, and the harder it becomes to replicate from outside because its value is not in any individual component but in the architecture that connects them.
The innovation dynamic shifts. In a bilateral architecture, innovation is directed — the central organisation identifies the need, commissions the development, validates the output, and distributes the result. In a governed ecosystem architecture, innovation is also emergent — it appears at the intersections between actors that the central organisation did not predict, in response to problems the network surfaces that no single actor saw clearly enough to name, through combinations of capability that become visible only when the intelligence of multiple actors flows through a shared governance layer.
Directed innovation and emergent innovation are not in competition. But the second produces things the first structurally cannot — and the organisations designing for emergence now will find themselves holding innovations in five years that their competitors have not yet imagined.
The evolution dynamic shifts most profoundly of all. An organisation that adapts and reacts is always, to some degree, behind. It responds to what has already happened. An ecosystem that evolves — that senses what is changing at its edges, routes that signal to where decisions are made, and adjusts its architecture in response before the change becomes a crisis — is operating on a different temporal logic entirely. It is not faster in the conventional sense. It is ahead in a structural sense. The network learns before any individual actor within it has processed what is changing. That is not acceleration. That is transformation.
The organisations that have built most carefully during this period have earned something important. They have earned the right to ask the next question.
Not what more can we extract from what we have built. Not how do we scale what is working. Not what is the next product feature or the next enterprise agreement or the next AI application that defends the position we have established. Those questions have been asked and answered with considerable skill. They have produced the results that make the next question possible.
The next question is what do we design now that moves what we have built — the data, the intelligence, the partnerships, the platform, the clinical relationships, the years of learning embedded in all of it — into something that generates knowledge and value in ways the current architecture cannot reach.
Not because the current architecture has failed. But because it has succeeded well enough to reveal what comes after it.
The organisations that ask this question seriously — that treat it as a design challenge rather than a strategic aspiration, that build the governance and orchestration architecture that makes the answer real rather than rhetorical — will find that the period of adapting and reacting was not the destination. It was the foundation.
What gets built on that foundation, deliberately and with the right architectural intent, is what determines whether the value created in this period compounds into something that sustains and transforms — or simply scales until the next disruption requires another round of adapting and reacting.
The design decision that changes that is available now. The organisations positioned to make it have everything they need except the architecture itself.
* Six leading organisations have been evaluated for this post through the opening part of the IIBE diagnostic– Siemens Healthineers, GE Healthcare, Roche Diagnostics , Bayer Global, Novartis and Royal Philips but can be recognised for all the Healthcare organisations today building Ecosystems and their networks
Paul Hobcraft is the creator of the Intelligent Integrated Business Ecosystem (IIBE) framework, working with large industrial enterprises and institutional bodies on ecosystem architecture, governance, and orchestration design.
paul4innovating.com · ecosystems4innovating.com