Base registries and secure data exchange

Base registries are the official registers that record the basic facts public services rely on: who lives where, which companies exist, who owns a piece of land, which vehicle belongs to whom. They matter because almost every service either checks or reuses one of these facts. When registries are accurate and can be queried securely, agencies can stop asking people for the same information again and again; when they are not, every service built on them inherits the problem.

What a base registry is

The European Interoperability Framework (EIF), adopted by the European Commission in 2017, defines a base registry as a trusted and authoritative source of information that can and should be digitally reused by others, where one organisation is responsible and accountable for collecting, using, updating and preserving it.¹ It gives population, businesses, vehicles and cadastres (land registers) as types of base registry, covering data about people, companies, vehicles, licences, buildings, locations and roads, and describes this as the master data for public administrations.¹ It also suggests administrations keep a high-level overview of their registries and what they hold, a registry of registries.¹

Authoritative here means the registry is treated as the source: it shows the correct status, is up to date and is of the highest possible quality and integrity.¹ An address register, for example, is not just a list of addresses. It is the record other services should check against, rather than keeping their own copies that slowly drift apart.

Why registries are the backbone of once-only services

The once-only principle says people and businesses should provide a piece of information to government only once. That only works if there is somewhere reliable for the second agency to fetch it from. Base registries are that somewhere: a birth recorded in the population register can be used by the benefits agency, the health service and the school admissions system without the parents filling in three forms.

Registries also underpin identity. When a digital credential vouches for a person's address or a company's directors, it is ultimately drawing on a register, which is why digital identity schemes are only as good as the registries behind them.

Principles for good registries

The EIF sets out recommendations that apply whatever technology a country uses.¹ Together with the basic need to link records reliably, they come down to a short list:

• One accountable owner. A single organisation must be responsible for each registry, or for each part of a distributed one, with one body coordinating the whole.¹
• Stable unique identifiers. Records need identifiers, such as a personal identification code or a company number, that other registers reuse instead of matching on names.
• Data quality you can check. Registries should follow a data quality assurance plan, and citizens and businesses should be able to check the accuracy and completeness of their own data.¹
• Clear access rules. Access should be regulated to comply with privacy and other law, with security and control mechanisms in place.¹
• Documented interfaces and meaning. Registries should publish their interfaces and metadata, including a glossary of terms, so others know what each field means.¹ Shared core vocabularies help here.

How Estonia's X-Road exchanges data

Estonia connects its registries through a data exchange layer called X-tee in Estonian. It was called X-Road in English until 2018; since then X-Road has referred to the technology developed jointly by Estonia, Finland and Iceland through the Nordic Institute for Interoperability Solutions (NIIS).² X-tee is not a central database. A member describes the data it is willing to share and other members can use it on the basis of an agreement; in the words of Estonia's Information System Authority (RIA), the owner controls the data throughout and the technology only offers a secure exchange.²

Every organisation connects through a security server, which signs messages, sends them over a secure channel, time-stamps them and logs them.³ A central server holds the register of members and the security policy, including which certification and time-stamping authorities are trusted.³ X-Road carries the two main styles of web service interface but does not convert between them, so the two ends still have to agree what they are exchanging.³ As at October 2026, e-Estonia's X-Road page lists over 3,800 e-services and 2.2 billion transactions a year.⁴

On the technical side, joining takes three steps. An organisation installs a security server, makes an agreement with the service provider whose data it needs, and builds the logic to send requests and process the replies.² Public and private sector organisations can both join.²

Exchange across borders

X-Road supports cross-border exchange through federation, which joins two national X-Road environments so their members can use each other's services; Estonia and Finland federated in February 2018.⁴ Their business registers and tax boards were connected in 2019, and in September 2020 automated exchange between the two population registers replaced batch exchanges that had run on average once a year under a 2005 agreement.⁵

The Finnish Digital Agency's account is candid about where the effort lies. Technology was no longer the barrier, it says; the 2005 agreement still limits which data can be exchanged, and widening it depends on further negotiation.⁵ It also describes what remains manual: when someone moves to Finland, identity is checked with a passport and family relations with legalised paper certificates from the country of origin, which direct queries to the other country's population register could one day replace.⁵

Risks and how to manage them

Connecting registries concentrates value, and with it risk. Three risks deserve particular attention, and none of them is solved by technology alone.

• Single points of failure. If shared infrastructure goes down, many services stop at once. X-Road's design limits this: security servers keep a local copy of the central configuration and certificate status, so they can keep working while those sources are unavailable.³ A registry itself can still be a single point of failure if it is offline or wrong.
• Misuse. Wider access means more people who could look at records without good reason. Logging every exchange helps, and since 2017 Estonia's data tracker has let people with an electronic identity (eID) see on the state portal which queries were made about their personal data in the registers that take part.⁶
• Poor data quality. A wrong address in an authoritative register is reused everywhere, so mistakes spread faster than before. Quality plans and a simple way for people to see and correct their own records are the main defence.¹