Learn AI /AI Governance and UN Terminology /Interoperability
Interoperability
- Intermediate
- AI Governance and UN Terminology
- Policy officers
- Technical readers
Also called: interoperable.
Back to the milestone you came from
In five seconds
What it is
The ability of systems or organisations to exchange information and use it correctly under compatible rules.
In plain words
Different systems or organisations can share information and use it properly, instead of forcing people to re-enter or reinterpret everything by hand.
An everyday example
A parcel may travel through several delivery companies. Interoperability means each company can scan the label, interpret the address and handling codes in the same way, and update the delivery record under compatible rules. If every scanner reads the barcode but one courier treats “keep upright” as “deliver urgently”, the systems exchange data but do not use it correctly.
A report template is a simple object, but real interoperability often involves many moving parts at once: software interfaces, identifiers, permissions, legal constraints and different definitions. Two systems may exchange a file successfully yet still not be truly interoperable if they classify the same event differently, apply different access rules or lose important context during transfer.
Remember thisInteroperability means systems can exchange information and preserve enough shared format, meaning, process and governance for it to be used correctly.
This term is contested
The core idea is widely used, but the exact scope can vary by context: some communities stress technical compatibility, while others include organisational, legal and semantic alignment as essential parts.
Understand it
Understand it
Why it matters
For non-specialists, interoperability matters because many policy and operational failures come from systems that cannot share usable information. That can mean duplicate work, delayed analysis, inconsistent oversight and poor comparisons across organisations or countries. In AI governance, it affects whether audit results, incident reports, risk classifications and technical documentation can be reused across borders and institutions. Good interoperability can lower costs and support coordination, but weak interoperability can create false confidence if data moves without preserving meaning, context or safeguards.
How interoperability turns separate systems into usable exchange
Show that interoperability requires not just transfer, but also shared meaning and usable action across systems.
01
Separate systems
Two organisations collect similar information, but they store it differently.
Draw two boxes labelled System A and System B. Inside each, show different field names for similar concepts, such as 'incident_date' in one and 'date of event' in the other.
02
Shared bridge
They agree on mappings, formats, identifiers and rules for exchange.
Place a middle layer between the systems labelled Shared schema, metadata and exchange rules. Add arrows from both systems into this layer.
03
Correct interpretation
When information moves across, the receiving side can place each item in the right category and keep its meaning.
Show an arrow from the bridge to a receiving box where fields line up correctly: date to date, location to location, category to category.
04
Usable joint output
Because the data can be exchanged and interpreted, people can compare, combine or act on it more reliably.
End with a combined output panel showing a simple chart, alert list or merged report built from both sources.
A left-to-right flow with four stages. Stage 1 shows two separate systems with different internal formats. Stage 2 shows a bridge layer with shared fields, identifiers and rules. Stage 3 shows exchanged data being interpreted correctly. Stage 4 shows a joint output such as a combined dashboard or report. Read from left to right to see that simple transfer is not enough; the receiving side must preserve meaning and use the information.
Hover or tap each stage to reveal one extra note: format, meaning, governance, then outcome.
Describe this without the diagram
The diagram is a four-stage flow from left to right. First, two separate systems hold similar information in different structures. Second, a shared bridge layer aligns fields, metadata, identifiers and exchange rules. Third, data passes through that bridge and is interpreted correctly by the receiving system, so categories and dates still mean the same thing after transfer. Fourth, the aligned information is used in a combined output such as a merged report or dashboard. The main lesson is that interoperability is more than sending data; the receiver must also preserve meaning and be able to use it.
With reduced motion: A static four-column diagram shows separate systems, then a shared bridge, then correct interpretation, then a joint output, with labels explaining that transfer alone does not guarantee interoperability.
Interoperability means separate systems can work together without people having to rebuild or retype everything each time. What goes in can be data, documents, messages, technical formats or agreed procedures. What happens in the middle is that the parts match well enough to exchange and interpret that input. What comes out is coordinated work across tools, teams or institutions.
This idea applies at more than one level. Technical interoperability is about compatible file formats, interfaces and data structures. Organisational interoperability is about workflows, roles and responsibilities lining up. Legal or policy interoperability is about rules that allow exchange and use under agreed conditions. A system may succeed at one level and fail at another.
In AI governance, the term often appears when countries, agencies or platforms need to share information about AI systems, risks, audits or standards-based assessments. For example, one body may record an incident in one format and another body may need to compare it with its own records. If the categories, definitions and metadata are aligned, the information can travel and still keep its meaning.
Interoperability is often confused with standardisation, but they are not the same. A standard is a documented specification or agreed method. Interoperability is the practical ability to connect and use information across boundaries. Standards can help create interoperability, but systems can follow a standard and still fail to work together if implementation, governance or context differ.
How “A parcel changing couriers” maps onto the real thing
| In the story | In the AI system |
|---|---|
| shared report template with clear headings | common structure or schema for information exchange |
| different office software opening the same file correctly | different systems reading the same format |
| dashboard importing date and event type into the right boxes | receiving system interpreting data fields correctly |
| team spending time comparing reports instead of cleaning them | reduced friction and better coordination across organisations |
A worked example
A programme officer in a regional bureau must combine country office progress reports in the corporate portal before the reporting window closes.
Starting from: One office reports activities by workplan output, another by project code, and a third by results-framework indicator. Their exports also represent reporting periods and implementation status differently.
- The programme officer identifies which fields are technically exchangeable and maps each local field to the portal structure.
- The reporting focal points agree common definitions for reporting period, completion status and responsible office. A shared label without a shared meaning would merely produce tidier confusion.
- A conversion rule changes the files into the required structure while retaining source identifiers and flagging entries that do not map cleanly.
- The offices review the flagged entries and confirm the applicable clearance and access rules before upload.
Result: The portal can combine and display the reports without changing their intended meaning. Entries that remain ambiguous are held for manual review rather than silently assigned to the wrong result.
In a United Nations workplace
A gender adviser in a UN Country Team working group is consolidating agency inputs for the situation report before the regional bulletin closes. The source systems export compatible spreadsheets, but they use different definitions for age groups, referral status and reporting periods.
Interoperability requires more than files that open. The working group must align field formats, definitions, metadata, clearance steps and access rules so that each contribution is interpreted and used as intended.
Before you try thisUse only aggregated, appropriately cleared information. Do not enter respondent-level, survivor, witness or other protection-sensitive data into an external tool that has not been approved for it. Combining datasets can expose identities through linked attributes even when names have been removed.
Where you may hear it
- A vendor demo before a procurement unit
- An inter-agency working group reviewing data-sharing arrangements
- An ICT governance board considering a new corporate platform
- Informals on language for digital governance
Avoid confusion
Avoid confusion
Often confused with
International standard
A document approved through a recognised international standards process that sets common requirements, guidance or methods for repeated use.
Regulation
A regulation is a binding rule made by a competent authority under rule-making powers granted by law for those within its scope.
Digital public infrastructure and digital public goods
Shared digital building blocks and reusable digital tools that help countries deliver public services, especially when they are designed for broad access and interoperability.
Common misconceptions
Common misconception: If two systems can send files to each other, they are interoperable.
Correction: File transfer is only one part. True interoperability also requires the receiving side to interpret the information correctly and use it in a meaningful workflow. If categories, identifiers or definitions do not match, the exchange may succeed technically but fail in practice.
Common misconception: Interoperability simply means using one international standard everywhere.
Correction: Standards often help, but interoperability is broader. It depends on implementation choices, governance, legal permissions, metadata and shared definitions. Two organisations may use the same standard and still not work together well, or they may achieve partial interoperability through mappings between different standards.
Common misconception: More interoperability is always better.
Correction: Not always. Greater connectivity can increase privacy, security and governance risks if it enables inappropriate sharing or unclear responsibility. Good design sets limits on what is exchanged, who can access it and for what purpose.
Quick check
Which situation best shows interoperability rather than simple data transfer?
The key test is not whether data moves, but whether it arrives in a form the receiving side can interpret and use correctly. Shared format, definitions and rules make that possible. The other options either still require manual repair or confuse interoperability with uniformity.
Go deeper
Go deeper
The simple version
Different systems or organisations can share information and use it properly, instead of forcing people to re-enter or reinterpret everything by hand.
The technical version
Interoperability is the capacity of heterogeneous systems, institutions or regulatory arrangements to exchange data, messages or artefacts and preserve sufficient semantic consistency, procedural alignment and governance compatibility for the receiving party to use them as intended. It can include syntactic compatibility, such as common file formats or APIs; semantic compatibility, meaning shared definitions and metadata; organisational compatibility, such as aligned workflows and responsibilities; and legal compatibility, including lawful bases, access conditions and accountability arrangements. It is therefore an outcome across layers, not just a feature of one technical interface.
Reviewed external resources
Primary sourceGlobal Digital Compact (opens in a new tab)United Nations
This link shows how the United Nations uses the idea in a wider digital cooperation agenda, and suits policy readers looking for official framing.
Intermediatelink checked 2026-07-31
Primary sourceGoverning AI for Humanity (opens in a new tab)UN Secretary-General's High-level Advisory Body on AI
This link offers high-level governance context for how cooperation across systems and institutions matters for AI, and suits readers connecting technical concepts to global policy.
Intermediatelink checked 2026-07-31
EncyclopaediaInteroperability (opens in a new tab)Wikipedia
This link gives a broad overview of the term, its main types and related ideas, and suits readers who want a quick starting point.
Intermediatelink checked 2026-07-31
VideoVideo explanations: Interoperability (opens in a new tab)YouTube search
This search results page offers a range of video explainers with different levels of depth, and suits readers who learn better by watching and comparing sources.
search results, not one pagelink checked 2026-07-31
DiscussionCommunity discussion: Interoperability (opens in a new tab)Reddit search
This search results page shows informal community discussions and examples of how people use the term in practice, and suits readers who want plain-language perspectives with caution about reliability.
search results, not one pagelink checked 2026-07-31
Where this came from
Drafted with a language model through an offline pipeline, checked against this site's schema, and every external link above fetched to see whether it answers. Treat it as a starting point and check anything that matters against the primary sources. How this site is built and what that means.
The one thing to remember
Interoperability means systems can exchange information and preserve enough shared format, meaning, process and governance for it to be used correctly.