Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
en:nap:portaly_verejne_spravy_a_soukromopravnich_uzivatelu_udaju [2021/06/01 13:06] – created Tomáš Šedivecen: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 [[:ikcr|Information Concept of the Czech Republic]] - Informational, Interactive and Transactional. This implies, among other things, that the portal is a public administration information system. +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:ikcr|Information Concept of the Czech Republic]] - Informational, Interactive and Transactional. This implies, among other things, that the portal is a public administration information system. 
  
   * 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, authentication and authorization.     * Transactional services require user identification, authentication and authorization.
  
-Therefore, portals cannot be stand-alone and unconnected applications, but instead must be a resource that is integrated with the information systems in the Authority. In particular, with the electronic filing service, with agency information systems, but also with economic systems where they are used to collect data on payments or fees by individual client. In the case of providing all 3 types of services, these are so-called integrated online public administration services according to [[:ikcr|Information Concept of the Czech Republic]]. +Therefore, portals cannot be stand-alone and unconnected applications, but instead must be a resource that is integrated with the information systems in the Authority. In particular, with the electronic filing service, with agency information systems, but also with economic systems where they are used to collect data on payments or fees by individual client. In the case of providing all 3 types of services, these are so-called integrated online public administration services according to [[en:ikcr|Information Concept of the Czech Republic]]. 
  
-The portal is intended to serve the client to obtain information, as a means of publishing open data, statistics and public outputs, for electronic submissions and communication between the client and the authority. The portal must also serve the holders of a guaranteed electronic identification as a means of obtaining their data, for various [[nap:notifications|notifications]], but also for interactive submission of applications or requests for statements. It must also provide the client with a so-called profile or personified part, where the portal holds basic information about the client that is known to the authority or that the client discloses of his/her own free will.+The portal is intended to serve the client to obtain information, as a means of publishing open data, statistics and public outputs, for electronic submissions and communication between the client and the authority. The portal must also serve the holders of a guaranteed electronic identification as a means of obtaining their data, for various [[en:nap:notifikace|notifications]], but also for interactive submission of applications or requests for statements. It must also provide the client with a so-called profile or personified part, where the portal holds basic information about the client that is known to the authority or that the client discloses of his/her own free will.
  
 The overall behavior and interaction of the Portal towards citizens and officials is called [[https://wiki.digitalnicesko.cz/wiki/Jednotn%C3%A9_UX|User Experience (UX)]]. The UX includes not only the graphical design, but also the language (form, expertise, ...), the way of interaction, communication channels, similar ways of identifying users, etc. The overall behavior and interaction of the Portal towards citizens and officials is called [[https://wiki.digitalnicesko.cz/wiki/Jednotn%C3%A9_UX|User Experience (UX)]]. The UX includes not only the graphical design, but also the language (form, expertise, ...), the way of interaction, communication channels, similar ways of identifying users, etc.
-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:portal_obcana|Citizen Portal]] described above.+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:portal_obcana|Citizen Portal]] described above.
  
 ==== 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/citizen can make submissions to the public administration and use its services through self-service under his/her guaranteed electronic identity. For more information see the separate [[nap:portal_obcana|functional unit]]+The Citizen Portal refers to the transactional part of the Public Administration Portal, where the client/citizen can make submissions to the public administration and use its services through self-service under his/her guaranteed electronic identity. For more information see the separate [[en:nap:portal_obcana|functional unit]]
  
 ==== 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:portal_obcana|Citizen 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 [[en:nap:portal_obcana|Citizen Portal]]. 
  
  
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, city, city district - collectively they can be referred to as local governments. A territory portal may contain, in addition to self-governing services such as local tax administration, also delegated services, but there should not be a situation where a delegated service is created only for the territory portal. It is the responsibility of the administrator to create a central environment for the handling of the delegated services that the territory portal will use but not create. In the case of territory portals, two trends are foreseen:   A territory portal is meant to be a portal providing services that fall under a certain territory of the country, typically a region, municipality, city, city district - collectively they can be referred to as local governments. A territory portal may contain, in addition to self-governing services such as local tax administration, also delegated services, but there should not be a situation where a delegated service is created only for the territory portal. It is the responsibility of the administrator to create a central environment for the handling of the delegated services that the territory portal will use but not create. In the case of territory portals, two trends are foreseen:  
  
-  * 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:portal_obcana|Citizen Portal]]. +  * local portals can be replaced in the long term by locally adapted services of the central [[en:nap:portal_obcana|Citizen Portal]]. 
  
  
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:2._agendovy_informacni_portal2.png |}}+{{ :nap-dokument:2._agendovy_informacni_portal2.png |}}
  
-=== Agenda Information Portal === +=== Portal as === 
-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:iszr|information system of basic registers]], [[nap:egsb|eGSB/ISSS]] or AIS, which are managed by the same administrator as the agenda information portal. It is still the case that all documents generated in the course of processing a service must go into the [[nap:document_management system|document management|file services]].+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:iszr|information system of basic registers]], [[en:nap:egsb|eGSB/ISSS]] or AIS, which are managed by the same administrator as the agenda information portal. It is still the case that all documents generated in the course of processing a service must go into the [[en:nap:system_spravy_dokumentu|document management file services]].
  
-{{ :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://designsystem.gov.cz/|graphic manual of the Ministry of the Interior]]. Next, a form engine is needed that not only allows pre-populating all data already known to the state from the [[nap:linked_datovy_fond|linked data pool]] and [[nap:nia|electronic identity provided by the national identity authority]]. Last but not least, it is necessary to ensure that all submissions made in the portal are forwarded to the agency information systems in which the submissions are processed according to the agenda and also to the office's filing service. +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://designsystem.gov.cz/|graphic manual of the Ministry of the Interior]]. Next, a form engine is needed that not only allows pre-populating all data already known to the state from the [[:en:nap:propojeny_datovy_fond|linked data pool]] and [[en:nap:nia|electronic identity provided by the national identity authority]]. Last but not least, it is necessary to ensure that all submissions made in the portal are forwarded to the agency information systems in which the submissions are processed according to the agenda and also to the office's filing service. 
  
-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#mandates_roles_and_corrections|mandates in electronic communication]] are dealt with. If the portal implements and supports the [[nap:agendovy_model_verejne_spravy|agenda of public administration]] according to [[nap:rpp|register of rights and obligations]], it must behave like any other agenda information system and work according to the definition of an agenda.+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#mandates_roles_and_corrections|mandates in electronic communication]] are dealt with. If the portal implements and supports the [[en:nap:agendovy_model_verejne_spravy|agenda of public administration]] according to [[en:nap:rpp|register of rights and obligations]], it must behave like any other agenda information system and work according to the definition of an agenda.
  
 Thus, when submitting submissions from the portal, functionality needs to be provided to make the submission "human-readable" and "machine-readable" information within a single document, typically PDF/A3 and above. This "container" format is then used both to meet the "readability" requirement and to provide the requirement for automated data processing (embedded XML with data for automated processing). Furthermore, the document must be provided with the requisites according to Act No. 297/2016 Coll., typically an electronic signature or an electronic seal and a time stamp. The human-readable format, typically PDF, goes to the filing service for registration and the machine-readable format goes from the agenda system. Neither technology nor infrastructure matters in the operation of the portal. So neither On Premise solution nor cloud solution is preferred, it all depends on the needs of the office and the possibilities that technology can offer. It is always necessary to think about load distribution, for example: Thus, when submitting submissions from the portal, functionality needs to be provided to make the submission "human-readable" and "machine-readable" information within a single document, typically PDF/A3 and above. This "container" format is then used both to meet the "readability" requirement and to provide the requirement for automated data processing (embedded XML with data for automated processing). Furthermore, the document must be provided with the requisites according to Act No. 297/2016 Coll., typically an electronic signature or an electronic seal and a time stamp. The human-readable format, typically PDF, goes to the filing service for registration and the machine-readable format goes from the agenda system. Neither technology nor infrastructure matters in the operation of the portal. So neither On Premise solution nor cloud solution is preferred, it all depends on the needs of the office and the possibilities that technology can offer. It is always necessary to think about load distribution, for example:
Line 64: Line 64:
   - applications for various subsidies (e.g. "boiler") are submitted by a certain date, some load can be expected from the time of launch until the end when the demands on the infrastructure will be high (with an increasing trend) and after the deadline when they will be minimal.   - applications for various subsidies (e.g. "boiler") are submitted by a certain date, some load can be expected from the time of launch until the end when the demands on the infrastructure will be high (with an increasing trend) and after the deadline when they will be minimal.
  
-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://rpp-ais.egon.gov.cz/AISP/verejne|register of public administration information systems]]   * It must be registered as a public administration information system in the [[https://rpp-ais.egon.gov.cz/AISP/verejne|register of public administration information systems]]
   * It has a public administration authority that performs one or more agendas according to the [[https://rpp-ais.egon.gov.cz/gen/agendy-detail/|list of public administration agendas]]    * It has a public administration authority that performs one or more agendas according to the [[https://rpp-ais.egon.gov.cz/gen/agendy-detail/|list of public administration agendas]] 
-  * Must be federated to [[nap:portal_obcana|Citizen Portal]] +  * Must be federated to [[en:nap:portal_obcana|Citizen Portal]] 
-  * Must be federated to [[nap:nia|National Identity Authority]] and [[nap:nia#rules_for_national_identity_authority|announced as a qualified service provider]] +  * Must be federated to [[en:nap:nia|National Identity Authority]] and [[en:nap:nia#rules_for_national_identity_authority|announced as a qualified service provider]] 
-  * Must, according to its agency law, be able to draw and provide data through the [[:nap:egsb|eGON Service Bus/Shared Service Information System]]+  * Must, according to its agency law, be able to draw and provide data through the [[en:nap:egsb|eGON Service Bus/Shared Service Information System]]
   * 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:rpp|RPP]]+  * Must use the same [[en:nap:katalog_sluzeb|service and life situations catalogue]] structure as in [[en:nap:rpp|RPP]]
   * Must comply with [[https://designsystem.gov.cz/|graphic manual of the Ministry of the Interior]]   * Must comply with [[https://designsystem.gov.cz/|graphic manual of the Ministry of the Interior]]
  
 Procedure for client work activities, client identification and service selection Procedure for client work activities, client identification and service selection
-  * Clients connect through [[nap:nia|NIA]] and are identified by BSI until the client selects a service that is provided by [[https://rpp-ais.egon.gov.cz/gen/agendy-detail/|agenda]] +  * Clients connect through [[en:nap:nia|NIA]] and are identified by BSI until the client selects a service that is provided by [[https://rpp-ais.egon.gov.cz/gen/agendy-detail/|agenda]] 
-  * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service's agenda) using [[nap:iszr|eGON of the ISZR services]]+  * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service's agenda) using [[en:nap:iszr|eGON of the ISZR services]]
   * 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://rpp-ais.egon.gov.cz/AISP/verejne|system on public administration information systems]]   * It must be registered as a public administration information system in the [[https://rpp-ais.egon.gov.cz/AISP/verejne|system on public administration information systems]]
-  * It must be federated to the [[nap:portal_obcana|Citizen Portal]] +  * It must be federated to the [[en:nap:portal_obcana|Citizen Portal]] 
-  * Must be federated to [[nap:nia|National Identity Authority]] and [[nap:nia#rules_for_national_identity_authority|announced as a qualified service provider]] +  * Must be federated to [[en:nap:nia|National Identity Authority]] and [[en:nap:nia#rules_for_national_identity_authority|announced as a qualified service provider]] 
-  * Must, according to its agency law, be able to draw and provide data through the [[:nap:egsb|eGON Service Bus/Shared Service Information System]]+  * Must, according to its agency law, be able to draw and provide data through the [[en:nap:egsb|eGON Service Bus/Shared Service Information System]]
   * 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:rpp|RPP]]+  * Must use the same [[en:nap:katalog_sluzeb|service and life situations catalogue]] structure as in [[en:nap:rpp|RPP]]
   * Must comply with [[https://designsystem.gov.cz/|graphic manual of the Ministry of the Interior]]   * Must comply with [[https://designsystem.gov.cz/|graphic manual of the Ministry of the Interior]]
  
 Procedure for client work activities, client identification and service selection Procedure for client work activities, client identification and service selection
   * Clients connect through [[nap:nia|NIA]] and are identified by BSI until the client selects a service that is provided by [[https://rpp-ais.egon.gov.cz/gen/agendy-detail/|agenda]]   * Clients connect through [[nap:nia|NIA]] and are identified by BSI until the client selects a service that is provided by [[https://rpp-ais.egon.gov.cz/gen/agendy-detail/|agenda]]
-  * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service's agenda) using [[nap:iszr|eGON of the ISZR services]]+  * After the client selects the service, the OVS provides identity translation (BSI-AIFO of the selected service's agenda) using [[en:nap:iszr|eGON of the ISZR services]]
   * 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