HL7 FHIR has moved from a technical aspiration to a regulatory expectation across European health systems. Yet the gap between policy mandate and operational reality remains wide. For hospital administrators and healthcare decision-makers, understanding where that gap sits and why is increasingly urgent, as the European Health Data Space begins to impose concrete timelines on medical record system vendors and health institutions alike.

What HL7 FHIR is and why it matters for European hospitals

Fast Healthcare Interoperability Resources (HL7 FHIR) is an internationally recognised standard for exchanging clinical data between health information systems. Developed by Health Level Seven International, FHIR defines a set of modular components called "resources" that represent discrete units of clinical information: a patient record, a diagnostic result, a medication order, a discharge summary. These resources can be exchanged over standard web application programming interfaces (APIs), making FHIR considerably more accessible than the older HL7 v2 and v3 standards it is gradually displacing.

For hospital administrators, the significance of FHIR is not primarily technical. It is operational and strategic. When clinical systems cannot exchange data reliably between a hospital's medical record system, a radiology platform, a general practitioner (GP) system, or a cross-border registry, care continuity suffers, administrative burden increases, and the data infrastructure required to support AI-driven clinical tools remains out of reach. FHIR's flexibility for personalised profiles and incremental adoption has made it the reference standard of choice for European policymakers, but that flexibility also introduces implementation complexity that this article explores throughout.

The EU policy framework driving FHIR adoption

The most significant regulatory development shaping FHIR adoption in Europe is the European Health Data Space (EHDS) Regulation, which entered into force in March 2025. The EHDS mandates that medical record systems across EU member states adopt the European Electronic Health Record Exchange Format (EEHRxF), which is built on FHIR specifications. This is a legal requirement for health data interoperability across the Union, not a recommendation.

The EHDS framework includes a "yellow button" mechanism, known as xShare, which gives patients the right to access and share their health data in a standardised FHIR format. The EU Implementing Acts, expected by March 2027, will define the precise technical and semantic requirements that medical record systems must meet. Until those acts are finalised, implementation timelines remain somewhat uncertain for health system planners.

Beyond the EHDS, the eHealth Network, a voluntary body of national digital health authorities, has consistently identified HL7 FHIR as the recommended standard for the EEHRxF. National digital health strategies in several member states have gone further, embedding FHIR as a foundational infrastructure requirement rather than an optional upgrade.

In November 2025, HL7 Europe published three new FHIR Implementation Guides covering FHIR R4, R5, and Extensions, developed through a balloting process involving all 22 European HL7 affiliates and hundreds of expert contributors. These guides give member states a harmonised technical baseline for EHDS compliance. In March 2026, HL7 Europe and IHE-Europe announced the EURIDICE collaboration, producing coordinated FHIR Implementation Guides for the EHDS Imaging Study Report and EU Health Data API, extending standardisation into radiology and secondary data use.

Where FHIR adoption is most advanced: leading European markets

Progress is uneven across Europe, but several markets have established measurable infrastructure.

The Nordic countries represent some of the most advanced implementations. Finland's Kanta system, a national health information repository, was originally built on CDA (Clinical Document Architecture) standards and has been progressively aligned with FHIR standards. Denmark's national health data infrastructure similarly benefits from a high degree of centralisation and a tradition of national medical record system standardisation, which reduces the fragmentation that slows adoption elsewhere.

The Netherlands has made significant progress through the MedMij framework, a national programme that defines how citizens can access and share their personal health records. MedMij mandates FHIR-based APIs for data exchange between healthcare providers and personal health environments, creating a regulated market incentive for medical record system vendors to achieve conformance.

Germany presents a more complex picture. The Telematikinfrastruktur (TI), Germany's national digital health infrastructure, provides a secure network connecting hospitals, GP practices, and pharmacies. Within hospital settings, the ISiK (Informationstechnische Systeme im Krankenhaus) standard mandates FHIR-based APIs for specific hospital use cases, including patient admission data and encounter information. The October 2025 "Hospitals on FHIR User Days" in Berlin brought together real-world implementation experiences from European hospitals and introduced the Hospital on FHIR Maturity Model, a framework for assessing how far individual institutions have progressed toward full FHIR operability.

The structural conditions enabling faster uptake in these markets share common characteristics:

• Centralised national health data infrastructure with clear governance

• Regulatory mandates that create procurement requirements for medical record system vendors

• Sustained public investment in digital health programmes

• National FHIR profiles that reduce implementation variation

Mid-tier adopters: countries making progress but facing gaps

Several European health systems have initiated FHIR programmes but have not yet achieved system-wide deployment.

France has active FHIR pilots, with the University Hospital of Toulouse among the institutions sharing implementation experiences through the pan-European "Hospitals on FHIR" community of practice. France's health data infrastructure, centred on the Système National des Données de Santé (SNDS), has historically prioritised secondary data use over real-time clinical exchange, and hospital-level FHIR adoption remains fragmented.

Spain faces a structural challenge common to federal health systems: health governance is devolved to 17 autonomous communities, each with its own digital health strategy and procurement frameworks. FHIR pilots exist in specific regional contexts, but cross-regional interoperability remains limited. A survey of IT specialists across six European countries, including Spain and Italy, found that unaligned medical record system infrastructure was among the primary barriers to implementing interoperable eHealth solutions, alongside inconsistent use of international coding systems.

Belgium has made progress through its eHealth platform, which coordinates health data exchange between federal and regional actors. FHIR-based services are in development, but the coexistence of Dutch-speaking, French-speaking, and German-speaking health systems creates additional coordination complexity.

Italy offers a detailed case study of a mid-tier adopter navigating structural constraints. A November 2025 peer-reviewed analysis documented growing participation in HL7 Italy FHIR training programmes between 2021 and 2025, and noted that national recovery funding through Italy's National Recovery and Resilience Plan (NRRP) has accelerated FHIR uptake in specific programmes. The same analysis identified a critical structural barrier: limited biomedical informatics education in Italian universities, producing a workforce with insufficient FHIR expertise to sustain implementation at scale.

Where adoption is stalling: structural and technical barriers

Across much of Europe, FHIR adoption is proceeding more slowly than policy ambitions suggest. The barriers are well-documented and consistent across health systems.

Legacy medical record systems represent the single most significant obstacle. Many European hospitals operate on clinical systems designed before FHIR existed and lacking native FHIR support. A multi-site FHIR deployment study found that mapping data from legacy systems to FHIR was the biggest barrier to implementation, a finding directly applicable to European hospital contexts. The S-RACE platform, a secure cloud-based system developed to transform raw hospital data into FHIR-formatted research-grade evidence, illustrates one approach to this problem: using Natural Language Processing (NLP) to extract and standardise clinical information from unstructured legacy data. Such solutions require significant technical investment and do not resolve the underlying fragmentation.

Skills gaps compound the legacy system problem. Practitioner-facing analyses consistently identify a shortage of in-house FHIR expertise within hospital IT teams as a core barrier, alongside the cost and complexity of middleware development and custom API integration. For smaller hospitals and those in health systems with limited digital health investment, this skills gap is effectively prohibitive.

Inconsistent national API standards create additional friction. Even within a single country, different hospitals may operate on different FHIR versions, different national profiles, and different terminology bindings. A federated analysis study across six Bavarian university hospitals, which successfully transformed oncological data into FHIR format across diverse IT infrastructures, acknowledged that the modular pipeline required significant customisation to accommodate each site's distinct systems.

Cost and migration complexity remain underestimated in many procurement and planning processes. Backward compatibility with legacy data, data quality remediation, and the need to maintain operational continuity during migration all extend timelines and increase costs beyond initial projections.

The interoperability problem FHIR alone cannot solve

A common misconception among non-technical decision-makers is that adopting FHIR automatically produces interoperability. It does not. FHIR is a framework, a set of rules for structuring and exchanging data, but it permits significant variation in how those rules are applied.

The core challenge is implementation variation. Different health systems, and even different hospitals within the same health system, may implement FHIR using different versions (R3, R4, R4B, R5), different national profiles, and different extensions. A FHIR resource produced by one system may be structurally valid but semantically incompatible with a resource produced by another. Research on patient data fragmentation has documented semantic inconsistencies even when identical medical record system products are deployed across sites, a finding that underscores the limits of standardisation at the format level alone.

Terminology bindings are equally critical. FHIR resources must reference shared clinical terminologies, such as SNOMED CT for clinical concepts and LOINC for laboratory results, to be semantically interoperable. Where these bindings are absent, inconsistent, or locally customised, data exchange produces records that are syntactically correct but clinically ambiguous. The EHDS interoperability framework acknowledges the dynamic regulatory landscape as a complicating factor, noting that consistent terminology binding across member states remains an unresolved challenge.

The Hospital on FHIR Maturity Model, introduced at the October 2025 Berlin event, provides a structured framework for assessing and improving implementation quality, not just adoption breadth. Decision-makers should internalise the distinction between "having FHIR" and "achieving interoperability through FHIR" before committing to implementation programmes.

Data governance and GDPR as compounding factors

FHIR-based data exchange does not occur in a regulatory vacuum. For European health systems, the General Data Protection Regulation (GDPR) and national data sovereignty frameworks create a compliance layer that significantly affects how FHIR infrastructure can be designed and operated.

The most acute tension arises in cloud-hosted FHIR server deployments. Many FHIR implementation approaches rely on cloud infrastructure for scalability and cost efficiency. GDPR requirements around data residency, and national-level restrictions in countries such as Germany and France on where health data can be processed and stored, constrain the use of non-EU cloud providers and in some cases require on-premises or sovereign cloud deployments. This adds cost and complexity to implementations that might otherwise be straightforward.

For cross-border data exchange under the EHDS framework, GDPR compliance obligations intersect with the technical requirements of the xShare specification. Health data shared across member state borders must satisfy both the technical interoperability requirements of the EHDS and the data protection requirements of the jurisdiction in which the data subject resides. The survey of IT specialists across six European countries identified pseudonymisation of personal health data and data retention policies as primary concerns across all three health system scenarios examined: national, regional, and hospital-based.

The EURIDICE collaboration's FHIR Implementation Guides include specifications for the EU Health Data API designed to address some of these governance requirements at the technical level. The legal and organisational dimensions of cross-border data governance cannot be resolved by technical standards alone.

What clinical administrators and decision-makers should assess before adopting FHIR

For hospital leadership evaluating FHIR adoption, the relevant questions are not primarily about the standard itself. They concern the readiness of the surrounding ecosystem and the realistic scope of what can be achieved within a given institutional context.

Medical record system vendor FHIR readiness is the first and most consequential assessment. Decision-makers should establish which version of FHIR their current vendor supports, whether that support is native or delivered through middleware, and what the vendor's roadmap is for EHDS compliance. Vendor commitments made in procurement processes do not always translate into delivered functionality on the timelines promised.

National profile conformance is the second critical dimension. Most European countries either have or are developing national FHIR profiles that specify how the standard should be implemented in that health system context. Implementing FHIR without reference to the applicable national profile risks producing a system that is technically FHIR-compliant but not interoperable with national infrastructure.

Integration with existing clinical workflows is frequently underweighted in FHIR business cases. FHIR is a data exchange standard, not a workflow platform. Its value is realised when it gives clinicians access to the right information at the right time, but achieving that outcome requires integration work extending well beyond the data layer into clinical system design and change management.

Realistic timelines are essential for governance and budgeting. Practical implementation experience consistently shows that the cost and duration of legacy system migration are underestimated. The March 2027 deadline for EU Implementing Acts provides a regulatory pressure point, but full FHIR operability across all hospital systems is not achievable by that date for most institutions. Phased implementation, starting with the highest-value use cases, is more realistic than a comprehensive migration approach.

Key questions for decision-makers to ask:

• Does our medical record system vendor have a confirmed FHIR R4 or R5 roadmap with delivery dates?

• Are we implementing against the national FHIR profile, or a vendor-specific variant?

• Have we assessed the terminology bindings (SNOMED CT, LOINC) required for semantic interoperability?

• What is the data governance and GDPR compliance approach for our FHIR server infrastructure?

• Do we have, or can we access, sufficient FHIR implementation expertise to manage this project?

The role of medical record system vendors in accelerating or blocking progress

Medical record system vendors are a decisive variable in FHIR adoption at the hospital level. Their technical choices, commercial incentives, and product roadmaps directly determine how quickly and how fully hospitals can implement FHIR-based interoperability.

Epic, which has expanded significantly in European markets including the Netherlands and Denmark, has invested heavily in FHIR APIs. Epic's FHIR R4 support is among the most mature of any major medical record system vendor, and its App Orchard marketplace lets third-party applications connect via FHIR. Epic's FHIR implementation reflects US regulatory requirements, and adaptation to European national profiles requires additional configuration work.

Dedalus, one of the largest medical record system vendors operating across continental Europe, has been active in the "Hospitals on FHIR" community and has presented implementation experiences at European events. Its presence across France, Italy, Germany, and other markets makes its FHIR roadmap particularly consequential for mid-tier adopter countries.

CompuGroup Medical (CGM) serves a large share of the German primary and secondary care market and has been engaged in ISiK compliance work within the Telematikinfrastruktur context. Philips operates primarily in imaging and diagnostic informatics, where the EURIDICE FHIR Implementation Guide for the EHDS Imaging Study Report is directly relevant.

A consistent pattern across vendors is the use of middleware and API gateway layers as a pragmatic short-term solution, exposing FHIR endpoints without requiring a full re-architecture of the underlying system. This approach supports compliance with regulatory requirements but does not deliver the same depth of interoperability as native FHIR support. It also creates ongoing maintenance complexity and can limit the granularity of data available through the FHIR interface.

Vendor lock-in remains a structural concern. Hospitals that have made long-term investments in proprietary medical record systems face significant switching costs, which reduces their leverage in demanding FHIR conformance from vendors. The EHDS Regulation's mandatory EEHRxF requirements are intended partly to address this dynamic, by creating a regulatory floor below which vendors cannot fall without risking non-compliance in EU markets.

What the next three to five years look like for FHIR in Europe

The trajectory of FHIR adoption in Europe over the 2026 to 2030 period will be shaped by three converging forces: regulatory pressure from the EHDS, medical record system vendor product development cycles, and growing demand for FHIR-enabled clinical applications.

Regulatory pressure will intensify as the March 2027 deadline for EU Implementing Acts approaches. Once those acts are finalised, medical record system vendors operating in EU markets will face binding technical requirements for EEHRxF compliance. Health systems that have not begun FHIR implementation programmes will face a compressed timeline. The peer-reviewed policy analysis of the EEHRxF implementation landscape argues for harmonised, predictable implementation timelines, but also acknowledges that the current absence of finalised Implementing Acts is slowing hospital-level planning.

Medical record system vendor consolidation is likely to accelerate FHIR standardisation in some markets while entrenching proprietary approaches in others. Markets where a small number of vendors hold dominant positions and where those vendors have strong FHIR roadmaps are likely to see faster progress than fragmented markets with many legacy systems.

AI-driven clinical tools represent a significant emerging demand signal for FHIR infrastructure. Clinical decision support systems, ambient documentation tools, and research platforms all depend on access to structured, standardised clinical data. The S-RACE platform's approach, using NLP to transform unstructured hospital data into FHIR format as a foundation for AI model development, illustrates how FHIR infrastructure and AI capability are becoming interdependent. The federated analysis study across Bavarian hospitals demonstrated that FHIR-based data transformation at scale can support multi-site research without requiring centralised data pooling, a model with direct implications for privacy-preserving AI development across European health networks.

The EHDS's projected €11 billion in savings from improved health data accessibility provides the economic rationale for sustained investment. Realising those savings requires resolving the implementation variation, skills gaps, and governance challenges that currently constrain FHIR's practical impact. Those challenges are unlikely to be fully resolved within the next three to five years, even as regulatory pressure and vendor capability continue to improve.

For healthcare decision-makers, the realistic near-term horizon is one of incremental progress: FHIR adoption advancing in specific care settings and use cases, national profiles becoming more settled as EHDS Implementing Acts are finalised, and a growing body of implementation evidence from the Hospitals on FHIR community and similar networks providing practical guidance for institutions beginning their own programmes. System-wide, semantically interoperable FHIR deployment across European hospital networks remains a medium-term ambition rather than an imminent reality.

Frequently asked questions

▶ What is HL7 FHIR and why does it matter for European hospitals?

Fast Healthcare Interoperability Resources (HL7 FHIR) is an internationally recognised standard for exchanging clinical data between health information systems. It defines modular components called "resources" that represent discrete units of clinical information, such as a patient record, a diagnostic result, or a discharge summary, and exchanges them over standard web application programming interfaces. For hospital administrators, the significance is operational: when clinical systems can't exchange data reliably, care continuity suffers, admin burden increases, and the data infrastructure needed to support AI-driven clinical tools stays out of reach.

▶ What EU regulation is driving FHIR adoption, and what are the key deadlines?

The European Health Data Space (EHDS) Regulation, which entered into force in March 2025, mandates that medical record systems across EU member states adopt the European Electronic Health Record Exchange Format, which is built on FHIR specifications. EU Implementing Acts, expected by March 2027, will define the precise technical and semantic requirements that medical record systems must meet. Until those acts are finalised, implementation timelines remain somewhat uncertain for health system planners.

▶ Which European countries are furthest ahead with FHIR adoption?

The Nordic countries, particularly Finland and Denmark, represent some of the most advanced implementations, benefiting from centralised national health data infrastructure and a tradition of medical record system standardisation. The Netherlands has made significant progress through the MedMij framework, which mandates FHIR-based APIs for data exchange between healthcare providers and personal health environments. Germany has embedded FHIR requirements for specific hospital use cases through the ISiK standard within its national digital health infrastructure. Common factors across these markets include clear national governance, regulatory mandates that shape procurement, sustained public investment, and national FHIR profiles that reduce implementation variation.

▶ What are the main barriers to FHIR adoption in European hospitals?

Legacy medical record systems are the single most significant obstacle. Many European hospitals operate on clinical systems designed before FHIR existed and lacking native FHIR support, and mapping data from those systems to FHIR has been identified as the biggest implementation barrier in multi-site deployment studies. Skills gaps compound the problem: hospital IT teams frequently lack in-house FHIR expertise, and this is effectively prohibitive for smaller hospitals. Inconsistent national API standards, different FHIR versions across sites, and the underestimated cost and complexity of legacy migration all extend timelines and increase costs beyond initial projections.

▶ Does adopting FHIR automatically produce interoperability between health systems?

No. FHIR is a framework, a set of rules for structuring and exchanging data, but it permits significant variation in how those rules are applied. Different health systems may implement FHIR using different versions, different national profiles, and different extensions. A FHIR resource produced by one system may be structurally valid but semantically incompatible with a resource produced by another. Terminology bindings, such as SNOMED CT for clinical concepts and LOINC for laboratory results, are equally critical: where these are absent or inconsistently applied, data exchange produces records that are syntactically correct but clinically ambiguous.

▶ How does GDPR affect FHIR implementation in European hospitals?

GDPR and national data sovereignty frameworks create a compliance layer that significantly affects how FHIR infrastructure can be designed and operated. The most acute tension arises in cloud-hosted FHIR server deployments. Countries such as Germany and France restrict where health data can be processed and stored, which constrains the use of non-EU cloud providers and in some cases requires on-premises or sovereign cloud deployments. For cross-border data exchange under the EHDS framework, health data shared across member state borders must satisfy both the technical interoperability requirements of the EHDS and the data protection requirements of the jurisdiction in which the data subject resides.

▶ What should hospital decision-makers assess before committing to a FHIR implementation programme?

The most consequential first step is assessing medical record system vendor FHIR readiness: which version of FHIR the current vendor supports, whether that support is native or delivered through middleware, and what the vendor's roadmap is for EHDS compliance. Decision-makers should also confirm they're implementing against the applicable national FHIR profile rather than a vendor-specific variant, assess the terminology bindings required for semantic interoperability, establish a clear data governance and GDPR compliance approach for FHIR server infrastructure, and verify that sufficient FHIR implementation expertise is available. Phased implementation, starting with the highest-value use cases, is more realistic than a comprehensive migration approach for most institutions.

▶ How do medical record system vendors affect FHIR adoption at the hospital level?

Medical record system vendors are a decisive variable. Their technical choices, commercial incentives, and product roadmaps directly determine how quickly and how fully hospitals can implement FHIR-based interoperability. A consistent pattern across vendors is the use of middleware and API gateway layers as a short-term solution, exposing FHIR endpoints without requiring a full re-architecture of the underlying system. This supports regulatory compliance but doesn't deliver the same depth of interoperability as native FHIR support, and creates ongoing maintenance complexity. Vendor lock-in remains a structural concern: hospitals with long-term investments in proprietary systems face significant switching costs, which reduces their leverage in demanding FHIR conformance.

▶ What is the realistic outlook for FHIR adoption across European hospitals over the next three to five years?

The trajectory will be shaped by regulatory pressure from the EHDS, medical record system vendor product development cycles, and growing demand for FHIR-enabled clinical applications, including AI-driven clinical decision support and ambient documentation tools. The March 2027 deadline for EU Implementing Acts will intensify pressure on vendors and health systems that haven't yet begun implementation. However, the implementation variation, skills gaps, and governance challenges that currently constrain FHIR's practical impact are unlikely to be fully resolved within that timeframe. System-wide, semantically interoperable FHIR deployment across European hospital networks remains a medium-term ambition rather than an imminent reality.