The OOTS reuses the eDelivery Building Block and uses its Access Point specification for the evidence exchange process. Being connected to the eDelivery network of nodes with an Access Point set up is a prerequisite to implementing the OOTS in your Member State. An Access Point in the Once-Only Technical System performs key security and reliability functions. It signs and encrypts messages and, in a delegated role, provides integrity, confidentiality, authenticity and non-repudiation of origin and receipt as explained in the Security Controls guidance document.

The eDelivery Access Points will enable the secure exchange of evidence between European countries required in administrative procedures (such as birth certificates, university diplomas and alike) with one another.

You can access the eDelivery building block here:

eDelivery building block

To secure Access Point messaging, you can choose to use your certificate. Otherwise, you can request an X.509 certificate from the eDelivery PKI.

To do this, you should follow the instructions detailed in the OOTS Onboarding Toolkit

If you are not yet connected to the eDelivery network of nodes with an Access Point set up or need support with regards to your eDelivery Access Point, please contact the eDelivery Service Desk

Member States' Procedure Portals acting as Evidence Requesters need to understand how their role fit into the Once Only Technical System Architecture in order to be able to perform the technical integrations required for operating in such role.

Evidence Requester Architecture Elements

Evidence Requester role is the one triggering the Data Exchange process and needs to understand it in order to be able to make the necessary requests and manage responses.

Exchange Data Model and Protocol

Before triggering the Exchange Data process, some parameters need to be queried to the Common Services using the APIs provided.

Data Services Directory API

Evidence Broker API

The OOTS Common Services Administration Tool allows Member States to create and manage configurations related to the procedures in scope of the OOTS. The following procedures can be carried out using the Tool:

Evidence Providers can:

• Create a data service
• Create an evidence provider
• Create an evidence type
• Link an evidence provider to an evidence type
• Link an evidence type to a requirement
• Link a requirement to a group of evidence types

Evidence Requesters can:

• Link a procedure to requirement(s)

OOTS provides MS with a set of tools to help implementors understand the end-to-end journey and the user’s pain points by creating a common understanding of the UX issues that need to be addressed and providing actionable recommendations that create a coherent user experience.

UX Lab is a community with designers from all member states to discuss about UX implementations and improve together whose output is a set of document with UX recommendations and some reusable components for the implementation.

OOTS UX Lab

Discover the UX guidelines

Testing services are a useful resource for development teams in the Member States while developing their OOTS components or integrations. E.g. the testing services allow developers to have a look at how the interfaces look like and what the expected behaviour is of the different components. They can start with the sample projects in the testing tools while their components are under development and gradually replace the testing tools with their own components.

The details of the testing service will further be discussed and elaborated in the testing and deployment sub-group.

The testing information currently available is intended as testing services for Member State teams:

• to get early access to the services and tools as prepared by the EC team.
• to familiarise yourselves with the testing approach and to see if this fits within their development and integration procedures.
• to provide feedback and think about further improvements or additions, to be picked up by the testing and deployment sub-group.

OOTS Testing Services

For both Evidence Requesters and Evidence Providers, once you have explored the standalone tests that you can execute at any time, in any order and on your own against the Test Platform, the following step is to attend one or more Projectathon events. These events bring together teams, either physically, virtually or in a hybrid format, to ensure functionality, interoperability and production-like scenarios and data flows.

All relevant information to plan and prepare your participation to a Projectathon is available via the link below:

Participate in Projectathons

OOTS provides information on security policy and objectives, as mandated by the legal framework. Each security objective is mapped to either a system functionality or a responsible for procedural or operational arrangement. Information on OOTS security policy and objectives is available via:

OOTS Security Policy

OOTS also provides recommendations on security and policy requirements for the management of eDelivery Access Points. The recommendations on security for the management of eDelivery Access Points is available via:

eDelivery Security Requirements

ANNEX: Security Framework