BRAIF Conceptual model

The Base Registries Access and Interconnection Framework (BRAIF) aims to guide on the creation of an ecosystem of interconnected base registries which exchange data and, therefore, facilitate the set up of integrated public services.

In the context of the European Strategy for Data, BRAIF supports its implementation by provision to Member States of a set of good practices in the area of base registries interconnection, allowing secure cross-border sharing of data, and establishing a base for the future European Registry of Base Registries. The current state of Base Registries in Member States indicates they are in different phases of maturity, hindering, thus, their ability to implement any common data framework. Here you can see how the move from a legacy environment to a future state of affairs should look like.

BRAIF Conceptual model

The BRAIF conceptual model defines a series of steps to take in order to establish structure-based Base Registries that enable the delivery of cross-border integrated public services. Integrated public services are services, which are delivered under different legal frameworks, policies and strategies. The BRAIF conceptual model presents the necessary phases needed to establish cross-based Base registries within the State, and interoperability governance based on such Base Registries. The starting point of the cycle differs among services depends on their respective maturity levels.

The justification of this approach is illustrated by the most common maturity use cases available for further read in the BRAIF document, page 16.

BRIAF conceptual model — *BRAIF conceptual model*

Phases of the cycle

There are different phases of the cycle, which can be grouped in the following categories

Phase I

Passing from the legacy environment into a Common Governance with a specific Strategy under certain interoperability agreements

Outputs of this phase:

Data governance
Metrics

Phases concerning the interconnection of base registries
Phase	Description/Scope
*1. Model Data Governance*	This phase aims to establish a cross-domain data governance organisation, which then sets the rules and policies on how to manage the data.
2. Reuse the data in base registries via integrated public services	This phase aims to set up the integrated public services that reuse data from base registries, and establish the interoperability agreements.

Phase II

Setting the standards and creating more lean processes

Output of this phase:

Data Architecture

In detail explained in section 2.2, pages 26-29 of the BRAIF, this group of phases focuses on the actual implementation based on the global principles defined for the delivery of the integrated public service.

Standards and Processes
Phase	Description/Scope
1. Development of a trusted registry	This phase takes place when important pieces of authoritative information are not managed by Base Registries. Hence, two main scenarios can occur to trigger the need for this phase: either a new base registry should be built from scratch, or the mandate or scope of existing base registries has to be significantly changed
2. Information Exchange	Information exchange is the first step towards the construction of an integrated public service, where multiple base registries are really collaborating and contributing technically to build a future integrated public service. The data stored in the base registry will be exchanged with other stakeholders following the defined data policies and the interoperability agreements.
3. Once-Only Principle	The Once-Only Principle entails that citizens and businesses provide diverse data only once in contact with public administrations, while public administration bodies take actions to internally share and reuse these data – even across borders – always in respect of data protection regulations and other constraints.
4. Aggregation / Enrichment	Aggregation and enrichment are transformations that can be made to raw data in order to adjust the information to the needs of the end users.
*5. Data Evaluation*	The service, once provided, should be monitored and evaluated. It should be assessed whether it meets the objectives established during the definition of the service. The result of this assessment is the driver for possible changes to the service, its objectives and/or its organisation.

Phase III

Using common data models and mastering the data under profound Data Security and Quality

Outputs of this phase:

Master data management
Metadata management
Data security
Data quality

In detail explained in section 2.3, pages 29-39 of the BRAIF, this group of phases focuses on the conceptualisation of data models through management of Master data, the main asset of a Base registry, with a continuous cycle of Data Quality, having the data protected and secured.

Master Data Management phases
Phase	Description/Scope
1. Plan	This phase consists of a sequence of actions, intended for the creation of a data management plan. In a data management plan, the sources from which data will be retrieved are identified and secured, and the processes for data gathering, management and use are defined.
2. Specify	The aim of this phase is to ensure a comprehensive and consistent data definition. This is done through the standardisation of data in the data model, which establishes the relationship between data itself, and the properties of the entities that they represent.
3. Enable	This phase has an objective of ensuring all necessary infrastructure for the adoption of the predefined data models in place. This should include several aspects, starting from the construction of the repositories and interfaces of the solution. Once built, they should be tested in order to ensure their full operability. If the tests are satisfactory, the components of the solution are deployed. Finally, this phase will also include the maintenance of all solution components while the service is running.
4. Create	Once all the necessary infrastructure is in place and in normal operation, the data shall be designed. This data has to comply with the data model and other characteristics, previously defined in the service’s data policies, set by the data governance body. It also has to be relevant from the point of view of the service in terms of business value.
*5. Acquire*	This phase consists of the acquisition of data from other repositories to store it in a Base Registry. The acquired data has to be analysed in order to determine their degree of compliance with the different sets of characteristics for data, defined by the Base Registry itself, like the format and the terminology in which data are expressed.
6. Maintain	This phase consists of performing the necessary activities to ensure the integrity and comprehensiveness of data during the service’s lifecycle. One of the main activities performed in the context of this task is data cleansing. Data cleansing covers detecting and correcting inaccurate or corrupt data stored in the Base Registry, identifying the affected parts of the data, and replacing them with other data.
7. Archive	In this phase, the data is archived in the Base Registry. The actual repository in which the data is archived depends on the layout of the base registries for the delivery of the integrated public service. A centralised Base Registry will archive its data primarily in a main repository, while a federated Base Registry will rely on a set of repositories distributed across its Base Registries.
8. Retrieve	In this phase, the archived data is being retrieved, when needed. It is essential to study the related regulatory requirements for data archiving and retrieving in order to adopt the best solution.
9. Purge	This is the last phase of the data lifecycle and it implies the elimination of data that have been evaluated as not relevant or necessary anymore, or which an entrusted actor has requested their elimination. One example is a request for the elimination of personal data.

Potential barriers

Base Registries Access and Interconnection Framework (BRAIF) detected a list of potential barriers which can hinder the process for reforming the state of Base Registries in Member States:

Lack of legal frameworks and relevant regulations, which negatively affect the implementation of Legal Interoperability;
Lack of coordination between officials, which hinders Organisational Interoperability;
Difficulties to apply the basic principles of EIF, which lowers the trust in EC recommendations;
Poor data quality, which results in wrong decision-making, poor operations and cost increase;
Lack of strategic orientation, which corresponds to poor (or non-existent) policy-making;
Unclear technical and semantic specifications, which hinder proper implementation of the respective EIF levels and the adoption of standards.

To help overcome these barriers, BRAIF supports in the following aspects:

Enabling Base Registry access, interconnection and integration with a clear methodology and a systematic approach;
Defining a common terminology and regulated procedures on national and cross-border levels between Member States. This should be the basis for a common language for Base Registry Interoperability (BRI).
Providing the means for data quality and management plans by defining the systematic approach for integrated digital public services;
Improving the coordination and control between State officials, as the common language of BRI, thus, fostering Organisational Interoperability;
Supporting the development of technical and semantic requirements that in turn facilitates the creation of Base Registries.
Strengthening policy drafting and the preparation of national and cross-border interoperability strategies.
Enabling the efficient, agile and secure reuse of data and services to empower citizens and businesses.

Report abusive content Share

BRAIF Conceptual model