| Next revisionBoth sides next revision |
| en:nap_dokument:pravidla_tvorby_a_udrzby_vlastni_ctyrvrstve_architektury_jednotlivych_uradu [2021/06/01 14:42] – created Tomáš Šedivec | en:nap_dokument:pravidla_tvorby_a_udrzby_vlastni_ctyrvrstve_architektury_jednotlivych_uradu [2021/07/01 10:30] – Tomáš Šedivec |
|---|
| First and foremost, user interfaces of ISVs and operational systems must be ergonomically optimal to best support appropriate user roles and their performance of external and internal government functions. | First and foremost, user interfaces of ISVs and operational systems must be ergonomically optimal to best support appropriate user roles and their performance of external and internal government functions. |
| |
| * The authority must have all its forms primarily in the authenticated zone of the [[nap:portaly_verejne_spravy_a_soukromopravnich_uzivatel_udaju|portal]] and allow pre-filling of data from the [[nap:linked_datovy_fond|PPDF]] using [[nap:elektronicka_identification_pro_klienty_verejne_spravy|guaranteed client identity]] | * The authority must have all its forms primarily in the authenticated zone of the [[nap:portaly_verejne_spravy_a_soukromopravnich_uzivatel_udaju|portal]] and allow pre-filling of data from the [[:en:nap:propojeny_datovy_fond|PPDF]] using [[nap:elektronicka_identification_pro_klienty_verejne_spravy|guaranteed client identity]] |
| * Agency and local portals will be expanded from informational to transactional | * Agency and local portals will be expanded from informational to transactional |
| * Transactional portal content (forms or portal application user interfaces) must be integrated (federated) with PVS - [[nap:portal_obcana|Citizen Portal]] | * Transactional portal content (forms or portal application user interfaces) must be integrated (federated) with PVS - [[nap:portal_obcana|Citizen Portal]] |
| The principle of [[nap:notification|notification]] is fundamentally of the **pull** type and without passing data during [[nap:notification|notification]]. Thus, the agenda using the data requests a list of subjects or objects for which the data has changed in the past period (typically one day). It then uses this list to actively query the data source to retrieve data according to its permissions. This ensures that during [[nap:notifications|notifications]] no data can be passed that the agenda does not have permission to. At the same time, when querying a natural or legal person, an entry is created in the basic registers and the right holder concerned is informed that the agenda has updated the data about him in its data stem. | The principle of [[nap:notification|notification]] is fundamentally of the **pull** type and without passing data during [[nap:notification|notification]]. Thus, the agenda using the data requests a list of subjects or objects for which the data has changed in the past period (typically one day). It then uses this list to actively query the data source to retrieve data according to its permissions. This ensures that during [[nap:notifications|notifications]] no data can be passed that the agenda does not have permission to. At the same time, when querying a natural or legal person, an entry is created in the basic registers and the right holder concerned is informed that the agenda has updated the data about him in its data stem. |
| |
| In case the OVS uses more than one own (local) agency information system and uses reference and agency master data, a local master data management solution must be implemented which, after the initial identification, keeps the agency master data up-to-date by receiving [[nap:notifications|notifications]] from the PPDF and does not burden the [[nap:linked_datovy_fond|linked data pool]] with continuous on-line queries. Personal data obtained in this way is stored outside other agency information systems and is only used by individual systems when necessary. This ensures the separation and security of personal data with unquestionable auditing of access to personal data. | In case the OVS uses more than one own (local) agency information system and uses reference and agency master data, a local master data management solution must be implemented which, after the initial identification, keeps the agency master data up-to-date by receiving [[nap:notifications|notifications]] from the PPDF and does not burden the [[:en:nap:propojeny_datovy_fond|linked data pool]] with continuous on-line queries. Personal data obtained in this way is stored outside other agency information systems and is only used by individual systems when necessary. This ensures the separation and security of personal data with unquestionable auditing of access to personal data. |
| |
| |