The Infrastructure Problem That Sits Behind Every Digital Health Promise
Every significant promise made about digital health over the past decade rests on an assumption that is not yet reliably true. The assumption is that health data can flow where it needs to flow to enable the clinical decision, the care coordination, or the population health intervention that the digital health application is designed to deliver. In practice, health data sits in systems that were not designed to communicate with each other, managed by organisations whose data governance frameworks were not designed with interoperability as a primary requirement, and subject to regulatory and liability constraints whose navigation adds friction to every data exchange that clinical care or research requires. The digital health infrastructure problem is not primarily a technology problem, although technology is part of it. It is a coordination problem whose resolution requires the alignment of commercial interests, regulatory frameworks, and institutional behaviours that technology alone cannot achieve.
The clinical consequences of health data fragmentation are well documented but insufficiently priced by the healthcare system. A patient presenting at an emergency department whose primary care records, specialist letters, and medication history are held in systems that cannot communicate with the emergency setting creates a clinical risk that duplication of diagnostics, medication errors, and delayed treatment decisions impose on patient outcomes and on healthcare costs. The cost of this fragmentation is distributed across patients, healthcare providers, and payers in ways that make it difficult to attribute and therefore difficult to mobilise commercial and policy motivation to resolve. But the aggregate cost is substantial, and the commercial market for the technology that addresses it is growing as the evidence accumulates that health data interoperability is not a nice-to-have feature of healthcare IT infrastructure but a prerequisite for the clinical performance that modern healthcare systems are expected to deliver.
Interoperability Standards and the Commercial Market
The FHIR standard, developed by HL7 International, has established the technical foundation for health data interoperability that the healthcare IT market is progressively building on. FHIR defines a common data model and application programming interface that allows health information systems to exchange patient data in a standardised format regardless of the underlying system architecture. Its adoption has been mandated in the United States through the 21st Century Cures Act regulations that require certified electronic health record systems to support FHIR-based data access. This regulatory mandate has created the commercial incentive for EHR vendors to implement FHIR interfaces that were previously a voluntary development investment.
The commercial market for FHIR-based health data integration is growing as the regulatory mandate creates the API infrastructure that digital health application developers can build on. Health app developers, population health management platforms, clinical decision support tools, and the remote patient monitoring applications whose value depends on access to the patient's clinical data from primary care and specialist records are all building on FHIR APIs to access the data they need. The commercial ecosystem developing around health data interoperability includes the integration platform vendors, the health data networks, and the API gateway providers whose infrastructure manages the authentication, consent, and data transformation between the source systems and the applications that consume the data. This infrastructure layer is becoming commercially significant as the volume of FHIR-based health data exchange increases and as the complexity of managing that exchange at scale creates demand for specialised technical services.
The Electronic Health Record as Infrastructure
The electronic health record is the central repository of clinical information for most healthcare encounters in markets where EHR adoption is complete. Its role as infrastructure rather than simply a clinical documentation tool has become clearer as the digital health applications that require access to patient data have proliferated. The EHR that cannot make its data accessible to the clinical decision support tool, the patient-facing health app, or the population health analytics platform is an infrastructure bottleneck whose consequences accumulate across the clinical and commercial value that digital health investment is intended to create. The major EHR vendors including Epic, Oracle Health, and Meditech have made significant investments in the interoperability capabilities that their market position makes necessary as regulatory pressure and customer demand both push toward more open data access.
The commercial dynamics of the EHR market are relevant to understanding how quickly interoperability progress occurs. The installed base of healthcare provider organisations is concentrated among a small number of large EHR vendors whose market position creates limited competitive incentive to accelerate interoperability investment beyond the regulatory minimum. Healthcare provider organisations whose EHR contracts provide limited leverage over vendor development priorities have found that achieving the data access they need for digital health programmes requires significant project investment and technical complexity that the EHR vendor's standard platform does not make straightforward. This implementation gap between the regulatory promise of interoperability and the operational reality of achieving it is the commercial opportunity that the health data integration market is building its business model around.
Remote Monitoring and the Connectivity Requirement
Remote patient monitoring is among the most commercially active segments of digital health and the one whose clinical value is most directly dependent on the data connectivity that health infrastructure currently provides imperfectly. A continuous glucose monitor that cannot transmit its readings to the patient's primary care record creates a data island that the clinical team cannot act on without a separate data access step that time-pressured clinical workflows do not accommodate reliably. A cardiac monitor whose alerts reach a monitoring centre but cannot automatically populate the patient's EHR or trigger a care coordination workflow creates a gap between detection and response that defeats the purpose of the monitoring investment. These connectivity failures are not edge cases. They are the routine experience of remote monitoring deployments that have not resolved the integration infrastructure requirements before deployment. The commercial market for the middleware, integration engines, and device connectivity platforms that bridge the gap between medical device data streams and the clinical systems that need to act on them is growing as remote monitoring adoption accelerates and as the cost of integration failure in clinical terms becomes more visible to healthcare provider organisations making remote monitoring investment decisions.