Interoperability Requirements

Interoperability requirements in public procurement specify that a technology system must be capable of communicating, exchanging data, and working alongside other systems without special configuration or proprietary agreements. For public sector organisations across Europe, interoperability is not merely a technical preference but a policy priority enshrined in the European Interoperability Framework (EIF) and reinforced by the Interoperable Europe Act, which creates binding obligations for EU public administrations to assess and promote interoperability in cross-border digital services.

What are interoperability requirements?

Interoperability requirements in a procurement specification define the protocols, APIs, data formats, and integration points that a supplied system must support. They may address technical interoperability (the ability to exchange data using defined protocols), semantic interoperability (the ability to understand the meaning of exchanged data through shared vocabularies and ontologies), organisational interoperability (the alignment of processes to enable joined-up service delivery), and legal interoperability (consistent regulatory frameworks enabling data sharing across borders).

In practice, procurement specifications for enterprise systems typically require: documented and publicly accessible APIs using standard protocols (REST, SOAP, SPARQL); data exchange using open formats (XML, JSON, CSV with defined schemas); support for EU common standards such as the Core Vocabularies (developed by the European Commission's ISA2 programme for person, business, location, and public service data); and compliance with national data exchange frameworks (such as the UK's G2G API standards or the Nordic countries' digital infrastructure layers).

The Interoperable Europe Act (Regulation (EU) 2024/903) creates a specific duty for EU public administrations to conduct interoperability assessments when procuring or developing ICT systems used for cross-border data exchange. This assessment must be published, adding a new compliance step for public sector buyers across EU member states.

Open standards in procurement are the mechanism through which interoperability is typically achieved. The technology code of practice in the UK requires all government technology to be designed for interoperability and to use open standards.

Why it matters for bidders

Suppliers must design for interoperability as a baseline expectation in European public sector procurement, not as an optional extra. Tender specifications increasingly include specific API and data format requirements as pass/fail criteria. Suppliers whose products rely on proprietary integration methods, or who do not publish API documentation, will struggle to pass selection at the specification compliance stage.

For software as a service (SaaS) and cloud hosting suppliers, interoperability requirements also cover exit provisions: buyers will require that data can be exported in open formats and that the supplier supports migration to an alternative at contract end. Suppliers should document their data portability capabilities and make this information available in their procurement responses.

Example

A Finnish regional health authority procures a new patient data platform and specifies compliance with the HL7 FHIR standard for health data exchange, REST APIs documented using OpenAPI 3.0, and support for the EU Patient Summary standard enabling cross-border data sharing under the European Health Data Space. Suppliers must demonstrate conformance testing results against these standards as part of their technical evaluation.

Frequently Asked Questions

What is the European Interoperability Framework?

The European Interoperability Framework (EIF) is a set of guidelines published by the European Commission that recommends how public administrations across EU member states should design and provide their digital services to be interoperable. It defines four layers of interoperability (legal, organisational, semantic, and technical) and provides practical recommendations for procurement, data exchange, and service design.

Are interoperability requirements the same as open standards requirements?

They are closely related but not identical. Open standards are the technical specifications used to achieve interoperability. Interoperability requirements describe what the system must be able to do (exchange data with system X using format Y). Open standards requirements describe how this must be achieved (using a published specification rather than a proprietary protocol). In practice, both appear together in well-drafted ICT specifications.

What happens if a procured system fails to meet interoperability requirements after contract award?

Failure to meet specified interoperability requirements is a breach of contract. Buyers should include specific acceptance criteria and milestone checks for interoperability compliance, particularly at system go-live and at key integration points. Exit planning should also verify that data can be extracted in the specified formats before the incumbent contract ends.