======Global architecture of the interconnected data pool======
The {{:znalostni-baze:ga_ppdf_hlavni_dokument_v1.5.docx |Global interconnected data fund Architecture}} is an annex of the [[[:nap_dokument|NAP]] itself and is elaborated in [[:znalostni_baze|expanding knowledge base]].
====== Executive Summary ======
===== Document Objectives =====
The Global Architecture of the Linked Data Pool of Public Administration of the Czech Republic presents a description of the Linked Data Pool, the rules of work of individual roles (editor, publisher, reader, manager, auditor) and the rules of providing data on subjects and objects in public administration information systems.
Due to the fact that this is a strategic document, not all the rules and requirements for the linked data pool may be in line with the current technical and procedural state of public administration information systems and the legislation in force. The aim of the document is to create a binding strategic framework that will be further developed in individual areas (information systems architecture, legislative framework).
===== High-Level view of the Linked Data Fund =====
The Linked Data Fund is being developed:
* **Agenda information systems**, which, by virtue of the execution of agendas, ensure the creation of data on subjects or objects of law (the data are created here) - hereinafter referred to as "authoritative data originator".
* **Basic registers ROB and ROS**, which, as specialised Agenda Information Systems, provide reference data on subjects of law and ensure unambiguous linking of data to the subject of law.
* **Basic register RÚIAN**, which as a specialised Agenda Information System provides unambiguous linking of data to territorial elements and addresses.
* **The ORG converter,** which ensures the conversion of the Basic Identifier of the natural person and the split electronic identity in the individual agendas (Agenda Identifier of the natural person).
* **Registry of Rights and Obligations - provides** reference data for the management and administration of the linked data pool.
* **Reference Interface** - a shared and secure interface to public administration information systems accessible via the Central Service Point.
* **Basic Registry Information System and Shared Service Information System -** part of the reference interface that provides application access to reference and agency information system data
> The linked data pool is therefore used for the exchange of data on subjects and objects of law.
The Linked Public Administration Data Pool creates a complete data base that contains all data on subjects or objects of law that are held in public administration information systems. However, the merging of data on a single subject cannot be carried out without the necessary authorisations of the individual agencies, and in particular the personal data of natural persons are highly secured against unauthorised merging.
The individual roles of the Agency Information Systems for activities in the linked data pool are:
* **Publisher** - Agenda Information Systems providing data on identified subjects or objects.
* **Reader -** Agency Information Systems and designated private data user information systems.
* **Reference interfaces** providing communication between readers and publishers.
Figure 1: Data distribution and exchange scheme
{{ :znalostni-baze:ga_ppdf1.png?600 |Figure 1: Data distribution and exchange scheme}}
Within each agenda, the following types of data are maintained about the entities in each role (context) in terms of the linked data pool:
* Reference data from basic registers.
* Data from other agendas (Agenda Information Systems).
* Data created within the framework of the agenda activity - only these data can be provided by the agenda to the linked data pool as data of the agenda information system.
It should be emphasised that reference data and data from agency information systems can only be provided within the linked data pool on entities that exist or have existed (e.g. deceased persons for a period of time before the deletion of the registration) in the basic registers. For other persons, there is no such unambiguous link to the entry in the basic registers and therefore the primary condition of unambiguous identification of the person about whom the data are transmitted is not ensured, and therefore the data are always of an informative nature only and it is not the case that the public authority using the data does not have to verify their validity.
The interconnected public administration data pool provides the highest benefit to the subjects of law, as it ensures that the public administration will work with their up-to-date data and that individual authorities/agencies will not repeatedly require citizens or legal entities to prove their data.
A significant benefit for public administration employees is precisely the status of //correctness// of the data on legal entities that they obtain through the linked data pool. This means that the data is guaranteed by the agencies in which it is created and the recipient does not have to carry out complex verification of the data necessary for the performance of their agenda.
====== Background and rules of the Linked Data Pool ======
===== Summary of functionality =====
The primary means of securing individuals' personal data is through the use of split identity, where an individual is held in each Agency Information System with a unique electronic identification using an AIFO (Agency Identifier of the Individual), which varies between Agencies. The converter of these AIFOs (ORG) is managed by the Data Protection Authority and is only available through the Information System of Basic Registers (ISZR). Therefore, without the cooperation of the ORG converter and the ISZR, it is not possible to merge data on one natural person from different agencies (including the basic registers of the Register of Population and the Register of Persons).
The management and description of the entire interconnected data pool is stored in the Register of Rights and Obligations, which contains a description of all parts of the interconnected data pool down to the technical details, enabling unambiguous implementation and management of all functionality, including the orchestration map of data folding.
This information is then used by the individual components of the Linked Data Pool to manage the processes and permissions for the transfer and use of data.
The Rights and Obligations Register is, amongst other things, the repository of all the information required for the transfer of data within the Linked Data Pool. It contains data on the individual process participants (Agency Information Systems, Public Authorities and Private Users), the structure of the data to be transferred, its representation (forms) and the structures for managing data access permissions. All participants in the linked data pool are obliged to follow these data.
==== Transmission of data ====
The transfer of Linked Data Pool data may be made on the basis of **direct** or **indirect** linkage
* **Direct linkage** - direct communication between different public administration information systems. In this communication, data are exchanged **without the participation** of the ISZR or ISSS**.** In the case of direct link communication on law subjects **__must__** not be transmitted by AIFO and the communication **__must__** be supplemented by indirect communication via the ISZR or ISSS, in which, in addition to the translation of the AIFO, the list of data that are transmitted in the direct link is also supplemented (in order to record this transmission).
* **Direct linkage** - transmission of data via ISZR and ISSS. When using this link, the link to the basic registers (verification of the existence of the entity in the basic registers and translation of the AIFO) and the recording of the list of data transferred is ensured. The indirect link also facilitates the work of the publisher, who does not have to create and maintain his own interface according to the PPDF rules.
The Rights and Obligations Register contains the control data for data transfer, including access permissions and technical details of individual components and data.
**It should be emphasised that the preferred approach is to use __indirect linkage__, i.e. use of the ISZR and ISSS.** Direct linkage can only be used when transferring large volumes of data on entities (e.g. periodic statements) and then only until indirect linkage via ISSS is assured. The direct link can still be used for the transmission of data on objects without a link to subjects.
==== Obligations of the publisher ====
The publisher must provide the following functionality:
* The output of data about an identified subject in an identified role (context) in accordance with the permissions of the reader.
* Identification of a subject according to a given set of data submitted by the reader about that subject in a given role (context).
* A record of all requests and responses (log) including data that is protected against unauthorized access and use. This record shall be provided with technical means (transaction identifiers) to ensure that records are linked across the entire linked data pool. The same obligation also applies to the reader and, consequently, to each ISVS according to the Decree on Act 365/2000, in particular the Decree on the reference interface.
* Means for receiving data complaints in accordance with the legal rules of the agenda
* Means for transmitting information on changes to the data of registered entities
* Means for technical verification of the availability of the publisher's services (probe).
The exchange of data must always follow the logic expressed in the following diagram.
Figure 2: Data exchange schema
{{ :znalostni-baze:ga_ppdf2.jpg?600 |Figure 2: Data exchange schema}}
This schema, with the necessary simplification, lays down the rules for creating and sharing data and for its subsequent maintenance by means of complaints.
The responsibilities of the publisher must be ensured by the subject administrator in cooperation with the technical administrator of the information system(s), if any, that ensure the execution of the agenda. It is emphasised below whether the information is intended primarily for the substantive administrator of the agenda or the technical administrator of the information systems.
===== Operational rules =====
This section summarizes the operational rules on the linked data pool, which are described in more detail in the following text.
A necessary condition for ensuring //the correctness/// of data and the use of the linked data pool is that the individual public authorities publish data from their agendas (agency information systems) properly to the linked data pool. It should be noted here that by publishing data from their information systems, the agenda manager immediately gains the following advantages:
* They do not need to build and maintain communication interfaces to different entities (providing a direct link), communication with the central components of the reference interface (indirect link) is sufficient for the purpose.
* It does not need to maintain and manage authentication of communication partners, reader data (public authority, agenda, Agenda Information System, etc.) is authenticated by central components and trusted.
* It does not have to manage the access authorisation system. It obtains the authorisation data from the Register of Rights and Obligations.
It is therefore in the interest of all Agency Administrators to maximise the speed of publication of Agency Information System data within the linked data pool.
==== Process Background ====
The Linked Data Pool ensures that public administrations processes work with up-to-date data on subjects and objects that are **correct**. The word correct means that the authoritative originator (the editor of the agenda providing the data or the editor of the reference data in the basic registers) confirms its correctness to the best of his knowledge.
Therefore, the data obtained from the linked data pool does not need to be verified by the recipient. A situation may arise where the authoritative originator of the data has doubts about the correctness of the data (handling a complaint), then the data is marked as incorrect by this originator. Conversely, the recipient of the data may discover facts in the course of its activities that are inconsistent with the data provided, then it initiates the complaint process, i.e. it notifies the originator of this doubt in the form of a data complaint.
The subject of the right, natural or legal person, then does not have to prove the accuracy of the data that can be obtained from the linked data pool when contacting the public administration.
The administrator of the AIS maintains the data pool of this AIS in an up-to-date form by using the processes of notification of changes to the data on the linked data pool and the user of the AIS is therefore assured that he is working with the correct data (in the sense mentioned above). From the point of view of the AIS user (official), this is therefore a major increase in efficiency and certainty in his work.
The data from the linked data pool is provided from one agency to another agency via the respective agency information systems. This process is done in the background through a reference interface and does not place any burden on the AIS user.
The second way of using the data is through a standard form of data release request (even bulk data such as a list of changes over a certain period). This form process is handled by the Forms Agency Information System (FAIS), which provides the interface between the Data Boxes (request and output) and the Linked Public Administration Data Pool (FAIS uses the services of the reference interface to handle the request).
In the following chapters of this document, the individual processes are described in detail with the addition of the required architectural and technical standards.
==== Technical background ====
The interconnected public administration data pool serves primarily to increase the efficiency of public administration performance support in terms of information systems support. Basic background of the Linked Data Pool:
* Each subject or object of law appears in information systems in a role (context) expressed in legislation (e.g. Citizen, Vehicle Owner, Patient, etc.). One agenda may contain several roles (contexts) for a given type of subject (natural person, natural person doing business, legal entity), thus differentiating the scope of data kept on a given subject. Similarly with law objects. Each context is defined by a unique code in the Register of Rights and Obligations.
* Data on subjects or objects of law "arise" uniquely
* The data maintained on the subject or object in the information systems supporting the execution of the agenda (Agenda Information System according to Act 111/2009 Coll. on Basic Registers) is defined in the relevant laws governing the execution of the agenda. Thus, the law determines what data is kept in the agenda information system about a given subject of law in the relevant role (context). Similarly for the objects of law. The agenda notifier is obliged to include this list in the Register of Rights and Obligations.
* Each entry is defined by a unique code in the Register of Rights and Obligations and there is a unique location from where it is provided to the linked data pool. The data provided in this way is marked in the agenda declaration as 'reference' in the sense of 'guaranteed' (either a reference from the basic registers or data from the agenda information system). The purpose of the marking as reference is that the public authority can use this data 'without verifying its correctness' within the meaning of the Basic Registers Act for data from the basic registers and individual laws regulating the execution of agendas. The data that already exists about the right holder in the linked data pool does not need to be proven by the right holder.
* Each reader of data from the linked data pool must ensure that the subject or object for which the data is drawn is identified. Thus, the agenda providing the specific data is not responsible for correctly identifying the data subject, but relies on the identification provided by the reader as part of the query.
* A reader must not provide back data retrieved from a linked data pool on the basis that it is providing it as guaranteed data, i.e. data from its agency information system (it may only ever provide it as informative data).
* Reference data and data of the agency information system (within the meaning of the Basic Registers Act) may only be provided on subjects of law that are or have been entered in the basic registers of the Register of Population and the Register of Persons (i.e. there is an AIFO/AIFO or ID number assigned to them according to the Basic Registers Act). Data of agency information systems on other subjects of law (without a link to an AIFO or ID number) may only be provided as informative data on the basis of identification of the subject according to the data.
* Data can be provided within the linked data pool only through the reference interface (§ 2(j) of Act No. 365/2000 Coll. on public administration information systems). The reference interface is mainly provided by
* Identity of the source and the reader - each information system is uniquely identifiable by means of an SSL certificate issued by the Certification Authority of the Basic Registers Administration.
* Privacy - all data exchange is carried out in a closed communication environment.
* Confidentiality - all management data is stored in the Register of Rights and Obligations, neither the source of the data nor the identity of the data reader can be compromised.
* Auditability - The Reference Interface stores operational data to ensure that communications are auditable.
* Unquestionability - Rules are set to ensure the unquestionability and provability of the data transmitted (in terms of its transmission and origin, not in terms of its factual correctness, the latter must be ensured legislatively when the data is created).
* The reference interface is drawn exclusively through the Central Service Point (CMS).
The above basic rules ensure that, throughout the linked data pool, it is always unquestionably clear who is the originator of the data, about which specific entity the data are transmitted, what data are transmitted (including their referential status) and who is the recipient of the data. Due to the logical imprecision of the descriptive names of individual data (e.g. the term 'name' can be seen as a plain name, first names, full name without titles, full name with titles, etc.), each data is listed in the Register of Rights and Obligations under a unique identifier so that confusion cannot occur based on a misinterpretation of the name.
The Global Architecture of the Linked Data Pool also includes the definition of operational rules for the individual parts of the Linked Data Pool to unify the requirements for these individual parts.
==== Agency Information System Administrator ====
Each Agency Information System Administrator, in collaboration with the subject matter administrators of the Agencies it supports, must take the following steps:
* Conduct a basic analysis of the required and stored agenda data and divide it into:
* Reference data from basic registers,
* Data originating from other agendas (although not currently drawn from these agendas),
* Data generated by the activities of the agenda it is performing.
* Make a technical connection to the ISZR and ISSS, if not already done so, in the role of reader. Ensure technical conditions such as transaction logging.
* Identify its entire data trunk. The result of the identification for a natural person is the acquisition of an AIFO, the result of the identification for a legal person (including a natural person doing business) is an ID number.
* For reference data and data from other agency information systems, update the data from the linked data pool and start receiving notifications of data changes.
* Prepare the publication of the context/contexts "subject data" in full for each context (legal status of the legal entity in the agenda) and publish this context on ISSS:
* The right holder has access to the full context,
* Other agendas request access to individual parts/data via RPP.
* Provide data change notification services so that readers can update their data trunks.
It cannot be expected that these steps will be completed for all public administration information systems in the short term, however it is in the interest of all AIS administrators to take these steps and then gradually retrieve data from other AIS. These steps **are absolutely necessary** in order to fulfil the strategy of the interconnected data pool and the synergy and activity of all substantive and technical administrators of agencies and AIS is absolutely necessary.
==== Right holder - natural person ====
The natural person benefits from the existence of the Linked Data Pool without any action on his/her part. If individual agency and agency information system administrators work on the linked data pool strategy according to the above rules, they will not require the right holder to provide evidence of facts that are already available through the PPDF, thus significantly reducing the burden on individuals and legal entities.
However, if an individual wants to take an active role, which is a welcome approach, then the following steps are recommended for full use and exploitation of the linked data pool environment by the public administration:
* **Establishment of a means of remote identification and authentication** - this will allow the individual to view the data held on them in the individual agency/agency information systems. The data obtained in this way is primarily used to ensure that the public administration is working with the correct data. Otherwise, the right holder can immediately reclaim the data and ensure that the public administration is working with the correct data.
* **Establishment of a data box of a natural person - allows** sending and receiving documents between the public administration and that person. This process fulfils all the requirements of personal submission or receipt of documents and is a necessary condition for the data box holder to be able to communicate with the public administration in a trusted and secure remote manner.
An individual equipped with a remote identification and authentication device will be able to fully benefit from all digital eGovernment services.
Figure 3: Illustrative diagram of the use of digital eGovernment services by natural persons
{{ :znalostni-baze:ga_ppdf3.png?600 |Figure 3: Illustrative diagram of the use of digital eGovernment services by natural persons}}
==== Subject of the law - legal entity and natural person in business ====
Many legal entities and self-employed persons already have a data box. For legal entities registered in the Commercial Register or established by law, as well as for some types of natural persons (e.g. lawyers), a data box is established directly by Act No. 300/2008 Coll. on electronic acts and authorised conversion of documents. For legal entities and natural persons engaged in business, whether they have a data box compulsorily or not, the same recommendation applies as for natural persons, i.e. the universal establishment of a data box to ensure trustworthy and free communication with the public administration.
By its nature, a legal person can never act 'alone', but only through a natural person who is authorised to do so. It is therefore in the interest of all legal persons to:
* **To establish a means of remote identification and authentication for all natural persons who can act on its behalf.**
* **Verifying that the basic mandates (i.e. the authority of a person to act on behalf of another person) for actions recorded in the Register of Persons are valid -** otherwise, raising a complaint with the editor of that data to seek redress.
* **Require each agenda manager** to provide an electronic mandate register where an authorised person according to the Register of Persons can authorise a specified individual to carry out relevant actions.
The basis is therefore again remote identification and authentication of the natural person and the maintenance of a link for that natural person to perform acts on behalf of the legal entity in the given agenda. In the Register of Persons, basic mandates are kept as reference data, i.e. mandates resulting from a position such as the statutory body of a legal person. Other mandates, typically mandates arising from a representation agreement (based on a power of attorney) or from a status not registered in the ROS (e.g. an employee in a certain job title) cannot be kept centrally and must be kept in the individual AIS according to the rules of the agendas they perform.
==== Official - AIS user ====
From the point of view of the AIS user, there must be no increased requirements. The retrieval of the necessary data from the linked data pool is handled by the AIS with which it is working, in the background, and the data retrieved from the PPDF is displayed to the AIS user with an indication that it is actual reference data or data from other AISs retrieved via the PPDF and therefore does not need to be further verified.
If the AIS user, in the course of his/her activities, finds that the submitted data is not in accordance with the reality, then he/she has to use the data complaint process. This process must be supported by the agenda manager, ideally directly in the AIS in which the user is working.
Figure 4: Illustrative diagram of the use of Linked Data data from a clerk's perspective
{{ :znalostni-baze:ga_ppdf4.png?600 |Figure 4: Illustrative diagram of the use of Linked Data data from a clerk's perspective}}
==== Technical Administrator of the Agenda Information System ====
The AIS Technical Administrator provides the technical link to the PPDF and the connection to all data exchange support services (i.e. not only reading but also receiving change notifications, updating data, etc.).
An important activity is keeping the AIS data pool up to date. For this process, it mandatorily registers in the ORG those AIFOs that are kept in the agenda for receiving notifications of data changes and similarly de-registers AIFOs that are no longer kept in the production environment (transferred to the archive) and thus there is no longer a need to update data on these persons. The updating process is carried out regularly in accordance with the working procedures issued by the Administration of the basic registers.
The updating of data for a longer period of time is carried out **only** in the event of a data breach (restoration from backup, etc.). Repeated reading of data change notifications and updates over a long period of time places a disproportionate burden on both the reference interface and the data source (basic registers and AIS).
In cooperation with the subject matter manager, the agenda manager addresses the identification of the data stem on natural persons (obtaining the AIFO) so that subsequent data maintenance can be carried out by communication according to the AIFO.
Re-identification of the same person according to the data without storing the AIFO in the agenda is an unacceptable waste of the reference interface and data resources.
====== Description of the Linked Data Pool ======
===== Architectural views of PPDF =====
==== Overall view of PPDF in terms of its components, users and technologies ====
The following figure, or rather architectural diagram, shows the future state of the Linked Data Pool in terms of its components, services, actors, HW and SW technologies and physical interconnection. It is therefore a comprehensive view through all layers of the so-called four-layer architecture of the Czech eGovernment in accordance with the National Architectural Framework.
On the left side are the PPDF clients with their systems and technologies they use to deliver services to the end user. On the right are PPDF sources or editors and publishers with their systems and technologies. In the middle are the PPDF systems and technologies.
Figure 5: View of the future state of PPDF in terms of its components, services, actors, HW and SW technologies and physical interconnection
{{ :znalostni-baze:ga_ppdf5.jpg?600 |Figure 5: View of the future state of PPDF in terms of its components, services, actors, HW and SW technologies and physical interconnection}}
==== View of the business logic and data extraction of VS agendas ====
The following architectural diagram illustrates the future state of the PPDF from the perspective of a rights holder. A rights holder can access its data in the PPDF using specific interfaces provided by the PPDF reader. The aim is for the right holder to access all his data in all public administration agencies of the Czech Republic using the most convenient access for him.
Figure 6: Viewing the future state of the PPDF from the perspective of the right holder
{{ :znalostni-baze:ga_ppdf6.jpg?600 |Figure 6: Viewing the future state of the PPDF from the perspective of the right holder}}
==== View of the business logic from the perspective of the rights holder ====
The following architectural diagram illustrates the current state of PPDF from the perspective of the rights holder and their ability to access the data of each agenda. The individual unbound agendas do not currently provide any data to the subject using PPDF services, yet they are shown here to show the breadth that PPDF is intended to encompass for the rights holder.
Figure 7: Viewing the current state of PPDF from the perspective of the rights holder
{{ :znalostni-baze:ga_ppdf7.jpg?600 |Figure 7: Viewing the current state of PPDF from the perspective of the rights holder}}
==== Relationship between PPDF and VDF ====
In addition to the PPDF, data is also shared through the Public Data Fund (PDF). Through the VDF, data is shared in the following scenarios:
- When sharing data via the PPDF, the OVM needs the content of a codebook or the definition of selected codebook entries managed by another OVM. It does not receive them via PPDF but via VDF as open data.
- The OVM does not perform an administrative activity but performs another complementary task (e.g. compiling an analytical report). It then uses public data in the form of open data available from the VDF. The difference with general open data and open data available from the VDF is that the data in the VDF is guaranteed to be available to the OVM and the publishing OVM guarantees its accuracy.
Other than through PPDF and VDF, no data is exchanged between OVMs.
From the perspective of PPDF, the first scenario is important. The second scenario is elaborated in more detail in the VDF Architecture document. The aim of the first scenario is to avoid duplication and uncontrolled and unconceptual extension of the codebooks in different ISVs. If an OMC needs a codebook managed by another OMC to interpret data obtained from the PPDF, then this OMC does not create a copy of the codebook in its information system in the form of a new codebook. In the data obtained from the PPDF, it obtains the IRI of the codebook entries that encode the data values. It obtains the full data of the codebook entries by dereferencing the IRIs in the VDF. There it also obtains the IRI of the codebook and by further dereferencing it can obtain the full codebook if necessary. However, if it stores the codebook, then it always does so only for optimization or availability reasons and always keeps this copy up-to-date with respect to the source via the VDF. The specific mechanisms are described in the VDF Architecture.
In the future, the set of data types that are not shared via PPDF but only exclusively via VDF may be extended from just dialers to other types.
===== Component Description =====
The Linked Data Facility (also referred to as PPDF) is a subject area consisting mainly of the Basic Registry Information System and the Shared Service Information System, whose services are published through the Central Service Point. The PPDF and its systems/services are the physical representation of the public administration reference interface. The basic function of the PPDF is to implement the principles of "Once-only" and "Data circulate, not people" into the common practice of public administration in the Czech Republic.
PPDF is the primary source of valid and legally binding data for the subjects of law and for all OVM and SPUU in the exercise of their competences. Thus, the PPDF will lead to the replacement of manual interactions between authorities by automated data exchange between different Agenda Information Systems.
The link between the Agency Information Systems and the basic registers is provided by the Basic Registers Information System, while the link between the Agency Information Systems and each other is provided by the Shared Services Information System.
All service provision within the PPDF is always linked to the basic registers by means of reference links to reference data on subjects of law (natural persons, legal persons and OVM) and reference data on objects of law (territorial elements and rights and obligations). For the reference links of data on natural persons, the Agency Identifier of Natural Persons (AIFO) is used, for the reference links of legal persons and natural persons in business, the Personal Identification Number (PIN) is used, and for the reference links of territorial elements, their respective identifiers assigned by RUIAN are used.
In addition to the development and support of the linked principles of data stem management and pseudonymisation, the main objective of the PPDF is the development of data sharing with additional agency sources of non-public data from key areas of public administration (transport, health, social services...) with a clearly defined guarantor and editor. There is a greater emphasis on interoperability between EU Member States, and the PPDF will be ready to provide services for cross-border data exchange, as described more in Chapter 4.
In realistic 2020, about 3,500 information systems out of a total of about 7,000 are connected to PPDF services. In addition to connecting all public administration information systems, the basic objective of the PPDF is to ensure that the connection for the relevant ISVS is not only reader-type (drawing data) but also publisher-type (providing their data). It is only when all relevant public administration information systems are drawing on and providing PPDF services that we can speak of a connected data pool.
The basic services of the PPDF for authorised PPDF readers are:
* Identification (assignment of an identifier) of the subject/object of the right held in the AIS and thus support pseudonymisation.
* Issue of data on the subject/rights holder according to the required context within the scope of the authorisations held in the RPP for the relevant AIS-supported agenda.
* V on changes to reference and agency data for data held in AIS.
* Support for claiming erroneous data.
==== Reference interface ====
The reference interface, in accordance with its de facto definition, means the interface for the implementation of links between public administration information systems, especially in the implementation of the interconnected data pool by sharing data between individual agency information systems in the form of shared services. The reference interface is therefore the communication interface for the provision and use of shared services by individual administrators of public administration information systems.
Access to the services of the reference interface is possible at the network level only through the Central Service Point (CMS), i.e. the Communication Infrastructure of Public Administration (CIPA), which is defined in Act 365/2000 Coll. The Central Service Point is a system whose primary purpose is to provide a controlled and registered connection of the information systems of the OVM and the SPUU to services (applications) provided by information systems of other entities with defined security and SLA parameters, i.e. access to eGovernment services. CMS can thus be called a private network for the performance of public administration on the territory of the state.
Connection to the CMS can be realized through:
- Non-public KIVS operator (Regional Networks, Metropolitan Networks, ITS of the Ministry of Interior and others).
- Public KIVS operator (KIVS operator competition through the central contracting authority of the Ministry of the Interior).
- IPsec VPN.
- SSL VPN.
Communication between individual OSSs is conducted exclusively via KIVS/CMS, i.e. individual OSSs are obliged to access public administration information systems only via KIVS/CMS.
The centrally managed and administered part of the reference interface ensures data sharing in the interconnected data pool with respect to Act 111/2009 Coll. on basic registers with central provision of all requirements imposed on the reference interface.
This centrally controlled and managed part of the Reference Interface consists of three components.
Table 1: Components of the centrally managed and administered part of the reference interface
^**Component ** ^**Abbreviation** ^**Description of functionality ** ^
|Basic registers information system |ISZR |Provides all services related to the use of basic registers data, also implements services for editors to the CR and for sharing CR editors' data.
|Information Sharing Service System |ISSS (formerly also eGSB)|Interface for sharing and exchanging data between ISVS and making links between them. |
|Information system for bulk data output in multiagenda queries (Form Agency Information System)|FAIS |It is used for processing queries and outputting data in the form of forms, including bulk forms, also from multiple PIs or other ISVS. Queries and outputs are transmitted via Data Boxes.|
The use of data via the reference interface is always made exclusively on the basis of the relevant authorisations recorded in the RPP, but this does not mean that the RPP controls the actual release of data. The final decision whether or not to provide data is always the responsibility of the source AIS (the one whose data is requested). It makes this decision on the basis of the reference entitlement data recorded in the RPP.
In the future development of the PPDF, it is envisaged that authorisations for data or specific services will be checked by the ISZR and ISSS using reference data from the RPP. The end state should therefore be that the requesting system calling the service receives the requested data or information that it does not have the necessary permissions for the request. The permissions, and therefore the access to data and services, would therefore not have to be done by the system or its administrator, but everything would be managed using the RPP reference data.
Through the reference interface:
* The entry and editing of data in the basic registers is carried out.
* The editing of the basic registers is carried out by the editors of the basic registers using the services of the external interface of the ISZR.
* Exploitation of data from the basic registers.
* With regard to the permissions to access data in the basic registers, according to the announcement of the individual agencies in the RPP, using the services of the external interface of the ISZR.
* Notification of data changes and updates of basic registers data are also implemented using the services of the external interface of the ISZR.
* Data exchange in the form of shared services between AIS is implemented.
Implemented by OVM between each other using services and data exchange. In case of data exchange on natural persons, performs translation of AIFOs through ORG services.
* Implement bulk data output and query and response composition services for multiple data.
* Implemented by the FAIS component and used by OVM or SPUU with appropriate authorization.
* FAIS makes calls to the ISZR and ISSS services on the basis of a request received via the data box and returns the compiled response to the requester again via the data box.
* Implement the services of notification of data changes and data updates in individual agendas using the central component.
**Basic rules for the use of the reference interface:**
* Comply with the Decree on Act 365/2000 Coll. on Public Administration Information Systems, especially on the technical and functional parameters of the connection to the reference interface.
* The reference interface shall be accessed by the OVM through its AIS and by the SPUU through its PIS or through the AIS of another OVM.
* Each AIS or DMS of a PSC accessing the reference interface shall prove its identity by means of a system certificate issued by a Certification Authority under the management of the HRA.
* When exchanging data on subjects or objects of law, it is verified whether these subjects (ROB, ROS) or objects (RÚIAN, RPP) are listed in the basic registers (verification of the reference link).
* The OVM or SPUU requesting data on a specific subject is responsible for its proper identification in its agenda, i.e. obtaining the AIFO if it is a natural person or the ID number if it is a legal person or an entrepreneurial natural person. If the subject is not properly identified, then the data held in the AIS may be indicative only.
* Records (logs) of the identification of the requesting system, the time of response, the structure and content of the data provided shall be kept by the providing system. The identification of the providing system, the time of receipt of the response, the structure and content of the data shall be kept by the receiving system. The reference interface shall record the identification of both systems, the time and the structure of the data transmitted.
* Procedural interfacing with the filing service (eSSL) when the reference interface is used to transmit documents according to the rules of the filing service. This only applies to situations where the content is actually a document and therefore not just a data transfer.
=== Information system for the management of the use and publication of data of the reference interface of the public administration of the Czech Republic ===
The Information System for the Management of the Extraction and Publication of the Data of the Public Administration Reference Interface of the Czech Republic (also referred to as the "Connection Management System") is a Public Administration Information System that allows any entity that is connected to the Public Administration Reference Interface (according to Act 365/2000 Coll. on Public Administration Information Systems) to manage data on information systems that provide or extract data through the Reference Interface.
The link management system will be created as an extension of the current RAZR system (registration authority of basic registers) or as a new system and must support the following functionalities:
* Login via JIP/KAAS
* Login via the NIA system
* Registration of all connected IS (agency information systems and private data use systems) according to the register of public administration information systems
* Records of all subject administrators of connected IS and their administrators (editors)
* Records of all contexts according to the agendas defined in the RPP
* Control of data permissions according to RPP
* History of the use and publication of data of the connected IS according to the logs of the reference interface
* Individualisation of information for logged-in and authorised user
* Enabling reporting of unauthorised use / provision of data, including monitoring of the progress of processing
* Enabling reporting of certificate misuse, including progress tracking
* Enable ordering of a new certificate, including progress tracking
* Enabling context management (creation, modification, deletion)
{{ :znalostni-baze:ga_ppdf8.png?600 |}}
==== Reference interface design ====
=== Basic registry information system ===
The information system of basic registers is legislatively enshrined in Act No. 111/2009 Coll., on basic registers. The ISZR is a public administration information system, through which data sharing between the basic registers with each other, basic registers and agency information systems with each other, management of data access permissions and other activities is ensured. The ISZR consists of two basic interfaces.
Table 2: Interfaces of the ISZR
^**Interface ** ^**Main users ** ^**Description of functionality ** ^
|Services of the internal interface|Only the ISZR in relation to the basic registers|Internal services that can only be used by the ISZR to retrieve and dereference data from the individual basic registers.
|External Interface Services |Agenda Information Systems |Services enabling the use of data from the basic registers and basic register editors.
In particular, the following are implemented through the ISZR services:
* Access to data held in the basic registers.
* Services of complaint, contestation, notification of data changes, updating of data from basic registers.
* Entry and changes to data in the basic registers.
* Translation of agency identifiers of natural persons.
* Enforcement of compliance with the authorisations recorded in the RPP.
To connect to the basic registers, users follow the table below:
^**User ** ^**Path ** ^**Provides ** ^
|Subject of the right |Cannot access directly, indirectly e.g. through the citizen's portal or universal contact points and extracts from it.|Citizen's portal, public administration contact points or FAIS (sending a request via data box) through published forms. Data extraction and data complaints are ensured. The data obtained can be used in the forms of another OVM forms administrator.|
|Authority of the public authority |With its Agenda Information System. |Provided by the Basic Registers Administration after fulfilling the conditions. |
| | |Agenda information system of another administrator. |Provided by the administrator of the AIS. | |
| |Through the CzechPOINT@office interface. |Provided by the Ministry of the Interior of the Czech Republic, the CzechPOINT@office administrator in cooperation with the local administrator. |
|Private data user| Through the end-user information system built by the OVM. |Provided by the OVM which administers the relevant AIS.
| |Private legal information system for data exploitation. |Provided by the DPA authorised to operate such a system. |
In order to connect the agency information systems to the basic registers, certain basic conditions must be fulfilled, which are laid down by the Administration of the basic registers in its operational documentation for the ISZR. In particular:
- The AIS administrator must have its IS registered in the ISVS register in the RPP
- It must have declared in the RPP the competence in the agenda(s) it will perform with this AIS for the relevant OVM
- The AIS administrator must indicate in the RPP which OVMs/SPMUs can access the RO or other AISs via its AIS.
- The AIS must be connected to the relevant access point (KIVS or Internet). The method and process of connecting the AIS to the KIVS is outside the scope of the RoW system
- The AIS must be certified to access the eGON interface. Certification is a process within the competence of the SZR. Within this process the scope of the AIS is defined - agenda, agenda roles and OVM This process is described in a separate document available on the SZR website.
- The AIS must be issued with an electronic client certificate. The issuance of the client certificate is the last step in the AIS certification process, which is carried out by SZR
- The AIS must be allowed access to specific eGON services within the RAZR (Registration Authority of the RoW) according to the security profile. Permissions to individual data are defined based on the OVM / agenda / agenda role combination, and are derived from the information in the RPP
- Must have implemented calls to the eGIS services in its AIS, or be able to properly call, consume and use the web services of the eGIS external interface according to the eGIS operational documentation
=== Basic registries ===
The basic registers are a reference data source of data on subjects and objects of law and on the performance of public administration. These are reference data on
* natural persons,
* legal persons and natural persons engaged in business,
* addresses, territorial elements and real estate,
* public authorities and private data users,
* agendas and scope of public administration,
* certain decisions amending reference data.
The basic registers thus form the backbone of an interconnected public administration data pool, including a mechanism for pseudonymisation and linking of identifications from individual agencies. In addition, they provide, in particular, individuals with an overview of the use of their data by individual readers (OVM, SPUU, etc.) and the provision to others.
**Reference data**
Reference data are data held in the basic register which are marked as reference. It is a general legal and procedural premise that reference data are considered correct in the exercise of public administration unless proven otherwise or unless they are called into question by the relevant editor. It is therefore the case that the public administration must act on the basis of these reference data and, conversely, that if the public administration acts on the basis of these reference data, there can be no maladministration due to inconsistency with the facts.
**Recording and editing of reference data**
The editing and recording of reference data is always the responsibility of the relevant editor. The distinction between the editor's responsibility and that of the individual data is not a matter of the subject. There is also a situation where there is more than one editor per subject. In this case, the editors are divided into primary and secondary editors. The primary editor is responsible for the actual existence of the entire record (including creation, update and deletion), whereas the secondary editor is responsible only for the individual entity data (including updates). A typical example of a situation of a primary and a secondary editor are legal entities, where the relevant primary editor is responsible for the creation and registration of the relevant basic data (the court of registration, the regional office, the trade department of the municipality, etc.) and the secondary editor (the Ministry of the Interior as the ISDS administrator) is responsible for the additional data, e.g. on the data box. Therefore, the secondary editor cannot establish or cancel the entity, but only adds additional data to it.
The basic duties of the editor are therefore:
* To write and edit data on the basis of the procedural execution of the agenda, which determines whether there is a document registered in the filing service for the execution.
* To deal with the complaints process, including challenging the accuracy of the data from the base register manager, the editor himself or any public authority.
* Ensure the accuracy and timeliness of the data.
**Virtual reference data**
Virtual reference data are those data that are created by deriving, merging or otherwise modifying existing reference data. Thus, these data do not meet some of the requirements of traditional reference data, such as the responsibility of a specific editor. Virtual reference data have a label, a definition and a described process for how they are created in each specific service that can provide them. A typical example would be the virtual reference data "full name", which is composed of the reference data "first name or first names" and "last name". Other such virtual data may be:
* Age,
* name without accents,
* address in uppercase only,
* number of days until expiration of the identification document,
* telephone number in international format,
* etc.
Virtual reference data may not be explicitly mentioned in the law as content of a specific basic registry, as they are created and terminated with the call of a given ISZR or ISSS service, but are maintained in the RPP as a special type of data with a link to specific data of the basic registry.
At present, no ISZR or ISSS service has the possibility to provide virtual reference data. This functionality is foreseen in the framework of the development of the PPDF.
**Indicator data type**
An indicator is a reference data held in the basic register which serves to indicate that potentially relevant data on an entity are held in other information systems. The purpose of indicator data is to prevent unnecessary queries to information systems where such information is not held. The introduction of an indicator into the basic register is conditional on its inclusion as reference data in Act No 111/2009 Coll., on basic registers. In order to initiate such a legislative modification, it is necessary to assess whether the introduction of the new indicator will fulfil the purpose of eliminating unnecessary queries to the agency information systems (the indicated data occurs for a significant minority of persons or objects).
For a reference data of the indicator type, all the corresponding processes must be in place as for other reference data. Thus, a data editor must be identified, including the publication of services for editing the data by this editor, and other processes of the reference data life cycle must be ensured ( complaints, notification of data changes, provision of data on request of the subject, etc.).
The administrator of the basic registry is responsible for the allowed set of indicators, including their names.
The editor of the indicator data type is the information system administrator, who maintains the indicated data and enters them into the basic register in the same way as the reference data, i.e. by automatic processes. An indicator may also be a virtual data of the basic register and multiple indicators may relate to one subject.
The indicator data type has the following basic attributes:
* name - the unique name of the indicator,
* AIS identifier + agenda identifier,
* optional identifier of the context within which detailed data can be retrieved via ISSS,
* optional refinement code,
* optional text refinement.
The indicator data type contains other standard attributes:
* validity start date and time,
* expiry date and time,
* date and time of initial entry,
* date and time of last change,
* status (S, N, X, F).
Currently no ISZR or ISSS service has the capability to provide an indicator. This functionality is foreseen in the development of the PPDF, where the following modifications are required to implement this data:
* Add to AuthorizationInfo a text item ListIndicator, a string type, and structures for writing and reading. The names of the flags to be returned/written are entered into the ListIndicator. It is the equivalent of a ListIndicator, and the ISZR checks that the querying AIS has permission to read or write to a particular indicator.
* Access to indicator type data is controlled in the standard way by the Rights and Obligations Register. A user (OVM, agenda, activity role) must be allowed to access an indicator with a given name.
**Data accuracy complaint process**
Anyone who has doubts about the correctness of a reference can initiate the process of claiming the correctness of the reference. The process itself is then always handled by the primary source of the data - i.e. its editor. The process starts with the receipt of a message containing a doubt about the correctness of the data (from another OVM, a right holder, a registry administrator, etc.). The editor is then obliged to mark the data in question as questionable. Subsequently, the editor of the data must perform a validation of its correctness, which may result in the closure of the complaint as unjustified (and thus preserving the value of the data) or justified (and thus changing it to the correct value). At the same time as closing the claim, it removes the doubt from the data. The claim process itself is governed by the Administrative Procedure Code.
**Use of reference data**
Each public authority is obliged to use reference data from the basic registers within the scope of its competence in the individual agencies. In doing so, it either uses the services and links to its agency information systems or uses one of the other tools.
The basic obligations of the OVM and the SPÚÚ using the data are therefore:
* To use reference data in the agendas.
* Use up-to-date reference data, which can be achieved in one of two ways or a combination of the two, but always in accordance with the operational documentation of the ISZR:
- Using the mechanism of notification of changes to reference data and subsequent updates, or
- by querying the base registers for each transaction.
* If a discrepancy between the reference data and the reality is detected, implement a data complaint against the data editor.
* Do not request the data held in the registers from the right holder.
**Registry of Population (ROB) **
The Population Register is a basic register according to Act No. 111/2009 Coll., on basic registers((Act No. 111/2009 Coll., on basic registers, as amended by other legislation in force on 1 January 2025
)), which records reference data on natural persons. The administrator of the Population Register is the Ministry of the Interior. The primary editors are the Ministry of the Interior and the Police of the Czech Republic through the Agenda Information System for Population Registration and the Agenda Information System for Foreigners. The subjects of the rights recorded in the Population Register are:
* citizens of the Czech Republic,
* foreigners residing in the territory of the Czech Republic under permanent residence or on the basis of a long-term visa or long-term residence permit,
* citizens of other Member States of the European Union, citizens of States bound by an international treaty negotiated with the European Community, citizens of States bound by the Treaty on the European Economic Area and their family members who reside on the territory of the Czech Republic as part of their permanent residence or who have been issued a document of temporary residence on the territory of the Czech Republic for more than 3 months,
* foreigners who have been granted international protection in the form of asylum or subsidiary protection in the Czech Republic,
* other natural persons for whom another legal regulation requires an agency identifier of a natural person and stipulates that these natural persons shall be entered in the population register.
The reference data on natural persons are:
* surname, maiden name,
* first name, where appropriate,
* gender,
* the address of the place of residence, or, where applicable, the address to which documents are to be served in accordance with another legal regulation; these addresses are recorded in the form of a reference link (address location code) to the address reference in the territorial identification register; in the case of an address to which documents are to be served pursuant to another legal regulation, the identification of a post box or a delivery box or an address which is outside the territory of the Czech Republic and which has not been assigned an address place code in the territorial identification register is also recorded; in the case of an address of a place of residence, this information is marked as the address of the office if it is marked in the same way in the information system of the population register or the information system of foreigners,
* the date, place and district of birth, in the case of a subject of law who was born abroad, the date, place and state where he was born; the information on the place and district of birth on the territory of the Czech Republic is kept in the form of a reference link (territorial element code) to the reference in the territorial identification register,
* the date, place and district of death, if the death of the subject of the right is outside the territory of the Czech Republic, the date of death, the place and the State in whose territory the death occurred; if a court decision is issued declaring the subject of the right to be dead, the date indicated in the decision as the date of death, or as the date on which he/she did not survive, and the date on which the decision became final shall be entered; the place and district of death in the territory of the Czech Republic shall be entered in the form of a reference link (territorial element code) to the reference entry in the territorial identification register,
* nationality, or multiple nationalities, if applicable,
* limitation of legal capacity,
* marital status or registered partnership,
* numbers and types of identification documents and their expiry date,
* the type of data box and the identifier of the data box, if this data box is accessible.
Non-reference data on natural persons are also recorded in the population register:
* a telephone number for the public mobile telephone network or an e-mail address for sending a selected range of information,
* serial number, issuer and validity of the qualified certificate for electronic signature,
* personal security code, which is authentication data for the purposes of the population register (it is kept in encrypted form and is not public),
* the agenda identifier of the natural person, which is the identifier for the population register agenda.
The population register also holds operational data
* a record of the use of data from the population register for the purposes of agency information systems,
* a record of the disclosure of data to the subject of the right or to another person, which includes the date and time of the disclosure, an identifier of the consent of the subject of the right to disclose the data to another natural or legal person and the identification of the person who disclosed the data,
* the date of the last change to each entry in the population register,
* a record of the granting or withdrawal of the right holder's consent to disclose the data to another natural or legal person.
The data editors are:
* in the case of citizens of the Czech Republic, the editor is the Ministry of the Interior, which records the data through the agency information system of the population register and the register of identity cards or the register of travel documents,
* in the case of foreigners, the editor is the Police of the Czech Republic or the Ministry of the Interior, which record data through the agency information system on foreigners,
* for data boxes, the Ministry of the Interior as the administrator of the Data Box Information System is the editor,
* for non-reference data, the Ministry of the Interior and the Administration of Basic Registers are the editors.
**Register of Persons (ROS) **
The Register of Persons is a basic register according to Act No. 111/2009 Coll., on basic registers, which records reference data. The administrator of the register of persons is the Czech Statistical Office. The primary editors are authorities and institutions that are already legally obliged to register persons. These include the Commercial Register, the Trade Register, registers or information systems of selected ministries and central government bodies, professional chambers, municipalities, regions, etc. The Ministry of the Interior with the Data Box System (ISDS) and the Ministry of Justice with the Insolvency Register are secondary editors.
The subjects of law maintained in the register of persons are:
* legal entity,
* organizational unit and organizational unit of a legal person,
* organisational unit of the state,
* an internal organizational unit of an organizational unit of the state, if this internal organizational unit is entrusted by law with its own competence,
* an entrepreneurial natural person,
* a foreign person and an organisational unit of a foreign person,
* trust fund,
if they are entered in the register pursuant to this Act or another legal regulation.
The reference data on legal persons are:
* business name or designation or name, if applicable, and surname, if the natural person engaged in business is not registered in the Commercial Register,
* the name or, where applicable, the first and last names of the natural person engaged in business or of the foreign person and the organisational unit of the foreign person; if the person is entered in the population register, this information shall be kept in the form of a reference link (agency identifier of the natural person) to the reference entry in the population register,
* the agenda identifier of the natural person for the agenda of the register of persons,
* person identification number,
* date of creation or date of registration under other legislation,
* date of termination or date of deletion from the register under other legislation,
* legal form,
* type of data box and identifier of the data box, if this data box is accessible,
* the statutory body, expressed by reference to the population register or the register of persons or by the name, surname and residence of a natural person or the name and registered office of a legal person, if these persons are not entered in the population register or the register of persons,
* a liquidator expressed by reference to the population register or the register of persons, or by reference to the name, surname and residence of a natural person, if applicable, or to the name and registered office of a legal person, if these persons are not entered in the population register or the register of persons,
* the guardian of a legal person, expressed by reference to the population register or the register of persons, or by reference to the name, surname and residence of a natural person, if applicable, or to the name and registered office of a legal person, if these persons are not entered in the population register or the register of persons,
* the insolvency administrator, expressed by reference to the population register or the register of persons, or the name, surname and residence of a natural person or the name and registered office of a legal person, where these persons are not entered in the population register or the register of persons,
* a receiver expressed by reference to the population register or by the name, surname and residence, where applicable, of the person concerned, if that person is not entered in the population register,
* legal status,
* the address of the person's registered office; if the building is a building recorded in the territorial identification register, this information shall be recorded in the form of a reference link (address location code) to the address reference in the territorial identification register,
* date of commencement of the activity at the establishment,
* the identification number of the establishment,
* the date of cessation of the activity at the establishment,
* the address of the place of establishment; where the building is a building recorded in the territorial identification register, this information shall be entered in the form of a reference link (address place code) to the address reference in the territorial identification register,
* the address of the place of residence in the Czech Republic in the form of a reference link (address place code) to the address reference in the register of territorial identification, or the residence abroad of the natural person referred to in § 25(e) and (f); in the case of persons entered in the register of residents, the address of the place of residence in the form of a reference link (agency identifier code of the natural person) to the reference of the natural person in the register of residents,
* interruption or suspension of activities under another legal provision; in the case of activities corresponding to one agenda, the interruption of all such activities.
Non-reference data on legal persons shall also be kept in the register of persons:
* a telephone number for the public mobile telephone network or an e-mail address for sending a selected range of information.
Operational data shall also be kept in the register of persons:
* agenda code,
* editor's personal identification number,
* date of initial entry in the register of persons,
* date of the last change to the data recorded in the register of persons,
* record of the use of the data from the register of persons.
The current list of data editors in ROS is published on the following website: https://www.czso.cz/csu/czso/editori-ros. For non-reference data, the editor will be the Ministry of the Interior.
^**Name of the person** ^**Type of person**^**ROS editor** ^
|Attorneys |FO |Czech Bar Association |
|Employment Agencies |FO |Ministry of Labour and Social Affairs |
|Accredited person under the Consumer Credit Act |FO |Czech National Bank |
|Auditors |FO |Chamber of Auditors of the Czech Republic |
|Road Safety Auditors |FO |Ministry of Transport |
|Authorized Architects |FO |Czech Chamber of Architects |
|Authorized Engineers and Technicians |FO |Czech Chamber of Authorized Engineers and Technicians Active in Construction |
|Churches and Religious Societies |PO |Ministry of Culture |
|Czech National Bank, Czech Television, Czech Radio, Regional Council of the Cohesion Region, General Health Insurance Company |PO |Ministry of the Interior |
|Tax advisors |FO |Chamber of Tax Advisors of the Czech Republic |
|Voluntary associations of municipalities |PO |Locally competent regional authority or the Municipality of the capital city Prague |
|License holders for business in energy sectors |FO |Energy Regulatory Office |
|European Groupings for Territorial Cooperation |PO |Ministry for Regional Development |
|Natural Persons - Operators of Postal Services |FO |Czech Telecommunications Office |
|Persons operating a trade (tradesmen) |FO |Locally Competent Trade Licensing Authority |
|Community associations |PO |Locally competent municipality with extended competence, Ministry of Agriculture|
|Insolvency administrators |FO |Ministry of Justice |
|Investment intermediaries |FO |Czech National Bank |
|Communal Contributory Organisations |PO |Counties, Municipalities |
|Mediators |FO |Ministry of Justice |
|International military organisations established on the basis of an international treaty |PO |Ministry of Defence |
|Foundations and endowments |PO |Registrar's court with local jurisdiction |
|FO |FO |Chamber of Commerce of the Czech Republic |
|Public benefit corporations |PO |locally competent court of registration |
|Commercial companies; cooperatives, business units, other persons registered in the Commercial Register |PO |Locally competent court of registration |
| Trade unions and employers' organizations, affiliated trade unions and employers' organizations, international trade unions, international employers' organizations, affiliated international trade unions, affiliated international employers' organizations |PO |Locally competent court of registration |
|Organizational units of the State |PO |Ministry of the Interior |
|Persons handling high-risk biological agents and toxins |FO |State Office for Nuclear Safety |
|Persons carrying out mining and mining-related activities |FO |Czech Mining Authority |
|Persons involved in the production and distribution of pharmaceuticals |FO |State Institute for Drug Control |
|Persons authorised for exchange and foreign exchange activities |FO |Czech National Bank |
|Persons using nuclear energy and ionizing radiation |FO |State Office for Nuclear Safety |
|Patent Attorneys |FO |Chamber of Patent Attorneys of the Czech Republic |
|Entrepreneurs in electronic communications |FO |Czech Telecommunications Office |
|Insurance intermediaries |FO |Czech National Bank |
|Political Parties and Political Movements |PO |Ministry of the Interior |
|Audiovisual Media Service Providers |FO |Radio and Television Broadcasting Council |
|Providers of small-scale payment services |FO |Czech National Bank |
|Healthcare service providers |FO |Locally competent regional authority or the Capital City Municipality Prague |
|Providers of social services |FO |Locally competent regional authority or the Municipality of the Capital City of Prague Prague |
|Operators of aerial work and airport operators |FO |Civil Aviation Authority |
|Operators of professional veterinary activities |FO |State Veterinary Administration |
|Radio and Television Broadcasting Operators |FO |Radio and Television Broadcasting Council |
|Operators of emission measurement stations |FO |Local municipality with extended competence |
|Operators of technical inspection stations |FO |Locally competent regional authority or the Capital City Council Prague |
|Zoo operators |FO |Ministry of the Environment |
|Restaurate |FO |Ministry of Culture |
|Federal Insurance Claims Adjusters |FO |Czech National Bank |
|Federal Consumer Credit Intermediary |FO |Czech National Bank |
|Court Executors |FO |Executors' Chamber of the Czech Republic |
|Court Experts and Interpreters |FO |County Courts, City Court Prague |
|MO |PO |Registrar's Court with local jurisdiction |
|Clubs (formerly civic associations), affiliated associations (formerly an organizational unit of a civic association) |PO |Locally competent registry court |
|State Funds |PO |Ministry of the Interior |
|State contributory organisations |PO |Ministries and other central administrative authorities |PO
|Trust Funds |PO |Locally competent court of registration |
|School legal entities |PO |Ministry of Education, Youth and Sports |
|Institute |PO |Local registration court |
|Bound representative according to the Consumer Credit Act |FO |Czech National Bank |
|Public and State Universities |PO |Ministry of the Interior |
|Public Research Institutions |PO |Ministry of Education, Youth and Sports |
|Public corporations - region, municipality, capital city of Prague |PO |Ministry of the Interior |
|Veterinarians authorised to carry out veterinary therapeutic and preventive activities |FO |Chamber of Veterinary Surgeons of the Czech Republic |
|Foreign legal entity, branch plant of a foreign legal entity, branch plant of a foreign natural person |PO |Locally competent registration court |
|Foreign association, foreign branch association |PO |Locally competent court of registration |
|PO |PO |Locally competent court of registration |
|Representation of a foreign bank |PO |Czech National Bank |
|Agricultural Entrepreneurs |FO |Ministry of Agriculture |
|Bonded consumer credit intermediary |FO |Czech National Bank |
|Special organization for representation of Czech interests in international NGOs, organizational unit of special organization for representation of Czech interests in international NGOs, international NGO, organizational unit of international NGO|PO |Locally competent court of registration |
**Register of Territorial Identification of Addresses and Real Estate (RÚIAN) **
The Register of Territorial Identification of Addresses and Real Estate is a basic register according to Act No. 111/2009 Coll., on basic registers, which records basic territorial elements and addresses. The administrator of the Register of Territorial Identification is the Czech Geodetic and Cadastral Office. The primary editors are cadastral offices, through the cadastre information system, building authorities through the territorial identification information system, municipalities and the Czech Statistical Office.
The Register of Territorial Identification contains data on the following basic territorial elements:
* the territory of the state,
* the territory of a cohesion region according to another legal regulation,
* the territory of a higher territorial self-government unit,
* the territory of a region,
* the territory of a district,
* administrative district of a municipality with extended competence,
* the administrative district of a municipality with a designated municipal authority,
* territory of a municipality,
* the territory of a military district,
* administrative district in the capital city of Prague,
* the territory of a municipal district in the capital city of Prague,
* the territory of an urban district in the capital city of Prague,
* the territory of an urban district and an urban part of a zoned statutory city,
* cadastral territory,
* the territory of a basic settlement unit,
* building object,
* address place,
* land in the form of a parcel.
The register of territorial identification shall also contain data on special purpose territorial elements by means of which the territory is expressed by another legal regulation, if another legal regulation provides that such data shall be entered in the register of territorial identification and if these special purpose territorial elements are entirely composed of at least some of the basic territorial elements.
The territorial identification register shall also contain data on the following territorial registration units
* part of a municipality,
* a street or other public space .
The reference data in the territorial identification register are:
* identification data,
* data on links to other territorial elements or territorial registration units,
* data on the type and use of the land and its technical and economic attributes,
* data on the type and use of the building object,
* data on the type and method of protection of the property,
* addresses,
* locational data of cadastral areas and superior elements,
* locational data of territorial elements and territorial registration units - only in those cadastral territories where the cadastral map is kept in digital form.
**Register of rights and obligations (RPP) **
The Register of Rights and Obligations is administered by the Ministry of the Interior and information for controlling access to the data of other basic registers; at the same time, this register provides a basic overview of the agendas carried out by public authorities; information on citizens and legal entities is kept in this register on decisions that have led to changes in the data in the basic registers. Furthermore, the RPP serves as a source of information for the RoW information system in managing user access to data in the individual registers and agency information systems. This means that whenever a given subject attempts to obtain a certain data or even to change (edit) it, the system assesses whether the subject will be allowed to work with the data provided by the public administration on the basis of the legal authorisation, and thus the RPP becomes an important component of the RoW within the concept of using the interconnected data pool and sharing data across not only the state administration for the management of public administration performance.
The RPP includes in particular:
* public administration agendas and their responsibilities,
* list of Public Authorities and private users of data from the basic registers,
* a map of the competences of public authorities within the agenda model,
* data on data held in the agendas and on their provision and use,
* data on the entitlements of public authorities and private users to access data from the basic registers and agency information systems,
* decisions on the basis of which reference data in the Population Register and the Register of Persons are changed,
* a list of public administration information systems and their link to the agendas and data held in them.
The RPP also includes the technical structure of data, which, in addition to the obligations set out in the Decree on the Basic Registers Act 111/2009 Coll., is described in Chapter 3.2.
* Directory: a link to a dataset representing a codebook published in the National Catalogue of Open Data according to the rules of the Public Data Fund. If the data is created in the agenda, it is a reference that says the data is the source of the codebook, if it is a downloaded data, it is a reference to a codebook published by another entity.
The administrator of the Register of Rights and Obligations is the Ministry of the Interior, the primary editors are the notifiers of public administration agendas.
The basic elements for the [[https://archi.gov.cz/nap:agendovy_model_verejne_spravy|agenda model of public administration]] are maintained in the RPP. There is also a map of the shareable data of individual agencies and technical data on the data held within individual agencies and permissions to access the data.
Another part of the RPP is the registration of public administration information systems, their link to the OVM, agendas, data on their administrators, etc.
**Key roles in relation to basic registers**
** **The following roles are defined in relation to the use of basic registers.
Table 3: Roles defined in relation to the use of the RoR
^**Roles ** ^**Description and meaning ** ^**Examples ** ^
|Basic register manager |The public authority that manages the relevant basic register. |For ROB and RPP it is the Ministry of Interior, for ROS it is the CSU, for RÚIAN it is the ČÚZK. |
|Reference data editor |The public authority which, by law, edits and records reference data and is therefore responsible for their accuracy and is obliged to deal with complaints and data updates. |For ROB it is the Ministry of the Interior (e.g. through registration offices and registry offices), for ROS and RÚIAN it is the individual agency points according to the relevant laws. |
|Reference data user (reader) |A public authority or private user who is obliged or authorised to use reference data and accesses the RO for this purpose. |Individual OVMs operating in the agencies, AIS administrators, law subjects themselves.
|Subject of the law |Specific natural or legal person about whom data are kept in the registers. |Each natural or legal person for its data. A legal person is always linked to a natural person. |
|Reporter of an agenda |Reporter of an agenda held in the RPP (cf. [[https://archi.gov.cz/nap:agendovy_model_verejne_spravy|Agenda model of public administration]]). |For the registry agenda the Ministry of the Interior, for the health services agenda the Ministry of Health, for the pensions agenda the Ministry of Social Affairs |
|Authority acting in the agenda |Authority of public authority or SPUU which by law exercises competence in the agenda (see. [[https://archi.gov.cz/nap:agendovy_model_verejne_spravy|Agenda model of public administration]]). |In the registry office agenda, individual municipal authorities, in the social benefits agenda, for example the Labour Office and the Regional Office of Public Administration, in the building law agenda, the Ministry of Regional Development and the individual building authorities.
=== Editorial AIS with composite services ====
Systems whose data is published by composite services. Composite services are defined as AIS services that provide data held in editorial AIS systems with a link to reference data held in the AIS:
* Population registry - AISEO (administered by the Ministry of the Interior of the Czech Republic),
* Foreigners Information System - AISC (Administered by the Police of the Czech Republic),
* Travel documents register - AISECD (Administered by the Ministry of the Interior of the Czech Republic),
* Registration of identity cards - AISEOP (Administered by the Ministry of the Interior of the Czech Republic),
* Information System of the Cadastre of Real Estate - ISKN (Administered by the Czech Office of Surveying and Cadastre),
* Information System of Territorial Identification - ISÚI (Administered by the Czech Geodetic and Cadastral Office),
* AIS Competence - AISP (Administrator is the Ministry of the Interior of the Czech Republic),
* eIdentity - not currently an editor of the basic registers, but provides data in relation to the reference record in ROB (administrator is the Administration of Basic Registers).
Each ROB has its own editors who edit the data. The editors enter data into the individual ROBs and together with the subject administrator of each of the editors, this keeps the data in the ROB correct and up-to-date. A data reclaim mechanism is used to ensure that the data is up-to-date and correct. Editors edit the data in the RoW using their editing information systems on the basis of the procedural performance of the agenda, which determines whether there is an obligation for the performance to have documents recorded in the [[https://archi.gov.cz/nap:system_spravy_dokumentu|eSSL or separate document filing systems]] in accordance with the legislation. The reader may draw non-referential data in the form of composite services. Since only the current data which are correct and guaranteed by the State are contained in the CR (except for the non-referential data contained in the basic registers), it is possible to retrieve other non-referential data (historical data on the subject of the law and other data not contained in the CR) from the editors' editing systems as part of the composite services.
=== Shared service information system ====
The Shared Service Information System (referred to in the IT environment as the eGovernment On-Line Service Bus, eGSB) is a unified interface for sharing data between agency information systems. It is part of the reference interface allowing individual OVM AIS to draw on and publish data held on individual legal entities. Where an agency is required by law to maintain its own data records, it is obliged to publish its data to other agencies through the ISSS as a secure, standardised and documented interface for authorised readers. It is managed and operated by the Basic Registers Administration and enables:
* Publish data sharing services for data relating to specific subjects and data objects.
* Use data sharing based on published services.
* Translation of agency identifiers of individuals for whom data is exchanged between agencies (AIFO translation).
* Exchange data files with data on subjects based on pseudonymised identifiers in relation to translated AIFO identifiers.
* Provision of complaint services, notification of data changes and updating of data provided by AIS services.
* Providing independent auditing of data exchanges (stores information identifying the query and response and the technical cryptographic fingerprint of the message - hash).
The aim is to ensure that public administration clients are not forced to provide evidence of facts that the public administration already knows about or that have even arisen from a public administration decision. Most of the facts needed for public administration decision-making are already recorded somewhere, in the form of data in public administration information systems. There are also facts which, although they are the basis for public administration decisions, are not yet recorded as data in the AIS (examples are study certificates, sheltered workshop agreements, etc.). The mapping of the data in the individual agencies, which is now taking place as part of the new reporting obligations of the notifiers to the RPP, has gradually established a basic map of the data recorded, required and provided in the individual agencies and where and how they are recorded and in which AIS. This, as already described above, creates a basic data map of the public administration and it is therefore possible to analyse it and identify those data and facts that are used in multiple agencies.
The functionality of the principle is verified on the reference data held in the basic registers, where the client does not have to prove these data and their changes, but the whole public administration obtains these data through services and then makes decisions based on them. The principle of data sharing through the ISSS is only an extension of this functional unit to include other data. Two main roles are defined for the use of ISSS.
Table 4: Roles defined in relation to the use of ISSS
^**Role ** ^**Description ** ^**What it does ** ^
|The publisher (provider) |The ISVS administrator from which the data is provided. |Services publishing data through the ISSS, based on the agenda providing data from the AIS. |
|Reader (user) |OVM retrieving data from another agenda on the basis of its permission in RPP. |Connection to ISSS and calling publisher services (also multiple ISVS of a given agenda), AIFO translation from the provider's agenda is used, the reader calls according to the AIFO of its agenda in case of a natural person. No translation is used for a legal person.|
In the context of data sharing via ISSS, the following aspects apply:
* The data is reported in the register of rights and obligations as data that the agenda processes on the basis of legal authorisation.
* The data must be held in the AIS.
* It is clear for the data how it was created, who is responsible for its entry, changes, management and how it can be changed or cancelled.
* The data provider is always the AIS administrator in which the data is held and recorded.
* The data is always linked to the subject or object of the right in the RoW.
* It will be possible for the right holder to extract the data as an extract from the public administration information system.
As the aim is to link data efficiently and effectively, primarily to reduce the need for the client to prove facts, the data will be able to be retrieved by the public authority:
- on the basis of the consent of the right holder (on behalf of the right holder), or
- on the basis of a legal authorisation to keep the data in the agenda with the indication of the drawdown in the RPP (ex officio).
**Context used in ISSS**
Each agenda is defined by the relevant legislation. Within the agenda, the data necessary and specific for its execution are kept on subjects and objects. These data can also only be recorded on the basis of the relevant legal provisions. Subjects and objects are dealt with within an agenda in a certain context (given by the legislation), i.e. subjects and objects are understood in a certain 'context' within the performance of that agenda.
These contexts differ in the execution of different agendas, which is reflected, inter alia, by the fact that different objects are dealt with in relation to subjects in different agendas and different data are recorded and, where appropriate, exchanged on subjects and objects. We can therefore say that the context:
* determines the legal status of the entity (subject or object) within the agendas and
* the specific data (attributes) of the entity defined in the agenda are associated with it.
Methodologies for creating contexts address the detailed process
* [[https://archi.gov.cz/dokumenty:dk003_-_metodika_tvorby_kontextu_3.docx|Context Creation Methodology]].
* [[https://archi.gov.cz/dokumenty:metodika_egsb_prefinal.docx|Methodology for implementing a new context for an entity or data object passed through ISSS]].
The context creation methodology introduces two levels of context - technical and conceptual. The technical level of context consists of an XSD schema that defines the syntax of the XML messages in which the shared data is expressed. In order to use ISSS services for a linked data pool, it is necessary to know in particular:
>
Agenda from which the reader wants to use the data.
>
The agency that the reader is performing and in which the data is being read.
>
Context for querying data from the publishing AIS.