The European Interoperability Framework (EIF) is the EU's commonly agreed approach to delivering public services that work across organisations and borders. It sets out principles, models and recommendations for public administrations to follow when they design services, write rules and build systems.1 The current version was published by the European Commission in March 2017, and since 2024 it has had a footing in law through the Interoperable Europe Act.14
What the EIF is and where it came from
The EIF defines interoperability as the ability of organisations to interact towards mutually beneficial goals, sharing information and knowledge through their business processes by exchanging data between their information and communication technology (ICT) systems.1 It is written for everyone who defines, designs, develops or delivers European public services, meaning public services with a cross-border dimension, whether provided to other administrations, to businesses or to citizens.1
The Commission dates the first EIF to 2004.3 A 2010 Communication, "Towards interoperability for European public services", carried an updated framework that, in the Commission's account, became the basis of most national interoperability frameworks.1 The 2017 revision, published as Annex 2 to Communication COM(2017) 134, raised the number of recommendations from 25 to 47, made them more specific and put more weight on openness, information management, data portability, interoperability governance and integrated service delivery.1
The twelve principles
The EIF's twelve underlying principles describe how interoperable public services should behave. They fall into four groups.1
| Group | Principles |
|---|---|
| Setting the context for EU action | 1. Subsidiarity and proportionality |
| Core interoperability principles | 2. Openness; 3. Transparency; 4. Reusability; 5. Technological neutrality and data portability |
| Generic user needs and expectations | 6. User-centricity; 7. Inclusion and accessibility; 8. Security and privacy; 9. Multilingualism |
| Cooperation among public administrations | 10. Administrative simplification; 11. Preservation of information; 12. Assessment of effectiveness and efficiency |
Subsidiarity comes first for a reason. The EIF is meant to be the "common denominator" of national policies, leaving Member States free to tailor and extend it.1 User-centricity carries the once-only idea: as far as the law allows, users should provide data only once, and administrations should retrieve and share it to serve them, in line with data protection rules.1 The guide to the once-only principle explains how the EU has turned that into a cross-border system.
The layered model and the conceptual model
The interoperability model has four layers, legal, organisational, semantic and technical, with integrated public service governance cutting across them and interoperability governance in the background.1 The guide to semantic interoperability explains each layer and why shared meaning is so often the weak point.
The conceptual model describes how integrated public services should be put together, and promotes "interoperability by design" as the standard approach.1 Its main parts are:
- a coordination function that removes complexity for the user and takes a request through need identification, planning, execution and evaluation;
- a "no wrong door" delivery policy, which offers alternative options and channels while making sure digital channels are always available ("digital by default");
- reuse of existing data and services, from base registries and open data to shared services such as electronic identification;
- catalogues that describe reusable services, data and solutions so that others can find them;
- integrated public service governance, and security and privacy.
The EIF calls base registries the cornerstone of European public service delivery: trusted, authoritative sources of basic information on people, companies, vehicles, licences, buildings, locations and roads, each with one organisation accountable for it.1 There is more on how they work in base registries and data exchange.
The 47 recommendations
The 47 recommendations are the actionable part of the framework, addressed to public administrations and spread across its chapters.1 The Commission's monitoring groups them under three pillars (principles, layers and the conceptual model) and 25 thematic areas.2 A few show the range:1
- Align national frameworks with the EIF, tailoring and extending them to national needs (recommendation 1).
- As far as the law allows, ask users for information once only, and only for relevant information (recommendation 13).
- Screen legislation with "interoperability checks" and give draft laws a "digital check" (recommendation 27).
- Set an information management strategy at the highest possible level, prioritising metadata, master data and reference data (recommendation 31).
- Use open specifications, where available, for technical interoperability (recommendation 33).
- Make authoritative sources of information available to others, with access controls that protect security and privacy (recommendation 37).
How national frameworks use it, and how far it has taken hold
The EIF is not meant to be copied wholesale. National interoperability frameworks (NIFs) are expected to build on it, adding new elements or fine-tuning existing ones, and frameworks for particular domains should stay compatible with it.1 The EIF describes value in two directions: a NIF aligned with it prepares national services to work across borders, and EU laws that draw on it make national implementation more likely to fit together.1
Alignment on paper has been easier than delivery. The Commission's observatory found that alignment of NIFs with the EIF reached an average of 72% in 2014, but that NIF implementation in specific national projects was 45% in 2015.1 The Commission has since run an EIF Monitoring Mechanism with yearly data collection across European countries, although no data was collected in 2024.2
The evaluation published with the 2022 proposal for the Interoperable Europe Act was candid. It found that some EIF recommendations were already conceptually implemented in Member States, but that the framework did not sufficiently support the practical implementation of interoperable digital public services. The accompanying impact assessment called for better governance, more common and potentially binding rules, and closer alignment of EU policies and funding programmes with the EIF.3 The trade-off is a familiar one: a voluntary framework respected national differences, as the subsidiarity principle intends, but gave no one a duty to act.
The EIF under the Interoperable Europe Act
Regulation (EU) 2024/903, the Interoperable Europe Act, gives the EIF a legal role. The Interoperable Europe Board develops it and submits it to the Commission, which publishes it in the Official Journal if it adopts it. The Act describes the EIF as a model and a set of recommendations for legal, organisational, semantic and technical interoperability and for its governance.4
Two duties follow. Public bodies carrying out the Act's interoperability assessments use the EIF as a support tool, and a Member State developing a national interoperability framework must take the EIF into "utmost account".4 The Commission may also adopt specialised frameworks for particular sectors or levels of administration, which must be based on the EIF.4 The guide to the Interoperable Europe Act covers its other requirements.
A review is under way. The Commission and the Board have launched a revision of the EIF, with consultation activities, including a call for evidence, due to begin in May 2026.5 Until a revised framework is adopted, the 2017 version remains the reference.
In practice: the European Interoperability Framework
What it fixes
- Gives teams a shared checklist of principles and layers to test a service design against.
- Helps national frameworks line up, so services built to them are easier to connect across borders.
- Makes reuse of existing data, services and base registries the default starting point.
- Gives legal, policy and technical staff a common language for interoperability.
What gets in the way
- Voluntary recommendations were easy to endorse and easy to leave unimplemented.
- Alignment of national frameworks on paper has not always reached individual projects.
- Forty-seven recommendations are a lot for a small team to prioritise.
- Older systems and sector-specific rules limit how far a single body can follow it.
Where to start: Map one planned or existing service against the EIF's four layers and its conceptual model, noting where it already reuses data or services and where it doesn't. If your country has a national interoperability framework, start from that, since it should already tailor the EIF to your context.
Sources
- European Interoperability Framework - Implementation Strategy (COM(2017) 134 final), with Annex 2: the European Interoperability Framework, European Commission (EUR-Lex). Accessed 17 October 2026.
- EIF Monitoring, European Commission, Interoperable Europe Portal. Accessed 17 October 2026.
- Proposal for a Regulation laying down measures for a high level of public sector interoperability across the Union (Interoperable Europe Act), COM(2022) 720 final, European Commission (EUR-Lex). Accessed 17 October 2026.
- Regulation (EU) 2024/903 of the European Parliament and of the Council of 13 March 2024 laying down measures for a high level of public sector interoperability across the Union (Interoperable Europe Act), Official Journal of the European Union (EUR-Lex). Accessed 17 October 2026.
- Two years on, the Interoperable Europe Act moves from law to delivery, European Commission, Interoperable Europe Portal. Accessed 17 October 2026.