Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
en:nap:portaly_verejne_spravy_a_soukromopravnich_uzivatelu_udaju [2021/07/01 10:28] – Tomáš Šedivec | en:nap:portaly_verejne_spravy_a_soukromopravnich_uzivatelu_udaju [2021/11/12 10:42] (current) – Tomáš Šedivec | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Description of Public Administration and Private Data User Portals ===== | ===== Description of Public Administration and Private Data User Portals ===== | ||
- | The portal is perceived as a whole functional unit containing Front-end (logic displaying behaviour towards the client) and Back-end (logic implementing system behaviour and internal and external integration) implementing all types of services according to [[: | + | The portal is perceived as a whole functional unit containing Front-end (logic displaying behaviour towards the client) and Back-end (logic implementing system behaviour and internal and external integration) implementing all types of services according to [[en: |
* In the area of information services, it provides users with an overview and publicly available information in the area covered by the portal, including descriptions of life situations. | * In the area of information services, it provides users with an overview and publicly available information in the area covered by the portal, including descriptions of life situations. | ||
Line 12: | Line 12: | ||
* Transactional services require user identification, | * Transactional services require user identification, | ||
- | Therefore, portals cannot be stand-alone and unconnected applications, | + | Therefore, portals cannot be stand-alone and unconnected applications, |
- | The portal is intended to serve the client to obtain information, | + | The portal is intended to serve the client to obtain information, |
The overall behavior and interaction of the Portal towards citizens and officials is called [[https:// | The overall behavior and interaction of the Portal towards citizens and officials is called [[https:// | ||
- | For ease of use by the citizen, it is necessary that each portal uses a uniform, centrally defined UX. In simple terms, this is similar to the behaviour and interaction of the [[nap: | + | For ease of use by the citizen, it is necessary that each portal uses a uniform, centrally defined UX. In simple terms, this is similar to the behaviour and interaction of the [[en:nap: |
==== PO and PVS - Citizen Portal and Public Administration Portal ==== | ==== PO and PVS - Citizen Portal and Public Administration Portal ==== | ||
- | The Citizen Portal refers to the transactional part of the Public Administration Portal, where the client/ | + | The Citizen Portal refers to the transactional part of the Public Administration Portal, where the client/ |
==== Agenda portal ==== | ==== Agenda portal ==== | ||
- | An agenda portal is a portal providing services of a logically centralised system for other public authorities and public administration clients. Typically, it is therefore an agenda portal under delegated competence provided by the agenda manager (notifier). The client can be either a citizen or another public authority. It is valid that the services for the client-citizen must be published according to one of the federation forms to [[nap: | + | An agenda portal is a portal providing services of a logically centralised system for other public authorities and public administration clients. Typically, it is therefore an agenda portal under delegated competence provided by the agenda manager (notifier). The client can be either a citizen or another public authority. It is valid that the services for the client-citizen must be published according to one of the federation forms to [[en:nap: |
Line 32: | Line 32: | ||
A territory portal is meant to be a portal providing services that fall under a certain territory of the country, typically a region, municipality, | A territory portal is meant to be a portal providing services that fall under a certain territory of the country, typically a region, municipality, | ||
- | * First, local government portals will include a reverse navigation direction to the [[nap:portal_citizen|Citizen Portal]], where the client will be able to handle everything else from the government that they may not have found in the local portal and | + | * First, local government portals will include a reverse navigation direction to the [[en:nap:portal_obcana|Citizen Portal]], where the client will be able to handle everything else from the government that they may not have found in the local portal and |
- | * local portals can be replaced in the long term by locally adapted services of the central [[nap: | + | * local portals can be replaced in the long term by locally adapted services of the central [[en:nap: |
Line 43: | Line 43: | ||
=== Ordinary portal === | === Ordinary portal === | ||
- | By ordinary portal in this sense we mean all kinds of portals according to their focus, as mentioned above, but this diagram shows the work with data. A plain portal acts as a single interface used to handle a service, but the actual handling of the service takes place in an agency information system. The portal procures all the data and other information it provides to the client through the agency information system, and all the documents that are created during the service handling must go into the [[nap:document_management system|writing service]]. | + | By ordinary portal in this sense we mean all kinds of portals according to their focus, as mentioned above, but this diagram shows the work with data. A plain portal acts as a single interface used to handle a service, but the actual handling of the service takes place in an agency information system. The portal procures all the data and other information it provides to the client through the agency information system, and all the documents that are created during the service handling must go into the [[en:nap:system_spravy_dokumentu|writing service]]. |
- | {{ :nap-document: | + | {{ :nap-dokument: |
- | === Agenda Information | + | === Portal |
- | An agenda information portal (likened to an agenda information system) in this sense means all kinds of portals according to their focus, as mentioned above, but this diagram shows data handling. An agenda information portal behaves as a stand-alone agenda information system, i.e. it contains all the logic and supports the processes for receiving and processing the service in addition to the interface itself. The portal procures all the data and other information it provides to the client through a direct connection to [[nap: | + | An agenda information portal (likened to an agenda information system) in this sense means all kinds of portals according to their focus, as mentioned above, but this diagram shows data handling. An agenda information portal behaves as a stand-alone agenda information system, i.e. it contains all the logic and supports the processes for receiving and processing the service in addition to the interface itself. The portal procures all the data and other information it provides to the client through a direct connection to [[en:nap: |
- | {{ :nap-document:2._agenda_information_portal.png |}} | + | {{ :nap-dokument:2._agendovy_informacni_portal.png |}} |
Line 56: | Line 56: | ||
===== Public Administration and Private Data User Portals Rules ===== | ===== Public Administration and Private Data User Portals Rules ===== | ||
- | The authority must implement and change the current processes, which are primarily oriented towards personal contact with the client, when operating the portal. The current portals must already have the functionality of linking with a guaranteed identity according to Act 250/2017 Coll. and must be able to adapt to a situation where the client of the public administration will only communicate electronically. This starts with the user-friendly environment itself, which must comply with the [[https:// | + | The authority must implement and change the current processes, which are primarily oriented towards personal contact with the client, when operating the portal. The current portals must already have the functionality of linking with a guaranteed identity according to Act 250/2017 Coll. and must be able to adapt to a situation where the client of the public administration will only communicate electronically. This starts with the user-friendly environment itself, which must comply with the [[https:// |
- | The portal supports a self-service client that includes both delegated and self-governing competences and contains a description of the life situations in which [[nap:electronic_identification_for_clients_of_public_government# | + | The portal supports a self-service client that includes both delegated and self-governing competences and contains a description of the life situations in which [[en:nap:elektronicka_identifikace_pro_klienty_verejne_spravy# |
Thus, when submitting submissions from the portal, functionality needs to be provided to make the submission " | Thus, when submitting submissions from the portal, functionality needs to be provided to make the submission " | ||
Line 64: | Line 64: | ||
- applications for various subsidies (e.g. " | - applications for various subsidies (e.g. " | ||
- | However, any solution must support access to central eGovernment services and other public administration services through a secure [[nap:reference_interface|Public Administration Reference Interface]] infrastructure. | + | However, any solution must support access to central eGovernment services and other public administration services through a secure [[en:nap:referencni_rozhrani|Public Administration Reference Interface]] infrastructure. |
==== PO and PVS - Citizen Portal and Public Administration Portal ==== | ==== PO and PVS - Citizen Portal and Public Administration Portal ==== | ||
Line 78: | Line 78: | ||
* It must be registered as a public administration information system in the [[https:// | * It must be registered as a public administration information system in the [[https:// | ||
* It has a public administration authority that performs one or more agendas according to the [[https:// | * It has a public administration authority that performs one or more agendas according to the [[https:// | ||
- | * Must be federated to [[nap: | + | * Must be federated to [[en:nap: |
- | * Must be federated to [[nap: | + | * Must be federated to [[en:nap: |
- | * Must, according to its agency law, be able to draw and provide data through the [[: | + | * Must, according to its agency law, be able to draw and provide data through the [[en: |
* Must, according to its agenda law, be able to draw data from the basic registers information system | * Must, according to its agenda law, be able to draw data from the basic registers information system | ||
- | * Must use the same [[nap:service_catalogue|service and life situations catalogue]] structure as in [[nap: | + | * Must use the same [[en:nap:katalog_sluzeb|service and life situations catalogue]] structure as in [[en:nap: |
* Must comply with [[https:// | * Must comply with [[https:// | ||
Procedure for client work activities, client identification and service selection | Procedure for client work activities, client identification and service selection | ||
- | * Clients connect through [[nap: | + | * Clients connect through [[en:nap: |
- | * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service' | + | * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service' |
* OVS will query the authorized credentials for the needs of the service | * OVS will query the authorized credentials for the needs of the service | ||
- | * OVS will give the client a choice of which role he/she wants to fill according to the agenda in which the service is provided [[nap:electronic_identification_for_clients_of_public_government|(so-called mandate)]] | + | * OVS will give the client a choice of which role he/she wants to fill according to the agenda in which the service is provided [[en:nap:elektronicka_identifikace_pro_klienty_verejne_spravy|(so-called mandate)]] |
* After the service is completed, the OVS does not remember the AIFO or other data used for the service, unless required by the agenda itself | * After the service is completed, the OVS does not remember the AIFO or other data used for the service, unless required by the agenda itself | ||
* OVS remembers the BSI for the client profile on the portal | * OVS remembers the BSI for the client profile on the portal | ||
Line 99: | Line 99: | ||
* It must be one for each authority - everything that the authority is competent for is available on it. | * It must be one for each authority - everything that the authority is competent for is available on it. | ||
* It must be registered as a public administration information system in the [[https:// | * It must be registered as a public administration information system in the [[https:// | ||
- | * It must be federated to the [[nap: | + | * It must be federated to the [[en:nap: |
- | * Must be federated to [[nap: | + | * Must be federated to [[en:nap: |
- | * Must, according to its agency law, be able to draw and provide data through the [[: | + | * Must, according to its agency law, be able to draw and provide data through the [[en: |
* Must, according to its agenda law, be able to draw data from the basic registers information system | * Must, according to its agenda law, be able to draw data from the basic registers information system | ||
- | * Must use the same [[nap:service_catalogue|service and life situations catalogue]] structure as in [[nap: | + | * Must use the same [[en:nap:katalog_sluzeb|service and life situations catalogue]] structure as in [[en:nap: |
* Must comply with [[https:// | * Must comply with [[https:// | ||
Procedure for client work activities, client identification and service selection | Procedure for client work activities, client identification and service selection | ||
* Clients connect through [[nap: | * Clients connect through [[nap: | ||
- | * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service' | + | * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service' |
* OVS will query the authorized credentials for the needs of the service | * OVS will query the authorized credentials for the needs of the service | ||
* OVS distinguishes between autonomous and delegated competence | * OVS distinguishes between autonomous and delegated competence | ||
* An autonomous competence is a set of multiple agendas, the entire autonomous competence cannot be held as a single agenda | * An autonomous competence is a set of multiple agendas, the entire autonomous competence cannot be held as a single agenda | ||
- | * OVS will give the client a choice of which role he/she wants to fill according to the agenda in which the service is provided [[nap:electronic_identification_for_clients_of_public_government|(called mandate)]] | + | * OVS will give the client a choice of which role he/she wants to fill according to the agenda in which the service is provided [[en:nap:elektronicka_identifikace_pro_klienty_verejne_spravy|(called mandate)]] |
* After the service is completed, the OVS does not remember the AIFO or other data used for the service, unless required by the agenda itself | * After the service is completed, the OVS does not remember the AIFO or other data used for the service, unless required by the agenda itself | ||
* OVS remembers the BSI for the client profile on the portal | * OVS remembers the BSI for the client profile on the portal |