Glossary

Data factory API

A data factory programming interface available to other platform components that provides a set of functions for interacting with registry data.

A standard of graphical notation for modeling business processes.

The team responsible for consulting registry development teams and gathering feature requests and bug reports.

A resource that extends the OpenShift API by defining the configuration of a specific OpenShift instance. Not necessarily available out of the box when installing OpenShift.

A set of platform components that simplifies managing the central components of the platform, enables managing registries, and aggregates links to all web APIs of the central components.

A standard notation for modeling business rules using decision tables.

A distributed naming system that converts network resource names into IP addresses.

A way of implementing continuous deployment for cloud-native applications. The main idea of GitOps is that any changes to the configuration of the OpenShift cluster, cluster components, and Platform components are made by modifying the configuration of these components in their respective Git branches.

External traffic management subsystem component and gateway API.

An approach to creating, configuring, and modifying systems and applications that requires virtually no programming code. In the context of the Platform, these are the components that enable this approach.

A system for automatic deployment, scaling, and management of applications in containers.

A method of access control where privileges are assigned to users not directly, but via roles. Managing individual user’s privileges boils down to assigning roles.

A core concept of the Keycloak service. A realm manages a set of users, credentials, roles, and groups.

A form that allows users to send information when executing business processes.

A compact sequence of characters that uniquely identifies a resource on the Internet.

Verification of the authenticity of the identifier presented by the user.

Granting and verification of rights to perform any operations in the system.

Regulations administrator portal

A service that involves changing some status or other data in the registry. The Platform implements this as a business process that makes changes to the registry data.

A read-only database used by analytical tools such as Redash. Receives registry data through logical replication of the operational database.

Preconfigured registry statistics built using the Redash analytical reporting service. May include graphs, tables, scorecards, and notes on workflow performance.

A set of operations aimed at achieving a certain result through data processing. BPMN models of business processes are part of the registry regulations.

A logical representation of the state of the master version after applying the changes generated as part of the corresponding merge request.

A document generated as part of providing the information services through business processes, which can be downloaded by the user who ordered the information service. Excerpts are presented by separate templates at the registry regulations level.

Public information in a format that enables its automated processing by electronic means, as well as free and unlimited access and usage.

Registries that belong to the same owner and are related.

Information stored in the registry’s database.

Analytical reports

State Register of Individuals – Taxpayers. Refers to the code assigned to the taxpayers. See also RNOKPP (Registration number of the taxpayer’s account card)

In scope of this document, a digital signature can refer to individual’s or legal entity’s QES, AdES, or EDS, as well as legal entity’s electronic seal. The use of QES or AdES depends on the current legislation requirements.

Resource

An integration endpoint that allows two applications to exchange data with each other. APIs work by sending data requests from a web application or web server and receiving a response.

Data in electronic form, which is obtained as a result of cryptographic transformation and added to other data or documents to ensure the latter’s integrity and origin.

A unified state register of legal entities, individual entrepreneurs, and public organizations.

EDRPOU code is a unique ID code of a legal entity in the USREOU (Unified state register of enterprises and organizations of Ukraine).

A logical representation of changes relative to the current master version of the regulations. Merge requests must pass integrity and quality tests before actually being applied to the master version.

A software archive with installation scripts and Docker images that enables you to automatically deploy a specific version of the Platform to a target environment (cloud or data center) and upgrade the Platform to a specific version (for example, 1.9.0).

Control Plane

Analytical reports

A business process implemented on the level of an individual registry that fetches registry data in a specified form. It usually involves confirming a certain status in the registry. The result of the service is either an excerpt or confirmation of rights.

A client web application for administering the registries. Its web interface enables configuring the registry without advanced programming skills.

A common name for the web interface used by service recipients (citizens) and service providers (officers) to interact with the system.

A web interface used by service recipients (citizens) to interact with the registry in the form of a client web application.

A web interface used by service providers (officers) to interact with the registry in the form of a client web application.

The e-signature used to authenticate users and sign the data they provide.

An abstraction within the Control Plane that enables you to manage the central components of the platform.

Platform components installed separately for each registry.

A configuration of registry components that is available in the Control Plane and registry repository in line with the GitOps approach.

Any data that requires authorization to access it.

The current version of the regulations deployed to the registry instance.

A description of the content, structure, and integrity constraints used to create and maintain a registry database. It is defined using the Liquibase format at the registry regulations level.

Any entity owned by a subject.

Citizen initial authentication

The process of creating an account for a registry services recipient (citizen) using data obtained from the QES key and Unified state register. This includes creating all the database records necessary for user’s interaction with the registry (such as user profile, settings, and roles).

Officer initial authentication

The process of creating an account for a registry services provider (officer) using data obtained from the QES key and Unified state register. This includes creating all the database records necessary for user’s interaction with the registry (such as user profile, settings, and roles).

A database that stores registry data, settings, business processes data, and other operational data used by the registry’s applications and services.

A relational database that stores deployed models of business processes, the current execution state of process instances, the data generated by them, authorization settings, and general configurations.

A system role assigned to users who interact with the registry to receive administrative and informational services. This role can be assigned to an individual, PE’s representative, or a legal entity.

The process of creating a large number of user accounts for service providers (officers) in the registry by importing a CSV file.

Any information that relates to an identified or identifiable living individual. Data is classified as personal at the level of creating a registry data model, where appropriate processing and access mechanisms are applied.

An information system that enables authorized government officers to create and maintain registries according to the SaaS model "registry as a service." The platform can be deployed either in the cloud or on-premises data center, either for a single registry or a group of registries.

An OpenShift cluster with installed components necessary for creating and maintaining registries.

Data factory

Keys used for integration with id.gov.ua.

Central components

A system role assigned to government representatives who interact with the registry as part of performing their official duties.

One or more business processes in the registry aimed at processing a user’s request.

Any data that does not require authorization to access it.

A set of data models, business processes, and settings that define the registry’s functions.

A specialized information resource designed to store and process legally important information about people, their rights and obligations, as well as property and resources.

A process that applies configuration to the registry.

Keys used to sign the transformed data of business forms and excerpts.

A limit on the number of requests from a single user.

An element of the State Register of Individuals – Taxpayers (DRFO), which is assigned to natural persons - payers of taxes and other mandatory charges and does not change during their life.

The procedure for creating or updating registry services, business processes, and the structure of the registry database in accordance with the registry regulations.

Roles that are created during registry regulations deployment and configured in the registry regulations.

System roles and regulations roles that are assigned to a user.

The system of electronic interaction of state electronic information resources. Based on the X-Road® solution.

Roles created by the Platform during registry deployment or Platform installation.

Any natural or legal entity that owns an object.

A formal description of a UI form’s structure, fields, and validation rules. Presented as a file at the registry regulations level.

A database that stores significant business processes execution history events (such as a history of business processes initiated by a user, completed business processes, and completed user tasks).

A distributed database of key-value pairs that temporarily stores data provided by users through the UI forms of business process tasks.

The platform subsystem responsible for storing data and providing access to it.

UI form

System components that all registries share. The cluster contains a single copy of each central component.

Files that can be uploaded, downloaded, and viewed by users through the UI forms of business processes tasks. Documents are stored in the registry’s object storage. The content of digital documents is not the object of operations at the level of business processes.