You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Back to news

Formal Publication of Once-Only Technical System Technical Design Documents – Q4 2023 release 

09 Januuary 2024 | 4 minutes read

On 22 December 2023, the European Commission published the formalised Technical Design Documents for the Once-Only Technical System (OOTS). The publication of these documents is a major achievement for the national teams from EU countries working to implement Europe’s Once-Only Technical System.

The Once-Only Technical System is a technical framework for data sharing. When completing an online procedure, EU citizens and businesses will be able to make an (explicit) request to retrieve official documents or data (known as ‘evidence’) from a public authority in one Member State – such as for a diploma or driving license – and have it automatically exchanged with a competent authority in another EU country (educational institutions, population registers or company registers, for example).

These Technical Design Documents are non-binding technical and operational specifications that are prepared jointly by the European Commission and EU Member States. These documents add further detail and granularity to Implementing Regulation (EU) 2022/1463, which sets out the technical and operational specifications of the Once-Only Technical System (itself mandated through Article 14 of the Single Digital Gateway Regulation ((EU) No 1024/2012). Prior to December 2023, EU Member States referred to the draft Technical Design Documents.

Following the December 2023 Go-Live of the Once-Only Technical System Common Services, this Q4 2023 release of the OOTS Technical Design Documents should be used by EU Member States as the technical reference point for their respective Once-Only infrastructures implementations.

You can consult the latest Technical Design Document release on the Once-Only Hub. This content is complemented by additional documentation of the Common Services APIs and modelling, validating and testing artifacts maintained at the project’s GIT repository.

  • No labels