From 7953dc4fe9187e6766346d5303df9bdf7fdb381c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 17 Jul 2024 21:26:14 +0000 Subject: [PATCH] chore: autopublish 2024-07-17T21:26:12Z --- .../am_ET/.cache_timestamp | 2 +- .../ar/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../cs/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-238__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../es_419/.cache_timestamp | 2 +- ...FERENCE__DHIS-CORE-VERSION-232__web-api-md | 2 +- ...FERENCE__DHIS-CORE-VERSION-235__web-api-md | 2 +- ...ENCE__DHIS-CORE-VERSION-MASTER__web-api-md | 4 +- ...DHIS-CORE-VERSION-235__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-236__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 20 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 20 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 32 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 34 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 40 +- .../es_419/IMPLEMENT__chis-implementation-md | 2 +- .../IMPLEMENT__dhis2-implementation-guide-md | 4 +- ...ERSION-237__system-administration-guide-md | 4 +- ...ERSION-238__system-administration-guide-md | 4 +- ...ERSION-239__system-administration-guide-md | 2 +- ...ERSION-240__system-administration-guide-md | 6 +- ...ION-MASTER__system-administration-guide-md | 8 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 10 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 10 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 4 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 12 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 10 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 2 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 10 +- .../es_419/USE__dhis2-android-app-md | 2 +- .../fr/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-238__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../id_ID/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-238__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../ko/.cache_timestamp | 2 +- .../ko_KR/.cache_timestamp | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../pt/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-238__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../ru/.cache_timestamp | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../si/.cache_timestamp | 2 +- .../ur_PK/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-238__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../zh/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../zh_CN/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 2 +- .../zh_TW/.cache_timestamp | 2 +- projects/docs-full-site/ar/.cache_timestamp | 2 +- projects/docs-full-site/cs/.cache_timestamp | 2 +- ...E-API__DHIS-CORE-VERSION-238__analytics-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__apps-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__audit-md | 2 +- ...I__DHIS-CORE-VERSION-238__data-approval-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__data-md | 2 +- ...-API__DHIS-CORE-VERSION-238__data-store-md | 2 +- ..._DHIS-CORE-VERSION-238__data-validation-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__email-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__i18n-md | 2 +- ...PI__DHIS-CORE-VERSION-238__introduction-md | 2 +- ...API__DHIS-CORE-VERSION-238__maintenance-md | 2 +- ...E-API__DHIS-CORE-VERSION-238__messaging-md | 2 +- ...I__DHIS-CORE-VERSION-238__metadata-gist-md | 2 +- ...HE-API__DHIS-CORE-VERSION-238__metadata-md | 2 +- ...API__DHIS-CORE-VERSION-238__new-tracker-md | 2 +- ...DHIS-CORE-VERSION-238__org-unit-profile-md | 2 +- ...-API__DHIS-CORE-VERSION-238__scheduling-md | 2 +- ...VERSION-238__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-238__sharing-md | 2 +- ...ING-THE-API__DHIS-CORE-VERSION-238__sms-md | 2 +- ..._DHIS-CORE-VERSION-238__synchronization-md | 2 +- ...THE-API__DHIS-CORE-VERSION-238__tracker-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__users-md | 2 +- ...__DHIS-CORE-VERSION-238__visualizations-md | 2 +- ..._DHIS-CORE-VERSION-240__data-validation-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__email-md | 2 +- ...PI__DHIS-CORE-VERSION-240__introduction-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__sharing-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 10 +- ...G-THE-API__DHIS-CORE-VERSION-240__users-md | 2 +- ...__DHIS-CORE-VERSION-240__visualizations-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-241__apps-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-241__audit-md | 2 +- ...I__DHIS-CORE-VERSION-241__data-approval-md | 2 +- ...-API__DHIS-CORE-VERSION-241__data-entry-md | 2 +- ...IS-CORE-VERSION-241__tracker-deprecated-md | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...S-APP__APP-VERSION-140__USAGE__map-view-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...-APP__APP-VERSION-250__about-this-guide-md | 2 +- ...0__accessing-and-transilating-scorecard-md | 2 +- ...CORECARD-APP__APP-VERSION-250__browsing-md | 2 +- ...PP__APP-VERSION-250__creating-scorecard-md | 2 +- ...-250__introduction-to-the-scorecard-app-md | 2 +- ..._APP-VERSION-250__saving-configurations-md | 2 +- ...VERSION-250__scorecard-app-architecture-md | 2 +- ...ON-250__support-and-maintenance-options-md | 2 +- ...APP__APP-VERSION-250__viewing-scorecard-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...APP-DEMO__architecture-and-installation-md | 2 +- ...ALONE-ACTION-TRACKER-APP-DEMO__browsing-md | 2 +- ...E-ACTION-TRACKER-APP-DEMO__introduction-md | 2 +- ...ON-TRACKER-CONFIGURATION__configuration-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-238__ANALYSING-DATA__dashboards-md | 2 +- ...ON-238__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-238__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-238__ANALYSING-DATA__reports-md | 2 +- ...ION-238__APPROVING-DATA__approving-data-md | 2 +- ...SION-238__APPROVING-DATA__data-approval-md | 2 +- ...ERSION-238__COLLECTING-DATA__data-entry-md | 2 +- ...SION-238__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-238__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-238__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...SION-238__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-238__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...238__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...8__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...VERSION-239__ANALYSING-DATA__dashboards-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...ION-239__APPROVING-DATA__approving-data-md | 2 +- ...SION-239__APPROVING-DATA__data-approval-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 2 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...SION-MASTER__ANALYSING-DATA__dashboards-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...VERSION-MASTER__ANALYSING-DATA__reports-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-md | 2 +- ...N-MASTER__APPROVING-DATA__data-approval-md | 2 +- ...ASTER__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ION-MASTER__COLLECTING-DATA__data-entry-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...-MASTER__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...-MASTER__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- .../docs-full-site/es_419/.cache_timestamp | 2 +- ...THE-API__DHIS-CORE-VERSION-232__web-api-md | 2 +- ...THE-API__DHIS-CORE-VERSION-235__web-api-md | 2 +- ...HE-API__DHIS-CORE-VERSION-236__metadata-md | 3909 +++++++++++++++++ ...I__DHIS-CORE-VERSION-237__metadata-gist-md | 4 +- ...HE-API__DHIS-CORE-VERSION-237__metadata-md | 6 +- ...API__DHIS-CORE-VERSION-237__new-tracker-md | 2 +- ...THE-API__DHIS-CORE-VERSION-237__sharing-md | 4 +- ...__DHIS-CORE-VERSION-237__visualizations-md | 4 +- ...E-API__DHIS-CORE-VERSION-238__analytics-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__apps-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__audit-md | 2 +- ...I__DHIS-CORE-VERSION-238__data-approval-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__data-md | 2 +- ...-API__DHIS-CORE-VERSION-238__data-store-md | 2 +- ..._DHIS-CORE-VERSION-238__data-validation-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__email-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__i18n-md | 2 +- ...PI__DHIS-CORE-VERSION-238__introduction-md | 2 +- ...API__DHIS-CORE-VERSION-238__maintenance-md | 2 +- ...E-API__DHIS-CORE-VERSION-238__messaging-md | 2 +- ...I__DHIS-CORE-VERSION-238__metadata-gist-md | 6 +- ...HE-API__DHIS-CORE-VERSION-238__metadata-md | 8 +- ...API__DHIS-CORE-VERSION-238__new-tracker-md | 4 +- ...DHIS-CORE-VERSION-238__org-unit-profile-md | 2 +- ...-API__DHIS-CORE-VERSION-238__scheduling-md | 2 +- ...VERSION-238__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-238__sharing-md | 6 +- ...ING-THE-API__DHIS-CORE-VERSION-238__sms-md | 2 +- ..._DHIS-CORE-VERSION-238__synchronization-md | 2 +- ...THE-API__DHIS-CORE-VERSION-238__tracker-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__users-md | 2 +- ...__DHIS-CORE-VERSION-238__visualizations-md | 6 +- ...I__DHIS-CORE-VERSION-239__data-exchange-md | 12 +- ...I__DHIS-CORE-VERSION-239__metadata-gist-md | 4 +- ...HE-API__DHIS-CORE-VERSION-239__metadata-md | 6 +- ...API__DHIS-CORE-VERSION-239__new-tracker-md | 2 +- ...THE-API__DHIS-CORE-VERSION-239__sharing-md | 4 +- ...__DHIS-CORE-VERSION-239__visualizations-md | 4 +- ...I__DHIS-CORE-VERSION-240__data-exchange-md | 12 +- ..._DHIS-CORE-VERSION-240__data-validation-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__email-md | 2 +- ...PI__DHIS-CORE-VERSION-240__introduction-md | 2 +- ...API__DHIS-CORE-VERSION-240__maintenance-md | 2 +- ...I__DHIS-CORE-VERSION-240__metadata-gist-md | 4 +- ...HE-API__DHIS-CORE-VERSION-240__metadata-md | 18 +- ...DHIS-CORE-VERSION-240__org-unit-profile-md | 2 +- ...-API__DHIS-CORE-VERSION-240__scheduling-md | 2 +- ...VERSION-240__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__sharing-md | 8 +- ...ING-THE-API__DHIS-CORE-VERSION-240__sms-md | 2 +- ...IS-CORE-VERSION-240__tracker-deprecated-md | 6 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 14 +- ...G-THE-API__DHIS-CORE-VERSION-240__users-md | 2 +- ...__DHIS-CORE-VERSION-240__visualizations-md | 6 +- ...E-API__DHIS-CORE-VERSION-241__analytics-md | 4 +- ...NG-THE-API__DHIS-CORE-VERSION-241__apps-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-241__audit-md | 2 +- ...I__DHIS-CORE-VERSION-241__data-approval-md | 2 +- ...-API__DHIS-CORE-VERSION-241__data-entry-md | 2 +- ...I__DHIS-CORE-VERSION-241__data-exchange-md | 12 +- ...-API__DHIS-CORE-VERSION-241__data-store-md | 8 +- ..._DHIS-CORE-VERSION-241__data-validation-md | 2 +- ...I__DHIS-CORE-VERSION-241__metadata-gist-md | 4 +- ...HE-API__DHIS-CORE-VERSION-241__metadata-md | 28 +- ...THE-API__DHIS-CORE-VERSION-241__sharing-md | 6 +- ...IS-CORE-VERSION-241__tracker-deprecated-md | 6 +- ...THE-API__DHIS-CORE-VERSION-241__tracker-md | 4 +- ...G-THE-API__DHIS-CORE-VERSION-241__users-md | 2 +- ...__DHIS-CORE-VERSION-241__visualizations-md | 4 +- ...PI__DHIS-CORE-VERSION-MASTER__analytics-md | 6 +- ...THE-API__DHIS-CORE-VERSION-MASTER__apps-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-approval-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-entry-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 14 +- ...THE-API__DHIS-CORE-VERSION-MASTER__data-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-store-md | 10 +- ...IS-CORE-VERSION-MASTER__data-validation-md | 4 +- ...HE-API__DHIS-CORE-VERSION-MASTER__email-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__event-hooks-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__i18n-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__introduction-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__maintenance-md | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__messaging-md | 2 +- ...DHIS-CORE-VERSION-MASTER__metadata-gist-md | 6 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 252 +- ...__DHIS-CORE-VERSION-MASTER__new-tracker-md | 2154 +++++++++ ...S-CORE-VERSION-MASTER__org-unit-profile-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__route-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__scheduling-md | 2 +- ...SION-MASTER__settings-and-configuration-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__sharing-md | 8 +- ...-THE-API__DHIS-CORE-VERSION-MASTER__sms-md | 2 +- ...IS-CORE-VERSION-MASTER__synchronization-md | 2 +- ...CORE-VERSION-MASTER__tracker-deprecated-md | 4 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 32 +- ...HE-API__DHIS-CORE-VERSION-MASTER__users-md | 2 +- ...HIS-CORE-VERSION-MASTER__visualizations-md | 6 +- ...ENTATION__sustainability-and-governance-md | 574 +++ ...ttings-web-app-android-settings-web-app-md | 182 + ...E-ANDROID-APP__android-settings-web-app-md | 182 + ...GN__AGGREGATE-SYSTEM-DESIGN__indicators-md | 97 + ...RACKER-SYSTEM-DESIGN__tracker-analytics-md | 2 +- ...NT__DATABASE-DESIGN__organisation-units-md | 163 + ...EALTH__EVENT-BASED-SURVEILLANCE__design-md | 22 +- ..._EVENT-BASED-SURVEILLANCE__installation-md | 86 +- ...ATION-SYSTEM__DESIGN__adolescant-health-md | 334 ++ ...NFORMATION-SYSTEM__DESIGN__child-health-md | 306 ++ ...d-protection-and-interpersonal-violence-md | 107 + ...ION-SYSTEM__DESIGN__chis-general-design-md | 4 +- ...civil-registration-and-vital-statistics-md | 166 + ...NFORMATION-SYSTEM__DESIGN__clean-energy-md | 82 + ...M__DESIGN__community-based-surveillance-md | 75 + ...NFORMATION-SYSTEM__DESIGN__immunization-md | 116 + ...N__integrated-community-case-management-md | 243 + ...LTH-INFORMATION-SYSTEM__DESIGN__malaria-md | 176 + ...RMATION-SYSTEM__DESIGN__maternal-health-md | 248 ++ ...FORMATION-SYSTEM__DESIGN__mental-health-md | 272 ++ ...EM__DESIGN__neglected-tropical-diseases-md | 267 ++ ...ORMATION-SYSTEM__DESIGN__newborn-health-md | 143 + ...STEM__DESIGN__non-communicable-diseases-md | 183 + ...H-INFORMATION-SYSTEM__DESIGN__nutrition-md | 251 ++ ...YSTEM__DESIGN__people-centered-services-md | 114 + ...-SYSTEM__DESIGN__population-composition-md | 114 + ..._DESIGN__sexual-and-reproductive-health-md | 194 + ...NFORMATION-SYSTEM__DESIGN__tuberculosis-md | 234 + ...M__DESIGN__water-sanitation-and-hygiene-md | 125 + ...ENTATION__sustainability-and-governance-md | 574 +++ ...HEALTH-INFORMATION-SYSTEM__installation-md | 40 +- ...HEALTH-INFORMATION-SYSTEM__release-note-md | 37 + ...URVEILLANCE__COVID-19-AGGREGATE__design-md | 6 +- ...LANCE__COVID-19-AGGREGATE__installation-md | 40 +- ...NCE__COVID-19-CASE-SURVEILLANCE__design-md | 2 +- ...OVID-19-CASE-SURVEILLANCE__installation-md | 80 +- ...OVID-19-CASE-SURVEILLANCE__release-note-md | 56 + ...-19-POINTS-OF-ENTRYDISCONTINUED__design-md | 2 +- ...URVEILLANCE-EVENTS-DISCONTINUED__design-md | 4 +- ...TH__COVID-19-SURVEILLANCE__release-note-md | 56 + ...DELIVERY__COVAC-AGGREGATE__installation-md | 40 +- ...DELIVERY__COVAC-AGGREGATE__release-note-md | 17 + ...LECTRONIC-IMMUNIZATION-REGISTRY__design-md | 4 +- ...NIC-IMMUNIZATION-REGISTRY__installation-md | 148 +- ...MORTALITY__CAUSE-OF-DEATH__installation-md | 135 + ...MORTALITY__CAUSE-OF-DEATH__release-note-md | 2 +- ...Y__RAPID-MORTALITY-SURVEILLANCE__design-md | 4 +- ...ID-MORTALITY-SURVEILLANCE__installation-md | 124 +- ...H__CRVS-MORTALITY__VITAL-EVENTS__design-md | 2 +- ...S-MORTALITY__VITAL-EVENTS__installation-md | 152 +- ...__COMMON-METADATA-LIBRARY__installation-md | 93 + ...CE__ACUTE-FEBRILE-ILLNESS__installation-md | 92 +- ...RVEILLANCE__IDS-AGGREGATE__installation-md | 124 +- ...CE__VPD-CASE-SURVEILLANCE__installation-md | 88 +- ...S-MONITORING__LARVICIDING__installation-md | 122 +- ...SIDUAL-SPRAYING__CAMPAIGN__installation-md | 72 +- ...IDUAL-EFFICACY-MONITORING__installation-md | 122 +- ...TREATED-NETS__BIOEFFICACY__installation-md | 122 +- ...ASS-DISTRIBUTION-CAMPAIGN__installation-md | 82 +- ...LOGY-AND-VECTOR-CONTROL__general-design-md | 2 +- ...HEALTH__HEALTH-FACILITY-PROFILE__design-md | 2 +- ...__HEALTH-FACILITY-PROFILE__installation-md | 88 +- ...LTH__HIV__HIV-CASE-SURVEILLANCE__design-md | 45 +- ...IV__HIV-CASE-SURVEILLANCE__installation-md | 96 +- ...VENTION__DESIGN__hiv-prevention-tracker-md | 488 +- ...ALTH__HIV__HIV-PREVENTION__installation-md | 106 +- ...LLOWING-IMMUNIZATION-AEFI__installation-md | 80 +- ...IR-IMMUNIZATION-EREGISTRY__installation-md | 84 +- ...MUNIZATION__EPI-LOGISTICS__installation-md | 40 +- ...MMUNIZATION-EPI-AGGREGATE__installation-md | 154 +- ...LYSIS-APP__APP-VERSION-103__user-manual-md | 2 +- ...MUNIZATION__IMMUNIZATION-CAMPAIGNS__use-md | 2 +- ...N-TRIANGULATION-DASHBOARD__installation-md | 88 +- ...MMUNIZATION__VACCINATION-CAMPAIGNS__use-md | 2 +- ...TH__MALARIA__MALARIA-HMIS__installation-md | 154 +- ...ALARIA__MALARIA-LOGISTICS__installation-md | 154 +- ...RIA__MALARIA-SURVEILLANCE__installation-md | 140 +- ...-DISEASES__HYPERTENSION-CONTROL__design-md | 2 +- ...SES__HYPERTENSION-CONTROL__installation-md | 76 +- ...FUNCTION-EYE-AND-EAR-CARE__installation-md | 130 +- ...TION__NUTRITION-AGGREGATE__installation-md | 150 +- ...T__HEALTH__REHABILITATION__installation-md | 134 +- ...EALTH__RMNCAH__RMNCAH-AGGREGATE__design-md | 2 +- ..._RMNCAH__RMNCAH-AGGREGATE__installation-md | 40 +- ...H-ANTENATAL-CARE-REGISTRY__installation-md | 68 +- ...RUG-RESISTANCE-SURVEY-DRS__installation-md | 108 +- ...SIS__TB-CASE-SURVEILLANCE__installation-md | 118 +- ...OVID-19-IMPACT-ASSESSMENT__installation-md | 134 +- ...__DESIGN__tb-notifications-and-outcomes-md | 2 +- ...TH__TUBERCULOSIS__TB-HMIS__installation-md | 146 +- ...LD-CONTACTS-INVESTIGATION__installation-md | 116 +- ...UBERCULOSIS__TB-LOGISTICS__installation-md | 146 +- ...NTENANCE-AND-USE__localization-of-dhis2-md | 218 + ...-IMPLEMENTATION__localization-of-dhis-2-md | 227 + ...ON__DHIS-CORE-VERSION-237__installation-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-238__audit-md | 2 +- ...ON__DHIS-CORE-VERSION-238__installation-md | 4 +- ...TION__DHIS-CORE-VERSION-238__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-238__upgrading-md | 2 +- ...N-238__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-239__audit-md | 2 +- ...ON__DHIS-CORE-VERSION-239__installation-md | 4 +- ...TION__DHIS-CORE-VERSION-239__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-239__upgrading-md | 2 +- ...N-239__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-240__audit-md | 2 +- ...-VERSION-240__debugging-as-another-user-md | 6 +- ...ON__DHIS-CORE-VERSION-240__installation-md | 4 +- ...TION__DHIS-CORE-VERSION-240__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-240__upgrading-md | 2 +- ...N-240__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-241__audit-md | 2 +- ...-VERSION-241__debugging-as-another-user-md | 6 +- ...ON__DHIS-CORE-VERSION-241__installation-md | 4 +- ...TION__DHIS-CORE-VERSION-241__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-241__upgrading-md | 2 +- ...N-241__using-gateways-for-sms-reporting-md | 2 +- ...RATION__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...RSION-MASTER__debugging-as-another-user-md | 6 +- ..._DHIS-CORE-VERSION-MASTER__installation-md | 4 +- ...HEALTH-INFORMATION-SYSTEM__installation-md | 40 +- ...LANCE__COVID-19-AGGREGATE__installation-md | 40 +- ...CASE-SURVEILLANCE-TRACKER__installation-md | 50 +- ...OVID-19-CASE-SURVEILLANCE__installation-md | 78 +- ...OVID-19-CASE-SURVEILLANCE__release-note-md | 56 + ...-POE-TRACKER-DISCONTINUED__installation-md | 50 +- ...NCE__COVID-19-POE-TRACKER__installation-md | 50 +- ...INTS-OF-ENTRYDISCONTINUED__installation-md | 50 +- ...LANCE-EVENTS-DISCONTINUED__installation-md | 40 +- ...TA__COVID-19-SURVEILLANCE__release-note-md | 56 + ...AC-AGGREGATE__VERSION-100__installation-md | 18 +- ...AC-AGGREGATE__VERSION-110__installation-md | 18 +- ...DELIVERY__COVAC-AGGREGATE__installation-md | 40 +- ...NIZATION-REGISTRY-TRACKER__installation-md | 110 +- ...NIC-IMMUNIZATION-REGISTRY__installation-md | 144 +- ...-DEATH-TRACKER-DISCONTINUED__change-log-md | 82 + ...EATH-TRACKER-DISCONTINUED__installation-md | 132 + ...ITY__CAUSE-OF-DEATH-TRACKER__change-log-md | 82 + ...Y__CAUSE-OF-DEATH-TRACKER__installation-md | 132 + ...USE-OF-DEATH__VERSION-120__installation-md | 135 + ...USE-OF-DEATH__VERSION-120__release-note-md | 89 + ...USE-OF-DEATH__VERSION-121__installation-md | 135 + ...USE-OF-DEATH__VERSION-121__release-note-md | 89 + ...S-MORTALITY__CAUSE-OF-DEATH__change-log-md | 82 + ...MORTALITY__CAUSE-OF-DEATH__installation-md | 135 + ...MORTALITY__CAUSE-OF-DEATH__release-note-md | 2 +- ...D-MORTALITY-SURVEILLANCE-EVENTS__design-md | 2 +- ...ALITY-SURVEILLANCE-EVENTS__installation-md | 88 +- ...Y__RAPID-MORTALITY-SURVEILLANCE__design-md | 2 +- ...ID-MORTALITY-SURVEILLANCE__installation-md | 122 +- ...ENTS-TRACKER__VERSION-100__installation-md | 110 +- ...ENTS-TRACKER__VERSION-110__installation-md | 110 +- ...VITAL-EVENTS__VERSION-100__installation-md | 110 +- ...VITAL-EVENTS__VERSION-110__installation-md | 110 +- ...S-MORTALITY__VITAL-EVENTS__installation-md | 148 +- ...__COMMON-METADATA-LIBRARY__installation-md | 93 + ...H-DATA-TOOLKIT__common-metadata-library-md | 60 + ...CE__ACUTE-FEBRILE-ILLNESS__installation-md | 92 +- ...DS-AGGREGATE__VERSION-120__installation-md | 86 +- ...RVEILLANCE__IDS-AGGREGATE__installation-md | 124 +- ...CASE-SURVEILLANCE-TRACKER__installation-md | 58 +- ...ANCE-TRACKER__vpd-cs-installation-annex-md | 58 +- ...CE__VPD-CASE-SURVEILLANCE__installation-md | 88 +- ...S-MONITORING__LARVICIDING__installation-md | 122 +- ...SIDUAL-SPRAYING__CAMPAIGN__installation-md | 72 +- ...IDUAL-EFFICACY-MONITORING__installation-md | 122 +- ...TREATED-NETS__BIOEFFICACY__installation-md | 122 +- ...ASS-DISTRIBUTION-CAMPAIGN__installation-md | 82 +- ...IV-AGGREGATE__VERSION-110__installation-md | 18 +- ...IV-AGGREGATE__VERSION-120__installation-md | 132 +- ...CASE-SURVEILLANCE-TRACKER__installation-md | 50 +- ...ATA__HIV__HIV-CASE-SURVEILLANCE__design-md | 20 +- ...IV__HIV-CASE-SURVEILLANCE__installation-md | 90 +- ...IV__HIV-HMIS__VERSION-110__installation-md | 18 +- projects/docs-full-site/fr/.cache_timestamp | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 27 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 25 +- projects/docs-full-site/pt/.cache_timestamp | 2 +- ..._DHIS-CORE-VERSION-238__data-validation-md | 2 +- ...PI__DHIS-CORE-VERSION-238__introduction-md | 2 +- ...THE-API__DHIS-CORE-VERSION-238__sharing-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-239__apps-md | 2 +- ...-API__DHIS-CORE-VERSION-239__data-entry-md | 2 +- ...VERSION-239__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-239__tracker-md | 2 +- ...E-API__DHIS-CORE-VERSION-240__analytics-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-240__apps-md | 2 +- ...-API__DHIS-CORE-VERSION-240__data-store-md | 2 +- ..._DHIS-CORE-VERSION-240__data-validation-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__email-md | 2 +- ...PI__DHIS-CORE-VERSION-240__introduction-md | 2 +- ...API__DHIS-CORE-VERSION-240__maintenance-md | 2 +- ...DHIS-CORE-VERSION-240__org-unit-profile-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__route-md | 2 +- ...-API__DHIS-CORE-VERSION-240__scheduling-md | 2 +- ...VERSION-240__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__sharing-md | 2 +- ...ING-THE-API__DHIS-CORE-VERSION-240__sms-md | 2 +- ...IS-CORE-VERSION-240__tracker-deprecated-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 10 +- ...G-THE-API__DHIS-CORE-VERSION-240__users-md | 2 +- ...__DHIS-CORE-VERSION-240__visualizations-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-241__apps-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-241__audit-md | 2 +- ...I__DHIS-CORE-VERSION-241__data-approval-md | 2 +- ...-API__DHIS-CORE-VERSION-241__data-entry-md | 2 +- ...IS-CORE-VERSION-241__tracker-deprecated-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-241__users-md | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__analytics-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__apps-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-approval-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-entry-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__data-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-store-md | 2 +- ...IS-CORE-VERSION-MASTER__data-validation-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__email-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__event-hooks-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__i18n-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__introduction-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__maintenance-md | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__messaging-md | 2 +- ...DHIS-CORE-VERSION-MASTER__metadata-gist-md | 2 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 224 +- ...S-CORE-VERSION-MASTER__org-unit-profile-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__route-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__scheduling-md | 2 +- ...SION-MASTER__settings-and-configuration-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__sharing-md | 2 +- ...-THE-API__DHIS-CORE-VERSION-MASTER__sms-md | 2 +- ...IS-CORE-VERSION-MASTER__synchronization-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 28 +- ...HE-API__DHIS-CORE-VERSION-MASTER__users-md | 2 +- ...HIS-CORE-VERSION-MASTER__visualizations-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-238__audit-md | 2 +- ...ON__DHIS-CORE-VERSION-238__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-238__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-238__upgrading-md | 2 +- ...N-238__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-239__audit-md | 2 +- ...ON__DHIS-CORE-VERSION-239__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-239__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-239__upgrading-md | 2 +- ...N-239__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-240__audit-md | 2 +- ...-VERSION-240__debugging-as-another-user-md | 2 +- ...ON__DHIS-CORE-VERSION-240__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-240__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-240__upgrading-md | 2 +- ...N-240__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-241__audit-md | 2 +- ...-VERSION-241__debugging-as-another-user-md | 2 +- ...ON__DHIS-CORE-VERSION-241__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-241__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-241__upgrading-md | 2 +- ...N-241__using-gateways-for-sms-reporting-md | 2 +- ...RATION__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...RSION-MASTER__debugging-as-another-user-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__installation-md | 2 +- ...N__DHIS-CORE-VERSION-MASTER__monitoring-md | 2 +- ...ON__DHIS-CORE-VERSION-MASTER__upgrading-md | 2 +- ...ASTER__using-gateways-for-sms-reporting-md | 2 +- ...10__DASHBOARD-AND-DEMO-SERVER__browsing-md | 2 +- ...DASHBOARD-AND-DEMO-SERVER__introduction-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-planning-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-tracking-md | 2 +- ...LLATION-AND-CONFIGURATION__installation-md | 2 +- ...ALLATION-AND-CONFIGURATION__maintenance-md | 2 +- ...-AND-USAGE__analysis-and-interpretation-md | 2 +- ...NTRODUCTION-AND-USAGE__app-architecture-md | 2 +- ...RODUCTION-AND-USAGE__dashboard-and-demo-md | 2 +- ...RODUCTION-AND-USAGE__navigating-the-app-md | 2 +- ...ION-AND-USAGE__visualization-operations-md | 2 +- ...ER-IMPLEMENTATION__adopting-the-bna-app-md | 2 +- ..._USER-IMPLEMENTATION__capacity-building-md | 2 +- ..._USER-IMPLEMENTATION__end-user-training-md | 2 +- ...IMPLEMENTATION__implementation-overview-md | 2 +- ...ER-IMPLEMENTATION__integration-concepts-md | 2 +- ...MENTATION__opportunities-and-challenges-md | 2 +- ...IMPLEMENTATION__planning-and-organising-md | 2 +- ...USER-IMPLEMENTATION__setting-up-the-app-md | 2 +- ...ER-IMPLEMENTATION__support-and-scale-up-md | 2 +- ...22__USER-IMPLEMENTATION__sustainability-md | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...S-APP__APP-VERSION-140__USAGE__map-view-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 23 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-239__ANALYSING-DATA__dashboards-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...ION-239__APPROVING-DATA__approving-data-md | 2 +- ...SION-239__APPROVING-DATA__data-approval-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 13 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 10 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 25 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...ERSION-240__COLLECTING-DATA__data-entry-md | 11 +- ...N-240__CONFIGURING-THE-SYSTEM__programs-md | 8 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 23 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 25 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...SION-MASTER__ANALYSING-DATA__dashboards-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...VERSION-MASTER__ANALYSING-DATA__reports-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-md | 2 +- ...N-MASTER__APPROVING-DATA__data-approval-md | 2 +- ...ASTER__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ION-MASTER__COLLECTING-DATA__data-entry-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...-MASTER__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...-MASTER__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- projects/docs-full-site/ru/.cache_timestamp | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...S-APP__APP-VERSION-140__USAGE__map-view-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...-APP__APP-VERSION-250__about-this-guide-md | 2 +- ...0__accessing-and-transilating-scorecard-md | 2 +- ...CORECARD-APP__APP-VERSION-250__browsing-md | 2 +- ...PP__APP-VERSION-250__creating-scorecard-md | 2 +- ...-250__introduction-to-the-scorecard-app-md | 2 +- ..._APP-VERSION-250__saving-configurations-md | 2 +- ...VERSION-250__scorecard-app-architecture-md | 2 +- ...ON-250__support-and-maintenance-options-md | 2 +- ...APP__APP-VERSION-250__viewing-scorecard-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...APP-DEMO__architecture-and-installation-md | 2 +- ...ALONE-ACTION-TRACKER-APP-DEMO__browsing-md | 2 +- ...E-ACTION-TRACKER-APP-DEMO__introduction-md | 2 +- ...ON-TRACKER-CONFIGURATION__configuration-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-238__ANALYSING-DATA__dashboards-md | 2 +- ...ON-238__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-238__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-238__ANALYSING-DATA__reports-md | 2 +- ...ION-238__APPROVING-DATA__approving-data-md | 2 +- ...SION-238__APPROVING-DATA__data-approval-md | 2 +- ...ERSION-238__COLLECTING-DATA__data-entry-md | 2 +- ...SION-238__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-238__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-238__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...SION-238__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-238__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...238__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...8__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-239__ANALYSING-DATA__dashboards-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...ION-239__APPROVING-DATA__approving-data-md | 2 +- ...SION-239__APPROVING-DATA__data-approval-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 2 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...SION-MASTER__ANALYSING-DATA__dashboards-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...VERSION-MASTER__ANALYSING-DATA__reports-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-md | 2 +- ...N-MASTER__APPROVING-DATA__data-approval-md | 2 +- ...ASTER__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ION-MASTER__COLLECTING-DATA__data-entry-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...-MASTER__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...-MASTER__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- projects/docs-full-site/si/.cache_timestamp | 2 +- projects/docs-full-site/zh/.cache_timestamp | 2 +- ...E-API__DHIS-CORE-VERSION-238__analytics-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__apps-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__audit-md | 2 +- ...I__DHIS-CORE-VERSION-238__data-approval-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__data-md | 2 +- ...-API__DHIS-CORE-VERSION-238__data-store-md | 2 +- ..._DHIS-CORE-VERSION-238__data-validation-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__email-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-238__i18n-md | 2 +- ...PI__DHIS-CORE-VERSION-238__introduction-md | 2 +- ...API__DHIS-CORE-VERSION-238__maintenance-md | 2 +- ...E-API__DHIS-CORE-VERSION-238__messaging-md | 2 +- ...I__DHIS-CORE-VERSION-238__metadata-gist-md | 2 +- ...HE-API__DHIS-CORE-VERSION-238__metadata-md | 2 +- ...API__DHIS-CORE-VERSION-238__new-tracker-md | 2 +- ...DHIS-CORE-VERSION-238__org-unit-profile-md | 2 +- ...-API__DHIS-CORE-VERSION-238__scheduling-md | 2 +- ...VERSION-238__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-238__sharing-md | 2 +- ...ING-THE-API__DHIS-CORE-VERSION-238__sms-md | 2 +- ..._DHIS-CORE-VERSION-238__synchronization-md | 2 +- ...THE-API__DHIS-CORE-VERSION-238__tracker-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-238__users-md | 2 +- ...__DHIS-CORE-VERSION-238__visualizations-md | 2 +- ..._DHIS-CORE-VERSION-240__data-validation-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__email-md | 2 +- ...PI__DHIS-CORE-VERSION-240__introduction-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__sharing-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 10 +- ...G-THE-API__DHIS-CORE-VERSION-240__users-md | 2 +- ...__DHIS-CORE-VERSION-240__visualizations-md | 2 +- ...NG-THE-API__DHIS-CORE-VERSION-241__apps-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-241__audit-md | 2 +- ...I__DHIS-CORE-VERSION-241__data-approval-md | 2 +- ...-API__DHIS-CORE-VERSION-241__data-entry-md | 2 +- ...IS-CORE-VERSION-241__tracker-deprecated-md | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...S-APP__APP-VERSION-140__USAGE__map-view-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...-APP__APP-VERSION-250__about-this-guide-md | 2 +- ...0__accessing-and-transilating-scorecard-md | 2 +- ...CORECARD-APP__APP-VERSION-250__browsing-md | 2 +- ...PP__APP-VERSION-250__creating-scorecard-md | 2 +- ...-250__introduction-to-the-scorecard-app-md | 2 +- ..._APP-VERSION-250__saving-configurations-md | 2 +- ...VERSION-250__scorecard-app-architecture-md | 2 +- ...ON-250__support-and-maintenance-options-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 23 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-239__ANALYSING-DATA__dashboards-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...ION-239__APPROVING-DATA__approving-data-md | 2 +- ...SION-239__APPROVING-DATA__data-approval-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 13 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 10 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 25 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...ERSION-240__COLLECTING-DATA__data-entry-md | 11 +- ...N-240__CONFIGURING-THE-SYSTEM__programs-md | 8 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 23 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 25 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 25 +- 1215 files changed, 19512 insertions(+), 5264 deletions(-) create mode 100644 projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md create mode 100644 projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__CHIS-IMPLEMENTATION__sustainability-and-governance-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-android-settings-web-app-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__AGGREGATE-SYSTEM-DESIGN__indicators-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__organisation-units-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__adolescant-health-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-health-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-protection-and-interpersonal-violence-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__civil-registration-and-vital-statistics-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__clean-energy-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__community-based-surveillance-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__immunization-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__integrated-community-case-management-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__malaria-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__maternal-health-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__mental-health-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__neglected-tropical-diseases-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__newborn-health-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__non-communicable-diseases-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__nutrition-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__people-centered-services-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__population-composition-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__sexual-and-reproductive-health-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__tuberculosis-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__water-sanitation-and-hygiene-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__IMPLEMENTATION__sustainability-and-governance-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__release-note-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__release-note-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__release-note-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DHIS2-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__MAINTENANCE-AND-USE__localization-of-dhis2-md create mode 100644 projects/docs-full-site/es_419/IMPLEMENT__UNDERSTANDING-DHIS2-IMPLEMENTATION__localization-of-dhis-2-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__release-note-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__change-log-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__installation-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__change-log-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__installation-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__installation-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__release-note-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__installation-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__release-note-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__change-log-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md create mode 100644 projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__common-metadata-library-md diff --git a/projects/dhis2-single-page-docs/am_ET/.cache_timestamp b/projects/dhis2-single-page-docs/am_ET/.cache_timestamp index bc48cfbf7..d78df2763 100644 --- a/projects/dhis2-single-page-docs/am_ET/.cache_timestamp +++ b/projects/dhis2-single-page-docs/am_ET/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:22:50Z \ No newline at end of file +2024-07-17T21:24:54Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ar/.cache_timestamp b/projects/dhis2-single-page-docs/ar/.cache_timestamp index bc48cfbf7..d78df2763 100644 --- a/projects/dhis2-single-page-docs/ar/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ar/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:22:50Z \ No newline at end of file +2024-07-17T21:24:54Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 6f4df44d0..398256811 100644 --- a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- Develop - DHIS core version 2.40 +- Develop template: single.html --- diff --git a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 07ba81c0d..b332db3ea 100644 --- a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- DHIS core version master - Develop +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 0fa45a110..b3a709f9e 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Use - DHIS core version 2.39 +- Use template: single.html --- diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 3cc959ed3..efb8b86be 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Use - DHIS core version 2.39 +- Use template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/.cache_timestamp b/projects/dhis2-single-page-docs/cs/.cache_timestamp index d58193004..e84a23380 100644 --- a/projects/dhis2-single-page-docs/cs/.cache_timestamp +++ b/projects/dhis2-single-page-docs/cs/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:22:57Z \ No newline at end of file +2024-07-17T21:25:02Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index cc702e83d..46a481cdf 100644 --- a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- Vývoj - DHIS základní verze 2.40 +- Vývoj template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 4eee6d308..247dbc0b2 100644 --- a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- Hlavní verze jádra DHIS - Vývoj +- Hlavní verze jádra DHIS template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index f646d136b..ea9770944 100644 --- a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- DHIS core verze 2.37 - Správa +- DHIS core verze 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md index 0015ebca3..1c6ef1a29 100644 --- a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- DHIS core version 2.38 - Správa +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index 21fb3ce97..572cd7e33 100644 --- a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-06-18' tags: -- Hlavní verze jádra DHIS - Správa +- Hlavní verze jádra DHIS template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 84c6000fd..630763000 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Použití - DHIS základní verze 2.39 +- Použití template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index dca6b0197..455aa3f32 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Použití - DHIS základní verze 2.39 +- Použití template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/.cache_timestamp b/projects/dhis2-single-page-docs/es_419/.cache_timestamp index 9b003604c..0fc2ad9c4 100644 --- a/projects/dhis2-single-page-docs/es_419/.cache_timestamp +++ b/projects/dhis2-single-page-docs/es_419/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:06Z \ No newline at end of file +2024-07-17T21:25:09Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md index 38cf2ebdb..15d7de566 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md @@ -2236,7 +2236,7 @@ supported: - Data element groups - - Category options + - Opciones de categoría - Category option groups diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md index f04684e9f..9b026ab0b 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md @@ -21857,7 +21857,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{\} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{\.\ | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md index a7cd6c2e5..21ae8a611 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md @@ -2933,7 +2933,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{\} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{\.\ | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -7550,7 +7550,7 @@ can make a GET request similar to this: -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md index d2c7dc3c3..1e189372c 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md @@ -18996,7 +18996,7 @@ A predictor always has a generator expression that describes how the predicted v The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | --- | --- | --- | | #{\} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{\.\ | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md index c753a3c3d..4c15e00f5 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md @@ -2430,7 +2430,7 @@ A predictor always has a generator expression that describes how the predicted v The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | --- | --- | --- | | #{\<dataelement-id>} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{\<dataelement-id>.\<categoryoptcombo-id>} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index 2040f72a6..11e63d297 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1818,7 +1818,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -2308,7 +2308,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2575,7 +2575,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -3657,7 +3657,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -4220,7 +4220,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | @@ -6361,7 +6361,7 @@ can make a GET request similar to this: - `F_DATA_APPROVAL_LEVEL` : allow user to Add/Update Data Approval Level -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -6557,7 +6557,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - The sharing solution supports cascade sharing for Dashboard. - This function will copy `userAccesses` and `userGroupAccesses` of a Dashboard to all of its DashboardItem's objects including `Map`, `EventReport`, `EventChart`, `Visualization`. @@ -7753,8 +7753,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } @@ -17522,7 +17522,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index 0ed0d5eed..a519fda98 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1876,7 +1876,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -2371,7 +2371,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2639,7 +2639,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -3723,7 +3723,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -4350,7 +4350,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | @@ -6699,7 +6699,7 @@ can make a GET request similar to this: - `F_DATA_APPROVAL_LEVEL` : allow user to Add/Update Data Approval Level -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -6895,7 +6895,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. @@ -8365,8 +8365,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } @@ -18896,7 +18896,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index 4a5f1035a..15af25be5 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -2145,7 +2145,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -2640,7 +2640,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2908,7 +2908,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -3997,7 +3997,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -4624,7 +4624,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | @@ -7003,7 +7003,7 @@ can make a GET request similar to this: - `F_DATA_APPROVAL_LEVEL` : allow user to Add/Update Data Approval Level -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -7199,7 +7199,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. @@ -8671,8 +8671,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } @@ -14011,7 +14011,7 @@ The aggregate data exchange service is suitable for use-cases such as: * Precomputation of tracker data with program indicators saved as aggregate data values. * Data reporting from a national HMIS to a global donor. -### Overview { #overview } +### Visión general { #overview } The aggregate data exchange service allows for data exchange between a *source* instance of DHIS 2 and a *target* instance of DHIS 2. A data exchange can be *external*, for which the target instance is different/external to the source instance. A data exchange can also be *internal*, for which the target instance is the same as the source instance. The aggregate data exchange source can contain multiple source requests, where a source request roughly corresponds to an analytics API request. @@ -14336,8 +14336,8 @@ The aggregate data exchange data model / payload is described in the following s | Field | Tipo de dato | Mandatory | Descripción | | ------------------------------------------------- | -------------- | ----------- | ------------------------------------------------------------ | | name | Cadena | Sí | Name of aggregate data exchange. Unique. | -| source | Object | Sí | Source for aggregate data exchange. | -| source.params | Object | No | Parameters for source request. | +| source | Objeto | Sí | Source for aggregate data exchange. | +| source.params | Objeto | No | Parameters for source request. | | source.params.periodTypes | Array/String | No | Allowed period types for overriding periods in source request. | | source.requests | Array/Object | Sí | Source requests. | | source.requests.name | Cadena | Sí | Name of source request. | @@ -14352,14 +14352,14 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.outputDataElementIdScheme | Cadena | No | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output organisation unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | -| source.target | Object | Sí | Target for aggregate data exchange. | +| source.target | Objeto | Sí | Target for aggregate data exchange. | | source.target.type | Cadena | Sí | Type of target, can be `EXTERNAL`, `INTERNAL`. | -| source.target.api | Object | Conditional | Target API information, only mandatory for type `EXTERNAL`. | +| source.target.api | Objeto | Conditional | Target API information, only mandatory for type `EXTERNAL`. | | source.target.api.url | Cadena | Conditional | Base URL of target DHIS 2 instance, do not include the `/api` part. | | source.target.api.accessToken | Cadena | Conditional | Access token (PAT) for target DHIS 2 instance, used for PAT authentication. | | source.target.api.username | Cadena | Conditional | Username for target DHIS 2 instance, used for basic authentication. | | source.target.api.password | Cadena | Conditional | Password for target DHIS 2 instance, used for basic authentication. | -| source.target.request | Object | No | Target request information. | +| source.target.request | Objeto | No | Target request information. | | source.target.request.dataElementIdScheme | Cadena | No | Input data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.orgUnitIdScheme | Cadena | No | Input organisation unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | @@ -19739,7 +19739,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index f75655098..4fce30c27 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- Desarrollar - DHIS core version 2.40 +- Desarrollar template: single.html --- @@ -2127,7 +2127,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -2622,7 +2622,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2890,7 +2890,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -4040,7 +4040,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -4667,7 +4667,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | @@ -7081,7 +7081,7 @@ can make a GET request similar to this: - `F_DATA_APPROVAL_LEVEL` : allow user to Add/Update Data Approval Level -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -7277,7 +7277,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. @@ -8916,8 +8916,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } @@ -14271,7 +14271,7 @@ The aggregate data exchange service is suitable for use-cases such as: * Precomputation of tracker data with program indicators saved as aggregate data values. * Data reporting from a national HMIS to a global donor. -### Overview { #overview } +### Visión general { #overview } The aggregate data exchange service allows for data exchange between a *source* instance of DHIS 2 and a *target* instance of DHIS 2. A data exchange can be *external*, for which the target instance is different/external to the source instance. A data exchange can also be *internal*, for which the target instance is the same as the source instance. The aggregate data exchange source can contain multiple source requests, where a source request roughly corresponds to an analytics API request. @@ -14630,8 +14630,8 @@ The aggregate data exchange data model / payload is described in the following s | Field | Tipo de dato | Mandatory | Descripción | | ------------------------------------------------- | -------------- | ----------- | ------------------------------------------------------------ | | name | Cadena | Sí | Name of aggregate data exchange. Unique. | -| source | Object | Sí | Source for aggregate data exchange. | -| source.params | Object | No | Parameters for source request. | +| source | Objeto | Sí | Source for aggregate data exchange. | +| source.params | Objeto | No | Parameters for source request. | | source.params.periodTypes | Array/String | No | Allowed period types for overriding periods in source request. | | source.requests | Array/Object | Sí | Source requests. | | source.requests.name | Cadena | Sí | Name of source request. | @@ -14646,14 +14646,14 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.outputDataElementIdScheme | Cadena | No | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | -| source.target | Object | Sí | Target for aggregate data exchange. | +| source.target | Objeto | Sí | Target for aggregate data exchange. | | source.target.type | Cadena | Sí | Type of target, can be `EXTERNAL`, `INTERNAL`. | -| source.target.api | Object | Conditional | Target API information, only mandatory for type `EXTERNAL`. | +| source.target.api | Objeto | Conditional | Target API information, only mandatory for type `EXTERNAL`. | | source.target.api.url | Cadena | Conditional | Base URL of target DHIS 2 instance, do not include the `/api` part. | | source.target.api.accessToken | Cadena | Conditional | Access token (PAT) for target DHIS 2 instance, used for PAT authentication. | | source.target.api.username | Cadena | Conditional | Username for target DHIS 2 instance, used for basic authentication. | | source.target.api.password | Cadena | Conditional | Password for target DHIS 2 instance, used for basic authentication. | -| source.target.request | Object | No | Target request information. | +| source.target.request | Objeto | No | Target request information. | | source.target.request.dataElementIdScheme | Cadena | No | Input data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.orgUnitIdScheme | Cadena | No | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | @@ -17422,7 +17422,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index e04880478..702fad4cb 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- DHIS core version master - Desarrollar +- DHIS core version master template: single.html --- @@ -2434,7 +2434,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -3167,7 +3167,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -3435,7 +3435,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -4533,7 +4533,7 @@ The response will also contain a `Location` header with a link to the newly-crea The API does allow the optional supplying of a custom prefix, which will be prefixed to the following properties. -| Object | Property | Info | +| Objeto | Property | Info | |------------------|-----------|------------------------------------------| | Programa | name | Help identify the new Program | | ProgramIndicator | name | Database constraint - needs to be unique | @@ -4631,7 +4631,7 @@ A shallow copy in this context means that an existing `Program` property will be All properties below have been deep copied. Anything not in included in this table means that it has been shallow copied. -| Object | Property of | +| Objeto | Property of | |--------------------------------|--------------| | Programa | | | ProgramSection | Programa | @@ -4646,7 +4646,7 @@ All properties below have been deep copied. Anything not in included in this tab > > The following properties have been set as empty as an initial approach. This approach should keep things simple to start off with. -| Object | Property | +| Objeto | Property | |-------------------------------|-------------------| | ProgramIndicator | groups | | ProgramStageSection | programIndicators | @@ -4771,7 +4771,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -5420,7 +5420,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | @@ -8027,7 +8027,7 @@ can make a GET request similar to this: - `F_DATA_APPROVAL_LEVEL` : allow user to Add/Update Data Approval Level -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -8223,7 +8223,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. @@ -9962,8 +9962,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } @@ -15833,7 +15833,7 @@ The aggregate data exchange service is suitable for use-cases such as: * Precomputation of tracker data with program indicators saved as aggregate data values. * Data reporting from a national HMIS to a global donor. -### Overview { #overview } +### Visión general { #overview } The aggregate data exchange service allows for data exchange between a *source* instance of DHIS 2 and a *target* instance of DHIS 2. A data exchange can be *external*, for which the target instance is different/external to the source instance. A data exchange can also be *internal*, for which the target instance is the same as the source instance. The aggregate data exchange source can contain multiple source requests, where a source request roughly corresponds to an analytics API request. @@ -16192,8 +16192,8 @@ The aggregate data exchange data model / payload is described in the following s | Field | Tipo de dato | Mandatory | Descripción | | ------------------------------------------------- | -------------- | ----------- | ------------------------------------------------------------ | | name | Cadena | Sí | Name of aggregate data exchange. Unique. | -| source | Object | Sí | Source for aggregate data exchange. | -| source.params | Object | No | Parameters for source request. | +| source | Objeto | Sí | Source for aggregate data exchange. | +| source.params | Objeto | No | Parameters for source request. | | source.params.periodTypes | Array/String | No | Allowed period types for overriding periods in source request. | | source.requests | Array/Object | Sí | Source requests. | | source.requests.name | Cadena | Sí | Name of source request. | @@ -16209,14 +16209,14 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.outputDataItemIdScheme | Cadena | No | Output data item ID scheme applies to data elements, indicators and program indicators, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | -| source.target | Object | Sí | Target for aggregate data exchange. | +| source.target | Objeto | Sí | Target for aggregate data exchange. | | source.target.type | Cadena | Sí | Type of target, can be `EXTERNAL`, `INTERNAL`. | -| source.target.api | Object | Conditional | Target API information, only mandatory for type `EXTERNAL`. | +| source.target.api | Objeto | Conditional | Target API information, only mandatory for type `EXTERNAL`. | | source.target.api.url | Cadena | Conditional | Base URL of target DHIS 2 instance, do not include the `/api` part. | | source.target.api.accessToken | Cadena | Conditional | Access token (PAT) for target DHIS 2 instance, used for PAT authentication. | | source.target.api.username | Cadena | Conditional | Username for target DHIS 2 instance, used for basic authentication. | | source.target.api.password | Cadena | Conditional | Password for target DHIS 2 instance, used for basic authentication. | -| source.target.request | Object | No | Target request information. | +| source.target.request | Objeto | No | Target request information. | | source.target.request.dataElementIdScheme | Cadena | No | Input data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.orgUnitIdScheme | Cadena | No | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | @@ -19462,7 +19462,7 @@ The import will validate unique attributes at the time of import. That means as value is unique for the attribute in the whole system, it will pass. However, if the unique value is found to be used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. diff --git a/projects/dhis2-single-page-docs/es_419/IMPLEMENT__chis-implementation-md b/projects/dhis2-single-page-docs/es_419/IMPLEMENT__chis-implementation-md index fcd24d935..6acaebc1c 100644 --- a/projects/dhis2-single-page-docs/es_419/IMPLEMENT__chis-implementation-md +++ b/projects/dhis2-single-page-docs/es_419/IMPLEMENT__chis-implementation-md @@ -2376,7 +2376,7 @@ SOPs are the translation of policies and procedures into day to day life of the There are many ways to define SOPs, and the actual SOPs vary tremendously from country to country and project to project. The SOPs outlined below represent some very basic, practical SOPs that could serve as the foundation for country or program specific SOPs. -#### Overview { #overview } +#### Visión general { #overview } There are three, basic SOPs outlined in this manual: diff --git a/projects/dhis2-single-page-docs/es_419/IMPLEMENT__dhis2-implementation-guide-md b/projects/dhis2-single-page-docs/es_419/IMPLEMENT__dhis2-implementation-guide-md index 380d05142..eb25cae8a 100644 --- a/projects/dhis2-single-page-docs/es_419/IMPLEMENT__dhis2-implementation-guide-md +++ b/projects/dhis2-single-page-docs/es_419/IMPLEMENT__dhis2-implementation-guide-md @@ -4174,7 +4174,7 @@ It is up to each user to choose to enable/disable forwarding of these messages a ![](resources/images/dqimp_image3.png) -# Organisation Units { #organisation-units } +# Unidades organizativas { #organisation-units } In DHIS2 the location of the data, the geographical context, is represented as organisational units. Organisational units can be either @@ -6584,7 +6584,7 @@ below. ## User Interface localization { #user-interface-localization } -### Overview { #overview } +### Visión general { #overview } DHIS 2 supports internationalization (i18n) of the user interface through the use of Java property strings and PO files. Java property files are used diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index 537fa465d..03a64b512 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- DHIS core version 2.37 - Gestionar +- DHIS core version 2.37 template: single.html --- @@ -816,7 +816,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md index 9d3937ab9..01d43c974 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- DHIS core version 2.38 - Gestionar +- DHIS core version 2.38 template: single.html --- @@ -830,7 +830,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md index 377547181..328ef7010 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md @@ -834,7 +834,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-240__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-240__system-administration-guide-md index 1711311d1..41e0edd00 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-240__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-240__system-administration-guide-md @@ -834,7 +834,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' @@ -2780,7 +2780,7 @@ When selecting an SMS gateway then, it is important to confirm that the phone ca # Using the User Impersonation Feature in DHIS2 { #user_impersonation } -## Overview { #overview } +## Visión general { #overview } User impersonation, also known as user switching, is a powerful feature provided in DHIS2 for administrative users to log in as another user. This feature is especially useful for troubleshooting or resolving user-related issues, as it @@ -2829,7 +2829,7 @@ Follow these steps to use the user impersonation feature: 6. When you're finished, navigate to the URL to end impersonation (e.g., `/impersonateExit`). Your session will be switched back to your original administrative user. -## Configuration { #configuration } +## Configuración { #configuration } The user impersonation feature configuration options. diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index 332042d65..2accbc6e1 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-06-18' tags: -- DHIS core version master - Gestionar +- DHIS core version master template: single.html --- @@ -883,7 +883,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' @@ -2895,7 +2895,7 @@ When selecting an SMS gateway then, it is important to confirm that the phone ca # Using the User Impersonation Feature in DHIS2 { #user_impersonation } -## Overview { #overview } +## Visión general { #overview } User impersonation, also known as user switching, is a powerful feature provided in DHIS2 for administrative users to log in as another user. This feature is especially useful for troubleshooting or resolving user-related issues, as it @@ -2944,7 +2944,7 @@ Follow these steps to use the user impersonation feature: 6. When you're finished, navigate to the URL to end impersonation (e.g., `/impersonateExit`). Your session will be switched back to your original administrative user. -## Configuration { #configuration } +## Configuración { #configuration } The user impersonation feature configuration options. diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index 7d8deb18b..d23752581 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md @@ -5706,7 +5706,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index 79fa89706..9bfe937a8 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md @@ -6142,7 +6142,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | @@ -7694,7 +7694,7 @@ Table: Category objects in the Maintenance app | Opción de categoría | Create, edit, clone, share, delete, show details and translate | | Categoría | Create, edit, clone, share, delete, show details and translate | | Combinación de categoría | Create, edit, clone, share, delete, show details and translate | -| Category option combination | Edit and show details | +| Combinación de opciones de categoría | Edit and show details | | Category option group | Create, edit, clone, share, delete, show details and translate | | Category option group set | Create, edit, clone, share, delete, show details and translate | @@ -12459,7 +12459,7 @@ Table: Program metadata objects in the Maintenance app | Regla de programa | Allows you to create and control dynamic behaviour of the user interface in the **Tracker Capture** and **Event Capture** apps. | Create, edit, clone, delete, show details and translate | | Program rule variable | Variables you use to create program rule expressions. | Create, edit, clone, delete, show details and translate | | Relationship type | Defines the relationship between tracked entity A and tracked entity B, for example mother and child. | Create, edit, clone, share, delete, show details and translate | -| Tracked entity type | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | +| Tipo de entidad Tracked | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | | Tracked entity attribute | Used to register extra information for a tracked entity.

Can be shared between programs. | Create, edit, clone, share, delete, show details and translate | | Programa | A program consist of program stages. | Create, edit, share, delete, assign to organisation units, show details and translate | | Program stage | A program stage defines which actions should be taken at each stage. | Create, edit, share, change sort order, delete, show details and translate | @@ -18954,7 +18954,7 @@ versioning table: ![](resources/images/settings/metadata_versioning_table.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version in the system. | | Versión | Name of the version. The name is automatically generated by system. | @@ -18968,7 +18968,7 @@ table: ![](resources/images/settings/metadata_versioning_table_failure_case.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version of the central instance.

**Note**

The master version information is the central instance's latest version. This is important to look at the difference between the versions of metadata that exist at central and at local. | | Last sync attempt | If the last sync attempt is a failure, this will be displayed. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md index c521109e5..57cc04f9f 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md @@ -6464,7 +6464,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md index 5696a80c6..ef296cc2c 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md @@ -6896,7 +6896,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | @@ -8448,7 +8448,7 @@ Table: Category objects in the Maintenance app | Opción de categoría | Create, edit, clone, share, delete, show details and translate | | Categoría | Create, edit, clone, share, delete, show details and translate | | Combinación de categoría | Create, edit, clone, share, delete, show details and translate | -| Category option combination | Edit and show details | +| Combinación de opciones de categoría | Edit and show details | | Category option group | Create, edit, clone, share, delete, show details and translate | | Category option group set | Create, edit, clone, share, delete, show details and translate | @@ -13282,7 +13282,7 @@ Table: Program metadata objects in the Maintenance app | Regla de programa | Allows you to create and control dynamic behaviour of the user interface in the **Tracker Capture** and **Event Capture** apps. | Create, edit, clone, delete, show details and translate | | Program rule variable | Variables you use to create program rule expressions. | Create, edit, clone, delete, show details and translate | | Relationship type | Defines the relationship between tracked entity A and tracked entity B, for example mother and child. | Create, edit, clone, share, delete, show details and translate | -| Tracked entity type | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | +| Tipo de entidad Tracked | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | | Tracked entity attribute | Used to register extra information for a tracked entity.

Can be shared between programs. | Create, edit, clone, share, delete, show details and translate | | Programa | A program consist of program stages. | Create, edit, share, delete, assign to organisation units, show details and translate | | Program stage | A program stage defines which actions should be taken at each stage. | Create, edit, share, change sort order, delete, show details and translate | @@ -19904,7 +19904,7 @@ versioning table: ![](resources/images/settings/metadata_versioning_table.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version in the system. | | Versión | Name of the version. The name is automatically generated by system. | @@ -19918,7 +19918,7 @@ table: ![](resources/images/settings/metadata_versioning_table_failure_case.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version of the central instance.

**Note**

The master version information is the central instance's latest version. This is important to look at the difference between the versions of metadata that exist at central and at local. | | Last sync attempt | If the last sync attempt is a failure, this will be displayed. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 7a5d19495..5e342af09 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Uso - DHIS core version 2.39 +- Uso template: single.html --- @@ -6210,7 +6210,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 252ca5efe..bd67c211b 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Uso - DHIS core version 2.39 +- Uso template: single.html --- @@ -6845,7 +6845,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | @@ -8397,7 +8397,7 @@ Table: Category objects in the Maintenance app | Opción de categoría | Create, edit, clone, share, delete, show details and translate | | Categoría | Create, edit, clone, share, delete, show details and translate | | Combinación de categoría | Create, edit, clone, share, delete, show details and translate | -| Category option combination | Edit and show details | +| Combinación de opciones de categoría | Edit and show details | | Category option group | Create, edit, clone, share, delete, show details and translate | | Category option group set | Create, edit, clone, share, delete, show details and translate | @@ -13286,7 +13286,7 @@ Table: Program metadata objects in the Maintenance app | Regla de programa | Allows you to create and control dynamic behaviour of the user interface in the **Tracker Capture** and **Event Capture** apps. | Create, edit, clone, delete, show details and translate | | Program rule variable | Variables you use to create program rule expressions. | Create, edit, clone, delete, show details and translate | | Relationship type | Defines the relationship between tracked entity A and tracked entity B, for example mother and child. | Create, edit, clone, share, delete, show details and translate | -| Tracked entity type | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | +| Tipo de entidad Tracked | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | | Tracked entity attribute | Used to register extra information for a tracked entity.

Can be shared between programs. | Create, edit, clone, share, delete, show details and translate | | Programa | A program consist of program stages. | Create, edit, share, delete, assign to organisation units, show details and translate | | Program stage | A program stage defines which actions should be taken at each stage. | Create, edit, share, change sort order, delete, show details and translate | @@ -20305,7 +20305,7 @@ versioning table: ![](resources/images/settings/metadata_versioning_table.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version in the system. | | Versión | Name of the version. The name is automatically generated by system. | @@ -20319,7 +20319,7 @@ table: ![](resources/images/settings/metadata_versioning_table_failure_case.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version of the central instance.

**Note**

The master version information is the central instance's latest version. This is important to look at the difference between the versions of metadata that exist at central and at local. | | Last sync attempt | If the last sync attempt is a failure, this will be displayed. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md index 0a7e5c8ef..088ef84c9 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md @@ -6251,7 +6251,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md index 244b27447..2c9630b16 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md @@ -6886,7 +6886,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | @@ -8438,7 +8438,7 @@ Table: Category objects in the Maintenance app | Opción de categoría | Create, edit, clone, share, delete, show details and translate | | Categoría | Create, edit, clone, share, delete, show details and translate | | Combinación de categoría | Create, edit, clone, share, delete, show details and translate | -| Category option combination | Edit and show details | +| Combinación de opciones de categoría | Edit and show details | | Category option group | Create, edit, clone, share, delete, show details and translate | | Category option group set | Create, edit, clone, share, delete, show details and translate | @@ -13437,7 +13437,7 @@ Table: Program metadata objects in the Maintenance app | Regla de programa | Allows you to create and control dynamic behaviour of the user interface in the **Tracker Capture** and **Event Capture** apps. | Create, edit, clone, delete, show details and translate | | Program rule variable | Variables you use to create program rule expressions. | Create, edit, clone, delete, show details and translate | | Relationship type | Defines the relationship between tracked entity A and tracked entity B, for example mother and child. | Create, edit, clone, share, delete, show details and translate | -| Tracked entity type | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | +| Tipo de entidad Tracked | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | | Tracked entity attribute | Used to register extra information for a tracked entity.

Can be shared between programs. | Create, edit, clone, share, delete, show details and translate | | Programa | A program consist of program stages. | Create, edit, share, delete, assign to organisation units, show details and translate | | Program stage | A program stage defines which actions should be taken at each stage. | Create, edit, share, change sort order, delete, show details and translate | @@ -20501,7 +20501,7 @@ versioning table: ![](resources/images/settings/metadata_versioning_table.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version in the system. | | Versión | Name of the version. The name is automatically generated by system. | @@ -20515,7 +20515,7 @@ table: ![](resources/images/settings/metadata_versioning_table_failure_case.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version of the central instance.

**Note**

The master version information is the central instance's latest version. This is important to look at the difference between the versions of metadata that exist at central and at local. | | Last sync attempt | If the last sync attempt is a failure, this will be displayed. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md index 00ca9fd03..bdc062b26 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md @@ -6251,7 +6251,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md index c5e8149ba..68e8bea5b 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md @@ -6886,7 +6886,7 @@ Table: Data dimension types |---|---|---| | Indicadores | An indicator is a calculated formula based on data elements. | Coverage of immunization across a specific district. | | Data elements | Represents the phenomenon for which data has been captured. | Number of malaria cases; number of BCG doses given. | -| Data sets | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | +| Sets de datos | A collection of data elements grouped for data collection. You can select :
* **Reporting rates**: the percentage of actual reports compared to the expected number of reports
* **Reporting rates on time**: the reporting rates based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Actual reports**: the actual number of reports
* **Actual reports on time**: the actual number of reports based on timely form submissions. A timely submission must happen within a number of days after the reporting period.
* **Expected reports**: the number of expected reports based on organisation units where the data set and the reporting frequency has been assigned. | Reporting rates for immunization and morbidity forms. | | Event data items | A data element that is part of a program representing events that have been captured. | Average weight and height for children in a nutrition program. | | Indicadores de programa | A calculated formula based on data elements in a program representing events. | Average BMI score for children in a nutrition program. | @@ -8438,7 +8438,7 @@ Table: Category objects in the Maintenance app | Opción de categoría | Create, edit, clone, share, delete, show details and translate | | Categoría | Create, edit, clone, share, delete, show details and translate | | Combinación de categoría | Create, edit, clone, share, delete, show details and translate | -| Category option combination | Edit and show details | +| Combinación de opciones de categoría | Edit and show details | | Category option group | Create, edit, clone, share, delete, show details and translate | | Category option group set | Create, edit, clone, share, delete, show details and translate | @@ -13522,7 +13522,7 @@ Table: Program metadata objects in the Maintenance app | Regla de programa | Allows you to create and control dynamic behaviour of the user interface in the **Tracker Capture** and **Event Capture** apps. | Create, edit, clone, delete, show details and translate | | Program rule variable | Variables you use to create program rule expressions. | Create, edit, clone, delete, show details and translate | | Relationship type | Defines the relationship between tracked entity A and tracked entity B, for example mother and child. | Create, edit, clone, share, delete, show details and translate | -| Tracked entity type | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | +| Tipo de entidad Tracked | Types of entities which can be tracked through the system. Can be anything from persons to commodities, for example a medicine or a person.

A program must have one tracked entity. To enrol a tracked entity instance into a program, the tracked entity of an entity and tracked entity of a program must be the same.

**Note**

A program must be specified with only one tracked entity. Only tracked entity as same as the tracked entity of program can enroll into that program. | Create, edit, clone, share, delete, show details and translate | | Tracked entity attribute | Used to register extra information for a tracked entity.

Can be shared between programs. | Create, edit, clone, share, delete, show details and translate | | Programa | A program consist of program stages. | Create, edit, share, delete, assign to organisation units, show details and translate | | Program stage | A program stage defines which actions should be taken at each stage. | Create, edit, share, change sort order, delete, show details and translate | @@ -20763,7 +20763,7 @@ versioning table: ![](resources/images/settings/metadata_versioning_table.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version in the system. | | Versión | Name of the version. The name is automatically generated by system. | @@ -20777,7 +20777,7 @@ table: ![](resources/images/settings/metadata_versioning_table_failure_case.png) -| Object | Descripción | +| Objeto | Descripción | |---|---| | Master version | The latest version of the central instance.

**Note**

The master version information is the central instance's latest version. This is important to look at the difference between the versions of metadata that exist at central and at local. | | Last sync attempt | If the last sync attempt is a failure, this will be displayed. | diff --git a/projects/dhis2-single-page-docs/es_419/USE__dhis2-android-app-md b/projects/dhis2-single-page-docs/es_419/USE__dhis2-android-app-md index 354274c9a..83e36f38b 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__dhis2-android-app-md +++ b/projects/dhis2-single-page-docs/es_419/USE__dhis2-android-app-md @@ -3219,7 +3219,7 @@ Program on which the customized DHIS2-RTS is based on. | Elemento de datos | Name:
- "Deliver to": Text / Option set = "Deliver to"
- "Previous stock balance": Positive integer
- "Stock correction": Positive or Zero integer (**New 1.1**)
- "Stock count": Positive integer
- "Stock discard": Positive integer
- "Stock distribution": Positive integer
- "Stock on hand": Positive or Zero integer (**New 1.1**)
- "Stock received": Positive integer
Domain type: Tracker
Value type: see above | | Option set | Name: "Deliver to"
Value type: Text | | Tracked entity attribute | Name:
- "Item barcode"
- "Item code"
- "Item description"
"Value type": Text
"Aggregation type": None | -| Tracked entity type | Name: Item
"Feature type": None | +| Tipo de entidad Tracked | Name: Item
"Feature type": None | | Programa | Type: Tracker
Tracked entity type: Item
Program tracked entity attributes:
- Item barcode
- Item code
- Item description
Program stages:
Name: "Stock on Hand"
Scheduled days from start: 0
Repeatable | | Regla de programa | *Name*: "Assign Stock correction"
Condition: "d2:hasValue( #{Stock count} )”
Action: "Assign value"
*Name*: "Assign Stock on Hand"
Condition: "true"
Action: "Assign value"
*Name*: "Assign previous stock balance"
Condition: "d2:hasValue( #{Initial stock on hand - Previous event} )"
Action: "Assign value" | diff --git a/projects/dhis2-single-page-docs/fr/.cache_timestamp b/projects/dhis2-single-page-docs/fr/.cache_timestamp index 708edfdd3..90012c08f 100644 --- a/projects/dhis2-single-page-docs/fr/.cache_timestamp +++ b/projects/dhis2-single-page-docs/fr/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:16Z \ No newline at end of file +2024-07-17T21:25:21Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index c6b1d0e91..badf8436f 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- Développement - DHIS Version 2.40 +- Développement template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index ad7c5b1f4..3b2d05247 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- Version Master de DHIS2 Central - Développement +- Version Master de DHIS2 Central template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index d0db059ff..edaf5a6d2 100644 --- a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- DHIS core version 2.37 - Gestion +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md index 61d1b940a..a3b1cbb4b 100644 --- a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- Version principale de DHIS 2.38 - Gestion +- Version principale de DHIS 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index bab264336..fa93fd89f 100644 --- a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-06-18' tags: -- Version Master de DHIS2 Central - Gestion +- Version Master de DHIS2 Central template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index debe3a574..2b29e4c86 100644 --- a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Utilisation - DHIS version 2.39 +- Utilisation template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index de46f236e..44540bd29 100644 --- a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Utilisation - DHIS version 2.39 +- Utilisation template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/.cache_timestamp b/projects/dhis2-single-page-docs/id_ID/.cache_timestamp index 71f83f07c..cf4fbf566 100644 --- a/projects/dhis2-single-page-docs/id_ID/.cache_timestamp +++ b/projects/dhis2-single-page-docs/id_ID/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:25Z \ No newline at end of file +2024-07-17T21:25:31Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 6d4b84ec7..b923bc9af 100644 --- a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- pengembang - DHIS core version 2.40 +- pengembang template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index beb28c3a0..444e44ff7 100644 --- a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- DHIS core version master - pengembang +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index cd0f951fd..473e2b48a 100644 --- a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- DHIS core version 2.37 - mengatur +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md index b4dc9d1e3..e09e02b95 100644 --- a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- DHIS core version 2.38 - mengatur +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index ab8da6b9c..0d9a7551c 100644 --- a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-06-18' tags: -- DHIS core version master - mengatur +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 8b6ec6264..edfe9af0f 100644 --- a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- gunakan/pakai/masukkan - DHIS core version 2.39 +- gunakan/pakai/masukkan template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 88cac7e5c..d450f5529 100644 --- a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- gunakan/pakai/masukkan - DHIS core version 2.39 +- gunakan/pakai/masukkan template: single.html --- diff --git a/projects/dhis2-single-page-docs/ko/.cache_timestamp b/projects/dhis2-single-page-docs/ko/.cache_timestamp index e71b0642e..4e3e112b5 100644 --- a/projects/dhis2-single-page-docs/ko/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ko/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:33Z \ No newline at end of file +2024-07-17T21:25:38Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp b/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp index e71b0642e..4e3e112b5 100644 --- a/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:33Z \ No newline at end of file +2024-07-17T21:25:38Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 2bce8ec27..623efc40a 100644 --- a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- 사용 - DHIS core version 2.39 +- 사용 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 291e42a29..dbe972bb1 100644 --- a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- 사용 - DHIS core version 2.39 +- 사용 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/.cache_timestamp b/projects/dhis2-single-page-docs/pt/.cache_timestamp index 08a5b361f..f4437035c 100644 --- a/projects/dhis2-single-page-docs/pt/.cache_timestamp +++ b/projects/dhis2-single-page-docs/pt/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:39Z \ No newline at end of file +2024-07-17T21:25:43Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 66b2d6d6d..af13ff968 100644 --- a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- Desenvolver - DHIS core version 2.40 +- Desenvolver template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 362900d53..09a40de8f 100644 --- a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- DHIS core version master - Desenvolver +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index 1bbb4d944..50293e95f 100644 --- a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- DHIS core version 2.37 - Gerir +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md index dc91c3316..d7b6aeb43 100644 --- a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- DHIS core version 2.38 - Gerir +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index a25d80c9b..06f348d93 100644 --- a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-06-18' tags: -- DHIS core version master - Gerir +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index b9550546c..1baed5955 100644 --- a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Usar - DHIS core version 2.39 +- Usar template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 1a578abe4..ee0387977 100644 --- a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Usar - DHIS core version 2.39 +- Usar template: single.html --- diff --git a/projects/dhis2-single-page-docs/ru/.cache_timestamp b/projects/dhis2-single-page-docs/ru/.cache_timestamp index 4384485c9..37055512d 100644 --- a/projects/dhis2-single-page-docs/ru/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ru/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:46Z \ No newline at end of file +2024-07-17T21:25:48Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 3e249ffb8..87d9a2d62 100644 --- a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Использовать - DHIS core version 2.39 +- Использовать template: single.html --- diff --git a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 7b178b913..c5f786705 100644 --- a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- Использовать - DHIS core version 2.39 +- Использовать template: single.html --- diff --git a/projects/dhis2-single-page-docs/si/.cache_timestamp b/projects/dhis2-single-page-docs/si/.cache_timestamp index 1233ff531..90bf47a45 100644 --- a/projects/dhis2-single-page-docs/si/.cache_timestamp +++ b/projects/dhis2-single-page-docs/si/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:58Z \ No newline at end of file +2024-07-17T21:25:53Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp b/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp index 1233ff531..90bf47a45 100644 --- a/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:23:58Z \ No newline at end of file +2024-07-17T21:25:53Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 6f1fe662a..a0b307708 100644 --- a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- بنایا - DHIS core version 2.40 +- بنایا template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 27932f0c9..c6dcae26f 100644 --- a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- DHIS core version master - بنایا +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index cd13617cf..7c0b8dfe3 100644 --- a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- DHIS core version 2.37 - انتظام +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md index 542b943df..6dcc81472 100644 --- a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-238__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- DHIS core version 2.38 - انتظام +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index d7cf075f4..dbc44fec6 100644 --- a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-06-18' tags: -- DHIS core version master - انتظام +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 3abd2ba0c..e817ddc1a 100644 --- a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- استعمال کریں - DHIS core version 2.39 +- استعمال کریں template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 087c896a5..862a65fae 100644 --- a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- استعمال کریں - DHIS core version 2.39 +- استعمال کریں template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/.cache_timestamp b/projects/dhis2-single-page-docs/zh/.cache_timestamp index ad76281f1..b3ad3a0cf 100644 --- a/projects/dhis2-single-page-docs/zh/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:24:06Z \ No newline at end of file +2024-07-17T21:25:58Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index b44de2dc4..1b27d2b5d 100644 --- a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- Develop - DHIS core version 2.40 +- Develop template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index f638a6f37..10be434ee 100644 --- a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- DHIS核心 主版 - Develop +- DHIS核心 主版 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index 10f6beed7..cc588e0d6 100644 --- a/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-06-18' tags: -- DHIS核心 主版 - Manage +- DHIS核心 主版 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 3f083c0db..6a368aa79 100644 --- a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- 使用 - DHIS core version 2.39 +- 使用 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 1a214bc6c..2628dde1e 100644 --- a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-15' tags: -- 使用 - DHIS core version 2.39 +- 使用 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp b/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp index 246c5f4ef..f1ba1fe20 100644 --- a/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:24:14Z \ No newline at end of file +2024-07-17T21:26:07Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 4f48a2221..d9a701776 100644 --- a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-02' tags: -- Develop - DHIS core version 2.40 +- Develop template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index dd861f2cf..0792785a0 100644 --- a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-07-12' tags: -- DHIS core version master - Develop +- DHIS core version master template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp b/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp index 83f2053a7..1cac955fb 100644 --- a/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:24:18Z \ No newline at end of file +2024-07-17T21:26:12Z \ No newline at end of file diff --git a/projects/docs-full-site/ar/.cache_timestamp b/projects/docs-full-site/ar/.cache_timestamp index 71326079b..bf575adc1 100644 --- a/projects/docs-full-site/ar/.cache_timestamp +++ b/projects/docs-full-site/ar/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:19:45Z \ No newline at end of file +2024-07-17T21:19:49Z \ No newline at end of file diff --git a/projects/docs-full-site/cs/.cache_timestamp b/projects/docs-full-site/cs/.cache_timestamp index 3cfd20f7f..da79ce9e9 100644 --- a/projects/docs-full-site/cs/.cache_timestamp +++ b/projects/docs-full-site/cs/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:19:48Z \ No newline at end of file +2024-07-17T21:19:51Z \ No newline at end of file diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md index d541a2aaf..4b19a5904 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Analytika { #analytics } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md index 6d584ac10..fde4c28fc 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Aplikace { #apps } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md index 6b7340fd4..750202daf 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/audit.md" revision_date: '2021-06-14' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md index df98c83fd..15c45ae13 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Schválení dat { #data-approval } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md index 907a76c1b..d46ac8146 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data.md" revision_date: '2022-04-04' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Data { #data } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md index 9cdb23c38..2f72f0854 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-store.md" revision_date: '2022-03-24' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Data store { #data-store } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md index c721c6bd9..96d0b22da 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-validation.md" revision_date: '2022-02-23' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Ověření dat { #data-validation } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md index 30423781e..2affff31a 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # E-mail { #email } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md index 6bbbde9de..c2f0e2a3a 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/i18n.md" revision_date: '2022-04-27' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # I18n { #i18n } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md index 86a4bb71d..4aea8381f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/overview.md" revision_date: '2022-02-28' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Přehled { #webapi } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md index 838e6e56e..1dfca2c9c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/maintenance.md" revision_date: '2021-06-14' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Údržba { #maintenance } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md index 18d659b22..f6d15e2a7 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Zprávy { #messaging } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md index 2f7cf11e3..15cd049d3 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/metadata-gist.md" revision_date: '2021-11-23' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md index a9f7d958f..d4ad339cb 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/metadata.md" revision_date: '2023-08-03' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Metadata { #metadata } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md index dc2671e37..6531dc568 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/new-tracker.md" revision_date: '2024-05-21' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Nový Tracker { #new-tracker } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md index a2595b7b5..b2a984410 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Profil organizační jednotky { #org_unit_profile } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md index e4c456966..0d9fa5a85 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/scheduling.md" revision_date: '2022-05-05' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Plánování { #webapi_scheduling } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md index 0c6df7653..993769a21 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/settings-and-configuration.md" revision_date: '2023-12-14' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Nastavení a konfigurace { #settings-and-configuration } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md index dfdd820ba..f5765e410 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Sdílení { #sharing } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md index e1b15ad37..9b9e2b8ea 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # SMS { #sms } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md index bbceba1b9..843d6c4c3 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Synchronizace { #webapi_synchronization } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md index 500da49b8..57fdc78da 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/tracker.md" revision_date: '2024-01-05' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Trasovač { #tracker } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md index d70bcac64..efb81c298 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/users.md" revision_date: '2021-11-04' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Uživatelé { #users } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md index 03a669f82..509ce5c25 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/visualizations.md" revision_date: '2022-03-24' tags: -- Vývoj - DHIS core version 2.38 +- Vývoj --- # Vizualizace { #visualizations } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md index b0d2c624a..fc951d81a 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-validation.md" revision_date: '2023-04-14' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Ověření dat { #data-validation } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md index 76395c315..1cd577cf9 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # E-mail { #email } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md index 333e8d9b5..27677ec19 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Přehled { #webapi } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md index b9727597b..7d91ea0c7 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Sdílení { #sharing } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index a30980a43..5e24a923b 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" -revision_date: '2024-05-23' +revision_date: '2024-07-02' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Trasovač { #tracker } @@ -2144,7 +2144,11 @@ This, along with the Program's [Access Level](#webapi_nti_access_level) configur A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured with access level *OPEN* or *AUDITED* , the Owner OrganisationUnit has to be in the user's search scope. For Programs that are configured with access level *PROTECTED* or *CLOSED* , the Owner OrganisationUnit has to be in the user's capture scope to be able to access the corresponding program data for the specific tracked entity. -#### Přepsání vlastnictví trasovače: Rozbijte sklo { #webapi_nti_tracker_ownership_override } +When requesting tracked entities without specifying a program, the response will include only tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and one of the following criteria: +- The tracked entity is enrolled in at least one program the user has data access to, and the user has access to the owner organisation unit. +- The tracked entity is not enrolled in any program the user has data access to, but the user has access to the tracked entity registering organisation unit. + +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md index b8a6a9109..96344d6f8 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/users.md" revision_date: '2022-09-13' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Uživatelé { #users } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md index f96660ffd..37b355e06 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Vizualizace { #visualizations } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md index e7a4cbb64..f0144ad62 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Vývoj - DHIS core version 2.41 +- Vývoj --- # Aplikace { #apps } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md index 62fb989c5..2f8aa746c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Vývoj - DHIS core version 2.41 +- Vývoj --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md index 806a6f713..259486ada 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Vývoj - DHIS core version 2.41 +- Vývoj --- # Schválení dat { #data-approval } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md index 8cbf10e1f..6139b0841 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Vývoj - DHIS core version 2.41 +- Vývoj --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md index 4dffd11d4..11f115512 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker-old.md" revision_date: '2024-05-23' tags: -- Vývoj - DHIS core version 2.41 +- Vývoj --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index aba4ee369..3cd433398 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index 5d6a6b919..104d25c52 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index f085d47ab..2381f5025 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index 12ff31f1b..8de6b1117 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index a21267df0..f70bb3086 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- # O této příručce { #about_this_guide_ } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index a0fbfb7ad..3e91df2ea 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index 4e69b4ae0..25fac8452 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index 7ec54d8e1..6652ed136 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index 686e59e75..21c5cb370 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md index 037bc269f..484bcfb91 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/map-view.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Použití +- App version 1.4.0 --- Zobrazení mapy diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index 85a264995..cb1dc177e 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- App version 1.0.3 - Použití +- App version 1.0.3 --- # Uživatelská příručka k aplikaci pro analýzu imunizace DHIS2 { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md index 836fc1224..18896bcea 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/about-this-guide.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # About this guide { #about-this-guide } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md index e5c22c3b3..3666f2aba 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-and-translating-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Accessing and translating the Scorecard { #accessing-and-translating-the-scorecard } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md index d92c58ab1..51cb190e7 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-scorecard-app.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Login DHIS2 system { #login-dhis2-system } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md index 77485a627..29aa352cd 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/creating-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- ## Creating the Scorecard { #creating-the-scorecard } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md index 2869c25a6..9da64f611 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/introduction-to-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Introduction to the Scorecard App { #introduction-to-the-scorecard-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md index fe88fb351..b5f559243 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/saving-configurations.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- ## Saving configuration and load the scorecard { #saving-configuration-and-load-the-scorecard } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md index d16145581..e95d4f49c 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/scorecard-app-architecture.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Scorecard App architecture { #scorecard-app-architecture } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md index 30d8fe956..843c68b21 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/support-and-maintanace-options.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Scorecard App Built-in Support and Maintenance Options { #scorecard-app-built-in-support-and-maintenance-options } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md index 3d063e474..a7f26994c 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/viewing-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Viewing the Scorecard App Analysis outputs { #viewing-the-scorecard-app-analysis-outputs } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md index 5e1f8d881..7ce9e8536 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-maintenance.md" revision_date: '2024-02-27' tags: -- Použití - App version 2.0 +- Použití --- If a Standalone action tracker application is taking too long to load, and you’re not on a slow network, make sure you have cleared your browser cache. diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md index d22d196f0..078f5a7bc 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-architecture-and-installation.md" revision_date: '2024-02-22' tags: -- Použití - App version 2.0 +- Použití --- The Standalone Action Tracker Application is built on an architecture that eases user interactions by having a design concept that promotes the user to follow their intuition complemented with high performance that considers the lowest internet connection scenarios with descriptive notification messages if the user misses a step along the way. diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md index 11dd74159..1731bdbcf 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-browsing.md" revision_date: '2024-02-23' tags: -- Použití - App version 2.0 +- Použití --- The Standalone Action Tracker App can be found in the Apps menu. if the application has not yet been installed in your DHIS2 instance or the installation has issues, refer to the installation instructions (Section 3.5) of this documentation for further guidance, or contact the DHIS2 administrator for your instance. diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md index 7d80c9e4f..938b9caa1 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-introduction.md" revision_date: '2024-02-22' tags: -- Použití - App version 2.0 +- Použití --- # Introduction to the Standalone Action Tracker App { #introduction-to-the-standalone-action-tracker-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md index ea03ce2ac..6d3c21a75 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-configuration.md" revision_date: '2024-02-27' tags: -- Použití - App version 2.0 +- Použití --- The Standalone Action Tracker App includes a module for administrators to configure key metadata for the normal user. The administration configurable options include:- diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 154d90e52..ea119db75 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 0ee7e2b6d..da3af1042 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2024-06-07' tags: -- Použití - DHIS core version 2.38 +- Použití --- # DHIS2 Často kladené otázky { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index 5bffab587..c7e27d112 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 57a39d4ad..9294c6ef5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 3b7368a0b..c3981e4dc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Poznámky k vydání a upgradu { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index 1089654d0..31792ce18 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index 30911115f..7df7ad151 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index f78e40711..36bce72bb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Hlášení o události { #event_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index 105de9c8a..d3fc5c5dd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Vizualizér událostí { #event_visualizer_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index 9e5369841..0089148a2 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index ec7d52d92..a9bb8dea7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-maps-app.md" revision_date: '2022-03-23' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index fa7dcc8df..c39e379f8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Funkce hlášení v aplikaci pro přehledy { #using_the_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md index 2dcfdecfd..e2b99d59a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index 4fdac4057..ee8f9b2a7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index 838e653c3..ada780f02 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Zadávání dat { #data_entry_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index 4b0813231..84f95e063 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 829ba9312..d9a36cc42 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Použití - DHIS core version 2.38 +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index b7e0c6c4b..6490d99c5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-the-gis-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nakonfigurujte aplikaci Mapy { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index bdf038ae7..4a3b3ef77 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata.md" revision_date: '2022-10-02' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index c4006dd7c..357227467 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Konfigurace programů v aplikaci Údržba { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index 3a8318e3e..1c22749b6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index 9011a5d96..7686b95cb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/system-settings.md" revision_date: '2022-04-27' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index b56310061..0ab9fe85c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index a614019f2..c93c45995 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-03-10' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Spravujte uživatele, uživatelské role a skupiny uživatelů { #manage_user_role_group } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index 51e5ff351..19c75aab7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/importexport-app.md" revision_date: '2022-02-23' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index 47a1ef0c9..72ecfe81f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index ec9af8cea..4d9d1b57d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index 2fd038a87..9be310723 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index 388b35354..ff63fd278 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Správce datového úložiště { #datastore_manager_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index 036a604d9..9d7cfdbe3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Použití - DHIS core version 2.38 +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index 60a00c323..57f989558 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index 6e7d5a822..2ecd315f8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index a46a77be9..0512550cc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 23c260976..b6f244370 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 6b4d54ccf..cab40e951 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index a7e9f0b9a..e87220bb9 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index b2ee5160b..220a7e8ba 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Použití - DHIS core version 2.38 +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 0cca32a67..7a63a7684 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 61ba9a03c..57bee9f08 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Vztahový model { #relationship_model } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 43973577f..81f58feee 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index e4f6541f6..e4ac69e05 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index d84044fe8..1033b6881 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nastavte předvolby uživatelského účtu { #user_account_preferences } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 9459244ed..9b2e64894 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 4d14caabc..761f490d0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # DHIS2 Často kladené otázky { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index 3f7e0a3e3..f02cba5a6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index ae68e65b2..184234e5d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index efecd4ae5..874b8f494 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index d29d309ae..e4c80853e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index 80a9e679a..e4df62b8a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Hlášení o události { #event_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index bbb6bb7d8..86817b23b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Vizualizér událostí { #event_visualizer_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index 294abd92c..44cfb0324 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index fca4f5107..43a2bcfd5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index a0770e718..03c0c5d40 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Funkce hlášení v aplikaci pro přehledy { #using_the_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index de953cb13..e1f9a4687 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index 42749fe9a..b8f273134 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index ec2ed23e3..eeaafcd81 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index d5a576387..3567bd0eb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" revision_date: '2024-07-12' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Zadávání dat { #data_entry_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index b1f867cb5..3658b1c03 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index e396c0bda..4ab37e7ba 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index 72348ee52..d683bf1fd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index 999f5ce64..6abb2aca3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index 1eb3595f0..483a12df6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-07-12' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Konfigurace programů v aplikaci Údržba { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index b66b263f3..99662a899 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index 5d802bb18..7cab6e326 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index efaead558..0393d6709 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index be469c5f3..1964102d8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Spravujte uživatele, uživatelské role a skupiny uživatelů { #manage_user_role_group } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index 1e6c4ef98..f7eda30be 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Výměna dat { #data_exchange } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index f88a62d89..c33442d91 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index 693f51fd0..015b40b65 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index ae9e47552..8faadb0a0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index 3140391c4..437e5fc52 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 2fe1257b4..ebb9aafe8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Správce datového úložiště { #datastore_manager_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index e55a5069d..acaf400d4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index 60ef71256..7540172dc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index 0c16d34f5..702daf2c7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index c3a262aab..e7f38e7f0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index aaf3571a1..2765387cc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 569ad76c6..72a0adb27 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index b8fceb080..b9ba4601b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 376279a12..8e89fb704 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 3b2f71281..bdf6831cc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 5bf6c8993..e9ddedb57 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 77d479911..abd8c12bd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 918e22036..a926c1d75 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index c8c79bce1..6ecdd5c28 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # DHIS2 Často kladené otázky { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 3d792c6de..43f1de65a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 49aac097e..22809706f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index c712d94dc..0b93363a3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Poznámky k vydání a upgradu { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 2a155eb8c..6c6712ad8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 468799fe3..11844e121 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index 070eea840..feb9528d1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Hlášení o události { #event_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 409488539..569dffd51 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Vizualizér událostí { #event_visualizer_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index 0ceab01df..c856f19a5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 73181c298..be5e00fe5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index e5f72e43a..cd469d2f4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Funkce hlášení v aplikaci pro přehledy { #using_the_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index c68b6c223..5a6dab5ca 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index 01311194b..f72c7129f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index eb7745ce3..efd8c2166 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index e28bb9405..8e8bb4118 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Zadávání dat { #data_entry_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index c9e54f040..1d1573b84 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 3eddcc2ac..164b836e3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Použití - DHIS core version 2.41 +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 9093dbab7..f3dc2211b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index 3709512b1..524ad04e1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 48251d3bf..7b83f6d0f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Konfigurace programů v aplikaci Údržba { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 8d0093878..c6671d6de 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index e5747e8ef..68c7718f6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 8e6e04943..401d1292a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index edf8ec7dd..a0188d9ef 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Spravujte uživatele, uživatelské role a skupiny uživatelů { #manage_user_role_group } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index 8acedcc1e..fceb679ad 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Výměna dat { #data_exchange } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 8d841fde5..36b2f04ec 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index b8f993362..23aeeab28 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index c56756b54..ebbe4532c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 1eee26179..39074dce4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 2ee4d924b..43dd9affb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Správce datového úložiště { #datastore_manager_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 1f6057e82..1509c636e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Použití - DHIS core version 2.41 +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 8cb6374b3..71a26030a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index 0969c376d..33aacfe13 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 0e5690148..6df6851c3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index ddb5e6c39..498ed7dd3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 34e58a03f..b92c1da36 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 1b75a884d..5d2f00b41 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 64dbbf8a6..87a6e1a4e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Použití - DHIS core version 2.41 +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 5edd4117b..02eb3fcc8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index b549b70ca..419e15fa1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Vztahový model { #relationship_model } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index c60691232..f0d59c5c6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index df481a720..9cef82508 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 7f0623e48..74a3c476d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Nastavte předvolby uživatelského účtu { #user_account_preferences } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index edf288d38..52a822485 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 71e83e543..fcab6866b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2024-06-07' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # DHIS2 Často kladené otázky { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index 6ce71742d..1b9f6853d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 6a80a62ca..1f7559455 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index 19b375c55..152cfcaf0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index 723eb73d6..4909dd156 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index 9c2e5e2ac..f751a5e74 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Hlášení o události { #event_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index 683f59975..90f3e11d0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Vizualizér událostí { #event_visualizer_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index 920acf5c2..0b4728cf4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 7042d04aa..cd0d9ea3e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index d69d383d8..0c912f9f8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Funkce hlášení v aplikaci pro přehledy { #using_the_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index 544bae39b..cf2dc1dae 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index da136f9a5..4db844049 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index 059d58982..d28cdd6eb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index 995f4ca61..b38ae3e1c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-data-entry-app.md" revision_date: '2024-06-18' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Zadávání dat { #data_entry_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index b0378c825..6098c3698 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index a04b4ea1a..c27350a7f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 2964e5897..86e4aa565 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index becce7714..bbcdd326a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index 77551eb25..55aeb5f67 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-06-18' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Konfigurace programů v aplikaci Údržba { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index 61740a247..1627731ee 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index d13ee02b0..6d7fed935 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index 813135fe4..f21a7e5e8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 6ddee3839..75bd6389e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Spravujte uživatele, uživatelské role a skupiny uživatelů { #manage_user_role_group } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 69d79e9df..42376b0a4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Výměna dat { #data_exchange } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index a74d2d372..e50bafe69 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index bbf0873a8..7c59f30fe 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index 1baa7d93b..e3b6a9362 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index 5ec5f7f44..2bf6e8cc8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md index b1c5bf440..eeb5b3861 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Správce datového úložiště { #datastore_manager_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index 2839df5e7..240f1262c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index a66e9e375..92dd071d4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 5376d2bea..3b82f8ecb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index d8a86a331..14d7662cd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 24a554dc6..02d344033 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 5ffa08119..56eb2d23f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index b58e4ec07..68785c60c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 0556c3d21..e6636295d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index ae5867e5a..1f1d48d8e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index d6fbc83cf..6093c03a2 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 83c953641..4676f6d8e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/es_419/.cache_timestamp b/projects/docs-full-site/es_419/.cache_timestamp index b2db4f621..0e02e3d18 100644 --- a/projects/docs-full-site/es_419/.cache_timestamp +++ b/projects/docs-full-site/es_419/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:20:34Z \ No newline at end of file +2024-07-17T21:20:43Z \ No newline at end of file diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md index cf7dc2ccd..5fbb99e80 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md @@ -2235,7 +2235,7 @@ supported: - Data element groups - - Category options + - Opciones de categoría - Category option groups diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md index 354cfd744..aea0a6ff7 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md @@ -18995,7 +18995,7 @@ A predictor always has a generator expression that describes how the predicted v The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | --- | --- | --- | | #{\} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{\.\ | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md new file mode 100644 index 000000000..f660bd233 --- /dev/null +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md @@ -0,0 +1,3909 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.36/src/developer/web-api/metadata.md" +revision_date: "2022-01-17" +tags: + - Desarrollar + - DHIS core version 2.36 +--- + +# Metadata { #metadata } + +## Identifier schemes { #webapi_identifier_schemes } + +This section provides an explanation of the identifier scheme concept. Identifier schemes are used to map metadata objects to other metadata during import, and to render metadata as part of exports. Please note that not all schemes work for all API calls, and not all schemes can be used for both input and output. This is outlined in the sections explaining the various Web APIs. + +The full set of identifier scheme object types available are listed below, using the name of the property to use in queries: + +- idScheme + +- dataElementIdScheme + +- categoryOptionComboIdScheme + +- orgUnitIdScheme + +- programIdScheme + +- programStageIdScheme + +- trackedEntityIdScheme + +- trackedEntityAttributeIdScheme + +The general idScheme applies to all types of objects. It can be overridden by specific object types. + +The default scheme for all parameters is UID (stable DHIS2 identifiers). The supported identifier schemes are described in the table below. + + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
Scheme Values
SchemeDescription
ID, UIDMatch on DHIS2 stable Identifier, this is the default id scheme.
CODEMatch on DHIS2 Code, mainly used to exchange data with an external system.
NAMEMatch on DHIS2 Name, please note that this uses what is available as object.name, and not the translated name. Also note that names are not always unique, and in that case, they can not be used.
ATTRIBUTE:IDMatch on metadata attribute, this attribute needs to be assigned to the type you are matching on, and also that the unique property is set to true. The main usage of this is also to exchange data with external systems, it has some advantages over CODE since multiple attributes can be added, so it can be used to synchronize with more than one system.
+ +Note that identifier schemes is not an independent feature but needs to be used in combination with resources such as data value import and metadata import. + +As an example, to specify CODE as the general id scheme and override with UID for organisation unit id scheme you can use these query parameters: + + ?idScheme=CODE&orgUnitIdScheme=UID + +As another example, to specify an attribute for the organisation unit id scheme, code for the data element id scheme and use the default UID id scheme for all other objects you can use these parameters: + + ?orgUnitIdScheme=ATTRIBUTE:j38fk2dKFsG&dataElementIdScheme=CODE + +## Browsing the Web API { #webapi_browsing_the_web_api } + +The entry point for browsing the Web API is `/api`. This resource provides links to all available resources. Four resource representation formats are consistently available for all resources: HTML, XML, JSON, and JSONP. Some resources will have other formats available, like MS Excel, PDF, CSV, and PNG. To explore the API from a web browser, navigate to the `/api` entry point and follow the links to your desired resource, for instance `/api/dataElements`. For all resources which return a list of elements certain query parameters can be used to modify the response: + + + ++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Query parameters
ParamOption valuesDefault optionDescription
pagingtrue | falsetrueIndicates whether to return lists of elements in pages.
pagenumber1Defines which page number to return.
pageSizenumber50Defines the number of elements to return for each page.
orderproperty:asc/iasc/desc/idescOrder the output using a specified order, only properties that are both persisted and simple (no collections, idObjects etc) are supported. iasc and idesc are case insensitive sorting.
+ +An example of how these parameters can be used to get a full list of data element groups in XML response format is: + + /api/dataElementGroups.xml?links=false&paging=false + +You can query for elements on the name property instead of returning a full list of elements using the _query_ query variable. In this example we query for all data elements with the word "anaemia" in the name: + + /api/dataElements?query=anaemia + +You can get specific pages and page sizes of objects like this: + + /api/dataElements.json?page=2&pageSize=20 + +You can completely disable paging like this: + + /api/indicatorGroups.json?paging=false + +To order the result based on a specific property: + + /api/indicators.json?order=shortName:desc + +You can find an object based on its ID across all object types through the _identifiableObjects_ resource: + + /api/identifiableObjects/ + +### Translation { #webapi_translation } + +DHIS2 supports translations of database content, such as data elements, indicators, and programs. All metadata objects in the Web API have properties meant to be used for display / UI purposes, which include _displayName_, _displayShortName_ and _displayDescription_. + + + +++++ + + + + + + + + + + + + + + + + + + + +
Translate options
ParameterValuesDescription
translatetrue | falseTranslate display* properties in metadata output (displayName, displayShortName, displayDescription, and displayFormName for data elements). Default value is true.
localeLocale to useTranslate metadata output using a specified locale (requires translate=true).
+ +### Translation API { #webapi_translation_api } + +The translations for an object is rendered as part of the object itself in the _translations_ array. Note that the _translations_ array in the JSON/XML payloads is normally pre-filtered for you, which means they can not directly be used to import/export translations (as that would normally overwrite locales other than current users). + +Example of data element with translation array filtered on user locale: + +```json +{ + "id": "FTRrcoaog83", + "displayName": "Accute French", + "translations": [ + { + "property": "SHORT_NAME", + "locale": "fr", + "value": "Accute French" + }, + { + "property": "NAME", + "locale": "fr", + "value": "Accute French" + } + ] +} +``` + +Example of data element with translations turned off: + +```json +{ + "id": "FTRrcoaog83", + "displayName": "Accute Flaccid Paralysis (Deaths < 5 yrs)", + "translations": [ + { + "property": "FORM_NAME", + "locale": "en_FK", + "value": "aa" + }, + { + "property": "SHORT_NAME", + "locale": "en_GB", + "value": "Accute Flaccid Paral" + }, + { + "property": "SHORT_NAME", + "locale": "fr", + "value": "Accute French" + }, + { + "property": "NAME", + "locale": "fr", + "value": "Accute French" + }, + { + "property": "NAME", + "locale": "en_FK", + "value": "aa" + }, + { + "property": "DESCRIPTION", + "locale": "en_FK", + "value": "aa" + } + ] +} +``` + +Note that even if you get the unfiltered result, and are using the appropriate type endpoint i..e `/api/dataElements` we do not allow updates, as it would be too easy to make mistakes and overwrite the other available locales. + +To read and update translations you can use the special translations endpoint for each object resource. These can be accessed by _GET_ or _PUT_ on the appropriate `/api///translations` endpoint. + +As an example, for a data element with identifier `FTRrcoaog83`, you could use `/api/dataElements/FTRrcoaog83/translations` to get and update translations. The fields available are `property` with options _NAME_, _SHORT_NAME_, _DESCRIPTION_, `locale` which supports any valid locale ID and the translated property `value`. + +Example of NAME property for French locale: + +```json +{ + "property": "NAME", + "locale": "fr", + "value": "Paralysie Flasque Aiguë (Décès <5 ans)" +} +``` + +This payload would then be added to a translation array, and sent back to the appropriate endpoint: + +```json +{ + "translations": [ + { + "property": "NAME", + "locale": "fr", + "value": "Paralysie Flasque Aiguë (Décès <5 ans)" + } + ] +} +``` + +For a data element with ID _FTRrcoaog83_ you can _PUT_ this to `/api/dataElements/FTRrcoaog83/translations`. Make sure to send all translations for the specific object and not just for a single locale (if not you will potentially overwrite existing locales for other locales). + +### Web API versions { #webapi_api_versions } + +The Web API is versioned starting from DHIS 2.25. The API versioning follows the DHIS2 major version numbering. As an example, the API version for DHIS 2.33 is `33`. + +You can access a specific API version by including the version number after the `/api` component, as an example like this: + + /api/33/dataElements + +If you omit the version part of the URL, the system will use the current API version. As an example, for DHIS 2.25, when omitting the API part, the system will use API version 25. When developing API clients it is recommended to use explicit API versions (rather than omitting the API version), as this will protect the client from unforeseen API changes. + +The last three API versions will be supported. As an example, DHIS version 2.27 will support API version 27, 26 and 25. + +Note that the metadata model is not versioned and that you might experience changes e.g. in associations between objects. These changes will be documented in the DHIS2 major version release notes. + +## Metadata object filter { #webapi_metadata_object_filter } + +To filter the metadata there are several filter operations that can be applied to the returned list of metadata. The format of the filter itself is straight-forward and follows the pattern _property:operator:value_, where _property_ is the property on the metadata you want to filter on, _operator_ is the comparison operator you want to perform and _value_ is the value to check against (not all operators require value). Please see the _schema_ section to discover which properties are available. Recursive filtering, ie. filtering on associated objects or collection of objects, is supported as well. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Available Operators
OperatorTypesValue requiredDescription
eqstring | boolean | integer | float | enum | collection (checks for size) | datetrueEquality
!eqstring | boolean | integer | float | enum | collection (checks for size) | datetrueInequality
nestring | boolean | integer | float | enum | collection (checks for size) | datetrueInequality
likestringtrueCase sensitive string, match anywhere
!likestringtrueCase sensitive string, not match anywhere
\$likestringtrueCase sensitive string, match start
!\$likestringtrueCase sensitive string, not match start
like\$stringtrueCase sensitive string, match end
!like\$stringtrueCase sensitive string, not match end
ilikestringtrueCase insensitive string, match anywhere
!ilikestringtrueCase insensitive string, not match anywhere
\$ilikestringtrueCase insensitive string, match start
!\$ilikestringtrueCase insensitive string, not match start
ilike\$stringtrueCase insensitive string, match end
!ilike\$stringtrueCase insensitive string, not match end
gtstring | boolean | integer | float | collection (checks for size) | datetrueGreater than
gestring | boolean | integer | float | collection (checks for size) | datetrueGreater than or equal
ltstring | boolean | integer | float | collection (checks for size) | datetrueLess than
lestring | boolean | integer | float | collection (checks for size) | datetrueLess than or equal
nullallfalseProperty is null
!nullallfalseProperty is not null
emptycollectionfalseCollection is empty
tokenstringtrueMatch on multiple tokens in search property
!tokenstringtrueNot match on multiple tokens in search property
instring | boolean | integer | float | datetrueFind objects matching 1 or more values
!instring | boolean | integer | float | datetrueFind objects not matching 1 or more values
+ +Operators will be applied as logical _and_ query, if you need an _or_ query, you can have a look at our _in_ filter (also have a look at the section below). The filtering mechanism allows for recursion. See below for some examples. + +Get data elements with id property ID1 and aggregation operator "sum": + + /api/dataElements?filter=id:eq:ID1&filter=aggregationOperator:eq:sum + +Get all data elements which have the dataSet with id ID1: + + /api/dataElements?filter=dataSetElements.dataSet.id:eq:ID1 + +Get all data elements with aggregation operator "sum" and value type "int": + + /api/dataElements.json?filter=aggregationOperator:eq:sum&filter=type:eq:int + +You can do filtering within collections, e.g. to get data elements which are members of the "ANC" data element group you can use the following query using the id property of the associated data element groups: + + /api/dataElements.json?filter=dataElementGroups.id:eq:qfxEYY9xAl6 + +Since all operators are _and_ by default, you can't find a data element matching more than one id, for that purpose you can use the _in_ operator. + + /api/dataElements.json?filter=id:in:[fbfJHSPpUQD,cYeuwXTCPkU] + +### Logical operators { #webapi_metadata_logical_operator } + +As mentioned in the section before, the default logical operator applied to the filters is _AND_ which means that all object filters must be matched. There are however cases where you want to match on one of several filters (maybe id and code field) and in those cases, it is possible to switch the root logical operator from _AND_ to _OR_ using the _rootJunction_ parameter. + +Example: Normal filtering where both id and code must match to have a result returned + + /api/dataElements.json?filter=id:in:[id1,id2]&filter=code:eq:code1 + +Example: Filtering where the logical operator has been switched to OR and now only one of the filters must match to have a result returned + + /api/dataElements.json?filter=id:in:[id1,id2]&filter=code:eq:code1&rootJunction=OR + +### Identifiable token filter { #identifiable-token-filter } + +In addition to the specific property based filtering mentioned above, we also have _token_ based _AND_ filtering across a set of properties: id, code, and name (also shortName if available). These properties are commonly referred to as _identifiable_. The idea is to filter metadata whose id, name, code or short name containing something. + +Example: Filter all data elements containing _2nd_ in any of the following: id,name,code, shortName + + /api/dataElements.json?filter=identifiable:token:2nd + +It is also possible to specify multiple filtering values. + +Example: Get all data elements where _ANC visit_ is found in any of the _identifiable_ properties. The system returns all data elements where both tokens (ANC and visit) are found anywhere in identifiable properties. + + /api/dataElements.json?filter=identifiable:token:ANC visit + +It is also possible to combine the identifiable filter with property-based filter and expect the _rootJunction_ to be applied. + + /api/dataElements.json?filter=identifiable:token:ANC visit&filter=displayName:ilike:tt1 + + /api/dataElements.json?filter=identifiable:token:ANC visit + &filter=displayName:ilike:tt1&rootJunction=OR + +## Metadata field filter { #webapi_metadata_field_filter } + +In many situations, the default views of the metadata can be too verbose. A client might only need a few fields from each object and want to remove unnecessary fields from the response. To discover which fields are available for each object please see the _schema_ section. + +The format for include/exclude allows for infinite recursion. To filter at the "root" level you can just use the name of the field, i.e. `?fields=id,name` which would only display the `id` and `name` fields for every object. For objects that are either collections or complex objects with properties on their own, you can use the format `?fields=id,name,dataSets[id,name]` which would return `id`, `name` of the root, and the `id` and `name` of every data set on that object. Negation can be done with the exclamation operator, and we have a set of presets of field select. Both XML and JSON are supported. + +**Example**: Get `id` and `name` on the indicators resource: + + /api/indicators?fields=id,name + +**Example**: Get `id` and `name` from dataElements, and `id` and `name` from the dataSets on dataElements: + + /api/dataElements?fields=id,name,dataSets[id,name] + +To exclude a field from the output you can use the exclamation `!` operator. This is allowed anywhere in the query and will simply not include that property as it might have been inserted in some of the presets. + +A few presets (selected fields groups) are available and can be applied using the `:` operator. + + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Property operators
OperatorDescription
<field-name>Include property with name, if it exists.
<object>[<field-name>, ...]Includes a field within either a collection (will be applied to every object in that collection), or just on a single object.
!<field-name>, <object>[!<field-name>Do not include this field name, it also works inside objects/collections. Useful when you use a preset to include fields.
*, <object>[*]Include all fields on a certain object, if applied to a collection, it will include all fields on all objects on that collection.
:<preset>Alias to select multiple fields. Three presets are currently available, see the table below for descriptions.
+ + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Field presets
PresetDescription
allAll fields of the object
*Alias for all
identifiableIncludes id, name, code, created and lastUpdated fields
nameableIncludes id, name, shortName, code, description, created and lastUpdated fields
persistedReturns all persisted property on an object, does not take into consideration if the object is the owner of the relation.
ownerReturns all persisted property on an object where the object is the owner of all properties, this payload can be used to update through the API.
+ +**Example**: Include all fields from dataSets except organisationUnits: + + /api/dataSets?fields=:all,!organisationUnits + +**Example**: Include only id, name and the collection of organisation units from a data set, but exclude the id from organisation units: + + /api/dataSets/BfMAe6Itzgt?fields=id,name,organisationUnits[:all,!id] + +**Example**: Include nameable properties from all indicators: + + /api/indicators.json?fields=:nameable + +### Field transformers { #webapi_field_transformers } + +In DHIS2.17 we introduced field transformers, the idea is to allow further customization of the properties on the server-side. + + /api/dataElements/ID?fields=id~rename(i),name~rename(n) + +This will rename the _id_ property to _i_ and _name_ property to _n_. + +Multiple transformers can be used by repeating the transformer syntax: + + /api/dataElementGroups.json?fields=id,displayName,dataElements~isNotEmpty~rename(haveDataElements) + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Available Transformers
NameArgumentsDescription
sizeGives sizes of strings (length) and collections
isEmptyIs string or collection empty
isNotEmptyIs string or collection not empty
renameArg1: nameRenames the property name
pagingArg1: page,Arg2: pageSizePages a collection, default pageSize is 50.
pluckOptional Arg1: fieldNameConverts an array of objects to an array of a selected field of that object. By default, the first field that is returned by the collection is used (normally the ID).
+ +#### Examples { #webapi_field_transformers_examples } + +Examples of transformer usage. + +``` +/api/dataElements?fields=dataSets~size + +/api/dataElements?fields=dataSets~isEmpty + +/api/dataElements?fields=dataSets~isNotEmpty + +/api/dataElements/ID?fields=id~rename(i),name~rename(n) + +/api/dataElementGroups?fields=id,displayName,dataElements~paging(1;20) + +# Include array with IDs of organisation units: +/api/categoryOptions.json?fields=id,organisationUnits~pluck + +# Include array with names of organisation units (collection only returns field name): +/api/categoryOptions.json?fields=id,organisationUnits~pluck[name] +``` + +## Metadata create, read, update, delete, validate { #webapi_metadata_crud } + +All metadata entities in DHIS2 have their own API endpoint which supports _CRUD_ operations (create, read, update and delete). The endpoint URLs follows this format: + + /api/ + +The _entityName_ uses the camel-case notation. As an example, the endpoint for _data elements_ is: + + /api/dataElements + +### Create / update parameters { #webapi_metadata_create_update } + +The following request query parameters are available across all metadata endpoints. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Available Query Filters
ParamTypeRequiredOptions (default first)Description
preheatCachebooleanfalsetrue | falseTurn cache-map preheating on/off. This is on by default, turning this off will make initial load time for importer much shorter (but will make the import itself slower). This is mostly used for cases where you have a small XML/JSON file you want to import, and don't want to wait for cache-map preheating.
strategyenumfalseCREATE_AND_UPDATE | CREATE | UPDATE | DELETEImport strategy to use, see below for more information.
mergeModeenumfalseREPLACE, MERGEStrategy for merging of objects when doing updates. REPLACE will just overwrite the property with the new value provided, MERGE will only set the property if it is not null (only if the property was provided).
+ +### Creating and updating objects { #webapi_creating_updating_objects } + +For creating new objects you will need to know the endpoint, the type format, and make sure that you have the required authorities. As an example, we will create and update a _constant_. To figure out the format, we can use the new _schema_ endpoint for getting format description. So we will start with getting that info: + + http:///api/schemas/constant.json + +From the output, you can see that the required authorities for create are `F_CONSTANT_ADD`, and the important properties are: _name_ and _value_. From this, we can create a JSON payload and save it as a file called constant.json: + +```json +{ + "name": "PI", + "value": "3.14159265359" +} +``` + +The same content as an XML payload: + +```xml + + 3.14159265359 + +``` + +We are now ready to create the new _constant_ by sending a POST request to the *constants*endpoint with the JSON payload using curl: + +```bash +curl -d @constant.json "http://server/api/constants" -X POST + -H "Content-Type: application/json" -u user:password +``` + +A specific example of posting the constant to the demo server: + +```bash +curl -d @constant.json "https://play.dhis2.org/api/constants" -X POST + -H "Content-Type: application/json" -u admin:district +``` + +If everything went well, you should see an output similar to: + +```json +{ + "status": "SUCCESS", + "importCount": { + "imported": 1, + "updated": 0, + "ignored": 0, + "deleted": 0 + }, + "type": "Constant" +} +``` + +The process will be exactly the same for updating, you make your changes to the JSON/XML payload, find out the _ID_ of the constant, and then send a PUT request to the endpoint including ID: + +```bash +curl -X PUT -d @pi.json -H "Content-Type: application/json" + -u user:password "http://server/api/constants/ID" +``` + +### Deleting objects { #webapi_deleting_objects } + +Deleting objects is very straight forward, you will need to know the _ID_ and the endpoint of the type you want to delete, let's continue our example from the last section and use a _constant_. Let's assume that the id is _abc123_, then all you need to do is the send the DELETE request to the endpoint + id: + +```bash +curl -X DELETE -u user:password "http://server/api/constants/ID" +``` + +A successful delete should return HTTP status 204 (no content). + +### Adding and removing objects in collections { #webapi_adding_removing_objects_collections } + +The collections resource lets you modify collections of objects. + +#### Adding or removing single objects { #webapi_collections_adding_removing_single_objects } + +In order to add or remove objects to or from a collection of objects you can use the following pattern: + + /api/{collection-object}/{collection-object-id}/{collection-name}/{object-id} + +You should use the POST method to add, and the DELETE method to remove an object. When there is a many-to-many relationship between objects, you must first determine which object owns the relationship. If it isn't clear which object this is, try the call both ways to see which works. + +The components of the pattern are: + +- collection object: The type of objects that owns the collection you want to modify. + +- collection object id: The identifier of the object that owns the collection you want to modify. + +- collection name: The name of the collection you want to modify. + +- object id: The identifier of the object you want to add or remove from the collection. + +As an example, in order to remove a data element with identifier IDB from a data element group with identifier IDA you can do a DELETE request: + + DELETE /api/dataElementGroups/IDA/dataElements/IDB + +To add a category option with identifier IDB to a category with identifier IDA you can do a POST request: + + POST /api/categories/IDA/categoryOptions/IDB + +#### Adding or removing multiple objects { #webapi_collections_adding_removing_multiple_objects } + +You can add or remove multiple objects from a collection in one request with a payload like this: + +```json +{ + "identifiableObjects": [ + { + "id": "IDA" + }, + { + "id": "IDB" + }, + { + "id": "IDC" + } + ] +} +``` + +Using this payload you can add, replace or delete items: + +_Adding Items:_ + + POST /api/categories/IDA/categoryOptions + +_Replacing Items:_ + + PUT /api/categories/IDA/categoryOptions + +_Delete Items:_ + + DELETE /api/categories/IDA/categoryOptions + +#### Adding and removing objects in a single request { #webapi_collections_adding_removing_objects_single_request } + +You can both add and remove objects from a collection in a single POST request to the following URL: + + POST /api/categories/IDA/categoryOptions + +The payload format is: + +```json +{ + "additions": [ + { + "id": "IDA" + }, + { + "id": "IDB" + }, + { + "id": "IDC" + } + ], + "deletions": [ + { + "id": "IDD" + }, + { + "id": "IDE" + }, + { + "id": "IDF" + } + ] +} +``` + +### Validating payloads { #webapi_validating_payloads } + +DHIS 2 supports system wide validation of metadata payloads, which means that create and update operations on the API endpoints will be checked for valid payload before allowing changes to be made. To find out what validations are in place for a specific endpoint, have a look at the `/api/schemas` endpoint, i.e. to figure out which constraints a data element have, you would go to `/api/schemas/dataElement`. + +You can also validate your payload manually by sending it to the proper schema endpoint. If you wanted to validate the constant from the create section before, you would send it like this: + + POST /api/schemas/constant + +A simple (non-validating) example would be: + +```bash +curl -X POST -d "{\"name\": \"some name\"}" -H "Content-Type: application/json" + -u admin:district "https://play.dhis2.org/dev/api/schemas/dataElement" +``` + +Which would yield the result: + +```json +[ + { + "message": "Required property missing.", + "property": "type" + }, + { + "property": "aggregationOperator", + "message": "Required property missing." + }, + { + "property": "domainType", + "message": "Required property missing." + }, + { + "property": "shortName", + "message": "Required property missing." + } +] +``` + +### Partial updates { #webapi_partial_updates } + +For cases where you don't want or need to update all properties on a object (which means downloading a potentially huge payload, change one property, then upload again) we now support partial update, for one or more properties. + +The payload for doing partial updates are the same as when you are doing a full update, the only difference is that you only include the properties you want to update, i.e.: + +```json +{ + "name": "Updated Name", + "zeroIsSignificant": true +} +``` + +An example curl command looks like this: + +```bash +curl -X PATCH -d @file.json -H "Content-Type: application/json" + -u admin:district "https://play.dhis2.org/dev/api/dataElements/fbfJHSPpUQD" +``` + +## Metadata export { #webapi_metadata_export } + +This section explains the metatada API which is available at `/api/metadata`. XML and JSON resource representations are supported. + + /api/metadata + +The most common parameters are described below in the "Export Parameter" table. You can also apply this to all available types by using `type:fields=` and `type:filter=`. You can also enable/disable the export of certain types by setting `type=true|false`. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Export Parameter
NameOptionsDescription
fieldsSame as metadata field filterDefault field filter to apply for all types, default is `:owner`.
filterSame as metadata object filterDefault object filter to apply for all types, default is `none`.
orderSame as metadata orderDefault order to apply to all types, default is `name` if available, or `created` if not.
translatefalse/trueEnable translations. Be aware that this is turned off by default (in other endpoints this is on by default).
locale<locale>Change from user locale, to your own custom locale.
defaultsINCLUDE/EXCLUDEShould auto-generated category object be included or not in the payload. If you are moving metadata between 2 non-synced instances, it might make sense to set this to EXCLUDE to ease the handling of these generated objects.
skipSharingfalse/trueEnabling this will strip the sharing properties from the exported objects. This includes user, publicAccess, userGroupAccesses, userAccesses, and externalAccess.
downloadfalse/trueEnabling this will add HTTP header Content-Disposition that specifies that the data should be handled as an attachment and will be offered by web browsers as a download.
+ +### Metadata export examples { #webapi_metadata_export_examples } + +Export all metadata. Be careful as the response might be very large depending on your metadata configuration: + + /api/metadata + +Export all metadata ordered by lastUpdated descending: + + /api/metadata?defaultOrder=lastUpdated:desc + +Export metadata only including indicators and indicator groups: + + /api/metadata?indicators=true&indicatorGroups=true + +Export id and displayName for all data elements, ordered by displayName: + + /api/metadata?dataElements:fields=id,name&dataElements:order=displayName:desc + +Export data elements and indicators where name starts with "ANC": + + /api/metadata?filter=name:^like:ANC&dataElements=true&indicators=true + +### Metadata export with dependencies { #webapi_dataset_program_export_dependencies } + +When you want to exchange metadata for a data set, program or category combo from one DHIS2 instance to another instance there are three dedicated endpoints available: + +``` +/api/dataSets/{id}/metadata.json + +/api/programs/{id}/metadata.json + +/api/categoryCombos/{id}/metadata.json + +/api/dashboards/{id}/metadata.json +``` + +These exports can then be imported using `/api/metadata`. + +These endpoints also support the following parameters: + + + +++++ + + + + + + + + + + + + + + + + + + + +
Export Parameter
NameOptionsDescription
skipSharingfalse/trueEnabling this will strip the sharing properties from the exported objects. This includes user, publicAccess, userGroupAccesses, userAccesses, and externalAccess.
downloadfalse/trueEnabling this will add HTTP header Content-Disposition that specifies that the data should be handled as an attachment and will be offered by web browsers as a download.
+ +## Metadata import { #webapi_metadata_import } + +This section explains the metadata import API. XML and JSON resource representations are supported. Metadata can be imported using a _POST_ request. + + /api/metadata + +The importer allows you to import metadata payloads which may include many different entities and any number of objects per entity. The metadata export generated by the metadata export API can be imported directly. + +The metadata import endpoint support a variety of parameters, which are listed below. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Import Parameter
NameOptions (first is default)Description
importModeCOMMIT, VALIDATESets overall import mode, decides whether or not to only `VALIDATE` or also `COMMIT` the metadata, this has similar functionality as our old dryRun flag.
identifierUID, CODE, AUTOSets the identifier scheme to use for reference matching. `AUTO` means try `UID` first, then `CODE`.
importReportModeERRORS, FULL, DEBUGSets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes ObjectReports for object which has errors. `FULL` returns an ObjectReport for all objects imported, and `DEBUG` returns the same plus a name for the object (if available).
preheatModeREFERENCE, ALL, NONESets the preheater mode, used to signal if preheating should be done for `ALL` (as it was before with preheatCache=true) or do a more intelligent scan of the objects to see what to preheat (now the default), setting this to `NONE` is not recommended.
importStrategyCREATE_AND_UPDATE, CREATE, UPDATE, DELETESets import strategy, `CREATE_AND_UPDATE` will try and match on identifier, if it doesn't exist, it will create the object.
atomicModeALL, NONESets atomic mode, in the old importer we always did a best effort import, which means that even if some references did not exist, we would still import (i.e. missing data elements on a data element group import). Default for new importer is to not allow this, and similar reject any validation errors. Setting the `NONE` mode emulated the old behavior.
mergeModeREPLACE, MERGESets the merge mode, when doing updates we have two ways of merging the old object with the new one, `MERGE` mode will only overwrite the old property if the new one is not-null, for `REPLACE` mode all properties are overwritten regardless of null or not.
flushModeAUTO, OBJECTSets the flush mode, which controls when to flush the internal cache. It is strongly recommended to keep this to `AUTO` (which is the default). Only use `OBJECT` for debugging purposes, where you are seeing hibernate exceptions and want to pinpoint the exact place where the stack happens (hibernate will only throw when flushing, so it can be hard to know which object had issues).
skipSharingfalse, trueSkip sharing properties, does not merge sharing when doing updates, and does not add user group access when creating new objects.
skipValidationfalse, trueSkip validation for import. `NOT RECOMMENDED`.
asyncfalse, trueAsynchronous import, returns immediately with a Location header pointing to the location of the importReport. The payload also contains a json object of the job created.
inclusionStrategyNON_NULL, ALWAYS, NON_EMPTYNON_NULL includes properties which are not null, ALWAYS include all properties, NON_EMPTY includes non empty properties (will not include strings of 0 length, collections of size 0, etc.)
userOverrideModeNONE, CURRENT, SELECTEDAllows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X)
overrideUserUser IDIf userOverrideMode is SELECTED, use this parameter to select the user you want override with.
+ +An example of a metadata payload to be imported looks like this. Note how each entity type have their own property with an array of objects: + +```json +{ + "dataElements": [ + { + "name": "EPI - IPV 3 doses given", + "shortName": "EPI - IPV 3 doses given", + "aggregationType": "SUM", + "domainType": "AGGREGATE", + "valueType": "INTEGER_ZERO_OR_POSITIVE" + }, + { + "name": "EPI - IPV 4 doses given", + "shortName": "EPI - IPV 4 doses given", + "aggregationType": "SUM", + "domainType": "AGGREGATE", + "valueType": "INTEGER_ZERO_OR_POSITIVE" + } + ], + "indicators": [ + { + "name": "EPI - ADS stock used", + "shortName": "ADS stock used", + "numerator": "#{LTb8XeeqeqI}+#{Fs28ZQJET6V}-#{A3mHIZd2tPg}", + "numeratorDescription": "ADS 0.05 ml used", + "denominator": "1", + "denominatorDescription": "1", + "annualized": false, + "indicatorType": { + "id": "kHy61PbChXr" + } + } + ] +} +``` + +When posting this payload to the metadata endpoint, the response will contain information about the parameters used during the import and a summary per entity type including how many objects were created, updated, deleted and ignored: + +```json +{ + "importParams": { + "userOverrideMode": "NONE", + "importMode": "COMMIT", + "identifier": "UID", + "preheatMode": "REFERENCE", + "importStrategy": "CREATE_AND_UPDATE", + "atomicMode": "ALL", + "mergeMode": "REPLACE", + "flushMode": "AUTO", + "skipSharing": false, + "skipTranslation": false, + "skipValidation": false, + "metadataSyncImport": false, + "firstRowIsHeader": true, + "username": "UNICEF_admin" + }, + "status": "OK", + "typeReports": [ + { + "klass": "org.hisp.dhis.dataelement.DataElement", + "stats": { + "created": 2, + "updated": 0, + "deleted": 0, + "ignored": 0, + "total": 2 + } + }, + { + "klass": "org.hisp.dhis.indicator.Indicator", + "stats": { + "created": 1, + "updated": 0, + "deleted": 0, + "ignored": 0, + "total": 1 + } + } + ], + "stats": { + "created": 3, + "updated": 0, + "deleted": 0, + "ignored": 0, + "total": 3 + } +} +``` + +## Schema { #webapi_schema } + +A resource which can be used to introspect all available DXF 2 objects can be found on `/api/schemas`. For specific resources you can have a look at `/api/schemas/`. + +To get all available schemas in XML: + + GET /api/schemas.xml + +To get all available schemas in JSON: + + GET /api/schemas.json + +To get JSON schema for a specific class: + + GET /api/schemas/dataElement.json + +## Icons { #webapi_icons } + +DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons resource. + + GET /api/icons + +This endpoint returns a list of information about the available icons. Each entry contains information about the icon, and a reference to the actual icon. + +```json +{ + "key": "mosquito_outline", + "description": "Mosquito outline", + "keywords": ["malaria", "mosquito", "dengue"], + "href": "/api/icons/mosquito_outline/icon.svg" +} +``` + +The keywords can be used to filter which icons to return. Passing a list of keywords with the request will only return icons that match all the keywords: + + GET /api/icons?keywords=shape,small + +A list of all unique keywords can be found at the keywords resource: + + GET /api/icons/keywords + +## Render type { #webapi_render_type } + +Some metadata types have a property named _renderType_. The render type property is a map between a _device_ and a _renderingType_. Applications can use this information as a hint on how the object should be rendered on a specific device. For example, a mobile device might want to render a data element differently than a desktop computer. + +There is currently two different kinds of renderingTypes available: + +1. Value type rendering + +2. Program stage section rendering + +There is also 2 device types available: + +1. MOBILE + +2. DESKTOP + +The following table lists the metadata and rendering types available. The value type rendering has addition constraints based on the metadata configuration, which will be shown in a second table. + + + ++++ + + + + + + + + + + + + + + + + +
Metadata and RenderingType overview
Metadata typeAvailable RenderingTypes
Program Stage Section
    +

  • LISTING (default)

    • +

  • SEQUENTIAL

    • +

  • MATRIX

    • +
Data element
    +

  • DEFAULT

    • +

  • DROPDOWN

    • +

  • VERTICAL_RADIOBUTTONS

    • +

  • HORIZONTAL_RADIOBUTTONS

    • +

  • VERTICAL_CHECKBOXES

    • +

  • HORIZONTAL_CHECKBOXES

    • +

  • SHARED_HEADER_RADIOBUTTONS

    • +

  • ICONS_AS_BUTTONS

    • +

  • SPINNER

    • +

  • ICON

    • +

  • TOGGLE

    • +

  • VALUE

    • +

  • SLIDER

    • +

  • LINEAR_SCALE

    • +
+ +Since handling the default rendering of data elements and tracked entity attributes are depending on the value type of the object, there is also a DEFAULT type to tell the client it should be handled as normal. Program Stage Section is LISTING as default. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
RenderingTypes allowed based on value types
Value typeIs object an optionset?RenderingTypes allowed
TRUE_ONLYNoDEFAULT, VERTICAL_RADIOBUTTONS, HORIZONTAL_RADIOBUTTONS, VERTICAL_CHECKBOXES, HORIZONTAL_CHECKBOXES, TOGGLE
BOOLEANNo
-YesDEFAULT, DROPDOWN, VERTICAL_RADIOBUTTONS, HORIZONTAL_RADIOBUTTONS, VERTICAL_CHECKBOXES, HORIZONTAL_CHECKBOXES, SHARED_HEADER_RADIOBUTTONS, ICONS_AS_BUTTONS, SPINNER, ICON
INTEGERNoDEFAULT, VALUE, SLIDER, LINEAR_SCALE, SPINNER
INTEGER_POSITIVENo
INTEGER_NEGATIVENo
INTEGER_ZERO_OR_POSITIVENo
NUMBERNo
UNIT_INTERVALNo
PERCENTAGENo
+ +A complete reference of the previous table can also be retrieved using the following endpoint: + + GET /api/staticConfiguration/renderingOptions + +Value type rendering also has some additional properties that can be set, which is usually needed when rendering some of the specific types: + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
renderType object properties
PropertyDescriptionType
typeThe RenderingType of the object, as seen in the first table. This property is the same for both value type and program stage section, but is the only property available for program stage section.Enum (See list in the Metadata and Rendering Type table)
minOnly for value type rendering. Represents the minimum value this field can have.Integer
maxOnly for value type rendering. Represents the maximum value this field can have.Integer
stepOnly for value type rendering. Represents the size of the steps the value should increase, for example for SLIDER og LINEAR_SCALEInteger
decimalPointsOnly for value type rendering. Represents the number of decimal points the value should use.Integer
+ +The _renderingType_ can be set when creating or updating the metadata listed in the first table. An example payload for the rendering type for program stage section looks like this: + +```json +{ + "renderingType": { + "type": "MATRIX" + } +} +``` + +For data element and tracked entity attribute: + +```json +{ + "renderingType": { + "type": "SLIDER", + "min": 0, + "max": 1000, + "step": 50, + "decimalPoints": 0 + } +} +``` + +## Object Style { #webapi_object_style } + +Most metadata have a property names "style". This property can be used by clients to represent the object in a certain way. The properties currently supported by style is as follows: + + + +++++ + + + + + + + + + + + + + + + + + + + +
Style properties
PropertyDescriptionType
colorA color, represented by a hexadecimal.String (#000000)
iconAn icon, represented by a icon-name.String
+ +Currently, there is no official list or support for icon-libraries, so this is currently up to the client to provide. The following list shows all objects that support style: + +- Elemento de datos + +- Data element category option + +- Data set + +- Indicador + +- Opción + +- Programa + +- Program Indicator + +- Program Section + +- Program Stage + +- Program Stage Section + +- Relationship (Tracker) + +- Tracked Entity Attribute + +- Tracked Entity Type + +When creating or updating any of these objects, you can include the following payload to change the style: + +```json +{ + "style": { + "color": "#ffffff", + "icon": "my-beautiful-icon" + } +} +``` + +## Indicators { #webapi_indicators } + +This section describes indicators and indicator expressions. + +### Aggregate indicators { #webapi_aggregate_indicators } + +To retrieve indicators you can make a GET request to the indicators resource like this: + + /api/indicators + +Indicators represent expressions which can be calculated and presented as a result. The indicator expressions are split into a numerator and denominator. The numerators and denominators are mathematical expressions which can contain references to data elements, other indicators, constants and organisation unit groups. The variables will be substituted with data values when used e.g. in reports. Variables which are allowed in expressions are described in the following table. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Indicator variables
VariableObjectDescription
#{<dataelement-id>.<categoryoptcombo-id>.<attributeoptcombo-id>}Data element operandRefers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "*" symbol can be used to indicate any value.
#{<dataelement-id>.<categoryoptiongroup-id>.<attributeoptcombo-id>}Category Option GroupRefers to an aggregate data element and a category option group, containing multiple category option combinations.
#{<dataelement-id>}Aggregate data elementRefers to the total value of an aggregate data element across all category option combinations.
D{<program-id>.<dataelement-id>}Program data elementRefers to the value of a tracker data element within a program.
A{<program-id>.<attribute-id>}Program tracked entity attributeRefers to the value of a tracked entity attribute within a program.
I{<program-indicator-id>}Program indicatorRefers to the value of a program indicator.
R{<dataset-id>.<metric>}Reporting rateRefers to a reporting rate metric. The metric can be REPORTING_RATE, REPORTING_RATE_ON_TIME, ACTUAL_REPORTS, ACTUAL_REPORTS_ON_TIME, EXPECTED_REPORTS.
C{<constant-id>}ConstantRefers to a constant value.
N{<indicator-id>}IndicatorRefers to an existing Indicator.
OUG{<orgunitgroup-id>}Organisation unit groupRefers to the count of organisation units within an organisation unit group.
+ +The syntax looks like this: + + #{.} + C{} + OUG{} + +A corresponding example looks like this: + + #{P3jJH5Tu5VC.S34ULMcHMca} + C{Gfd3ppDfq8E} + OUG{CXw2yu5fodb} + +Note that for data element variables the category option combo identifier can be omitted. The variable will then represent the total for the data element, e.g. across all category option combos. Example: + + #{P3jJH5Tu5VC} + 2 + +Data element operands can include any of category option combination and attribute option combination, and use wildcards to indicate any value: + + #{P3jJH5Tu5VC.S34ULMcHMca} + #{P3jJH5Tu5VC.*.j8vBiBqGf6O} + #{P3jJH5Tu5VC.S34ULMcHMca.*} + +An example which uses a program data element and a program attribute: + + ( D{eBAyeGv0exc.vV9UWAZohSf} * A{IpHINAT79UW.cejWyOfXge6} ) / D{eBAyeGv0exc.GieVkTxp4HH} + +An example which combines program indicators and aggregate indicators: + + I{EMOt6Fwhs1n} * 1000 / #{WUg3MYWQ7pt} + +An example which uses a reporting rate looks like this: + + R{BfMAe6Itzgt.REPORTING_RATE} * #{P3jJH5Tu5VC.S34ULMcHMca} + +Another example which uses actual data set reports: + + R{BfMAe6Itzgt.ACTUAL_REPORTS} / R{BfMAe6Itzgt.EXPECTED_REPORTS} + +An example which uses an existing indicator would look like this: + + N{Rigf2d2Zbjp} * #{P3jJH5Tu5VC.S34ULMcHMca} + +Expressions can be any kind of valid mathematical expression, as an example: + + ( 2 * #{P3jJH5Tu5VC.S34ULMcHMca} ) / ( #{FQ2o8UBlcrS.S34ULMcHMca} - 200 ) * 25 + +### Program indicators { #webapi_program_indicators } + +To retrieve program indicators you can make a GET request to the program indicators resource like this: + + /api/programIndicators + +Program indicators can contain information collected in a program. Indicators have an expression which can contain references to data elements, attributes, constants and program variables. Variables which are allowed in expressions are described in the following table. + + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
Program indicator variables
VariableDescription
#{<programstage-id>.<dataelement-id>}Refers to a combination of program stage and data element id.
A{<attribute-id>}Refers to a tracked entity attribute.
V{<variable-id>}Refers to a program variable.
C{<constant-id>}Refers to a constant.
+ +The syntax looks like this: + + #{.} + #{} + V{} + C{} + +A corresponding example looks like this: + + #{A03MvHHogjR.a3kGcGDCuk6} + A{OvY4VVhSDeJ} + V{incident_date} + C{bCqvfPR02Im} + +### Expressions { #webapi_expressions } + +Expressions are mathematical formulas which can contain references to data elements, constants and organisation unit groups. To validate and get the textual description of an expression, you can make a GET request to the expressions resource: + + /api/expressions/description?expression= + +The response follows the standard JSON web message format. The _status_ property indicates the outcome of the validation and will be "OK" if successful and "ERROR" if failed. The _message_ property will be "Valid" if successful and provide a textual description of the reason why the validation failed if not. The _description_ provides a textual description of the expression. + +```json +{ + "httpStatus": "OK", + "httpStatusCode": 200, + "status": "OK", + "message": "Valid", + "description": "Acute Flaccid Paralysis" +} +``` + +## Organisation units { #webapi_organisation_units } + +The _organisationUnits_ resource follows the standard conventions as other metadata resources in DHIS2. This resource supports some additional query parameters. + +### Get list of organisation units { #webapi_list_of_organisation_units } + +To get a list of organisation units you can use the following resource. + + /api/33/organisationUnits + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Organisation units query parameters
Query parameterOptionsDescription
userOnlyfalse | trueData capture organisation units associated with current user only.
userDataViewOnlyfalse | trueData view organisation units associated with current user only.
userDataViewFallbackfalse | trueData view organisation units associated with current user only with fallback to data capture organisation units.
querystringQuery against the name, code and ID properties.
levelintegerOrganisation units at the given level in the hierarchy.
maxLevelintegerOrganisation units at the given max level or levels higher up in the hierarchy.
withinUserHierarchyfalse | trueLimits search and retrieval to organisation units that are within the users data capture scope.
withinUserSearchHierarchyfalse | trueLimits search and retrieval to organisation units that are within the current users search scope. Note: "withinUserHierarchy", if true, takes higher precedence.
memberCollectionstringFor displaying count of members within a collection, refers to the name of the collection associated with organisation units.
memberObjectUIDFor displaying count of members within a collection, refers to the identifier of the object member of the collection.
+ +### Get organisation unit with relations { #webapi_organisation_units_with_relations } + +To get an organisation unit with related organisation units you can use the following resource. + + /api/33/organisationUnits/{id} + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Organisation unit parameters
Query parameterOptionsDescription
includeChildrenfalse | trueInclude immediate children of the specified organisation unit, i.e. the units at the immediate level below in the subhierarchy.
includeDescendantsfalse | trueInclude all children of the specified organisation unit, i.e. all units in the sub-hierarchy.
includeAncestorsfalse | trueInclude all parents of the specified organisation unit.
levelintegerInclude children of the specified organisation unit at the given level of the sub-hierarchy (relative to the organisation unit where the immediate level below is level 1).
+ +### Get organisation units by programs { #webapi_organisation_units_by_programs } + +Purpose-built endpoint to retrieve associations between Programs and Organisation Units. This endpoint is the preferred way to retrieve program org unit associations. + + /api/33/programs/orgUnits?programs= + +responses will have the following format: + + { + "": [ + "", + "", + ..., + "" + ], + "": [ + "", + "", + ..., + "" + ], + "...": [ + ..., + ... + ], + "": [] + } + +programs with no associated uids (hence accessible by all orgUnits) are returned with an empty array [] of orgUnits. + +## Data sets { #webapi_data_sets } + +The _dataSets_ resource follows the standard conventions as other metadata resources in DHIS2. This resource supports some additional query parameters. + + /api/33/dataSets + +To retrieve the version of a data set you can issue a GET request: + + GET /api/33/dataSets//version + +To bump (increase by one) the version of a data set you can issue a POST request: + + POST /api/33/dataSets//version + +### DataSet Notification Template { #webapi_dataset_notifications } + +The _dataset notification templates_ resource follows the standard conventions as other metadata resources in DHIS2. + + GET /api/33/dataSetNotficationTemplates + +To retrieve data set notification template you can issue a GET request: + + GET /api/33/dataSetNotficationTemplates/ + +To add data set notification template you can issue a POST request: + + POST /api/33/dataSetNotficationTemplates + +To delete data set notification template you can issue a DELETE request: + + DELETE /api/33/dataSetNotficationTemplates/ + +JSON payload sample is given below: + +```json +{ + "name": "dataSetNotificationTemplate1", + "notificationTrigger": "COMPLETION", + "relativeScheduledDays": 0, + "notificationRecipient": "ORGANISATION_UNIT_CONTACT", + "dataSets": [ + { + "id": "eZDhcZi6FLP" + } + ], + "deliveryChannels": ["SMS"], + "subjectTemplate": "V{data_name}", + "messageTemplate": "V{data_name}V{complete_registration_period}", + "sendStrategy": "SINGLE_NOTIFICATION" +} +``` + +## Filled organisation unit levels { #webapi_filled_organisation_unit_levels } + +The _filledOrganisationUnitLevels_ resource provides an ordered list of organisation unit levels, where generated levels are injected into the list to fill positions for which it does not exist a persisted level. + + GET /api/33/filledOrganisationUnitLevels + +To set the organisation unit levels you can issue a POST request with a JSON payload looking like this. + +```json +{ + "organisationUnitLevels": [ + { + "name": "National", + "level": 1, + "offlineLevels": 3 + }, + { + "name": "District", + "level": 2 + }, + { + "name": "Chiefdom", + "level": 3 + }, + { + "name": "Facility", + "level": 4 + } + ] +} +``` + +To do functional testing with curl you can issue the following command. + +```bash +curl "http://localhost/api/33/filledOrganisationUnitLevels" -H "Content-Type:application/json" + -d @levels.json -u admin:district +``` + +## Predictors { #webapi_predictors } + +A predictor allows you to generate data values based on an expression. This can be used for example to generate targets, thresholds, or estimated values. + +To retrieve predictors you can make a GET request to the predictors resource like this: + + /api/predictors + +### Creating a predictor { #webapi_create_predictor } + +You can create a predictor with a POST request to the predictors resource: + + POST /api/predictors + +A sample payload looks like this: + +```json +{ + "id": "AG10KUJCrRk", + "name": "Malaria Outbreak Threshold Predictor", + "shortName": "Malaria Outbreak Predictor", + "description": "Computes the threshold for potential malaria outbreaks based on the mean plus 1.5x the std dev", + "output": { + "id": "nXJJZNVAy0Y" + }, + "generator": { + "expression": "AVG(#{r6nrJANOqMw})+1.5*STDDEV(#{r6nrJANOqMw})", + "description": "Maximum normal malaria case count", + "missingValueStrategy": "NEVER_SKIP", + "slidingWindow": false + }, + "periodType": "Monthly", + "sequentialSampleCount": 4, + "sequentialSkipCount": 1, + "annualSampleCount": 3, + "organisationUnitLevels": [4] +} +``` + +The output element refers to the identifier of the data element for which to saved predicted data values. The generator element refers to the expression to use when calculating the predicted values. + +### Predictor expressions { #webapi_predictor_expressions } + +A predictor always has a generator expression that describes how the predicted value is calculated. A predictor may also have a skip test expression returning a boolean value. When the skip test expression is present, it is evaluated in each of the sampled periods to tell whether values from that period should be skipped. + +The following variables may be used in either a generator expression or a skip test expression: + +| Variable | Objeto | Descripción | +| --- | --- | --- | +| #{\<dataelement-id>} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | +| #{\<dataelement-id>.\<categoryoptcombo-id>} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | +| D{\<program-id>.\<dataelement-id>} | Program data element | Refers to the value of a tracker data element within a program. | +| A{\<program-id>.\<attribute-id>} | Program tracked entity attribute | Refers to the value of a tracked entity attribute within a program. | +| I{\<program-indicator-id>} | Program indicator | Refers to the value of a program indicator. | +| R{\<dataset-id>.\<metric>} | Reporting rate | Refers to a reporting rate metric. The metric can be REPORTING_RATE, REPORTING_RATE_ON_TIME, ACTUAL_REPORTS, ACTUAL_REPORTS_ON_TIME, EXPECTED_REPORTS. | +| C{\<constant-id>} | Constante | Refers to a constant value. | +| OUG{\<orgunitgroup-id>} | Grupo de Unidades Organizativas | Refers to the count of organisation units within an organisation unit group. | +| [days] | Number of days | The number of days in the current period. | + +### Generating predicted values { #webapi_generating_predicted_values } + +To run all predictors (generating predicted values) you can make a POST request to the run resource: + + POST /api/predictors/run + +To run a single predictor you can make a POST request to the run resource for a predictor: + + POST /api/predictors/AG10KUJCrRk/run + +## Program rules { #webapi_program_rules } + +This section is about sending and reading program rules, and explains the program rules data model. The program rules give functionality to configure dynamic behaviour in the programs in DHIS2. + +### Program rule model { #webapi_program_rule_model } + +The program rules data model consists of programRuleVariables, programRules and programRuleActions. The programRule contains an expression - when this expression is true, the child programRuleActions is triggered. The programRuleVariables is used to address data elements, tracked entity data values and other data values needed to run the expressions. All programRules in a program share the same library of programRuleVariables, and one programRuleVariable can be used in several programRules' expressions. + +![](resources/images/program_rules/program-rule-model.jpg) + +#### Program rule model details { #program-rule-model-details } + +The following table gives a detailed overview over the programRule model. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
programRule
namedescriptionCompulsory
programThe program of which the programRule is executed in.Compulsory
nameThe name with which the program rule will be displayed to dhis2 configurators. Not visible to the end user of the program.Compulsory
descriptionThe description of the program rule, can be used by configurators to describe the rule. Not visible to the end user of the program.Compulsory
programStageIf a programStage is set for a program rule, the rule will only be evaluated inside the specified program stage.optional
conditionThe expression that needs to be evaluated to true in order for the program rule to trigger its child actions. The expression is written using operators, function calls, hard coded values, constants and program rule variables. +
d2:hasValue('hemoglobin') && #{hemoglobin} <= 7
Compulsory
priorityThe priority to run the rule in cases where the order of the rules matters. In most cases the rules does not depend on being run before or after other rules, and in these cases the priority can be omitted. If no priority is set, the rule will be run after any rules that has a priority defined. If a priority(integer) is set, the rule with the lowest priority will be run before rules with higher priority.optional
+ +#### Program rule action model details { #program-rule-action-model-details } + +The following table gives a detailed overview over the programRuleAction model. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
programRuleAction
namedescriptionCompulsory
programRuleThe programRule that is the parent of this action.Compulsory
programRule- ActionTypeThe type of action that is to be performed. +
    +

  • `DISPLAYTEXT` - Displays a text in a given widget.

    • +

  • `DISPLAYKEYVALUEPAIR` - Displays a key and value pair(like a program indicator) in a given widget.

    • +

  • `HIDEFIELD` - Hide a specified dataElement or trackedEntityAttribute.

    +
      +

    • content - if defined, the text in content will be displayed to the end user in the instance where a value is previously entered into a field that is now about to be hidden (and therefore blanked). If content is not defined, a standard message will be shown to the user in this instance.

      • +

    • dataElement - if defined, the HIDEFIELD action will hide this dataElement when the rule is effective.

      • +

    • trackedEntityDataValue - if defined, the HIDEFIELD action will hide this trackedEntityDataValue when the rule is effective.

      • +
    • +

  • `HIDESECTION` - Hide a specified section.

    +
      +

    • programStageSection - must be defined. This is the programStageSection that will be hidden in case the parent rule is effective.

      • +
    • +

  • `ASSIGN` - Assign a dataElement a value(help the user calculate something or fill in an obvious value somewhere)

    +
      +

    • content - if defined, the value in data is assigned to this variable. If content id defined, and thus a variable is assigned for use in other rules, it is important to also assign a programRule.priority to make sure the rule with an ASSIGN action runs before the rule that will in turn evaluate the assigned variable.

      • +

    • data - must be defined, data forms an expression that is evaluated and assigned to either a variable(#{myVariable}), a dataElement, or both.

      • +

    • dataElement - if defined, the value in data is assigned to this data element.

      • +
    +

    Either the content or dataElement must be defined for the ASSIGN action to be effective.

    • +

  • `SHOWWARNING` - Show a warning to the user, not blocking the user from completing the event or registration.

    +
      +

    • content - if defined, content is a static part that is displayed at the end of the error message.

      • +

    • data - if defined, data forms an expression that is evaluated and added to the end of the warning message.

      • +

    • dataElement - if defined, the warning message is displayed next to this data element.

      • +

    • trackedEntityAttribute - if defined, the warning message is displayed next to this tracked entity attribute.

      • +
    +

    Either dataElement or trackedEntityAttribute must be specified.

    • +

  • `SHOWERROR` - Show an error to the user, blocking the user from completing the event or registration.

    +
      +

    • content - if defined, content is a static part that is displayed in the start of the error message.

      • +

    • data - if defined, data forms an expression that is evaluated and added to the end of the error message.

      • +

    • dataElement - if defined, the error message is linked to this data element.

      • +

    • trackedEntityAttribute - if defined, the error message is linked to this tracked entity attribute.

      • +
    +

    Either dataElement or trackedEntityAttribute must be specified.

    • +

  • `WARNINGONCOMPLETINON` - Show a warning to the user on the "Complete form" dialog, but allowing the user to complete the event.

    +
      +

    • content - if defined, content is a static part that is displayed at the end of the error message.

      • +

    • data - if defined, data forms an expression that is evaluated and added to the end of the warning message.

      • +

    • dataElement - if defined, the warning message prefixed with the name/formName of the data element.

      • +
    • +

  • `ERRORONCOMPLETION` - Show an error to the user on in a modal window when the user tries to complete the event. The user is prevented from completing the event.

    +
      +

    • content - if defined, content is a static part that is displayed in the start of the error message.

      • +

    • data - if defined, data forms an expression that is evaluated and added to the end of the error message.

      • +

    • dataElement - if defined, the error message is linked to this data element.

      • +
    • +

  • `CREATEEVENT` - Create an event within the same enrollment.

    +
      +

    • content

      • +

    • data - if defined, contains data values to assign the created event. The format is <uid>:<data value>. Where several values is specified, these are separated with comma.

      +
      AcMrnleqHqc:100,AqK1IHqCkEE:'Polyhydramnios'
      • +

    • programStage - must be defined, and designates the program stage that the rule shall create an event of.

      • +
    • +

  • `SETMANDATORYFIELD` - Set a field to be mandatory.

    +
      +

    • dataElement - if defined, this data element will be set to be mandatory in the data entry form.

      • +

    • trackedEntityAttribute - if defined, this tracked entity attribute will be set to mandatory in the registration form or profile.

      • +
    • +

  • `SENDMESSAGE` - To send message at completion of event/enrollment or at data value update.

    +
      +

    • messageTemplate - if defined, this template will be delivered either as SMS or EMAIL depending upon DeliveryChannel value in message template.

      • +
    • +

  • `SCHEDULEMESSAGE` - To schedule message at completion of event/enrollment or at data value update.

    +
      +

    • messageTemplate - if defined, this template will be delivered either as SMS or EMAIL depending upon DeliveryChannel value in message template.

      • +

    • Date to send message - Expression which is going to be used for evaluation of scheduled date. This expression should result in Date, any other resultant will be discarded and notification will not get scheduled.

      • +
    • +
Compulsory
locationUsed for actionType DISPLAYKEYVALUEPAIR and DISPLAYTEXT to designate which widget to display the text or keyvaluepair in. Compulsory for DISPLAYKEYVALUEPAIR and DISPLAYTEXT.See description
contentUsed for user messages in the different actions. See the actionType overview for a detailed explanation for how it is used in each of the action types. Compulsory for SHOWWARNING, SHOWERROR, WARNINGONCOMPLETION, ERRORONCOMPLETION, DISPLAYTEXT and DISPLAYKEYVALUEPAIR. Optional for HIDEFIELD and ASSIGN.See description
dataUsed for expressions in the different actions. See the actionType overview for a detailed explanation for how it is used in each of the action types. Compulsory for ASSIGN. Optional for SHOWWARNING, SHOWERROR, WARNINGONCOMPLETION, ERRORONCOMPLETION, DISPLAYTEXT, CREATEEVENT and DISPLAYKEYVALUEPAIRSee description
dataElementUsed for linking rule actions to dataElements. See the actionType overview for a detailed explanation for how it is used in each of the action types. Optional for SHOWWARNING, SHOWERROR, WARNINGONCOMPLETION, ERRORONCOMPLETION, ASSIGN and HIDEFIELDSee description
trackedEntity- AttributeUsed for linking rule actions to trackedEntityAttributes. See the actionType overview for a detailed explanation for how it is used in each of the action types. Optional for SHOWWARNING, SHOWERROR and HIDEFIELD.See description
optionUsed for linking rule actions to options. See the actionType overview for a detailed explanation for how it is used in each of the action types. Optional for HIDEOPTIONSee description
optionGroupUsed for linking rule actions to optionGroups. See the actionType overview for a detailed explanation for how it is used in each of the action types. Compulsory for SHOWOPTIONGROUP, HIDEOPTIONGROUP.See description
programStageOnly used for CREATEEVENT rule actions. Compulsory for CREATEEEVENT.See description
programStage- SectionOnly used for HIDESECTION rule actions. Compulsory for HIDESECTIONSee description
+ +#### Program rule variable model details { #program-rule-variable-model-details } + +The following table gives a detailed overview over the programRuleVariable model. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
programRuleVariable
namedescriptionCompulsory
namethe name for the programRuleVariable - this name is used in expressions. +
#{myVariable} > 5
Compulsory
sourceTypeDefines how this variable is populated with data from the enrollment and events. +
    +

  • DATAELEMENT_NEWEST_EVENT_PROGRAM_STAGE - In tracker capture, gets the newest value that exists for a data element, within the events of a given program stage in the current enrollment. In event capture, gets the newest value among the 10 newest events on the organisation unit.

    • +

  • DATAELEMENT_NEWEST_EVENT_PROGRAM - In tracker capture, get the newest value that exists for a data element across the whole enrollment. In event capture, gets the newest value among the 10 newest events on the organisation unit.

    • +

  • DATAELEMENT_CURRENT_EVENT - Gets the value of the given data element in the current event only.

    • +

  • DATAELEMENT_PREVIOUS_EVENT - In tracker capture, gets the newest value that exists among events in the program that precedes the current event. In event capture, gets the newvest value among the 10 preceeding events registered on the organisation unit.

    • +

  • CALCULATED_VALUE - Used to reserve a variable name that will be assigned by a ASSIGN program rule action

    • +

  • TEI_ATTRIBUTE - Gets the value of a given tracked entity attribute

    • +
Compulsory
dataElementUsed for linking the programRuleVariable to a dataElement. Compulsory for all sourceTypes that starts with DATAELEMENT_.See description
trackedEntity- AttributeUsed for linking the programRuleVariable to a trackedEntityAttribute. Compulsory for sourceType TEI_ATTRIBUTE.See description
useCodeFor- OptionSetIf checked, the variable will be populated with the code - not the name - from any linked option set. Default is unchecked, meaning that the name of the option is populated.
programStageUsed for specifying a specific program stage to retreive the programRuleVariable value from. Compulsory for DATAELEMENT_NEWEST_EVENT_PROGRAM_STAGE.See description
+ +### Creating program rules { #webapi_creating_program_rules } + +- To perform crud operations, `programRules` resource is available in API. + +To retrieve list of programRules you can do a GET request like this: + + /api/programRules + +To retrieve single programRule you can do a GET request like this: + + /api/programRules/ + +To save/add single programRule you can do a POST request like this: + + /api/programRules/ + +To update single programRule you can do a PUT request like this: + + /api/programRules/ + +To delete single programRule you can do a DELETE request like this: + + /api/programRules/ + +To retrieve description of programRule condition you can use POST and provide condition string in the POST body. + + /api/programRules/condition/description? + +## Forms { #webapi_forms } + +To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form response is accessible as XML and JSON and will provide information about each section (group) in the form as well as each field in the sections, including labels and identifiers. By supplying period and organisation unit identifiers the form response will be populated with data values. + + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + +
Form query parameters
ParameterOptionDescription
peISO periodPeriod for which to populate form data values.
ouUIDOrganisation unit for which to populate form data values.
metaDatafalse | trueWhether to include metadata about each data element of form sections.
+ +To retrieve the form for a data set you can do a GET request like this: + + /api/dataSets//form.json + +To retrieve the form for the data set with identifier "BfMAe6Itzgt" in XML: + + /api/dataSets/BfMAe6Itzgt/form + +To retrieve the form including metadata in JSON: + + /api/dataSets/BfMAe6Itzgt/form.json?metaData=true + +To retrieve the form filled with data values for a specific period and organisation unit in XML: + + /api/dataSets/BfMAe6Itzgt/form.xml?ou=DiszpKrYNg8&pe=201401 + +When it comes to custom data entry forms, this resource also allows for creating such forms directly for a data set. This can be done through a POST or PUT request with content type text/html where the payload is the custom form markup such as: + +```bash +curl -d @form.html "localhost/api/dataSets/BfMAe6Itzgt/form" + -H "Content-Type:text/html" -u admin:district -X PUT +``` + +## Documents { #webapi_documents } + +References to files can be stored with the document resource. + + + ++++ + + + + + + + + + + + + + + + + + + + + +
Document fields
Field nameDescription
nameunique name of document
externalflag identifying the location of the document. TRUE for external files, FALSE for internal ones
urlthe location of the file. URL for external files. File resource id for internal ones (see File resources)
+ +A GET request to the documents endpoint will return all documents: + + /api/documents + +A POST request to the documents endpoint will create a new document: + +```bash +curl -X POST -d @document.json -H "Content-type: application/json" + "http://dhis.domain/api/documents" +``` + +```json +{ + "name": "dhis home", + "external": true, + "url": "https://www.dhis2.org" +} +``` + +A GET request with the id of a document appended will return information about the document. A PUT request to the same endpoint will update the fields of the document: + + /api/documents/ + +Appending _/data_ to the GET request will return the actual file content of the document: + + /api/documents//data + +## CSV metadata import { #webapi_csv_metadata_import } + +DHIS2 supports import of metadata in the CSV format, such as data elements, organisation units and validation rules. Properties for the various metadata objects are identified based on the column order/column index (see below for details). You can omit non-required object properties/columns, but since the column order is significant, an empty column must be included. In other words, if you would like to specify properties/columns which appear late in the column order but not specify certain columns which appear early in the order you can include empty/blank columns for them. + +The first row of the CSV file is considered to be a header and is ignored during import. The _comma_ character should be used as a text delimiter. Text which contains commas must be enclosed in _double quotes_. + +To upload metadata in CSV format you can make a POST request to the metadata endpoint: + + POST /api/metadata?classKey=CLASS-KEY + +The following object types are supported. The `classKey` query parameter is mandatory and can be found next to each object type in the table below. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Object types and keys
Object typeClass key
Data elementsDATA_ELEMENT
Data element groupsDATA_ELEMENT_GROUP +
Category optionsCATEGORY_OPTION
Category option groupsCATEGORY_OPTION_GROUP
Organisation unitsORGANISATION_UNIT
Organisation unit groupsORGANISATION_UNIT_GROUP
Validation rulesVALIDATION_RULE
Option setsOPTION_SET
TranslationsTRANSLATION
+ +> **Tip** +> +> If using _curl_, the `--data-binary` option should be used as it preserves line breaks and newlines, which is essential for CSV data. + +As an example, to upload a file of data elements in CSV format with `curl` you can use the following command: + +```bash +curl --data-binary @data_elements.csv "http://localhost/api/metadata?classKey=DATA_ELEMENT" + -H "Content-Type:application/csv" -u admin:district +``` + +The formats for the currently supported object types for CSV import are listed in the following sections. + +### Data elements { #webapi_csv_data_elements } + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Data Element CSV Format
IndexColumnRequiredValue (default first)Description
1NameYesName. Max 230 char. Unique.
2UIDNoUIDStable identifier. Exactly 11 alpha-numeric characters, beginning with a character. Will be generated by system if not specified.
3CodeNoStable code. Max 50 char.
4Short nameNo50 first char of nameWill fall back to first 50 characters of name if unspecified. Max 50 char. Unique.
5DescriptionNoFree text description.
6Form nameNoMax 230 char.
7Domain typeNoAGGREGATE | TRACKERDomain type for data element, can be aggregate or tracker. Max 16 char.
8Value typeNoINTEGER | NUMBER | UNIT_INTERVAL | PERCENTAGE | INTEGER_POSITIVE | INTEGER_NEGATIVE | INTEGER_ZERO_OR_POSITIVE | FILE_RESOURCE | COORDINATE |TEXT | LONG_TEXT | LETTER | PHONE_NUMBER | EMAIL | BOOLEAN | TRUE_ONLY | DATE | DATETIMEValue type. Max 16 char.
9Aggregation typeNoSUM | AVERAGE | AVERAGE_SUM_ORG_UNIT | COUNT | STDDEV | VARIANCE | MIN | MAX | NONEAggregation type indicating how to aggregate data in various dimensions. Max 16 char.
10Category combinationNoUIDUID of category combination. Will default to default category combination if not specified.
11UrlNoURL to data element resource. Max 255 char.
12Zero is significantNofalse | trueIndicates whether zero values will be stored for this data element.
13Option setNoUIDUID of option set to use for data.
14Comment option setNoUIDUID of option set to use for comments.
+ +An example of a CSV file for data elements can be seen below. The first row will always be ignored. Note how you can skip columns and rely on default values to be used by the system. You can also skip columns which you do not use which appear to the right of the ones + +```csv +name,uid,code,shortname,description +"Women participated skill development training",,"D0001","Women participated in training" +"Women participated community organizations",,"D0002","Women participated in organizations" +``` + +### Organisation units { #webapi_csv_org_units } + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Organisation Unit CSV Format
IndexColumnRequiredValue (default first)Description
1NameYesName. Max 230 characters. Unique.
2UIDNoUIDStable identifier. Max 11 char. Will be generated by system if not specified.
3CodeNoStable code. Max 50 char.
4ParentNoUIDUID of parent organisation unit.
5Short nameNo50 first char of nameWill fall back to first 50 characters of name if unspecified. Max 50 characters. Unique.
6DescriptionNoFree text description.
7Opening dateNo1970-01-01Opening date of organisation unit in YYYY-MM-DD format.
8Closed dateNoClosed date of organisation unit in YYYY-MM-DD format, skip if currently open.
9CommentNoFree text comment for organisation unit.
10Feature typeNoNONE | MULTI_POLYGON | POLYGON | POINT | SYMBOLGeospatial feature type.
11CoordinatesNoCoordinates used for geospatial analysis in Geo JSON format.
12URLNoURL to organisation unit resource. Max 255 char.
13Contact personNoContact person for organisation unit. Max 255 char.
14AddressNoAddress for organisation unit. Max 255 char.
15EmailNoEmail for organisation unit. Max 150 char.
16Phone numberNoPhone number for organisation unit. Max 150 char.
+ +A minimal example for importing organisation units with a parent unit looks like this: + +```csv +name,uid,code,parent +"West province",,"WESTP","ImspTQPwCqd" +"East province",,"EASTP","ImspTQPwCqd" +``` + +### Validation rules { #webapi_csv_validation_rules } + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Validation Rule CSV Format
IndexColumnRequiredValue (default first)Description
1NameYesName. Max 230 characters. Unique.
2UIDNoUIDStable identifier. Max 11 char. Will be generated by system if not specified.
3CodeNoStable code. Max 50
4DescriptionNoFree text description.
5InstructionNoFree text instruction.
6ImportanceNoMEDIUM | HIGH | LOWImportance of validation rule.
7Rule type (ignored)NoVALIDATION | SURVEILLANCEType of validation rule.
8OperatorNoequal_to | not_equal_to | greater_than | greater_than_or_equal_to | less_than | less_than_or_equal_to | compulsory_pair | exclusive_pairExpression operator.
9Period typeNoMonthly | Daily | Weekly | Quarterly | SixMontly | YearlyPeriod type.
10Left side expressionYesMathematical formula based on data element and option combo UIDs.
11Left side expression descriptionYesFree text.
12Left side missing value strategyNoSKIP_IF_ANY_VALUE_MISSING | SKIP_IF_ALL_VALUES_MISSING | NEVER_SKIPBehavior in case of missing values in left side expression.
13Right side expressionYesMathematical formula based on data element and option combo UIDs.
14Right side expression descriptionYesFree text.
15Right side missing value strategyNoSKIP_IF_ANY_VALUE_MISSING | SKIP_IF_ALL_VALUES_MISSING | NEVER_SKIPBehavior in case of missing values in right side expression.
+ +### Option sets { #webapi_csv_option_sets } + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Option Set CSV Format
IndexColumnRequiredValue (default first)Description
1OptionSetNameYesName. Max 230 characters. Unique. Should be repeated for each option.
2OptionSetUIDNoUIDStable identifier. Max 11 char. Will be generated by system if not specified. Should be repeated for each option.
3OptionSetCodeNoStable code. Max 50 char. Should be repeated for each option.
4OptionNameYesOption name. Max 230 characters.
5OptionUIDNoUIDStable identifier. Max 11 char. Will be generated by system if not specified.
6OptionCodeYesStable code. Max 50 char.
+ +The format for option sets is special. The three first values represent an option set. The three last values represent an option. The first three values representing the option set should be repeated for each option. + +```csv +optionsetname,optionsetuid,optionsetcode,optionname,optionuid,optioncode +"Color",,"COLOR","Blue",,"BLUE" +"Color",,"COLOR","Green",,"GREEN" +"Color",,"COLOR","Yellow",,"YELLOW" +"Sex",,,"Male",,"MALE" +"Sex",,,"Female",,"FEMALE" +"Sex",,,"Unknown",,"UNKNOWN" +"Result",,,"High",,"HIGH" +"Result",,,"Medium",,"MEDIUM" +"Result",,,"Low",,"LOW" +"Impact","cJ82jd8sd32","IMPACT","Great",,"GREAT" +"Impact","cJ82jd8sd32","IMPACT","Medium",,"MEDIUM" +"Impact","cJ82jd8sd32","IMPACT","Poor",,"POOR" +``` + +### Option group { #option-group } + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Option Group CSV Format
IndexColumnRequiredValue (default first)Description
1OptionGroupNameYesName. Max 230 characters. Unique. Should be repeated for each option.
2OptionGroupUidNoStable identifier. Max 11 char. Will be generated by system if not specified. Should be repeated for each option.
3OptionGroupCodeNoStable code. Max 50 char. Should be repeated for each option.
4OptionGroupShortNameYesShort Name. Max 50 characters. Unique. Should be repeated for each option.
5OptionSetUidYesStable identifier. Max 11 char. Should be repeated for each option.
6OptionUidNoStable identifier. Max 11 char.
7OptionCodeNoStable code. Max 50 char.
+ +Sample OptionGroup CSV payload + +```csv +optionGroupName,optionGroupUid,optionGroupCode,optionGroupShortName,optionSetUid,optionUid,optionCode +optionGroupA,,,groupA,xmRubJIhmaK,,OptionA +optionGroupA,,,groupA,xmRubJIhmaK,,OptionB +optionGroupB,,,groupB,QYDAByFgTr1,,OptionC +``` + +### Option Group Set { #option-group-set } + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Option Group Set CSV Format
IndexColumnRequiredValue (default first)Description
1OptionGroupSetNameYesName. Max 230 characters. Unique. Should be repeated for each option.
2OptionGroupSetUidNoStable identifier. Max 11 char. Will be generated by system if not specified. Should be repeated for each option.
3OptionGroupSetCodeNoStable code. Max 50 char. Should be repeated for each option.
4OptionGroupSetDescriptionNoDescription. Should be repeated for each option.
5DataDimensionNoTRUE, FALSE
6OptionSetUidNoOptionSet UID. Stable identifier. Max 11 char.
+ +Sample OptionGroupSet CSV payload + +```csv +name,uid,code,description,datadimension,optionsetuid +optiongroupsetA,,,,,xmRubJIhmaK +optiongroupsetB,,,,false,QYDAByFgTr1 +``` + +To add OptionGroups to an imported OptionGroupSet, follow the steps as importing collection membership + +### Collection membership { #collection-membership } + +In addition to importing objects, you can also choose to only import the group-member relationship between an object and a group. Currently, the following group and object pairs are supported + +- Organisation Unit Group - Organisation Unit + +- Data Element Group - Data Element + +- Indicator Group - Indicator + +- Option Group Set - Option Group + +The CSV format for these imports are the same + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + +
Collection membership CSV Format
IndexColumnRequiredValue (default first)Description
1UIDYesUIDThe UID of the collection to add an object to
2UIDYesUIDThe UID of the object to add to the collection
+ +### Other objects { #webapi_csv_other_objects } + + + +++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Data Element Group, Category Option, Category Option Group, Organisation Unit Group CSV Format
IndexColumnRequiredValue (default first)Description
1NameYesName. Max 230 characters. Unique.
2UIDNoUIDStable identifier. Max 11 chars. Will be generated by system if not specified.
3CodeNoStable code. Max 50 char.
4Short nameNoShort name. Max 50 characters.
+ +An example of category options looks like this: + +```csv +name,uid,code,shortname +"Male",,"MALE" +"Female",,"FEMALE" +``` + +## Deleted objects { #webapi_deleted_objects } + +The deleted objects resource provides a log of metadata objects being deleted. + + /api/deletedObjects + +Whenever an object of type metadata is deleted, a log is being kept of the uid, code, the type and the time of when it was deleted. This API is available at `/api/deletedObjects` field filtering and object filtering works similarly to other metadata resources. + +Get deleted objects of type data elements: + + GET /api/deletedObjects.json?klass=DataElement + +Get deleted object of type indicator which was deleted in 2015 and forward: + + GET /api/deletedObjects.json?klass=Indicator&deletedAt=2015-01-01 + +## Favorites { #webapi_favorites } + +Certain types of metadata objects can be marked as favorites for the currently logged in user. This applies currently for dashboards. + + /api/dashboards//favorite + +To make a dashboard a favorite you can make a _POST_ request (no content type required) to a URL like this: + + /api/dashboards/iMnYyBfSxmM/favorite + +To remove a dashboard as a favorite you can make a _DELETE_ request using the same URL as above. + +The favorite status will appear as a boolean _favorite_ field on the object (e.g. the dashboard) in the metadata response. + +## Subscriptions { #webapi_subscription } + +A logged user can subscribe to certain types of objects. Currently subscribable objects are those of type Chart, EventChart, EventReport, Map, ReportTable and Visualization. + +> **Note** +> +> The Chart and ReportTable objects are deprecated. Use Visualization instead. + +To get the subscribers of an object (return an array of user IDs) you can make a _GET_ request: + + /api///subscribers + +See example as follows: + + /api/charts/DkPKc1EUmC2/subscribers + +To check whether the current user is subscribed to an object (returns a boolean) you can perform a _GET_ call: + + /api///subscribed + +See example as follows: + + /api/charts/DkPKc1EUmC2/subscribed + +To subscribe/de-subscribe to an object you perform a _POST/DELETE_ request (no content type required): + + /api///subscriber + +## File resources { #webapi_file_resources } + +_File resources_ are objects used to represent and store binary content. The _FileResource_ object itself contains the file meta-data (name, Content-Type, size, etc.) as well as a key allowing retrieval of the contents from a database-external file store. The _FileResource_ object is stored in the database like any other but the content (file) is stored elsewhere and is retrievable using the contained reference _(storageKey)_. + + /api/fileResources + +The contents of file resources are not directly accessible but are referenced from other objects (such as data values) to store binary content of virtually unlimited size. + +To create a file resource that does not require a corresponding data value, POST to the endpoint `/api/fileResources` with a multipart upload: + +```bash +curl "https://server/api/fileResources" -X POST + -F "file=@/path/to/file/name-of-file.png" +``` + +To create both a file resource and a data value that references the file, POST to the `/api/dataValues/file` endpoint in DHIS 2.36 or later: + +```bash +curl "https://server/api/dataValues/file?de=xPTAT98T2Jd + &pe=201301&ou=DiszpKrYNg8&co=Prlt0C1RF0s" -X POST + -F "file=@/path/to/file/name-of-file.png" +``` + +For the `api/fileResources` endpoint, the only form parameter required is _file_, which is the file to upload. For the `api/dataValues/file` endpoint, the parameters required are the same as for a post to `api/dataValues`, with the addition of _file_. + +The filename and content-type should also be included in the request but will be replaced with defaults when not supplied. + +On successfully creating a file resource the returned data will contain a `response` field which in turn contains the `fileResource` like this: + +```json +{ + "httpStatus": "Accepted", + "httpStatusCode": 202, + "status": "OK", + "response": { + "responseType": "FileResource", + "fileResource": { + "name": "name-of-file.png", + "created": "2015-10-16T16:34:20.654+0000", + "lastUpdated": "2015-10-16T16:34:20.667+0000", + "externalAccess": false, + "publicAccess": "--------", + "user": { ... }, + "displayName": "name-of-file.png", + "contentType": "image/png", + "contentLength": 512571, + "contentMd5": "4e1fc1c3f999e5aa3228d531e4adde58", + "storageStatus": "PENDING", + "id": "xm4JwRwke0i" + } + } +} +``` + +Note that the response is a _202 Accepted_, indicating that the returned resource has been submitted for background processing (persisting to the external file store in this case). Also, note the `storageStatus` field which indicates whether the contents have been stored or not. At this point, the persistence to the external store is not yet finished (it is likely being uploaded to a cloud-based store somewhere) as seen by the `PENDING` status. + +Even though the content has not been fully stored yet the file resource can now be used, for example as referenced content in a data value (see [Working with file data values](#datavalue_file)). If we need to check the updated _storageStatus_ or otherwise retrieve the metadata of the file, the `fileResources` endpoint can be queried. + +```bash +curl "https://server/api/fileResources/xm4JwRwke0i" -H "Accept: application/json" +``` + +This request will return the `FileResource` object as seen in the response of the above example. + +### File resource constraints { #webapi_file_resources_constraints } + +- File resources _must_ be referenced (assigned) from another object in order to be persisted in the long term. A file resource which is created but not referenced by another object such as a data value is considered to be in _staging_. Any file resources which are in this state and are older than _two hours_ will be marked for deletion and will eventually be purged from the system. + +- The ID returned by the initial creation of the file resource is not retrievable from any other location unless the file resource has been referenced (in which the ID will be stored as the reference), so losing it will require the POST request to be repeated and a new object to be created. The _orphaned_ file resource will be cleaned up automatically. + +- File resource objects are _immutable_, meaning modification is not allowed and requires creating a completely new resource instead. + +### File resource blocklist { #file-resource-blocklist } + +Certain types of files are blocked from being uploaded for security reasons. + +The following content types are blocked. + +| Content type | Content type | +| --- | --- | +| text/html | application/x-ms-dos-executable | +| text/css | application/vnd.microsoft.portable-executable | +| text/javascript | application/vnd.apple.installer+xml | +| font/otf | application/vnd.mozilla.xul+xml | +| application/x-shockwave-flash | application/x-httpd-php | +| application/vnd.debian.binary-package | application/x-sh | +| application/x-rpm | application/x-csh | +| application/java-archive | | + +The following file extensions are blocked. + +| File extension | File extension | File extension | +| -------------- | -------------- | -------------- | +| html | deb | xul | +| htm | rpm | php | +| css | jar | bin | +| js | jsp | sh | +| mjs | exe | csh | +| otf | msi | bat | +| swf | mpkg | | + +## Metadata versioning { #webapi_metadata_versioning } + +This section explains the Metadata Versioning APIs available starting 2.24 + +- `/api/metadata/version`: This endpoint will return the current metadata version of the system on which it is invoked. + + + +++++ + + + + + + + + + + + + + + +
Query Parameters
NameRequiredDescription
versionNamefalseIf this parameter is not specified, it will return the current version of the system or otherwise it will return the details of the versionName passed as parameter. (versionName is of the syntax "Version_<id>"
+ +### Get metadata version examples { #webapi_metadata_versioning_examples } + +**Example:** Get the current metadata version of this system + +Request: + +``` +/api/metadata/version +``` + +Response: + +```json +{ + "name": "Version_4", + "created": "2016-06-30T06:01:28.684+0000", + "lastUpdated": "2016-06-30T06:01:28.685+0000", + "externalAccess": false, + "displayName": "Version_4", + "type": "BEST_EFFORT", + "hashCode": "848bf6edbaf4faeb7d1a1169445357b0", + "id": "Ayz2AEMB6ry" +} +``` + +**Example:** Get the details of version with name "Version_2" + +Request: + +``` +/api/metadata/version?versionName=Version_2 +``` + +Response: + +```json +{ + "name": "Version_2", + "created": "2016-06-30T05:59:33.238+0000", + "lastUpdated": "2016-06-30T05:59:33.239+0000", + "externalAccess": false, + "displayName": "Version_2", + "type": "BEST_EFFORT", + "hashCode": "8050fb1a604e29d5566675c86d02d10b", + "id": "SaNyhusVxBG" +} +``` + +- `/api/metadata/version/history`: This endpoint will return the list of all metadata versions of the system on which it is invoked. + + + +++++ + + + + + + + + + + + + + + +
Query Parameters

Name

Required

Description

baseline

false

If this parameter is not specified, it will return list of all metadata versions. Otherwise we need to pass a versionName parameter of the form "Version_<id>". It will then return the list of versions present in the system which were created after the version name supplied as the query parameter.

+ +### Get the list of all metadata versions { #webapi_get_list_of_metadata_versions } + +**Example:** Get the list of all versions in this system + +Request: + +``` +/api/metadata/version/history +``` + +Response: + +```json +{ + "metadataversions": [ + { + "name": "Version_1", + "type": "BEST_EFFORT", + "created": "2016-06-30T05:54:41.139+0000", + "id": "SjnhUp6r4hG", + "hashCode": "fd1398ff7ec9fcfd5b59d523c8680798" + }, + { + "name": "Version_2", + "type": "BEST_EFFORT", + "created": "2016-06-30T05:59:33.238+0000", + "id": "SaNyhusVxBG", + "hashCode": "8050fb1a604e29d5566675c86d02d10b" + }, + { + "name": "Version_3", + "type": "BEST_EFFORT", + "created": "2016-06-30T06:01:23.680+0000", + "id": "FVkGzSjAAYg", + "hashCode": "70b779ea448b0da23d8ae0bd59af6333" + } + ] +} +``` + +**Example:** Get the list of all versions in this system created after "Version_2" + +Request: + +``` +/api/metadata/version/history?baseline=Version_2 +``` + +Response: + +```json +{ + "metadataversions": [ + { + "name": "Version_3", + "type": "BEST_EFFORT", + "created": "2016-06-30T06:01:23.680+0000", + "id": "FVkGzSjAAYg", + "hashCode": "70b779ea448b0da23d8ae0bd59af6333" + }, + { + "name": "Version_4", + "type": "BEST_EFFORT", + "created": "2016-06-30T06:01:28.684+0000", + "id": "Ayz2AEMB6ry", + "hashCode": "848bf6edbaf4faeb7d1a1169445357b0" + } + ] +} +``` + +- `/api/metadata/version/create`: This endpoint will create the metadata version for the version type as specified in the parameter. + + + +++++ + + + + + + + + + + + + + + +
Query Parameters

Name

Required

Description

type

true

The type of metadata version which needs to be created.

+
    +

  • BEST_EFFORT

    • +

  • ATOMIC

    • +
+ +Users can select the type of metadata which needs to be created. Metadata Version type governs how the importer should treat the given version. This type will be used while importing the metadata. There are two types of metadata. + +- _BEST_EFFORT_: This type suggests that missing references can be ignored and the importer can continue importing the metadata (e.g. missing data elements on a data element group import). + +- _ATOMIC_: This type ensures a strict type checking of the metadata references and the metadata import will fail if any of the references do not exist. + +> **Note** +> +> It's recommended to have an ATOMIC type of versions to ensure that all systems (central and local) have the same metadata. Any missing reference is caught in the validation phase itself. Please see the importer details for a full explanation. + +### Create metadata version { #webapi_create_metadata_version } + +**Example:** Create metadata version of type `BEST_EFFORT` + +Request: + +```bash +curl -X POST -u admin:district "https://play.dhis2.org/dev/api/metadata/version/create?type=BEST_EFFORT" +``` + +Response: + +```json +{ + "name": "Version_1", + "created": "2016-06-30T05:54:41.139+0000", + "lastUpdated": "2016-06-30T05:54:41.333+0000", + "externalAccess": false, + "publicAccess": "--------", + "user": { + "name": "John Traore", + "created": "2013-04-18T17:15:08.407+0000", + "lastUpdated": "2016-04-06T00:06:06.571+0000", + "externalAccess": false, + "displayName": "John Traore", + "id": "xE7jOejl9FI" + }, + "displayName": "Version_1", + "type": "BEST_EFFORT", + "hashCode": "fd1398ff7ec9fcfd5b59d523c8680798", + "id": "SjnhUp6r4hG" +} +``` + +- `/api/metadata/version/{versionName}/data`: This endpoint will download the actual metadata specific to the version name passed as path parameter. + +- `/api/metadata/version/{versionName}/data.gz`: This endpoint will download the actual metadata specific to the version name passed as path parameter in a compressed format (gzipped). + + + +++++ + + + + + + + + + + + + + + +
Path parameters

Name

Required

Description

versionName

true

Path parameter of the form "Version_<id>" so that the API downloads the specific version

+ +### Download version metadata { #webapi_download_version_metadata } + +**Example:** Get the actual metadata for "Version 5" + +Request: + +```bash +curl -u admin:district "https://play.dhis2.org/dev/api/metadata/version/Version_5/data" +``` + +Response: + +```json +{ + "date": "2016-06-30T06:10:23.120+0000", + "dataElements": [ + { + "code": "ANC 5th Visit", + "created": "2016-06-30T06:10:09.870+0000", + "lastUpdated": "2016-06-30T06:10:09.870+0000", + "name": "ANC 5th Visit", + "id": "sCuZKDsix7Y", + "shortName": "ANC 5th Visit ", + "aggregationType": "SUM", + "domainType": "AGGREGATE", + "zeroIsSignificant": false, + "valueType": "NUMBER", + "categoryCombo": { + "id": "p0KPaWEg3cf" + }, + "user": { + "id": "xE7jOejl9FI" + } + } + ] +} +``` + +## Metadata Synchronization { #webapi_metadata_synchronization } + +This section explains the Metadata Synchronization API available starting 2.24 + +- `/api/metadata/sync`: This endpoint performs metadata sync of the version name passed in the query parameter by downloading and importing the specified version from the remote server as defined in the settings app. + + + +++++ + + + + + + + + + + + + + + +
Query parameters

Name

Required

Description

versionName

true

versionName query parameter of the form "Version_<id>" . The api downloads this version from the remote server and imports it in the local system.

+ +- This API should be used with utmost care. Please note that there is an alternate way to achieve sync in a completely automated manner by leveraging the Metadata Sync Task from the "Data Administration" app. See Chapter 22, Section 22.17 of User Manual for more details regarding Metadata Sync Task. + +- This sync API can alternatively be used to sync metadata for the versions which have failed from the metadata sync scheduler. Due to its dependence on the given metadata version number, care should be taken for the order in which this gets invoked. E.g. If this api is used to sync some higher version from the central instance, then the sync might fail as the metadata dependencies are not present in the local instance. + +- Assume the local instance is at `Version_12` and if this endpoint is used to sync `Version_15` (of type `BEST_EFFORT`) from the central instance, the scheduler will start syncing metadata from `Version_16`. So the local instance will not have the metadata versions between `Version_12` and `Version_15`. You need to manually sync the missing versions using these endpoints only. + +### Sync metadata version { #webapi_metadata_synchronization_version } + +**Example:** Sync Version_6 from central system to this system + +Request: + +```bash +curl -u admin:district "https://play.dhis2.org/dev/api/metadata/sync?versionName=Version_6" +``` + +## Metadata repository { #webapi_metadata_repository } + +DHIS2 provides a metadata repository containing metadata packages with various content. A metadata package is a DHIS2-compliant JSON document which describes a set of metadata objects. + +To retrieve an index over available metadata packages you can issue a GET request to the _metadataRepo_ resource: + + GET /api/synchronization/metadataRepo + +A metadata package entry contains information about the package and a URL to the relevant package. An index could look like this: + +```json +{ + "packages": [ + { + "id": "sierre-leone-demo", + "name": "Sierra Leone demo", + "description": "Sierra Leone demo database", + "version": "0.1", + "href": "https://dhis2.org/metadata-repo/221/sierra-leone-demo/metadata.json" + }, + { + "id": "trainingland-org-units", + "name": "Trainingland organisation units", + "description": "Trainingland organisation units with four levels", + "version": "0.1", + "href": "https://dhis2.org/metadata-repo/221/trainingland-org-units/metadata.json" + } + ] +} +``` + +A client can follow the URLs and install a metadata package through a POST request with content type _text/plain_ with the metadata package URL as the payload to the _metadataPull_ resource: + + POST /api/synchronization/metadataPull + +An example curl command looks like this: + +```bash +curl "localhost:8080/api/synchronization/metadataPull" -X POST + -d "https://dhis2.org/metadata-repo/221/trainingland-org-units/metadata.json" + -H "Content-Type:text/plain" -u admin:district +``` diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-gist-md index 5d6e3cfc6..a7bd59912 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-gist-md @@ -120,7 +120,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -683,7 +683,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md index 044e693bb..7cb030a85 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md @@ -1270,7 +1270,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -1760,7 +1760,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2027,7 +2027,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md index 3119ff610..05eeb0bc3 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md @@ -1002,7 +1002,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__sharing-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__sharing-md index 7369ddae2..bedf1c056 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__sharing-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__sharing-md @@ -6,7 +6,7 @@ tags: - Desarrollar --- -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -202,7 +202,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - The sharing solution supports cascade sharing for Dashboard. - This function will copy `userAccesses` and `userGroupAccesses` of a Dashboard to all of its DashboardItem's objects including `Map`, `EventReport`, `EventChart`, `Visualization`. diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md index c5ece918c..7017dbcf9 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md @@ -280,8 +280,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md index d57fccd40..4310e607c 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Analytics { #analytics } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md index 3dafbcb58..3d886e5d7 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Apps { #apps } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md index 18d08b847..76ac28add 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/audit.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md index d964c4e48..29dbe962d 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Data approval { #data-approval } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md index cc346281a..ef03de66b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data.md" revision_date: '2022-04-04' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Data { #data } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md index 662df0bca..bf4c81f34 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-store.md" revision_date: '2022-03-24' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Data store { #data-store } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md index b1c850960..84974de10 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-validation.md" revision_date: '2022-02-23' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md index fc5ef3507..374ac7204 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Email { #email } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md index 3275ea2db..e111f3e9d 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/i18n.md" revision_date: '2022-04-27' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # I18n { #i18n } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md index 084c65c16..c3d216720 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/overview.md" revision_date: '2022-02-28' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Overview { #webapi } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md index c62344e61..bb3c62aa7 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/maintenance.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md index 7f67922c6..24f3b6549 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Messaging { #messaging } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md index c88cd62cc..e5b6b7dab 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/metadata-gist.md" revision_date: '2021-11-23' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Metadata Gist API { #gist_api } @@ -122,7 +122,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -749,7 +749,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md index 259272abd..4c0477ffe 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/metadata.md" revision_date: '2023-08-03' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Metadata { #metadata } @@ -1287,7 +1287,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -1782,7 +1782,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2050,7 +2050,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md index 93943dbcf..ddd26911b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/new-tracker.md" revision_date: '2024-05-21' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # New Tracker { #new-tracker } @@ -1055,7 +1055,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md index 76d191c36..f1efaddf5 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Perfil de la unidad organizativa { #org_unit_profile } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md index b6e859a9a..013a7a618 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/scheduling.md" revision_date: '2022-05-05' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Scheduling { #webapi_scheduling } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md index 43201b335..3eb152de5 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/settings-and-configuration.md" revision_date: '2023-12-14' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md index a738eb4e5..43ae94e4c 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md @@ -2,11 +2,11 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -202,7 +202,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md index 694cf4951..c78abddc7 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # SMS { #sms } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md index e00235c39..c1ce8070f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Sincronización { #webapi_synchronization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md index 22486712e..818fb7d98 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/tracker.md" revision_date: '2024-01-05' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Tracker { #tracker } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md index 88458057f..1c53ad18d 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/users.md" revision_date: '2021-11-04' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Users { #users } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md index 020bead3b..c6e104073 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/visualizations.md" revision_date: '2022-03-24' tags: -- Desarrollar - DHIS core version 2.38 +- Desarrollar --- # Visualizations { #visualizations } @@ -291,8 +291,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-exchange-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-exchange-md index 11ce264f9..fb1a337e4 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-exchange-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-exchange-md @@ -23,7 +23,7 @@ The aggregate data exchange service is suitable for use-cases such as: * Precomputation of tracker data with program indicators saved as aggregate data values. * Data reporting from a national HMIS to a global donor. -### Overview { #overview } +### Visión general { #overview } The aggregate data exchange service allows for data exchange between a *source* instance of DHIS 2 and a *target* instance of DHIS 2. A data exchange can be *external*, for which the target instance is different/external to the source instance. A data exchange can also be *internal*, for which the target instance is the same as the source instance. The aggregate data exchange source can contain multiple source requests, where a source request roughly corresponds to an analytics API request. @@ -348,8 +348,8 @@ The aggregate data exchange data model / payload is described in the following s | Field | Tipo de dato | Mandatory | Descripción | | ------------------------------------------------- | -------------- | ----------- | ------------------------------------------------------------ | | name | Cadena | Sí | Name of aggregate data exchange. Unique. | -| source | Object | Sí | Source for aggregate data exchange. | -| source.params | Object | No | Parameters for source request. | +| source | Objeto | Sí | Source for aggregate data exchange. | +| source.params | Objeto | No | Parameters for source request. | | source.params.periodTypes | Array/String | No | Allowed period types for overriding periods in source request. | | source.requests | Array/Object | Sí | Source requests. | | source.requests.name | Cadena | Sí | Name of source request. | @@ -364,14 +364,14 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.outputDataElementIdScheme | Cadena | No | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output organisation unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | -| source.target | Object | Sí | Target for aggregate data exchange. | +| source.target | Objeto | Sí | Target for aggregate data exchange. | | source.target.type | Cadena | Sí | Type of target, can be `EXTERNAL`, `INTERNAL`. | -| source.target.api | Object | Conditional | Target API information, only mandatory for type `EXTERNAL`. | +| source.target.api | Objeto | Conditional | Target API information, only mandatory for type `EXTERNAL`. | | source.target.api.url | Cadena | Conditional | Base URL of target DHIS 2 instance, do not include the `/api` part. | | source.target.api.accessToken | Cadena | Conditional | Access token (PAT) for target DHIS 2 instance, used for PAT authentication. | | source.target.api.username | Cadena | Conditional | Username for target DHIS 2 instance, used for basic authentication. | | source.target.api.password | Cadena | Conditional | Password for target DHIS 2 instance, used for basic authentication. | -| source.target.request | Object | No | Target request information. | +| source.target.request | Objeto | No | Target request information. | | source.target.request.dataElementIdScheme | Cadena | No | Input data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.orgUnitIdScheme | Cadena | No | Input organisation unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md index 39e809773..13ac58e84 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md @@ -122,7 +122,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -749,7 +749,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md index 6cdd3d448..0d1c3a53b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md @@ -1557,7 +1557,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -2052,7 +2052,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2320,7 +2320,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md index 448c0f91c..6c711c36a 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md @@ -1055,7 +1055,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md index 51337388a..370b8ec13 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md @@ -6,7 +6,7 @@ tags: - DHIS core version 2.39 --- -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -202,7 +202,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md index 329d931ec..b652dd40b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md @@ -294,8 +294,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md index 9c9149331..d7124dad4 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md @@ -23,7 +23,7 @@ The aggregate data exchange service is suitable for use-cases such as: * Precomputation of tracker data with program indicators saved as aggregate data values. * Data reporting from a national HMIS to a global donor. -### Overview { #overview } +### Visión general { #overview } The aggregate data exchange service allows for data exchange between a *source* instance of DHIS 2 and a *target* instance of DHIS 2. A data exchange can be *external*, for which the target instance is different/external to the source instance. A data exchange can also be *internal*, for which the target instance is the same as the source instance. The aggregate data exchange source can contain multiple source requests, where a source request roughly corresponds to an analytics API request. @@ -382,8 +382,8 @@ The aggregate data exchange data model / payload is described in the following s | Field | Tipo de dato | Mandatory | Descripción | | ------------------------------------------------- | -------------- | ----------- | ------------------------------------------------------------ | | name | Cadena | Sí | Name of aggregate data exchange. Unique. | -| source | Object | Sí | Source for aggregate data exchange. | -| source.params | Object | No | Parameters for source request. | +| source | Objeto | Sí | Source for aggregate data exchange. | +| source.params | Objeto | No | Parameters for source request. | | source.params.periodTypes | Array/String | No | Allowed period types for overriding periods in source request. | | source.requests | Array/Object | Sí | Source requests. | | source.requests.name | Cadena | Sí | Name of source request. | @@ -398,14 +398,14 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.outputDataElementIdScheme | Cadena | No | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | -| source.target | Object | Sí | Target for aggregate data exchange. | +| source.target | Objeto | Sí | Target for aggregate data exchange. | | source.target.type | Cadena | Sí | Type of target, can be `EXTERNAL`, `INTERNAL`. | -| source.target.api | Object | Conditional | Target API information, only mandatory for type `EXTERNAL`. | +| source.target.api | Objeto | Conditional | Target API information, only mandatory for type `EXTERNAL`. | | source.target.api.url | Cadena | Conditional | Base URL of target DHIS 2 instance, do not include the `/api` part. | | source.target.api.accessToken | Cadena | Conditional | Access token (PAT) for target DHIS 2 instance, used for PAT authentication. | | source.target.api.username | Cadena | Conditional | Username for target DHIS 2 instance, used for basic authentication. | | source.target.api.password | Cadena | Conditional | Password for target DHIS 2 instance, used for basic authentication. | -| source.target.request | Object | No | Target request information. | +| source.target.request | Objeto | No | Target request information. | | source.target.request.dataElementIdScheme | Cadena | No | Input data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.orgUnitIdScheme | Cadena | No | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md index 786e6afa2..5559371ef 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-validation.md" revision_date: '2023-04-14' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md index eca0d88e3..094d300e3 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Email { #email } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md index bff16f064..ade1de92d 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Overview { #webapi } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md index 7bcb3bc6c..7aeabcbc5 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/maintenance.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index f937cb8f8..e7987ac71 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -122,7 +122,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -749,7 +749,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index def002337..75efd2922 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -294,7 +294,7 @@ objects, is supported as well. Table: Available Operators -| Operator | Types | Value required | Descripción | +| Operador | Types | Value required | Descripción | |---|---|---|---| | eq | string | boolean | integer | float | enum | collection (checks for size) | date | verdadero | Equality | | !eq | string | boolean | integer | float | enum | collection (checks for size) | date | verdadero | Inequality | @@ -471,7 +471,7 @@ using the `:` operator. Table: Property operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | | Include property with name, if it exists. | | [, ...] | Includes a field within either a collection (will be applied to every object in that collection), or just on a single object. | @@ -1563,7 +1563,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -1837,7 +1837,7 @@ The split operation will transfer all of the metadata associations of the source The operation will transfer all data records of the source org unit over to the org unit specified as the primary target, or if not specified, the first specified target org unit. This includes aggregate data values, data approval records, events, tracked entities and more. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -1897,7 +1897,7 @@ The merge operation will transfer all of the metadata associations of the source The specified data value merge strategy defines how data values are handled. For strategy `LAST_UPDATED`, data values for all source org units are transferred over to the target org unit, and in situation where data values exist for the same parameters, the last updated or created data value will be used. This is done to avoid duplication of data. For strategy `DISCARD`, data values are not transferred over to the target org unit, and simply deleted. The specified data approval merge strategy defines how data approval records are handled, and follows the same logic as data values. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -2058,7 +2058,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2326,7 +2326,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -2421,10 +2421,10 @@ Table: Validation Rule CSV Format | 2 | UID | No | UID | Stable identifier. Max 11 char. Will be generated by system if not specified. | | 3 | Code | No || Stable code. Max 50 | | 4 | Descripción | No || Free text description. | -| 5 | Instruction | No || Free text instruction. | +| 5 | Instrucción | No || Free text instruction. | | 6 | Importance | No | MEDIUM | HIGH | LOW | Importance of validation rule. | | 7 | Rule type (ignored) | No | VALIDATION | SURVEILLANCE | Type of validation rule. | -| 8 | Operator | No | equal_to | not_equal_to | greater_than | greater_than_or_equal_to | less_than | less_than_or_equal_to | compulsory_pair | exclusive_pair | Expression operator. | +| 8 | Operador | No | equal_to | not_equal_to | greater_than | greater_than_or_equal_to | less_than | less_than_or_equal_to | compulsory_pair | exclusive_pair | Expression operator. | | 9 | Period type | No | Monthly | Daily | Weekly | Quarterly | SixMontly | Yearly | Period type. | | 10 | Left side expression | Sí || Mathematical formula based on data element and option combo UIDs. | | 11 | Left side expression description | Sí || Free text. | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md index 5359d0ca7..68ec4b68c 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Perfil de la unidad organizativa { #org_unit_profile } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md index 843b7d057..72a81b380 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/scheduling.md" revision_date: '2023-04-14' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Scheduling { #webapi_scheduling } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index 7df394985..8b6b1da19 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-01-26' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md index c118e3d35..117ec4aea 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md @@ -2,11 +2,11 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -202,7 +202,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. @@ -302,7 +302,7 @@ curl -X PATCH -d @payload.json -H "Content-Type: application/json-patch+json" "h | atomic | falso | If this is set to true, then the batch function will stop and not updating any objects if there is an error
Otherwise, if this is false then the function will try to proceed with best effort mode. | -## Validation { #validation } +## Validación { #validation } - All object ID will be validated for existence. - Current User need to have metadata READ/WRITE permission on updating objects. - All existing validations from metadata import service will also be applied. diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md index bf697b1c8..147cb3f7f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # SMS { #sms } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md index 38c048173..85aaedf3e 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker-old.md" revision_date: '2024-02-12' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } @@ -726,7 +726,7 @@ You can use a range of operators for the filtering: Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | @@ -1068,7 +1068,7 @@ You can use a range of operators for the filtering: Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index 6438c6a50..c7dfcd478 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" -revision_date: '2024-05-23' +revision_date: '2024-07-02' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Tracker { #tracker } @@ -1078,7 +1078,7 @@ Mandatory attributes and data values are also checked. Currently, removing manda The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: - Feature type (For geometry) @@ -1397,7 +1397,7 @@ this you can use the page and pageSize query parameters: You can use a range of operators for the filtering: -|Operator| Descripción| +|Operador| Descripción| |---|---| |`EQ`| Equal to| |`GT`| Greater than| @@ -2146,7 +2146,11 @@ This, along with the Program's [Access Level](#webapi_nti_access_level) configur A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured with access level *OPEN* or *AUDITED* , the Owner OrganisationUnit has to be in the user's search scope. For Programs that are configured with access level *PROTECTED* or *CLOSED* , the Owner OrganisationUnit has to be in the user's capture scope to be able to access the corresponding program data for the specific tracked entity. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +When requesting tracked entities without specifying a program, the response will include only tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and one of the following criteria: +- The tracked entity is enrolled in at least one program the user has data access to, and the user has access to the owner organisation unit. +- The tracked entity is not enrolled in any program the user has data access to, but the user has access to the tracked entity registering organisation unit. + +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md index 504834100..0dee5b43c 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/users.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Users { #users } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md index 8700375b9..5cc618936 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Visualizations { #visualizations } @@ -294,8 +294,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md index 40cc725b4..a30ef29c3 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md @@ -945,7 +945,7 @@ The available operators are listed below. Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | !EQ | Not equal to | @@ -1695,7 +1695,7 @@ The available operators are listed below. Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md index 225265365..9e1b26a22 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version 2.41 +- Desarrollar --- # Apps { #apps } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md index d7721dc65..1894c6f66 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Desarrollar - DHIS core version 2.41 +- Desarrollar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md index f5e38b08d..f578c1214 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Desarrollar - DHIS core version 2.41 +- Desarrollar --- # Data approval { #data-approval } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md index f35cda7ea..2b63128ba 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Desarrollar - DHIS core version 2.41 +- Desarrollar --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md index 74ea630d9..b7f892ec3 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md @@ -23,7 +23,7 @@ The aggregate data exchange service is suitable for use-cases such as: * Precomputation of tracker data with program indicators saved as aggregate data values. * Data reporting from a national HMIS to a global donor. -### Overview { #overview } +### Visión general { #overview } The aggregate data exchange service allows for data exchange between a *source* instance of DHIS 2 and a *target* instance of DHIS 2. A data exchange can be *external*, for which the target instance is different/external to the source instance. A data exchange can also be *internal*, for which the target instance is the same as the source instance. The aggregate data exchange source can contain multiple source requests, where a source request roughly corresponds to an analytics API request. @@ -382,8 +382,8 @@ The aggregate data exchange data model / payload is described in the following s | Field | Tipo de dato | Mandatory | Descripción | | ------------------------------------------------- | -------------- | ----------- | ------------------------------------------------------------ | | name | Cadena | Sí | Name of aggregate data exchange. Unique. | -| source | Object | Sí | Source for aggregate data exchange. | -| source.params | Object | No | Parameters for source request. | +| source | Objeto | Sí | Source for aggregate data exchange. | +| source.params | Objeto | No | Parameters for source request. | | source.params.periodTypes | Array/String | No | Allowed period types for overriding periods in source request. | | source.requests | Array/Object | Sí | Source requests. | | source.requests.name | Cadena | Sí | Name of source request. | @@ -398,14 +398,14 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.outputDataElementIdScheme | Cadena | No | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | -| source.target | Object | Sí | Target for aggregate data exchange. | +| source.target | Objeto | Sí | Target for aggregate data exchange. | | source.target.type | Cadena | Sí | Type of target, can be `EXTERNAL`, `INTERNAL`. | -| source.target.api | Object | Conditional | Target API information, only mandatory for type `EXTERNAL`. | +| source.target.api | Objeto | Conditional | Target API information, only mandatory for type `EXTERNAL`. | | source.target.api.url | Cadena | Conditional | Base URL of target DHIS 2 instance, do not include the `/api` part. | | source.target.api.accessToken | Cadena | Conditional | Access token (PAT) for target DHIS 2 instance, used for PAT authentication. | | source.target.api.username | Cadena | Conditional | Username for target DHIS 2 instance, used for basic authentication. | | source.target.api.password | Cadena | Conditional | Password for target DHIS 2 instance, used for basic authentication. | -| source.target.request | Object | No | Target request information. | +| source.target.request | Objeto | No | Target request information. | | source.target.request.dataElementIdScheme | Cadena | No | Input data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.orgUnitIdScheme | Cadena | No | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md index 3885308f8..513ea9461 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md @@ -312,7 +312,7 @@ Each `filter` parameter has the following form: Unary operators are: -| Operator | Descripción | +| Operador | Descripción | | -------- | ----------- | | `null` | value is JSON `null` | | `!null` | value is defined but different to JSON `null` | @@ -321,7 +321,7 @@ Unary operators are: Binary operators are: -| Operator | Descripción | +| Operador | Descripción | | -------- | ----------- | | `eq` | value is equal to the given boolean, number or string | | `!eq`, `ne`, `neq` | value is not equal to the given boolean, number or string | @@ -332,7 +332,7 @@ Binary operators are: Text pattern matching binary operators are: -| Operator | Case Insensitive | Descripción | +| Operador | Case Insensitive | Descripción | | -------- | ---------------- | ----------- | | `like` | `ilike` | value matches the text pattern given | | `!like` | `!ilike` | value does not match the text pattern given | @@ -353,7 +353,7 @@ Otherwise, the value matches string JSON values or mixed types of values. Set operators are: -| Operator | Descripción | +| Operador | Descripción | | -------- | ----------- | | `in` | entry value is textually equal to one of the given values (is in set) | | `!in` | entry value is not textually equal to any of the given values (is not in set) | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md index 3091be218..007dc32a6 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md @@ -47,7 +47,7 @@ Table: Operators | greater_than | Greater than | | greater_than_or_equal_to | Greater than or equal to | | less_than | Less than | -| less_than_or_equal_to | Less than or equal to | +| menor_que_o_igual_que | Less than or equal to | | compulsory_pair | If either side is present, the other must also be | | exclusive_pair | If either side is present, the other must not be | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md index 8d6dde5e7..fb5fb1a0b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md @@ -124,7 +124,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -773,7 +773,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md index e7cb924ea..4c2ff76e9 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md @@ -298,7 +298,7 @@ objects, is supported as well. Table: Available Operators -| Operator | Types | Value required | Descripción | +| Operador | Types | Value required | Descripción | |---|---|---|---| | eq | string | boolean | integer | float | enum | collection (checks for size) | date | verdadero | Equality | | !eq | string | boolean | integer | float | enum | collection (checks for size) | date | verdadero | Inequality | @@ -480,7 +480,7 @@ using the `:` operator. Table: Property operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | | Include property with name, if it exists. | | [, ...] | Includes a field within either a collection (will be applied to every object in that collection), or just on a single object. | @@ -1650,7 +1650,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -1848,7 +1848,7 @@ The following metadata get updated: | Visualization | sorting | Replace any source reference with the target reference as Sorting dimension | -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -1961,7 +1961,7 @@ The merge operation will merge the source indicator types into the target indica The merge operation will transfer all of the indicator metadata associations to the source indicator types over to the target indicator type. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -2162,7 +2162,7 @@ The split operation will transfer all of the metadata associations of the source The operation will transfer all data records of the source org unit over to the org unit specified as the primary target, or if not specified, the first specified target org unit. This includes aggregate data values, data approval records, events, tracked entities and more. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -2222,7 +2222,7 @@ The merge operation will transfer all of the metadata associations of the source The specified data value merge strategy defines how data values are handled. For strategy `LAST_UPDATED`, data values for all source org units are transferred over to the target org unit, and in situation where data values exist for the same parameters, the last updated or created data value will be used. This is done to avoid duplication of data. For strategy `DISCARD`, data values are not transferred over to the target org unit, and simply deleted. The specified data approval merge strategy defines how data approval records are handled, and follows the same logic as data values. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -2383,7 +2383,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2651,7 +2651,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -2746,10 +2746,10 @@ Table: Validation Rule CSV Format | 2 | UID | No | UID | Stable identifier. Max 11 char. Will be generated by system if not specified. | | 3 | Code | No || Stable code. Max 50 | | 4 | Descripción | No || Free text description. | -| 5 | Instruction | No || Free text instruction. | +| 5 | Instrucción | No || Free text instruction. | | 6 | Importance | No | MEDIUM | HIGH | LOW | Importance of validation rule. | | 7 | Rule type (ignored) | No | VALIDATION | SURVEILLANCE | Type of validation rule. | -| 8 | Operator | No | equal_to | not_equal_to | greater_than | greater_than_or_equal_to | less_than | less_than_or_equal_to | compulsory_pair | exclusive_pair | Expression operator. | +| 8 | Operador | No | equal_to | not_equal_to | greater_than | greater_than_or_equal_to | less_than | less_than_or_equal_to | compulsory_pair | exclusive_pair | Expression operator. | | 9 | Period type | No | Monthly | Daily | Weekly | Quarterly | SixMontly | Yearly | Period type. | | 10 | Left side expression | Sí || Mathematical formula based on data element and option combo UIDs. | | 11 | Left side expression description | Sí || Free text. | @@ -3749,7 +3749,7 @@ The response will also contain a `Location` header with a link to the newly-crea The API does allow the optional supplying of a custom prefix, which will be prefixed to the following properties. -| Object | Property | Info | +| Objeto | Property | Info | |------------------|-----------|------------------------------------------| | Programa | name | Help identify the new Program | | ProgramIndicator | name | Database constraint - needs to be unique | @@ -3847,7 +3847,7 @@ A shallow copy in this context means that an existing `Program` property will be All properties below have been deep copied. Anything not in included in this table means that it has been shallow copied. -| Object | Property of | +| Objeto | Property of | |--------------------------------|--------------| | Programa | | | ProgramSection | Programa | @@ -3862,7 +3862,7 @@ All properties below have been deep copied. Anything not in included in this tab > > The following properties have been set as empty as an initial approach. This approach should keep things simple to start off with. -| Object | Property | +| Objeto | Property | |-------------------------------|-------------------| | ProgramIndicator | groups | | ProgramStageSection | programIndicators | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md index 7362038e3..c3944df71 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md @@ -6,7 +6,7 @@ tags: - DHIS core version 2.41 --- -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -202,7 +202,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. @@ -302,7 +302,7 @@ curl -X PATCH -d @payload.json -H "Content-Type: application/json-patch+json" "h | atomic | falso | If this is set to true, then the batch function will stop and not updating any objects if there is an error
Otherwise, if this is false then the function will try to proceed with best effort mode. | -## Validation { #validation } +## Validación { #validation } - All object ID will be validated for existence. - Current User need to have metadata READ/WRITE permission on updating objects. - All existing validations from metadata import service will also be applied. diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md index 680498ea1..21bb016be 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker-old.md" revision_date: '2024-05-23' tags: -- Desarrollar - DHIS core version 2.41 +- Desarrollar --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } @@ -770,7 +770,7 @@ You can use a range of operators for the filtering: Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | @@ -1112,7 +1112,7 @@ You can use a range of operators for the filtering: Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md index 3dd2b2ff8..b7ba75e8b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md @@ -1318,7 +1318,7 @@ The import will validate unique attributes at the time of import. That means as value is unique for the attribute in the whole system, it will pass. However, if the unique value is fpound used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. @@ -1665,7 +1665,7 @@ To query on an attribute using multiple values in an *IN* filter: You can use a range of operators for the filtering: -|Operator| Descripción| +|Operador| Descripción| |---|---| |`EQ`|Equal to| |`GE`|Greater than or equal to| diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md index 25239419d..762751e3d 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Users { #users } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md index cba087fc1..e58023c1e 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md @@ -294,8 +294,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index ef533c22c..7ada9092a 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/analytics.md" revision_date: '2024-05-31' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Analytics { #analytics } @@ -945,7 +945,7 @@ The available operators are listed below. Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | !EQ | Not equal to | @@ -1695,7 +1695,7 @@ The available operators are listed below. Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index 872b017f5..0556d26d6 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Apps { #apps } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index b1de91173..ff004af42 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" revision_date: '2024-06-24' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index cb1401dbf..1c3454a4d 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Data approval { #data-approval } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index 2c480e5c1..418983e57 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index 4cf4774ac..ca40c7f4e 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" revision_date: '2024-06-26' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Data exchange { #data-exchange } @@ -23,7 +23,7 @@ The aggregate data exchange service is suitable for use-cases such as: * Precomputation of tracker data with program indicators saved as aggregate data values. * Data reporting from a national HMIS to a global donor. -### Overview { #overview } +### Visión general { #overview } The aggregate data exchange service allows for data exchange between a *source* instance of DHIS 2 and a *target* instance of DHIS 2. A data exchange can be *external*, for which the target instance is different/external to the source instance. A data exchange can also be *internal*, for which the target instance is the same as the source instance. The aggregate data exchange source can contain multiple source requests, where a source request roughly corresponds to an analytics API request. @@ -382,8 +382,8 @@ The aggregate data exchange data model / payload is described in the following s | Field | Tipo de dato | Mandatory | Descripción | | ------------------------------------------------- | -------------- | ----------- | ------------------------------------------------------------ | | name | Cadena | Sí | Name of aggregate data exchange. Unique. | -| source | Object | Sí | Source for aggregate data exchange. | -| source.params | Object | No | Parameters for source request. | +| source | Objeto | Sí | Source for aggregate data exchange. | +| source.params | Objeto | No | Parameters for source request. | | source.params.periodTypes | Array/String | No | Allowed period types for overriding periods in source request. | | source.requests | Array/Object | Sí | Source requests. | | source.requests.name | Cadena | Sí | Name of source request. | @@ -399,14 +399,14 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.outputDataItemIdScheme | Cadena | No | Output data item ID scheme applies to data elements, indicators and program indicators, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | -| source.target | Object | Sí | Target for aggregate data exchange. | +| source.target | Objeto | Sí | Target for aggregate data exchange. | | source.target.type | Cadena | Sí | Type of target, can be `EXTERNAL`, `INTERNAL`. | -| source.target.api | Object | Conditional | Target API information, only mandatory for type `EXTERNAL`. | +| source.target.api | Objeto | Conditional | Target API information, only mandatory for type `EXTERNAL`. | | source.target.api.url | Cadena | Conditional | Base URL of target DHIS 2 instance, do not include the `/api` part. | | source.target.api.accessToken | Cadena | Conditional | Access token (PAT) for target DHIS 2 instance, used for PAT authentication. | | source.target.api.username | Cadena | Conditional | Username for target DHIS 2 instance, used for basic authentication. | | source.target.api.password | Cadena | Conditional | Password for target DHIS 2 instance, used for basic authentication. | -| source.target.request | Object | No | Target request information. | +| source.target.request | Objeto | No | Target request information. | | source.target.request.dataElementIdScheme | Cadena | No | Input data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.orgUnitIdScheme | Cadena | No | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index 9aa9998f8..a38b7c033 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Data { #data } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index facec65e8..ffb8be407 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Data store { #data-store } @@ -312,7 +312,7 @@ Each `filter` parameter has the following form: Unary operators are: -| Operator | Descripción | +| Operador | Descripción | | -------- | ----------- | | `null` | value is JSON `null` | | `!null` | value is defined but different to JSON `null` | @@ -321,7 +321,7 @@ Unary operators are: Binary operators are: -| Operator | Descripción | +| Operador | Descripción | | -------- | ----------- | | `eq` | value is equal to the given boolean, number or string | | `!eq`, `ne`, `neq` | value is not equal to the given boolean, number or string | @@ -332,7 +332,7 @@ Binary operators are: Text pattern matching binary operators are: -| Operator | Case Insensitive | Descripción | +| Operador | Case Insensitive | Descripción | | -------- | ---------------- | ----------- | | `like` | `ilike` | value matches the text pattern given | | `!like` | `!ilike` | value does not match the text pattern given | @@ -353,7 +353,7 @@ Otherwise, the value matches string JSON values or mixed types of values. Set operators are: -| Operator | Descripción | +| Operador | Descripción | | -------- | ----------- | | `in` | entry value is textually equal to one of the given values (is in set) | | `!in` | entry value is not textually equal to any of the given values (is not in set) | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index 16447acce..b280d021f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Data validation { #data-validation } @@ -47,7 +47,7 @@ Table: Operators | greater_than | Greater than | | greater_than_or_equal_to | Greater than or equal to | | less_than | Less than | -| less_than_or_equal_to | Less than or equal to | +| menor_que_o_igual_que | Less than or equal to | | compulsory_pair | If either side is present, the other must also be | | exclusive_pair | If either side is present, the other must not be | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md index 1c11721f8..dc6f6fd74 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Email { #email } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index b152b51cb..b96a07254 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 8829f31ce..004a2e862 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # I18n { #i18n } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index 89e82a32c..d0d2b81a9 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Overview { #webapi } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index 1ddb3c50f..ee7634fb3 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md index ecb25ce45..601f7fba3 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Messaging { #messaging } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index bf0afe532..c4d99bed8 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Metadata Gist API { #gist_api } @@ -124,7 +124,7 @@ Parameters and their options that do not make sense in the endpoint context are ignored. -### Overview { #overview } +### Visión general { #overview } Parameters in alphabetical order: | Parámetros | Options | Predeterminado | Descripción | @@ -773,7 +773,7 @@ all other synthetic properties are not included by default and have to be requested explicitly in the list of `fields`. -### Overview { #overview } +### Visión general { #overview } Synthetic fields in alphabetical order: | Field | Descripción | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index c36c8b551..fcb6cd9bd 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" -revision_date: '2024-06-03' +revision_date: '2024-07-12' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Metadata { #webapi_metadata } @@ -298,7 +298,7 @@ objects, is supported as well. Table: Available Operators -| Operator | Types | Value required | Descripción | +| Operador | Types | Value required | Descripción | |---|---|---|---| | eq | string | boolean | integer | float | enum | collection (checks for size) | date | verdadero | Equality | | !eq | string | boolean | integer | float | enum | collection (checks for size) | date | verdadero | Inequality | @@ -480,7 +480,7 @@ using the `:` operator. Table: Property operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | | Include property with name, if it exists. | | [, ...] | Includes a field within either a collection (will be applied to every object in that collection), or just on a single object. | @@ -1629,6 +1629,226 @@ following payload to change the style: } ``` +## Data Elements { #data-elements } + +### Merge data elements { #data_element_merge } + +> **Caution** +> +> Merging DataElements should be carried out with the utmost care. Particular attention +> should be given to the merging of data values that have data element references involved in the +> merge. Knowing the potential side effects of a merge should be fully understood before performing +> the merge. The merging of DataElements has far-reaching effects. The information below +> will try to help show what's involved in a DataElement merge. A DataElement merge +> touches all the major parts of the system (metadata, data, tracker, analytics and audit). +> +> System performance may be impacted if the source DataElements are linked to large amounts of Data/Audit records particularly. + +The data element merge endpoint allows you to merge a number of data elements (sources) into a target data element. + +#### Authorisation { #authorisation } + +The main authority required to perform a data element merge is `F_DATA_ELEMENT_MERGE`. +Other authorities required relate to the general sharing and access of data elements, `F_DATAELEMENT_PUBLIC_ADD` and `F_DATAELEMENT_DELETE`. + +#### Request { #request } + +Merge data elements with a POST request: + +``` +POST /api/dataElements/merge +``` + +The payload in JSON format looks like the following: + +```json +{ + "sources": [ + "jNb63DIHuwU", + "WAjjFMDJKcx" + ], + "target": "V9rfpjwHbYg", + "deleteSources": true, + "dataMergeStrategy": "DISCARD" +} +``` + +The JSON properties are described in the following table. + +Table: Merge payload fields + +| Field | Requerido | Value | +|-------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sources | Sí | Array of identifiers of the data elements to merge (the source data elements) | +| target | Sí | Identifier of the data element to merge the sources into (the target data element) | +| deleteSources | No | Whether to delete the source data elements after the operation. Default is false. If true is chosen, then all source audit records will also be deleted. | +| dataMergeStrategy | Sí | How to handle merging of data values. Options are 'DISCARD' or 'LAST_UPDATED'. DISCARD will delete all source data values. LAST_UPDATED will use the data value which was last updated. | + +The merge operation will merge the source data elements into the target data element. One or many source data elements can be specified. Only one target should be specified. + +The merge operation will transfer all source data element metadata associations to the target data element. +The following metadata get updated: + + +| Metadatos | Property | Action taken | +|-----------------------------------|---------------------------|----------------------------| +| DataDimensionItem | dataElement | set to target | +| EventVisualization | dataElementValueDimension | set to target | +| ProgramStageDataElement | dataElement | set to target | +| ProgramNotificationTemplate | recipientDataElement | set to target | +| ProgramRuleVariable | dataElement | set to target | +| ProgramRuleAction | dataElement | set to target | +| TrackedEntityDataElementDimension | dataElement | set to target | +| MinMaxDataElement | dataElement | set to target | +| SMSCode | dataElement | set to target | +| SMSCode | dataElement | set to target | +| Predictor | output | set to target | +| DataSetElement | dataElement | set to target | +| DataElementOperand | dataElement | set to target | +| ProgramStageDataElement | dataElements | remove sources, add target | +| Section | dataElements | remove sources, add target | +| DataElementGroup | members | remove sources, add target | +| Evento | eventDataValues | remove sources, add target | +| Indicador | numerator | replace source with target | +| Indicador | denominator | replace source with target | +| Predictor | generator | replace source with target | +| Predictor | sampleSkipTest | replace source with target | +| DataEntryForm | htmlCode | replace source with target | +| ProgramIndicator | expression | replace source with target | +| ProgramIndicator | filter | replace source with target | +| DataValue | dataElement | | + + +| Datos | Property | Action taken | +|---------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Evento | eventDataValues | action based on merge strategy (DISCARD / LAST_UPDATED). DISCARD will delete all source event data values. LAST_UPDATED will use the event data value which was last updated, when more than one exists. | +| DataValue | dataElement | action based on merge strategy (DISCARD / LAST_UPDATED). DISCARD will delete all source data values. LAST_UPDATED will use the data value which was last updated, when more than one exists. | +| TrackedEntityDataValueChangeLog | | deleted if sources are being deleted, otherwise no action. | +| DataValueAudit | | deleted if sources are being deleted, otherwise no action. | + + +#### Validación { #validation } + +The following constraints and error codes apply. + +Table: Constraints and error codes + +| Error code | Descripción | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| E1550 | At least one source data element must be specified | +| E1551 | Target data element must be specified | +| E1552 | Target data element cannot be a source indicator | +| E1553 | Source/Target data element does not exist: `{uid}` | +| E1554 | All source ValueTypes must match target ValueType: `ValueType`. Other ValueTypes found: `ValueType` | +| E1555 | All source DataElementDomains must match target DataElementDomain: `DataElementDomain`. Other DataElementDomains found: `DataElementDomain` | +| E1556 | dataMergeStrategy field must be specified. With value `DISCARD` or `LAST_UPDATED` | + +#### Database constraints { #database-constraints } +There are unique constraints in place that can prevent a successful merge. These constraints are set by DHIS2 in order to maintain a logical domain model. +Below are a list of the known database unique key constraints at the time of writing. For example, you +can only have 1 data set element with the same dataset and data element. + +Table: Database table unique key constraints + +| Table | Unique key constraint | +|-------------------------|-------------------------------------------| +| minmaxdataelement | orgunit, dataelement, categoryoptioncombo | +| programstagedataelement | programstage, dataelement | +| datasetelement | dataset, dataelement | + + +#### Response { #response } +##### Success { #success } +Sample success response looks like: + +```json +{ + "httpStatus": "OK", + "httpStatusCode": 200, + "status": "OK", + "response": { + "mergeReport": { + "mergeErrors": [], + "mergeType": "DATA_ELEMENT", + "sourcesDeleted": [ + "vQ0dGV9EDrw" + ], + "message": "DATA_ELEMENT merge complete" + } + } +} +``` + +##### Failure { #failure } +Sample error response looks like: + +```json +{ + "httpStatus": "Conflict", + "httpStatusCode": 409, + "status": "WARNING", + "message": "One or more errors occurred, please see full details in merge report.", + "response": { + "mergeReport": { + "mergeErrors": [ + { + "message": "At least one source data element must be specified", + "errorCode": "E1550", + "args": [] + }, + { + "message": "Target data element does not exist: `abcdefg1221`", + "errorCode": "E1553", + "args": [ + "Target", + "abcdefg1221" + ] + } + ], + "mergeType": "DATA_ELEMENT", + "sourcesDeleted": [], + "message": "DATA_ELEMENT merge has errors" + } + } +} +``` + +Another sample validation error response: + +```json +{ + "httpStatus": "Conflict", + "httpStatusCode": 409, + "status": "WARNING", + "message": "One or more errors occurred, please see full details in merge report.", + "response": { + "mergeReport": { + "mergeErrors": [ + { + "message": "All source ValueTypes must match target ValueType: `TEXT`. Other ValueTypes found: `NUMBER`", + "errorCode": "E1554", + "args": [] + } + ], + "mergeType": "DATA_ELEMENT", + "sourcesDeleted": [], + "message": "DATA_ELEMENT merge has errors" + } + } +} +``` + +A database constraint sample error response: + +```json +{ + "httpStatus": "Conflict", + "httpStatusCode": 409, + "status": "ERROR", + "message": "ERROR: duplicate key value violates unique constraint \"minmaxdataelement_unique_key\"\n Detail: Key (sourceid, dataelementid, categoryoptioncomboid)=(193236, 1148617, 167661) already exists." +} +``` + ## Indicators { #webapi_indicators } This section describes indicators and indicator expressions. @@ -1650,7 +1870,7 @@ expressions are described in the following table. Table: Indicator variables -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | |---|---|---| | #{..} | Data element operand | Refers to a combination of an aggregate data element and a category option combination. Both category and attribute option combo ids are optional, and a wildcard "\*" symbol can be used to indicate any value. | | #{..} | Category Option Group | Refers to an aggregate data element and a category option group, containing multiple category option combinations. | @@ -1848,7 +2068,7 @@ The following metadata get updated: | Visualization | sorting | Replace any source reference with the target reference as Sorting dimension | -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -1961,7 +2181,7 @@ The merge operation will merge the source indicator types into the target indica The merge operation will transfer all of the indicator metadata associations to the source indicator types over to the target indicator type. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -2162,7 +2382,7 @@ The split operation will transfer all of the metadata associations of the source The operation will transfer all data records of the source org unit over to the org unit specified as the primary target, or if not specified, the first specified target org unit. This includes aggregate data values, data approval records, events, tracked entities and more. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -2222,7 +2442,7 @@ The merge operation will transfer all of the metadata associations of the source The specified data value merge strategy defines how data values are handled. For strategy `LAST_UPDATED`, data values for all source org units are transferred over to the target org unit, and in situation where data values exist for the same parameters, the last updated or created data value will be used. This is done to avoid duplication of data. For strategy `DISCARD`, data values are not transferred over to the target org unit, and simply deleted. The specified data approval merge strategy defines how data approval records are handled, and follows the same logic as data values. -#### Validation { #validation } +#### Validación { #validation } The following constraints and error codes apply. @@ -2383,7 +2603,7 @@ values from that period should be skipped. The following variables may be used in either a generator expression or a skip test expression: -| Variable | Object | Descripción | +| Variable | Objeto | Descripción | | ----------- | ---------- | ----------- | | #{} | Aggregate data element | Refers to the total value of an aggregate data element across all category option combinations. | | #{. | Data element operand | Refers to a combination of an aggregate data element and a category option combination. | @@ -2651,7 +2871,7 @@ Table: Object types and keys |---|---| | Data elements | DATA_ELEMENT | | Data element groups | DATA_ELEMENT_GROUP | -| Category options | CATEGORY_OPTION | +| Opciones de categoría | CATEGORY_OPTION | | Category option groups | CATEGORY_OPTION_GROUP | | Organisation units | ORGANISATION_UNIT | | Grupos de unidades organizativas | ORGANISATION_UNIT_GROUP | @@ -2746,10 +2966,10 @@ Table: Validation Rule CSV Format | 2 | UID | No | UID | Stable identifier. Max 11 char. Will be generated by system if not specified. | | 3 | Code | No || Stable code. Max 50 | | 4 | Descripción | No || Free text description. | -| 5 | Instruction | No || Free text instruction. | +| 5 | Instrucción | No || Free text instruction. | | 6 | Importance | No | MEDIUM | HIGH | LOW | Importance of validation rule. | | 7 | Rule type (ignored) | No | VALIDATION | SURVEILLANCE | Type of validation rule. | -| 8 | Operator | No | equal_to | not_equal_to | greater_than | greater_than_or_equal_to | less_than | less_than_or_equal_to | compulsory_pair | exclusive_pair | Expression operator. | +| 8 | Operador | No | equal_to | not_equal_to | greater_than | greater_than_or_equal_to | less_than | less_than_or_equal_to | compulsory_pair | exclusive_pair | Expression operator. | | 9 | Period type | No | Monthly | Daily | Weekly | Quarterly | SixMontly | Yearly | Period type. | | 10 | Left side expression | Sí || Mathematical formula based on data element and option combo UIDs. | | 11 | Left side expression description | Sí || Free text. | @@ -3749,7 +3969,7 @@ The response will also contain a `Location` header with a link to the newly-crea The API does allow the optional supplying of a custom prefix, which will be prefixed to the following properties. -| Object | Property | Info | +| Objeto | Property | Info | |------------------|-----------|------------------------------------------| | Programa | name | Help identify the new Program | | ProgramIndicator | name | Database constraint - needs to be unique | @@ -3847,7 +4067,7 @@ A shallow copy in this context means that an existing `Program` property will be All properties below have been deep copied. Anything not in included in this table means that it has been shallow copied. -| Object | Property of | +| Objeto | Property of | |--------------------------------|--------------| | Programa | | | ProgramSection | Programa | @@ -3862,7 +4082,7 @@ All properties below have been deep copied. Anything not in included in this tab > > The following properties have been set as empty as an initial approach. This approach should keep things simple to start off with. -| Object | Property | +| Objeto | Property | |-------------------------------|-------------------| | ProgramIndicator | groups | | ProgramStageSection | programIndicators | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md new file mode 100644 index 000000000..17acd61ee --- /dev/null +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md @@ -0,0 +1,2154 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/new-tracker.md" +revision_date: "2023-04-04" +tags: + - DHIS core version master + - Desarrollar +--- + +# New Tracker { #new-tracker } + +Version 2.36 of DHIS2 introduced a set of new tracker endpoints dedicated to importing and querying tracker objects (Including tracked entities, enrollments, events, and relationships). These new endpoints set a discontinuity with earlier implementations. Re-engineering the endpoints allowed developers to improve, redesign, and formalize the API's behavior to improve the Tracker services. + +The newly introduced endpoints consist of: + +- `POST /api/tracker` +- `GET /api/tracker/enrollments` +- `GET /api/tracker/events` +- `GET /api/tracker/trackedEntities` +- `GET /api/tracker/relationships` + +> **NOTE** +> +> - The old endpoints are marked as deprecated but still work as before. +> - Some functionality is not yet ready in the new endpoints, but they support their primary use-cases. + +## Changes in the API { #changes-in-the-api } + +Property names used in the API have changed to use consistent naming across all the new endpoints. + +### Tracker Import changelog (`POST`) { #tracker-import-changelog-post } + +The following table highlights the differences between the previous tracker import endpoints (/api/trackedEntityInstance, /api/enrollments, /api/events and /api/relatiosnhips) and the new endpoint (/api/tracker). All endpoints are still currently available. + +| Tracker Object | Previously | Now | +| --- | --- | --- | +| **Attribute** | `created`
`lastUpdated` | `createdAt`
`updatedAt` | +| **DataValue** | `created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo` | `createdAt`
`updatedAt`
`createdBy`
`updatedBy` | +| **Inscripción** | `created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo` | `createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy` | +| **Evento** | `trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`\* | `trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`\* | +| **Nota** | `storedDate`
`lastUpdatedBy` | `storedAt`
`createdBy` | +| **ProgramOwner** | `ownerOrgUnit`
`trackedEntityInstance` | `orgUnit`
`trackedEntity` | +| **RelationshipItem** | `trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event` | `trackedEntity`
`enrollment`
`event` | +| **Relationship** | `created`
`lastUpdated` | `createdAt`
`updatedAt` | +| **TrackedEntity** | `trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo` | `trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy` | + +> **Note** +> +> Field `assignedUser` was a String before, now it is of type User: +> +> ```json +> { +> "assignedUser": { +> "uid": "ABCDEF12345", +> "username": "username", +> "firstName": "John", +> "surname": "Doe" +> } +> } +> ``` + +### Tracker Export changelog (`GET`) { #tracker-export-changelog-get } + +The `GET` endpoints all conform to the same naming conventions reported in the previous paragraph. Additionally, we made some changes regarding the request parameters to respect the same naming conventions here as well. + +These tables highlight the old endpoint differences in request parameters for `GET` endpoints compared to the new + +#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } + +| Previously | Now | +| -------------------------------------- | ----------------------------------- | +| `ou` | `orgUnit` | +| `lastUpdated`
`lastUpdateDuration` | `updatedAfter`
`updatedWithin` | +| `programStartDate`
`programEndDate` | `enrolledAfter`
`enrolledBefore` | +| `trackedEntityInstance` | `trackedEntity` | + +#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } + +| Previously | Now | +| --- | --- | +| `trackedEntityInstance` | `trackedEntity` | +| `startDate`
`endDate` | `occurredAfter`
`occurredBefore` | +| `dueDateStart`
`dueDateEnd` | `scheduledAfter`
`scheduledBefore` | +| `lastUpdated` | Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +| `lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration` | `updatedAfter`
`updatedBefore`
`updatedWithin` | + +#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } + +| Previously | Now | +| --- | --- | +| `trackedEntityInstance` | `trackedEntity` | +| `ou` | `orgUnit` | +| `programStartDate`
`programEndDate` | Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +| `programEnrollmentStartDate`
`programEnrollmentEndDate` | `enrollmentEnrolledAfter`
`enrollmentEnrolledBefore` | +| `programIncidentStartDate`
`programIncidentEndDate` | `enrollmentOccurredAfter`
`enrollmentOccurredBefore` | +| `eventStartDate`
`eventEndDate` | `eventOccurredAfter`
`eventOccurredBefore` | +| `lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration` | `updatedAfter`
`updatedBefore`
`updatedWithin` | + +## Tracker Objects { #webapi_nti_tracker_objects } + +Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. + +### Tracked Entity { #tracked-entity } + +`Tracked Entities` are the root object for the Tracker model. + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| trackedEntity | The identifier of the tracked entity. Generated if not supplied | No | Sí | String:Uid | ABCDEF12345 | +| trackedEntityType | The type of tracked entity. | Sí | Sí | String:Uid | ABCDEF12345 | +| createdAt | Timestamp when the user created the tracked entity. Set on the server. | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| createdAtClient | Timestamp when the user created the tracked entity on the client. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAt | Timestamp when the object was last updated. Set on the server. | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAtClient | Timestamp when the object was last updated on the client. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| orgUnit | The organisation unit where the user created the tracked entity. | Sí | Sí | String:Uid | ABCDEF12345 | +| inactive | Indicates whether the tracked entity is inactive or not. | No | Sí | Booleano | Default: False, True | +| deleted | Indicates whether the tracked entity has been deleted. It can only change when deleting. | No | No | Booleano | False until deleted | +| geometry | A geographical representation of the tracked entity. Based on the "featureType" of the TrackedEntityType. | No | Sí | GeoJson | {
"type": "POINT",
"coordinates": [123.0, 123.0]
} | +| storedBy | Client reference for who stored/created the tracked entity. | No | Sí | String:Any | John Doe | +| createdBy | Only for reading data. User that created the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| updatedBy | Only for reading data. User that last updated the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| attributes | A list of tracked entity attribute values owned by the tracked entity. | No | Sí | List of TrackedEntityAttributeValue | See Attribute | +| enrollments | A list of enrollments owned by the tracked entity. | No | Sí | List of Enrollment | See Enrollment | +| relationships | A list of relationships connected to the tracked entity. | No | Sí | List of Relationship | See Relationship | +| programOwners | A list of organisation units that have access through specific programs to this tracked entity. See "Program Ownership" for more. | No | Sí | List of ProgramOwner | See section "Program Ownership" | + +> **Note** +> +> `Tracked Entities` "owns" all `Tracked Entity Attribute Values` (Or "attributes" as described in the previous table). However, `Tracked Entity Attributes` are either connected to a `Tracked Entity` through its `Tracked Entity Type` or a `Program`. We often refer to this separation as `Tracked Entity Type Attributes` and `Tracked Entity Program Attributes`. The importance of this separation is related to access control and limiting what information the user can see. +> +> The "attributes" referred to in the `Tracked Entity` are `Tracked Entity Type Attributes`. + +### Enrollment { #enrollment } + +`Tracked Entities` can enroll into `Programs` for which they are eligible. Tracked entities are eligible as long as the program is configured with the same `Tracked Entity Type` as the tracked entity. We represent the enrollment with the `Enrollment` object, which we describe in this section. + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| enrollment | The identifier of the enrollment. Generated if not supplied | No | Sí | String:Uid | ABCDEF12345 | +| program | The program the enrollment represents. | Sí | No | String:Uid | ABCDEF12345 | +| trackedEntity | A reference to the tracked entity enrolled. | Sí | Sí | String:Uid | ABCDEF12345 | +| trackedEntityType | Only for reading data. The type of tracked entity enrolled | No | Sí | String:Uid | ABCDEF12345 | +| status | Status of the enrollment. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | +| orgUnit | The organisation unit where the user enrolled the tracked entity. | Sí | No | String:Uid | ABCDEF12345 | +| orgUnitName | Only for reading data. The name of the organisation unit where the enrollment took place. | No | No | String:Any | Sierra Leone | +| createdAt | Timestamp when the user created the object. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| createdAtClient | Timestamp when the user created the object on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAt | Timestamp when the object was last updated. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAtClient | Timestamp when the object was last updated on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| enrolledAt | Timestamp when the user enrolled the tracked entity. | Sí | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| occurredAt | Timestamp when enrollment occurred. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| completedAt | Timestamp when the user completed the enrollment. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| completedBy | Reference to who completed the enrollment | No | No | String:any | John Doe | +| followUp | Indicates whether the enrollment requires follow-up. False if not supplied | No | No | Booelan | Default: False, True | +| deleted | Indicates whether the enrollment has been deleted. It can only change when deleting. | No | Sí | Booleano | False until deleted | +| geometry | A geographical representation of the enrollment. Based on the "featureType" of the Program | No | No | GeoJson | {
"type": "POINT",
"coordinates": [123.0, 123.0]
} | +| storedBy | Client reference for who stored/created the enrollment. | No | No | String:Any | John Doe | +| createdBy | Only for reading data. User that created the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| updatedBy | Only for reading data. User that last updated the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| attributes | A list of tracked entity attribute values connected to the enrollment. | No | No | List of TrackedEntityAttributeValue | See Attribute | +| events | A list of events owned by the enrollment. | No | No | List of Event | See Event | +| relationships | A list of relationships connected to the enrollment. | No | No | List of Relationship | See Relationship | +| notes | Notes connected to the enrollment. It can only be created. | No | Sí | List of Note | See Note | + +> **Note** +> +> `Tracked Entities` "owns" all `Tracked Entity Attribute Values` (Or "attributes" as described in the previous table). However, `Tracked Entity Attributes` are either connected to a `Tracked Entity` through its `Tracked Entity Type` or a `Program`. We often refer to this separation as `Tracked Entity Type Attributes` and `Tracked Entity Program Attributes`. The importance of this separation is related to access control and limiting what information the user can see. +> +> The "attributes" referred to in the `Enrollment` are `Tracked Entity Program Attributes`. + +### Events { #events } + +`Events` are either part of an `EVENT PROGRAM` or `TRACKER PROGRAM`. For `TRACKER PROGRAM`, events belong to an `Enrollment`, which again belongs to a `Tracked Entity`. On the other hand, `EVENT PROGRAM` is `Events` not connected to a specific `Enrollment` or `Tracked Entity`. The difference is related to whether we track a specific `Tracked Entity` or not. We sometimes refer to `EVENT PROGRAM` events as "anonymous events" or "single events" since they only represent themselves and not another `Tracked Entity`. + +In the API, the significant difference is that all events are either connected to the same enrollment (`EVENT PROGRAM`) or different enrollments (`TRACKER PROGRAM`). The table below will point out any exceptional cases between these two. + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| event | The identifier of the event. Generated if not supplied | No | Sí | String:Uid | ABCDEF12345 | +| programStage | The program stage the event represents. | Sí | No | String:Uid | ABCDEF12345 | +| enrollment | A reference to the enrollment which owns the event. **_Not applicable for `EVENT PROGRAM`_** | Sí | Sí | String:Uid | ABCDEF12345 | +| program | Only for reading data. The type of program the enrollment which owns the event has. | No | Sí | String:Uid | ABCDEF12345 | +| trackedEntity | Only for reading data. The tracked entity which owns the event. **_Not applicable for `EVENT PROGRAM`_** | No | No | String:Uid | ABCDEF12345 | +| status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | +| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. **_Not applicable for `EVENT PROGRAM`_** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | +| orgUnit | The organisation unit where the user registered the event. | Sí | No | String:Uid | ABCDEF12345 | +| orgUnitName | Only for reading data. The name of the organisation unit where the user registered the event. | No | No | String:Any | Sierra Leone | +| createdAt | Timestamp when the user created the event. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAt | Timestamp when the event was last updated. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAtClient | Timestamp when the event was last updated on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| scheduledAt | Timestamp when the event was scheduled for. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| occurredAt | Timestamp when something occurred. | Sí | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| completedAt | Timestamp when the user completed the event. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| completedBy | Reference to who completed the event | No | No | String:Any | John Doe | +| followUp | Indicates whether the event has been flagged for follow-up. False if not supplied | No | No | Booelan | Default: False, True | +| deleted | Indicates whether the event has been deleted. It can only change when deleting. | No | Sí | Booleano | False until deleted | +| geometry | A geographical representation of the event. Based on the "featureType" of the Program Stage | No | No | GeoJson | {
"type": "POINT",
"coordinates": [123.0, 123.0]
} | +| storedBy | Client reference for who stored/created the event. | No | No | String:Any | John Doe | +| createdBy | Only for reading data. User that created the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| updatedBy | Only for reading data. User that last updated the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| attributeOptionCombo | Attribute option combo for the event. Default if not supplied or configured. | No | No | String:Uid | ABCDEF12345 | +| attributeCategoryOptions | Attribute category option for the event. Default if not supplied or configured. | No | No | String:Uid | ABCDEF12345 | +| assignedUser | A reference to a user who has been assigned to the event. | No | No | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| dataValues | A list of data values connected to the event. | No | No | List of TrackedEntityAttributeValue | See Attribute | +| relationships | A list of relationships connected to the event. | No | No | List of Relationship | See Relationship | +| notes | Notes connected to the event. It can only be created. | No | Sí | List of Note | See Note | + +### Relationship { #relationship } + +`Relationships` are objects that link together two other tracker objects. The constraints each side of the relationship must conform to are based on the `Relationship Type` of the `Relationship`. + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| relationship | The identifier of the relationship. Generated if not supplied. | No | Sí | String:Uid | ABCDEF12345 | +| relationshipType | The type of the relationship. Decides what objects can be linked in a relationship. | Sí | Sí | String:Uid | ABCDEF12345 | +| relationshipName | Only for reading data. The name of the relationship type of this relationship | No | No | String:Any | Sibling | +| createdAt | Timestamp when the user created the relationship. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAt | Timestamp when the relationship was last updated. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| bidirectional | Only for reading data. Indicated whether the relationship type is bidirectional or not. | No | No | Booleano | True or False | +| from, to | A reference to each side of the relationship. Must conform to the constraints set in the relationship type | Sí | Sí | RelationshipItem | {"trackedEntity": {"trackedEntity": "ABCEF12345"}}, {"enrollment": {"enrollment": "ABCDEF12345"}} or {"event": {"event": "ABCDEF12345" }} | + +> **Note** +> +> `Relationship item` represents a link to an object. Since a `relationship` can be between any tracker object like `tracked entity`, `enrollment`, and `event`, the value depends on the `relationship type`. For example, if the `relationship type` connects from an `event` to a `tracked entity`, the format is strict: +> +> ```json +> { +> "from": { +> "event": { "event": "ABCDEF12345" } +> }, +> "to": { +> "trackedEntity": { "trackedEntity": "FEDCBA12345" } +> } +> } +> ``` + +### Attribute { #attribute } + +`Attributes` are the actual values describing the `tracked entities`. They can either be connected through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of both a `tracked entity` and an `enrollment`. + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| attribute | A reference to the tracked entity attribute represented. | Sí | Sí | String:Uid | ABCDEF12345 | +| code | Only for reading data. The code of the tracked entity attribute. | No | No | String:Any | ABC | +| displayName | Only for reading data. The displayName of the tracked entity attribute. | No | No | String:Any | Nombre | +| createdAt | Timestamp when the value was added. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAt | Timestamp when the value was last updated. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| storedBy | Client reference for who stored/created the value. | No | No | String:Any | John Doe | +| valueType | Only for reading data. The type of value the attribute represents. | No | No | Enum | TEXT, INTEGER, and more | +| value | The value of the tracked entity attribute. | No | No | String:Any | John Doe | + +> **Note** +> +> For `attributes` only the "attribute" and "value" properties are required when adding data. "value" can be null, which implies the user should remove the value. +> +> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity Attribute Values` as "attributes". However, attributes are also their own thing, related to metadata. Therefore it's vital to separate Tracker attributes and metadata attributes. In the tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See request parameters for more information). + +### Data Values { #data-values } + +While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| dataElement | The data element this value represents. | Sí | Sí | String:Uid | ABCDEF12345 | +| value | The value of the data value. | No | No | String:Any | 123 | +| providedElsewhere | Indicates whether the user provided the value elsewhere or not. False if not supplied. | No | No | Booleano | False or True | +| createdAt | Timestamp when the user added the value. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| updatedAt | Timestamp when the value was last updated. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| storedBy | Client reference for who stored/created the value. | No | No | String:Any | John Doe | +| createdBy | Only for reading data. User that created the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | +| updatedBy | Only for reading data. User that last updated the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | + +> **Note** +> +> For `data elements` only the "dataElement" and "value" properties are required when adding data. "value" can be null, which implies the user should remove the value. + +### Tracker Notes { #tracker-notes } + +DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. However, sometimes there could be a situation where it is necessary to record additional information or comment about the issue at hand. Such additional information can be captured using tracker notes. Tracker notes are equivalent to data value comments from the Aggregate DHIS2 side. + +There are two types of tracker notes - notes recorded at the event level and those recorded at the enrollment level. An enrollment can have one or more events. Comments about each of the events - for example, why an event was missed, rescheduled, or why only a few data elements were filled and the like - can be documented using event notes. Each of the events within an enrollment can have its own story/notes. One can then record, for example, an overall observation of these events using the parent enrollment note. Enrollment notes are also helpful to document, for example, why an enrollment is canceled. It is the user's imagination and use-case when and how to use notes. + +Both enrollment and event can have as many notes as needed - there is no limit. However, it is not possible to delete or update neither of these notes. They are like a logbook. If one wants to amend a note, one can do so by creating another note. The only way to delete a note is by deleting the parent object - either event or enrollment. + +Tracker notes do not have their dedicated endpoint; they are exchanged as part of the parent event and/or enrollment payload. Below is a sample payload. + +```json +{ + "trackedEntityInstance": "oi3PMIGYJH8", + , + ], + "enrollments": [ + { + "enrollment": "EbRsJr8LSSO", + + "notes": [ + { + "note": "vxmCvYcPdaW", + "value": "Enrollment note 2.", + }, + { + "value": "Enrollment note 1", + } + ], + + "events": [ + { + "event": "zfzS9WeO0uM", + , + "notes": [ + { + "note": "MAQFb7fAggS", + "value": "Event Note 1.", + }, + { + "value": "Event Note 2.", + } + ], + }, + { + ... + } + ] + } + ] +} +``` + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| note | The reference of the note. Generated if empty | No | Sí | String:Uid | ABCDEF12345 | +| value | The content of the note. | Sí | Sí | String:Any | This is a note | +| storedAt | Timestamp when the user added the note. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | +| storedBy | Client reference for who stored/created the note. | No | No | String:Any | John Doe | +| createdBy | Only for reading data. User that created the object. Set on the server | No | Sí | Usuario | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | + +### Usuarios { #user } + +| Property | Descripción | Requerido | Immutable | Tipo | Example | +| --- | --- | --- | --- | --- | --- | +| uid | The identifier of the user. | Si\* | Sí | String:Uid | ABCDEF12345 | +| username | Username used by the user. | Si\* | Sí | String:Any | 123 | +| firstName | Only for reading data. First name of the user. | No | Sí | String:Any | John | +| surname | Only for reading data. Last name of the user. | No | Sí | String:Any | Doe | + +> One between `uid` or `username` field must be provided. If both are provided, only username is considered. + +### Program stage working lists { #webapi_working_list_filters } + +The program stage working lists feature within the Capture app is designed to display pre-established working lists relevant to a particular program stage. This functionality enables users to save filters and sorting preferences that are related to program stages, facilitating the organization and management of their workflow. To interact with them, you'll need to use the _/api/programStageWorkingLists_ resource. These lists can be shared and follow the same sharing pattern as any other metadata. When using the _/api/sharing_ the type parameter will be _programStageWorkingLists_. + + /api/40/programStageWorkingLists + +##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } + +The endpoint above can be used to get all program stage working lists. To get a single one, just add at the end the id of the one you are interested in. This is the same in case you want to delete it. On the other hand, if you are looking to create or update a program stage working list, besides the endpoint mentioned above, you'll need to provide a payload in the following format: + +Table: Payload + +| Payload values | Descripción | Example | +| --- | --- | --- | +| name | Name of the working list. Required. | | +| Descripción | A description of the working list. | | +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See _Program Stage Query Criteria_ definition table below. | + +Table: Program Stage Query Criteria | status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | | eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | | scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | | enrollmentStatus | Any valid ProgramStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | | enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | | enrollmentOccurredAt | DateFilterPeriod object filtering based on the event incident date. | {"type":"RELATIVE","period":"THIS_MONTH"} | | orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | | ouMode | A valid OU selection mode | "ouMode": "SELECTED" | | assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | | assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | | order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | | displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | | dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | | attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | + +See an example payload below: + +```json +{ + "name": "Test WL", + "program": { "id": "uy2gU8kT1jF" }, + "programStage": { "id": "oRySG82BKE6" }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "status": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" + }, + "scheduledAt": { "type": "RELATIVE", "period": "TODAY" }, + "enrollmentStatus": "COMPLETED", + "enrolledAt": { "type": "RELATIVE", "period": "THIS_MONTH" }, + "enrollmentOccurredAt": { "type": "RELATIVE", "period": "THIS_MONTH" }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": ["DXyJmlo9rge"], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": ["w75KJ2mc4zz", "zDhUuAYrxNC"], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } +} +``` + +## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } + +The `POST /api/tracker` endpoint allows clients to import the following tracker objects into DHIS2: + +- **Tracked entities** +- **Enrollments** +- **Events** +- **Relationships** +- Data embedded in other [tracker objects](#webapi_nti_tracker_objects) + +Main changes compared to the other endpoints for tracker import are: + +1. Import payload can be **_nested_** or **_flat_** +2. Invocation can be **_synchronous_** or **_asynchronous_** +3. Import **_CSV_** events payload + +### Request parameters { #request-parameters } + +Currently, the tracker import endpoint supports the following parameters: + +| Parameter name | Descripción | Tipo | Allowed values | +| --- | --- | --- | --- | +| async | Indicates whether the import should happen asynchronously or synchronously. | Booleano | `TRUE`, `FALSE` | +| reportMode | Only when performing synchronous import. See importSummary for more info. | Enum | `FULL`, `ERRORS`, `WARNINGS` | +| importMode | Indicates the mode of import. Can either be validate only (dry run) or commit (Default) | Enum | `VALIDATE`, `COMMIT` | +| idScheme | Indicates the overall idScheme to use for metadata references when importing. Default is UID. Can be overridden for specific metadata (Listed below) | Enum | `UID`, `CODE`, `NAME`, `ATTRIBUTE` | +| dataElementIdScheme | Indicates the idScheme to use for data elements when importing. | Enum | `UID`, `CODE`, `NAME`, `ATTRIBUTE` | +| orgUnitIdScheme | Indicates the idScheme to use for organisation units when importing. | Enum | `UID`, `CODE`, `NAME`, `ATTRIBUTE` | +| programIdScheme | Indicates the idScheme to use for programs when importing. | Enum | `UID`, `CODE`, `NAME`, `ATTRIBUTE` | +| programStageIdScheme | Indicates the idScheme to use for program stages when importing. | Enum | `UID`, `CODE`, `NAME`, `ATTRIBUTE` | +| categoryOptionComboIdScheme | Indicates the idScheme to use for category option combos when importing. | Enum | `UID`, `CODE`, `NAME`, `ATTRIBUTE` | +| categoryOptionIdScheme | Indicates the idScheme to use for category options when importing. | Enum | `UID`, `CODE`, `NAME`, `ATTRIBUTE` | +| importStrategy | Indicates the effect the import should have. Can either be `CREATE`, `UPDATE`, `CREATE_AND_UPDATE` and `DELETE`, which respectively only allows importing new data, importing changes to existing data, importing any new or updates to existing data, and finally deleting data. | Enum | `CREATE`, `UPDATE`, `CREATE_AND_UPDATE`, `DELETE` | +| atomicMode | Indicates how the import responds to validation errors. If `ALL`, all data imported must be valid for any data to be committed. For `OBJECT`, only the data committed needs to be valid, while other data can be invalid. | Enum | `ALL`, `OBJECT` | +| flushMode | Indicates the frequency of flushing. This is related to how often data is pushed into the database during the import. Primarily used for debugging reasons, and should not be changed in a production setting | Enum | `AUTO`, `OBJECT` | +| validationMode | Indicates the completeness of the validation step. It can be skipped, set to fail fast (Return on the first error), or full(Default), which will return any errors found | Enum | `FULL`, `FAIL_FAST`, `SKIP` | +| skipPatternValidation | If true, it will skip validating the pattern of generated attributes. | Booleano | `TRUE`, `FALSE` | +| skipSideEffects | If true, it will skip running any side effects for the import | Booleano | `TRUE`, `FALSE` | +| skipRuleEngine | If true, it will skip running any program rules for the import | Booleano | `TRUE`, `FALSE` | + +**NOTE**: idScheme and its metadata specific idScheme parameters like orgUnitIdScheme, programIdScheme, ... used to allow and use the default `AUTO`. `AUTO` has been removed. The default idScheme has already been `UID`. Any requests sent with idScheme `AUTO` will see the same behavior as before, namely matching done using `UID`. + +### Flat and nested payloads { #flat-and-nested-payloads } + +The importer support both flat and nested payloads. The main difference is how the client requires their data to be structured. + +**Flat** : The flat-structured payload is straightforward. It can contain collections for each of the core tracker objects we have. This works seamlessly with existing data, which already have UIDs assigned. However, for new data, the client will have to provide new UIDs for any references between objects. For example, if you import a new tracked entity with a new enrollment, the tracked entity requires the client to provide a UID so that the enrollment can be linked to that UID. + +**Nested** : Nested payloads are the most commonly used structure. Here, tracker objects are embedded within their parent object; For example, an enrollment within a tracked entity. The advantage of this structure is that the client does not need to provide UIDs for these connections since they will be given this connection during the import process since they are nested together. + +> **NOTE** +> +> While nested payloads might prove simpler for clients to deal with, the payload will always be flattened before the import. This means that for large imports, providing a flat structured payload will provide both more control and lower overhead for the import process itself. + +Examples for the **FLAT** and the **NESTED** versions of the payload are listed below. Both cases use the same data. + +#### **_FLAT_** payload { #flat-payload } + +```json +{ + "trackedEntities": [ + { + "orgUnit": "O6uvpzGd5pu", + "trackedEntity": "Kj6vYde4LHh", + "trackedEntityType": "Q9GufDoplCL" + } + ], + "enrollments": [ + { + "orgUnit": "O6uvpzGd5pu", + "program": "f1AyMswryyQ", + "trackedEntity": "Kj6vYde4LHh", + "enrollment": "MNWZ6hnuhSw", + "trackedEntityType": "Q9GufDoplCL", + "enrolledAt": "2019-08-19T00:00:00.000", + "deleted": false, + "occurredAt": "2019-08-19T00:00:00.000", + "status": "ACTIVE", + "notes": [], + "attributes": [] + } + ], + "events": [ + { + "scheduledAt": "2019-08-19T13:59:13.688", + "program": "f1AyMswryyQ", + "event": "ZwwuwNp6gVd", + "programStage": "nlXNK4b7LVr", + "orgUnit": "O6uvpzGd5pu", + "trackedEntity": "Kj6vYde4LHh", + "enrollment": "MNWZ6hnuhSw", + "enrollmentStatus": "ACTIVE", + "status": "ACTIVE", + "occurredAt": "2019-08-01T00:00:00.000", + "attributeCategoryOptions": "xYerKDKCefk", + "deleted": false, + "attributeOptionCombo": "HllvX50cXC0", + "dataValues": [ + { + "updatedAt": "2019-08-19T13:58:37.477", + "storedBy": "admin", + "dataElement": "BuZ5LGNfGEU", + "value": "20", + "providedElsewhere": false + }, + { + "updatedAt": "2019-08-19T13:58:40.031", + "storedBy": "admin", + "dataElement": "ZrqtjjveTFc", + "value": "Male", + "providedElsewhere": false + }, + { + "updatedAt": "2019-08-19T13:59:13.691", + "storedBy": "admin", + "dataElement": "mB2QHw1tU96", + "value": "[-11.566044,9.477801]", + "providedElsewhere": false + } + ], + "notes": [] + }, + { + "scheduledAt": "2019-08-19T13:59:13.688", + "program": "f1AyMswryyQ", + "event": "XwwuwNp6gVE", + "programStage": "PaOOjwLVW23", + "orgUnit": "O6uvpzGd5pu", + "trackedEntity": "Kj6vYde4LHh", + "enrollment": "MNWZ6hnuhSw", + "enrollmentStatus": "ACTIVE", + "status": "ACTIVE", + "occurredAt": "2019-08-01T00:00:00.000", + "attributeCategoryOptions": "xYerKDKCefk", + "deleted": false, + "attributeOptionCombo": "HllvX50cXC0", + "notes": [] + } + ], + "relationships": [ + { + "relationshipType": "Udhj3bsdHeT", + "from": { + "trackedEntity": { "trackedEntity": "Kj6vYde4LHh" } + }, + "to": { + "trackedEntity": { "trackedEntity": "Gjaiu3ea38E" } + } + } + ] +} +``` + +#### **_NESTED_** payload { #nested-payload } + +```json +{ + "trackedEntities": [ + { + "orgUnit": "O6uvpzGd5pu", + "trackedEntity": "Kj6vYde4LHh", + "trackedEntityType": "Q9GufDoplCL", + "relationships": [ + { + "relationshipType": "Udhj3bsdHeT", + "from": { + "trackedEntity": { "trackedEntity": "Kj6vYde4LHh" } + }, + "to": { + "trackedEntity": { "trackedEntity": "Gjaiu3ea38E" } + } + } + ], + "enrollments": [ + { + "orgUnit": "O6uvpzGd5pu", + "program": "f1AyMswryyQ", + "trackedEntity": "Kj6vYde4LHh", + "enrollment": "MNWZ6hnuhSw", + "trackedEntityType": "Q9GufDoplCL", + "enrolledAt": "2019-08-19T00:00:00.000", + "deleted": false, + "occurredAt": "2019-08-19T00:00:00.000", + "status": "ACTIVE", + "notes": [], + "relationships": [], + "attributes": [], + "events": [ + { + "scheduledAt": "2019-08-19T13:59:13.688", + "program": "f1AyMswryyQ", + "event": "ZwwuwNp6gVd", + "programStage": "nlXNK4b7LVr", + "orgUnit": "O6uvpzGd5pu", + "trackedEntity": "Kj6vYde4LHh", + "enrollment": "MNWZ6hnuhSw", + "enrollmentStatus": "ACTIVE", + "status": "ACTIVE", + "occurredAt": "2019-08-01T00:00:00.000", + "attributeCategoryOptions": "xYerKDKCefk", + "deleted": false, + "attributeOptionCombo": "HllvX50cXC0", + "dataValues": [ + { + "updatedAt": "2019-08-19T13:58:37.477", + "storedBy": "admin", + "dataElement": "BuZ5LGNfGEU", + "value": "20", + "providedElsewhere": false + }, + { + "updatedAt": "2019-08-19T13:58:40.031", + "storedBy": "admin", + "dataElement": "ZrqtjjveTFc", + "value": "Male", + "providedElsewhere": false + }, + { + "updatedAt": "2019-08-19T13:59:13.691", + "storedBy": "admin", + "dataElement": "mB2QHw1tU96", + "value": "[-11.566044,9.477801]", + "providedElsewhere": false + } + ], + "notes": [], + "relationships": [] + }, + { + "scheduledAt": "2019-08-19T13:59:13.688", + "program": "f1AyMswryyQ", + "event": "XwwuwNp6gVE", + "programStage": "PaOOjwLVW23", + "orgUnit": "O6uvpzGd5pu", + "trackedEntity": "Kj6vYde4LHh", + "enrollment": "MNWZ6hnuhSw", + "enrollmentStatus": "ACTIVE", + "status": "ACTIVE", + "occurredAt": "2019-08-01T00:00:00.000", + "attributeCategoryOptions": "xYerKDKCefk", + "deleted": false, + "attributeOptionCombo": "HllvX50cXC0", + "notes": [], + "relationships": [] + } + ] + } + ] + } + ] +} +``` + +### SYNC and ASYNC { #sync-and-async } + +For the user, the main difference between importing synchronously rather than asynchronously is the immediate response from the API. For the synchronous import, the response will be returned as soon as the import finishes with the importSummary. However, for asynchronous imports, the response will be immediate and contain a reference where the client can poll for updates to the import. + +For significant imports, it might be beneficial for the client to use the asynchronous import to avoid waiting too long for a response. + +Examples of the **ASYNC** response is shown below. For **SYNC** response, look at the [importSummary section](#webapi_nti_import_summary). + +```json +{ + "httpStatus": "OK", + "httpStatusCode": 200, + "status": "OK", + "message": "Tracker job added", + "response": { + "responseType": "TrackerJob", + "id": "LkXBUdIgbe3", + "location": "https://play.dhis2.org/dev/api/tracker/jobs/LkXBUdIgbe3" + } +} +``` + +### CSV Events payload { #csv-events-payload } + +In order to maintain compatibility with older versions of tracker, the API allows to import events using the CSV format. As this format does not allow list as field, every row of the CSV payload represents an event and a data value. So for events with multiple data values, the CSV file will have `x` rows per event where `x` is the number of data values in that event. Other fields that are lists as **_relationships_** and **_notes_** are not supported. To import a CSV payload, the content type of the request must be set to **_application/csv_** or **_text/csv_**. + +#### **_CSV PAYLOAD_** example { #csv-payload-example } + +| event | status | program | programStage | enrollment | orgUnit | occurredAt | scheduledAt | dataElement | value | storedBy | providedElsewhere | +| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | +| V1CerIi3sdL | COMPLETED | IpHINAT79UW | A03MvHHogjR | CCBLMntFuzb | DiszpKrYNg8 | 2020-02-26T23:00:00Z | 2020-02-27T23:00:00Z | a3kGcGDCuk6 | 11 | admin | falso | +| V1CerIi3sdL | COMPLETED | IpHINAT79UW | A03MvHHogjR | CCBLMntFuzb | DiszpKrYNg8 | 2020-02-26T23:00:00Z | 2020-02-27T23:00:00Z | mB2QHw1tU96 | [-11.566044,9.477801] | admin | falso | + +### Import Summary { #webapi_nti_import_summary } + +The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. These endpoints will return either the log related to the import or the import summary itself. + +> **Note** +> +> These endpoints rely on information stored in the application memory. This means the information will be unavailable after certain cases, as an application restart or after a large number of import requests have started after this one. + +After submitting a tracker import request, we can access the following endpoints in order to monitor the job progress based on logs: + +`GET /tracker/jobs/{uid}` + +| Parámetros | Descripción | Example | +| --------- | ----------------------------------------- | ----------- | +| `{uid}` | The UID of an existing tracker import job | ABCDEF12345 | + +#### **_REQUEST_** example { #request-example } + +`GET /tracker/jobs/mEfEaFSCKCC` + +#### **_RESPONSE_** example { #response-example } + +```json +[ + { + "uid": "mEfEaFSCKCC", + "level": "INFO", + "category": "TRACKER_IMPORT_JOB", + "time": "2021-01-01T00:00:06.00", + "message": "TRACKER_IMPORT_JOB ( mEfEaFSCKCC ) finished in 6.00000 sec. Import:Done", + "completed": true, + "id": "mEfEaFSCKCC" + }, + { + "uid": "mEfEaFSCKCC", + "level": "DEBUG", + "category": "TRACKER_IMPORT_JOB", + "time": "2021-01-01T00:00:05.00", + "message": "TRACKER_IMPORT_JOB ( mEfEaFSCKCC ) commit completed in 1.00000 sec. Import:commit", + "completed": true, + "id": "mEfEaFSCKCC" + }, + { + "uid": "mEfEaFSCKCC", + "level": "DEBUG", + "category": "TRACKER_IMPORT_JOB", + "time": "2021-01-01T00:00:04.00", + "message": "TRACKER_IMPORT_JOB ( mEfEaFSCKCC ) programruleValidation completed in 1.00000 sec. Import:programruleValidation", + "completed": true, + "id": "mEfEaFSCKCC" + }, + { + "uid": "mEfEaFSCKCC", + "level": "DEBUG", + "category": "TRACKER_IMPORT_JOB", + "time": "2021-01-01T00:00:03.00", + "message": "TRACKER_IMPORT_JOB ( mEfEaFSCKCC ) programrule completed in 1.00000 sec. Import:programrule", + "completed": true, + "id": "mEfEaFSCKCC" + }, + { + "uid": "mEfEaFSCKCC", + "level": "DEBUG", + "category": "TRACKER_IMPORT_JOB", + "time": "2021-01-01T00:00:02.00", + "message": "TRACKER_IMPORT_JOB ( mEfEaFSCKCC ) validation completed in 1.00000 sec. Import:validation", + "completed": true, + "id": "mEfEaFSCKCC" + }, + { + "uid": "mEfEaFSCKCC", + "level": "DEBUG", + "category": "TRACKER_IMPORT_JOB", + "time": "2021-01-01T00:00:01.00", + "message": "TRACKER_IMPORT_JOB ( mEfEaFSCKCC ) preheat completed in 1.00000 sec. Import:preheat", + "completed": true, + "id": "mEfEaFSCKCC" + }, + { + "uid": "mEfEaFSCKCC", + "level": "INFO", + "category": "TRACKER_IMPORT_JOB", + "time": "2021-01-01T00:00:00.00", + "message": "TRACKER_IMPORT_JOB ( mEfEaFSCKCC ) started by admin ( xE7jOejl9FI ) Import:Start", + "completed": true, + "id": "mEfEaFSCKCC" + } +] +``` + +Additionally, the following endpoint will return the import summary of the import job. This import summary will only be available after the import has completed: + +`GET /tracker/jobs/{uid}/report` + +| Parámetros | Descripción | Example | +| --- | --- | --- | +| path `/{uid}` | The UID of an existing tracker import job | ABCDEF12345 | +| `reportMode` | The level of the report to return | `FULL`|`ERRORS`|`WARNINGS` | + +#### **_REQUEST_** example { #request-example } + +`GET /tracker/jobs/mEfEaFSCKCC/report` + +#### **_RESPONSE_** example { #response-example } + +The [response payload](#sample-responses) is the same as the one returned after a sync import request. + +> **Note** +> +> Both endpoints are used primarily for async import; however, `GET /tracker/jobs/{uid}` would also work for sync requests as it eventually uses the same import process and logging as async requests. + +### Import Summary Structure { #import-summary-structure } + +Import summaries have the following overall structure, depending on the requested `reportMode`: + +```json +{ + "status": "...", + "validationReport": {}, + "stats": {}, + "timingsStats": {}, + "bundleReport": {}, + "message": {} +} +``` + +**_status_** + +The property, `status`, of the import summary indicates the overall status of the import. If no errors or warnings were raised during the import, the `status` is reported as `OK`. The presence of any error or warnings in the import will result in a status of type `ERROR` or `WARNING`. + +`status` is based on the presence of the most significant `validationReport`. `ERROR` has the highest significance, followed by `WARNING` and finally `OK`. This implies that `ERROR` is reported as long as a single error was found during the import, regardless of how many warnings occurred. + +> **Note** +> +> If the import is performed using the AtomicMode "OBJECT", where the import will import any data without validation errors, the overall status will still be `ERROR` if any errors were found. + +**_validationReport_** + +The `validationReport` might include `errorReports` and `warningReports` if any errors or warnings were present during the import. When present, they provide a detailed list of any errors or warnings encountered. + +For example, a validation error while importing a `TRACKED_ENTITY`: + +```json +{ + "validationReport": { + "errorReports": [ + { + "message": "Could not find TrackedEntityType: `Q9GufDoplCL`.", + "errorCode": "E1005", + "trackerType": "TRACKED_ENTITY", + "uid": "Kj6vYde4LHh" + }, + ... + ], + "warningReports" : [ ... ] + } +} +``` + +The report contains a message and a code describing the actual error (See the [error codes](#error-codes) section for more information about errors). Additionally, the report includes the `trackerType` and `uid`, which aims to describe where in the data the error was found. In this case, there was a `TRACKED_ENTITY` with the uid `Kj6vYde4LHh`, which had a reference to a tracked entity type that was not found. + +> **Note** +> +> When referring to the `uid` of tracker objects, they are labeled as their object names in the payload. For example, the `uid` of a tracked entity would in the payload have the name "trackedEntity". The same goes for "enrollment", "event" and "relationship" for enrollments, events, and relationships, respectively. +> +> If no uid is provided in the payload, the import process will generate new uids. This means the error report might refer to a uid that does not exist in your payload. +> +> Errors represent issues with the payload which the importer can not circumvent. Any errors will block that data from being imported. Warnings, on the other hand, are issues where it's safe to circumvent them, but the user should be made aware that it happened. Warnings will not block data from being imported. + +**_stats_** + +The stats provide a quick overview of the import. After an import is completed, these will be the actual counts representing how much data was created, updated, deleted, or ignored. + +Ejemplo: + +```json +{ + "stats": { + "created": 2, + "updated": 2, + "deleted": 1, + "ignored": 5, + "total": 10 + } +} +``` + +`created` refers to how many new objects were created. In general, objects without an existing uid in the payload will be treated as new objects. + +`updated` refers to the number of objects updated. If an object has a uid set in the payload, it will be treated as an update as long as that same uid exists in the database. + +`deleted` refers to the number of objects deleted during the import. Deletion only happens when the import is configured to delete data and only then when the objects in the payload have existing uids set. + +`ignored` refers to objects that were not persisted. Objects can be ignored for several reasons, for example trying to create something that already exists. Ignores should always be safe, so if something was ignored, it was not necessary, or it was due to the configuration of the import. + +**_timingsStats_** + +`timingStats` represents the time elapsed in different steps of the import. These stats do not provide an accurate overall time for the import but rather the time spent in the code for different steps. + +The `timingStats` are primarily helpful in debugging imports that are causing issues to see which part of the import is having issues. + +```json +{ + "timingsStats": { + "timers": { + "preheat": "0.234086 sec.", + "preprocess": "0.000058 sec.", + ... + "totalImport": "0.236810 sec.", + "validation": "0.001533 sec." + } + } +} +``` + +**_bundleReport_** + +When the import is completed, the `bundleReport` contains all the [tracker objects](#tracker-objects) imported. + +For example, `TRACKED_ENTITY`: + +```json +{ + "bundleReport": { + "typeReportMap": { + "TRACKED_ENTITY": { + "trackerType": "TRACKED_ENTITY", + "stats": { + "created": 1, + "updated": 0, + "deleted": 0, + "ignored": 0, + "total": 1 + }, + "objectReports": [ + { + "trackerType": "TRACKED_ENTITY", + "uid": "FkxTQC4EAKK", + "index": 0, + "errorReports": [] + } + ] + }, + ... + } + } +} +``` + +As seen, each type of tracker object will be reported, and each has its own stats and `objectReports`. These `objectReports` will provide details about each imported object, like their type, their uid, and any error or warning reports is applicable. + +**_message_** + +If the import ended abruptly, the `message` would contain further information in relation to what happened. + +### Import Summary Report Level { #import-summary-report-level } + +As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a specific `reportMode` parameter. By default the endpoint will return an `importSummary` with `reportMode` `ERROR`. + +| Parámetros | Descripción | +| --- | --- | +| `FULL` | Returns everything from `WARNINGS`, plus `timingsStats` | +| `WARNINGS` | Returns everything from `ERRORS`, plus `warningReports` in `validationReports` | +| `ERRORS` (default) | Returns only `errorReports` in `validationReports` | + +In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. + +### Error Codes { #webapi_nti_error_codes } + +There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional descriptions. The placeholders in the error messages (`{0}`,`{1}`,`{2}`..) are usually uids unless otherwise specified. + +| Error Code | Error Message | Descripción | +| :-- | :-- | :-- | +| E1000 | User: `{0}`, has no write access to OrganisationUnit: `{1}`. | This typically means that the OrganisationUnit `{1}` is not in the capture scope of the user `{0}` for the write operation to be authorized. | +| E1001 | User: `{0}`, has no data write access to TrackedEntityType: `{1}`. | The error occurs when the user is not authorized to create or modify data of the TrackedEntityType `{1}` | +| E1002 | TrackedEntityInstance: `{0}`, already exists. | This error is thrown when trying to create a new TrackedEntity with an already existing uid. Make sure a new uid is used when adding a new TrackedEntity. | +| E1005 | Could not find TrackedEntityType: `{0}`. | Error thrown when trying to fetch a non existing TrackedEntityType with uid `{0}` . This might also mean that the user does not have read access to the TrackedEntityType. | +| E1006 | Attribute: `{0}`, does not exist. | Error thrown when the system was not able to find a matching TrackedEntityAttribute with uid `{0}`. This might also mean that the user does not have access to the TrackedEntityAttribute. | +| E1007 | Error validating attribute value type: `{0}`; Error: `{1}`. | Mismatch between value type of a TrackedEntityAttribute and its provided attribute value. The actual validation error will be displayed in `{1}`. | +| E1009 | File resource: `{0}`, has already been assigned to a different object. | The File resource uid `{0}` is already assigned to another object in the system. | +| E1010 | Could not find Program: `{0}`, linked to Event. | The system was unable to find a Program with the uid `{0}` specified inside the Event payload. This might also mean that the specific Program is not accessible by the logged in user. | +| E1011 | Could not find OrganisationUnit: `{0}`, linked to Event. | The system was unable to find a OrganisationUnit with uid `{0}` specified inside the Event payload. | +| E1012 | Geometry does not conform to FeatureType: `{0}`. | FeatureType provided is either NONE or an incompatible one for the provided geometry value. | +| E1013 | Could not find ProgramStage: `{0}`, linked to Event. | The system was unable to find a ProgramStage with uid `{0}` specified inside the Event payload. This might also mean that the ProgramStage is not accessible to the logged in user. | +| E1014 | Provided Program: `{0}`, is a Program without registration. An Enrollment cannot be created into Program without registration. | Enrollments can only be created for Programs with registration. | +| E1015 | TrackedEntityInstance: `{0}`, already has an active Enrollment in Program `{1}`. | Cannot enroll into a Program if another active enrollment already exists for the Program. The active enrollment will have to be completed first atleast. | +| E1016 | TrackedEntityInstance: `{0}`, already has an active enrollment in Program: `{1}`, and this program only allows enrolling one time. | As per the Program `{1}` configuration, a TrackedEntity can only be enrolled into that Program once. It looks like the TrackedEntity `{0}` already has either an ACTIVE or COMPLETED enrollment in that Program. Hence another enrollment cannot be added. | +| E1018 | Attribute: `{0}`, is mandatory in program `{1}` but not declared in enrollment `{2}`. | Attribute value is missing in payload, for an attribute that is defined as mandatory for a Program. Make sure that attribute values for mandatory attributes are provided in the payload. | +| E1019 | Only Program attributes is allowed for enrollment; Non valid attribute: `{0}`. | Attribute uid `{0}` specified in the enrollment payload is not associated with the Program. | +| E1020 | Enrollment date: `{0}`, can`t be future date. | Cannot enroll into a future date unless the Program allows for it in its configuration. | +| E1021 | Incident date: `{0}`, can`t be future date. | Incident date cannot be a future date unless the Program allows for it in its configuration. | +| E1022 | TrackedEntityInstance: `{0}`, must have same TrackedEntityType as Program `{1}`. | The Program is configured to accept TrackedEntityType uid that is different from what is provided in the enrollment payload. | +| E1023 | DisplayIncidentDate is true but property occurredAt is null or has an invalid format: `{0}`. | Program is configured with DisplayIncidentDate but its either null or an invalid date in the payload. | +| E1025 | Property enrolledAt is null or has an invalid format: `{0}`. | EnrolledAt Date is mandatory for an Enrollment. Make sure it is not null and has a valid date format. | +| E1029 | Event OrganisationUnit: `{0}`, and Program: `{1}`, don't match. | The Event payload uses a Program `{1}` which is not configured to be accessible by OrganisationUnit `{0}`. | +| E1030 | Event: `{0}`, already exists. | This error is thrown when trying to add a new Event with an already existing uid. Make sure a new uid is used when adding a new Event. | +| E1031 | Event OccurredAt date is missing. | OccuredAt property is either null or has an invalidate date format in the payload. | +| E1032 | Event: `{0}`, do not exist. | | +| E1033 | Event: `{0}`, Enrollment value is NULL. | | +| E1035 | Event: `{0}`, ProgramStage value is NULL. | | +| E1036 | Event: `{0}`, TrackedEntityInstance does not point to a existing object. | The system was unable to find a TrackedEntity with the uid specified inside the event payload. This might also mean that the user does not have read access to the TrackedEntity. | +| E1039 | ProgramStage: `{0}`, is not repeatable and an event already exists. | An Event already exists for the ProgramStage for the specific Enrollment. Since the ProgramStage is configured to be non-repeatable, another Event for the same ProgramStage cannot be added. | +| E1041 | Enrollment OrganisationUnit: `{0}`, and Program: `{1}`, don't match. | The Enrollment payload contains a Program `{1}` which is not configured to be accessible by the OrganisationUnit `{0}`. | +| E1042 | Event: `{0}`, needs to have completed date. | If the program is configured to have completeExpiryDays, then CompletedDate is mandatory for a COMPLETED event payload. An Event with status as COMPLETED should have completedDate property as non-null and a valid date format. | +| E1048 | Object: `{0}`, uid: `{1}`, has an invalid uid format. | A valid uid has 11 characters. The first character has to be an alphabet (a-z or A-Z) and the remaining 10 characters can be alphanumeric (a-z or A-Z or 0-9). | +| E1049 | Could not find OrganisationUnit: `{0}`, linked to Tracked Entity. | The system could not find an OrganisationUnit with uid `{0}`. | +| E1050 | Event ScheduledAt date is missing. | ScheduledAt property in the Event payload is either missing or an invalid date format. | +| E1055 | Default AttributeOptionCombo is not allowed since program has non-default CategoryCombo. | The Program is configured to contain non-default CategoryCombo but the request uses the Default AttributeOptionCombo. | +| E1056 | Event date: `{0}`, is before start date: `{1}`, for AttributeOption: `{2}`. | The CategoryOption has a start date configured , the Event date in the payload cannot be earlier than this start date. | +| E1057 | Event date: `{0}`, is after end date: `{1}`, for AttributeOption; `{2}`. | The CategoryOption has an end date configured, the Event date in the payload cannot be later than this end date. | +| E1063 | TrackedEntityInstance: `{0}`, does not exist. | Error thrown when trying to fetch a non existing TrackedEntity with uid `{0}` . This might also mean that the user does not have read access to the TrackedEntity. | +| E1064 | Non-unique attribute value `{0}` for attribute `{1}` | The attribute value has to be unique within the defined scope. The error indicates that the attribute value already exists for another TrackedEntity. | +| E1068 | Could not find TrackedEntityInstance: `{0}`, linked to Enrollment. | The system could not find the TrackedEntity specified in the Enrollment payload. This might also mean that the user does not have read access to the TrackedEntity. | +| E1069 | Could not find Program: `{0}`, linked to Enrollment. | The system could not find the Program specified in the Enrollment payload. This might also mean that the user does not have read access to the Program. | +| E1070 | Could not find OrganisationUnit: `{0}`, linked to Enrollment. | The system could not find the OrganisationUnit specified in the Enrollment payload. | +| E1074 | FeatureType is missing. | | +| E1075 | Attribute: `{0}`, is missing uid. | | +| E1076 | `{0}` `{1}` is mandatory and can't be null | | +| E1077 | Attribute: `{0}`, text value exceed the maximum allowed length: `{0}`. | | +| E1080 | Enrollment: `{0}`, already exists. | This error is thrown when trying to create a new Enrollmentt with an already existing uid. Make sure a new uid is used when adding a new Enrollment. | +| E1081 | Enrollment: `{0}`, do not exist. | Error thrown when trying to fetch a non existing Enrollment with uid `{0}` . This might also mean that the user does not have read access to the Enrollment. | +| E1082 | Event: `{0}`, is already deleted and can't be modified. | If the event is soft deleted, no modifications on it are allowed. | +| E1083 | User: `{0}`, is not authorized to modify completed events. | Only a super user or a user with the authority "F_UNCOMPLETE_EVENT" can modify completed events. Completed Events are those Events with status as COMPLETED. | +| E1084 | File resource: `{0}`, reference could not be found. | | +| E1085 | Attribute: `{0}`, value does not match value type: `{1}`. | Mismatch between value type of an attribute and its provided attribute value. | +| E1089 | Event: `{0}`, references a Program Stage `{1}` that does not belong to Program `{2}`. | The ProgramStage uid and Program uid in the Event payload is incompatible. | +| E1090 | Attribute: `{0}`, is mandatory in tracked entity type `{1}` but not declared in tracked entity `{2}`. | The payload has missing values for mandatory TrackedEntityTypeAttributes. | +| E1091 | User: `{0}`, has no data write access to Program: `{1}`. | The Program sharing configuration is such that, the user does not have write access for this Program. | +| E1095 | User: `{0}`, has no data write access to ProgramStage: `{1}`. | The ProgramStage sharing configuration is such that, the user does not have write access for this ProgramStage. | +| E1096 | User: `{0}`, has no data read access to Program: `{1}`. | The Program sharing configuration is such that, the user does not have read access for this Program. | +| E1099 | User: `{0}`, has no write access to CategoryOption: `{1}`. | The CategoryOption sharing configuration is such that, the user does not have write access for this CategoryOption | +| E1100 | User: `{0}`, is lacking 'F_TEI_CASCADE_DELETE' authority to delete TrackedEntityInstance: `{1}`. | There exists undeleted Enrollments for this TrackedEntity. If the user does not have 'F_TEI_CASCADE_DELETE' authority, then these Enrollments has to be deleted first explicitly to be able to delete the TrackedEntity. | +| E1102 | User: `{0}`, does not have access to the tracked entity: `{1}`, Program: `{2}`, combination. | This error is thrown when the user's OrganisationUnit does not have the ownership of this TrackedEntity for this specific Program. The owning OrganisationUnit of the TrackedEntity-Program combination should fall into the capture scope (in some cases the search scope) of the user. | +| E1103 | User: `{0}`, is lacking 'F_ENROLLMENT_CASCADE_DELETE' authority to delete Enrollment : `{1}`. | There exists undeleted Events for this Enrollment. If the user does not have 'F_ENROLLMENT_CASCADE_DELETE' authority, then these Events has to be deleted first explicitly to be able to delete the Enrollment. | +| E1104 | User: `{0}`, has no data read access to program: `{1}`, TrackedEntityType: `{2}`. | The sharing configuration of the TrackedEntityType associated with the Program is such that, the user does not have data read access to it. | +| E1112 | Attribute value: `{0}`, is set to confidential but system is not properly configured to encrypt data. | Either JCE files is missing or the configuration property `encryption.password` might be missing in `dhis.conf`. | +| E1113 | Enrollment: `{0}`, is already deleted and can't be modified. | If the Enrollment is soft deleted, no modifications on it are allowed. | +| E1114 | TrackedEntity: `{0}`, is already deleted and can't be modified. | If the TrackedEntity is soft deleted, no modifications on it are allowed. | +| E1115 | Could not find CategoryOptionCombo: `{0}`. | | +| E1116 | Could not find CategoryOption: `{0}`. | This might also mean the CategoryOption is not accessible to the user. | +| E1117 | CategoryOptionCombo does not exist for given category combo and category options: `{0}`. | | +| E1118 | Assigned user `{0}` is not a valid uid. | | +| E1119 | A Tracker Note with uid `{0}` already exists. | | +| E1120 | ProgramStage `{0}` does not allow user assignment | Event payload has assignedUserId but the ProgramStage is not configured to allow user assignment. | +| E1121 | Missing required tracked entity property: `{0}`. | | +| E1122 | Missing required enrollment property: `{0}`. | | +| E1123 | Missing required event property: `{0}`. | | +| E1124 | Missing required relationship property: `{0}`. | | +| E1125 | Value `{0}` is not a valid option for `{1}` `{2}` in option set `{3}` | | +| E1017 | Attribute: `{0}`, does not exist. | | +| E1093 | User: `{0}`, has no search access to OrganisationUnit: `{1}`. | | +| E1094 | Not allowed to update Enrollment: `{0}`, existing Program `{1}`. | The Enrollment payload for an existing Enrollment has a different Program uid than the one it was originally enrolled with. | +| E1110 | Not allowed to update Event: `{0}`, existing Program `{1}`. | The Event payload for an existing Event has a different Program uid than the one it was originally created with. | +| E1111 | We have a generated attribute: `{0}`, but no pattern. | | +| E1043 | Event: `{0}`, completeness date has expired. Not possible to make changes to this event. | A user without 'F_EDIT_EXPIRED' autthority cannot update an Event that has passed its expiry days as configured in its Program. | +| E1046 | Event: `{0}`, needs to have at least one (event or schedule) date. | Either of occuredAt or scheduledAt property should be present in the Event payload. | +| E1047 | Event: `{0}`, date belongs to an expired period. It is not possible to create such event. | Event occuredAt or scheduledAt has a value that is earlier than the PeriodType start date. | +| E1300 | Generated by program rule (`{0}`) - `{1}` | | +| E1302 | Generated by program rule (`{0}`) - DataElement `{1}` is not valid: `{2}` | | +| E1303 | Generated by program rule (`{0}`) - Mandatory DataElement `{1}` is not present | | +| E1304 | Generated by program rule (`{0}`) - DataElement `{1}` is not a valid data element | | +| E1305 | Generated by program rule (`{0}`) - DataElement `{1}` is not part of `{2}` program stage | | +| E1306 | Generated by program rule (`{0}`) - Mandatory Attribute `{1}` is not present | | +| E1307 | Generated by program rule (`{0}`) - Unable to assign value to data element `{1}`. The provided value must be empty or match the calculated value `{2}` | | +| E1308 | Generated by program rule (`{0}`) - DataElement `{1}` is being replaced in event `{2}` | | +| E1309 | Generated by program rule (`{0}`) - Unable to assign value to attribute `{1}`. The provided value must be empty or match the calculated value `{2}` | | +| E1310 | Generated by program rule (`{0}`) - Attribute `{1}` is being replaced in tei `{2}` | | +| E4000 | Relationship: `{0}` cannot link to itself | | +| E4001 | Relationship Item `{0}` for Relationship `{1}` is invalid: an Item can link only one Tracker entity. | | +| E4006 | Could not find relationship Type: `{0}`. | | +| E4009 | Relationship Type `{0}` is not valid. | | +| E4010 | Relationship Type `{0}` constraint requires a {1} but a {2} was found. | | +| E4011 | Relationship: `{0}` cannot be persisted because {1} {2} referenced by this relationship is not valid. | | +| E4012 | Could not find `{0}`: `{1}`, linked to Relationship. | | +| E4013 | Relationship Type `{0}` constraint is missing {1}. | | +| E4014 | Relationship Type `{0}` constraint requires a Tracked Entity having type `{1}` but `{2}` was found. | | +| E4062 | Start date or end date not specified with ABSOLUTE date period type for item `{0}` | | +| E4063 | Assigned users cannot be empty when assigned user mode is set to PROVIDED | | +| E4064 | Organisation unit cannot be empty with `{0}` org unit mode | | +| E4065 | Data item UID is missing in filter | | +| E4066 | No data element found for item: `{0}` | | +| E4067 | Attribute UID is missing in filter | | +| E4068 | No tracked entity attribute found for attribute: `{0}` | | +| E9999 | N/A | Undefined error message. | + +### Validation { #webapi_nti_validation } + +While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed to provide a better understanding if validation fails for your import. + +#### Required properties { #required-properties } + +Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object section](#webapi_nti_tracker_objects). + +When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: + +1. The reference is present and not null in the payload. +2. The reference points to the correct type of data and exists in the database +3. The user has access to see the reference + +If the first condition fails, the import will fail with a message about a missing reference. However, suppose the reference points to something that doesn't exist or which the user cannot access. In that case, both cases will result in a message about the reference not being found. + +#### Formats { #formats } + +Some of the properties of tracker objects require a specific format. When importing data, each of these properties is validated against the expected format and will return different errors depending on which property has a wrong format. Some examples of properties that are validated this way: + +- UIDs (These cover all references to other data or metadata in DHIS2.) +- Dates +- Geometry (The coordinates must match the format as specified by its type) + +#### User access { #user-access } + +All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) and the organisation units ([Organisation Unit Scopes](#webapi_nti_ou_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. + +Sharing is validated at the same time as references are looked up in the database. Metadata outside of the user's access will be treated as if it doesn't exist. The import will validate any metadata referenced in the data. + +Organisation units, on the other hand, serve a dual purpose. It will primarily make sure that data can only be imported when imported for an organisation unit the user has within their "capture scope". Secondly, organisation units are also used to restrict what programs are available. That means if you are trying to import data for an organisation unit that does not have access to the Program you are importing, the import will be invalid. + +Users with the `ALL` authority will ignore the limits of sharing and organisation unit scopes when they import data. However, they can not import enrollments in organisation units that do not have access to the enrollment program. + +#### Attribute and Data values { #attribute-and-data-values } + +Attributes and data values are part of a tracked entity and an event, respectively. However, attributes can be linked to a tracked entity either through its type (TrackedEntityType) or its Program (Program). Additionally, attributes can also be unique. + +The initial validation done in the import is to make sure the value provided for an attribute or data element conforms to the type of value expected. For example, suppose you import a value for a data element with a numeric type. In that case, the value is expected to be numeric. Any errors related to a mismatch between a type and a value will result in the same error code but with a specific message related to the type of violation. + +Mandatory attributes and data values are also checked. Currently, removing mandatory attributes is not allowed. Some use-cases require values to be sent separately, while others require all values to be sent as one. Programs can be configured to either validate mandatory attributes `ON_COMPLETE` or `ON_UPDATE_AND_INSERT` to accommodate these use-cases. + +The import will validate unique attributes at the time of import. That means as long as the provided value is unique for the attribute in the whole system, it will pass. However, if the unique value is found used by any other tracked entity other than the one being imported, it will fail. + +#### Configuration { #configuration } + +The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. Some examples of configurable validations: + +- Feature type (For geometry) +- User-assignable events +- Allow future dates +- Enroll once +- And more. + +These configurations will further change how validation is performed during import. + +### Program Rules { #webapi_nti_program_rules } + +Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will also run a selection of these rules. Since the importer is also running these rules, we can ensure an additional level of validation. + +Not all program rule actions are supported since they are only suitable for a frontend presentation. A complete list of the supported program rule actions is presented below. + +| Program Rule Action | Soportado | +| ----------------------- | :-------: | +| **DISPLAYTEXT** | | +| **DISPLAYKEYVALUEPAIR** | | +| **HIDEFIELD** | | +| **HIDESECTION** | | +| **ASSIGN** | **X** | +| **SHOWWARNING** | **X** | +| **SHOWERROR** | **X** | +| **WARNINGONCOMPLETION** | **X** | +| **ERRORONCOMPLETION** | **X** | +| **CREATEEVENT** | | +| **SETMANDATORYFIELD** | **X** | +| **SENDMESSAGE** | **X** | +| **SCHEDULEMESSAGE** | **X** | + +Program rules are evaluated in the importer in the same way they are evaluated in the Tracker apps. To summarize, the following conditions are considered when enforcing the program rules: + +- The program rule must be linked to the data being imported. For example, a program stage or a data element. +- The Program rule's condition must be evaluated to true + +The results of the program rules depend on the actions defined in those rules: + +- Program rule actions may end in 2 different results: Warnings or Errors. + - Errors will make the validation fail, while the warnings will be reported as a message in the import summary. + - SHOWWARNING and WARNINGONCOMPLETION actions can generate only Warnings. + - SHOWERROR, ERRORONCOMPLETION, and SETMANDATORYFIELD actions can generate only Errors. + - ASSIGN action can generate both Warnings and Errors. + - When the action is assigning a value to an empty attribute/data element, a warning is generated. + - When the action is assigning a value to an attribute/data element that already has the same value to be assigned, a warning is generated. + - When the action is assigning a value to an attribute/data element that already has a value and the value to be assigned is different, an error is generated unless the `RULE_ENGINE_ASSIGN_OVERWRITE` system setting is set to true. + +Additionally, program rules can also result in side-effects, like send and schedule messages. More information about side effects can be found in the following section. + +> **NOTE** +> +> Program rules can be skipped during import using the `skipProgramRules` parameter. + +### Side Effects { #webapi_nti_side_effects } + +After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not affect the import itself. + +Side effects are tasks running detached from the import but are always triggered by an import. Since side effects are detached from the import, they can fail even when the import is successful. Additionally, side effects are only run when the import is successful, so they cannot fail the other way around. + +The following side effects are currently supported: + +| Side Effects | Soportado | Descripción | +| --- | :-: | --- | +| **Tracker Notification** | **X** | Updates can trigger notifications. Updates which trigger notifications are **enrollment**, **event update**, **event or enrollment completion**. | +| **ProgramRule Notification** | **X** | Program rules can trigger notifications. Note that these notifications are part of program rule effects which are generated through the DHIS2 rule engine. | + +> **NOTE** +> +> Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. + +### Assign user to events { #webapi_nti_user_event_assignment } + +Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. + +Assigning a user to an event will not change the access or permissions for users but will create a link between the Event and the user. When an event has a user assigned, you can query events from the API using the `assignedUser` field as a parameter. + +When you want to assign a user to an event, you simply provide the UID of the user you want to assign in the `assignedUser` field. See the following example: + +```json +{ + ... + "events": [ + { + "event": "ZwwuwNp6gVd", + "programStage": "nlXNK4b7LVr", + "orgUnit": "O6uvpzGd5pu", + "enrollment": "MNWZ6hnuhSw", + "assignedUser" : "M0fCOxtkURr" + } + ], + ... +} +``` + +In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event with uid `ZwwuwNp6gVd`. Only one user can be assigned to a single event. + +To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. + +## Tracker Export { #webapi_nti_export } + +Tracker export endpoints are a set of services that allow clients to query and retrieve objects stored using the import endpoint. + +Besides differences highlighted in **[Changes in the API](#Changes-in-the-API)**, request parameters for these endpoints match older ones. + +These endpoints are still being developed and are subject to change. However, the `request` and `response` interfaces will most likely not undergo significant changes. + +Tracker export endpoints deal with the following Tracker objects: + +- **Tracked Entities** +- **Events** +- **Enrollments** +- **Relationships** + +> **NOTE** +> +> - All these endpoints currently support `JSON`, `CSV` is only supported by only Tracked Entities and Events. +> +> - These endpoints adopt the new naming convention documented in **[Changes in the API](#Changes-in-the-API)** + +### Common request parameters { #common-request-parameters } + +The following endpoint supports standard parameters for pagination. + +- **Tracked Entities** `GET /api/tracker/trackedEntities` +- **Events** `GET /api/tracker/events` +- **Enrollments** `GET /api/tracker/enrollments` +- **Relationships** `GET /api/tracker/relationships` + +#### Request parameters for pagination { #request-parameters-for-pagination } + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `page` | `Integer` | Any positive integer | Page number to return. Defaults to 1 if missing | +| `pageSize` | `Integer` | Any positive integer | Page size. Defaults to 50. | +| `totalPages` | `Boolean` | `true`|`false` | Indicates whether to return the total number of pages in the response | +| `skipPaging` | `Boolean` | `true`|`false` | Indicates whether paging should be ignored and all rows should be returned. Defaults to `false`, meaning that by default all requests are paginated, unless `skipPaging=true` | +| `order` | `String` | comma-delimited list of `OrderCriteria` in the form of `propName:sortDirection`.

Example: `createdAt:desc`

**Note:** `propName` is case sensitive, `sortDirection` is case insensitive | Sort the response based on given `OrderCriteria` | + +> **Caution** +> +> Be aware that the performance is directly related to the amount of data requested. Larger pages will take more time to return. + +#### Request parameters for Organisational Unit selection mode { #request-parameters-for-organisational-unit-selection-mode } + +The available organisation unit selection modes are explained in the following table. + +| Mode | Descripción | +| --- | --- | +| `SELECTED` | Organisation units defined in the request. | +| `CHILDREN` | The selected organisation units and the immediate children, i.e., the organisation units at the level below. | +| `DESCENDANTS` | The selected organisation units and all children, i.e., all organisation units in the sub-hierarchy. | +| `ACCESSIBLE` | The data view organisation units associated with the current user and all children, i.e., all organisation units in the sub-hierarchy. Will fall back to data capture organisation units associated with the current user if the former is not defined. | +| `CAPTURE` | The data capture organisation units associated with the current user and all children, i.e., all organisation units in the sub-hierarchy. | +| `ALL` | All organisation units in the system. Requires the ALL authority. | + +#### Request parameter to filter responses { #webapi_nti_field_filter } + +All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few possible `fields` filters are shown below. Refer to [Metadata field filter](#webapi_metadata_field_filter) for a more complete guide on how to use `fields`. + +##### Ejemplos { #examples } + +| Parameter example | Meaning | +| :-- | :-- | +| `fields=*` | returns all fields | +| `fields=createdAt,uid` | only returns fields `createdAt` and `uid` | +| `fields=enrollments[*,!uid]` | returns all fields of `enrollments` except `uid` | +| `fields=enrollments[uid]` | only returns `enrollments` field `uid` | +| `fields=enrollments[uid,enrolledAt]` | only returns `enrollments` fields `uid` and `enrolledAt` | + +### Tracked Entities (`GET /api/tracker/trackedEntities`) { #tracked-entities-get-apitrackertrackedentities } + +Two endpoints are dedicated to tracked entities: + +- `GET /api/tracker/trackedEntities` + - retrieves tracked entities matching given criteria +- `GET /api/tracker/trackedEntities/{id}` + - retrieves a tracked entity given the provided id + +#### Tracked Entities Collection endpoint `GET /api/tracker/trackedEntities` { #tracked-entities-collection-endpoint-get-apitrackertrackedentities } + +The purpose of this endpoint is to retrieve tracked entities matching client-provided criteria. + +The endpoint returns a list of tracked entities that match the request parameters. + +##### Request syntax { #request-syntax } + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `query` | `String` | `{operator}:{filter-value}` | Creates a filter over tracked entity attributes. Only the filter value is mandatory. The `EQ` operator is used if `operator` is not specified. | +| `attribute` | `String` | Comma separated values of attribute `UID`s | For each tracked entity in the response, only returns specified attributes | +| `filter` | `String` | Comma separated values of attribute filters | Narrows response to TEIs matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it. | +| `orgUnit` | `String` | semicolon-delimited list of organisational unit `UID` | Only return tracked entity instances belonging to provided organisational units | +| `ouMode` see [ouModes](#Request-parameters-for-Organisational-Unit-selection-mode) | `String` | `SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL` | The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only. | +| `program` | `String` | Program `UID` | a Program `UID` for which instances in the response must be enrolled into | +| `programStatus` | `String` | `ACTIVE`|`COMPLETED`|`CANCELLED` | The ProgramStatus of the Tracked Entity Instance in the given program | +| `programStage` | `String` | `UID` | a Program Stage `UID` for which instances in the response must have events for | +| `followUp` | `Boolean` | `true`|`false` | Indicates whether the Tracked Entity Instance is marked for follow up for the specified Program | +| `updatedAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Start date for last updated | +| `updatedBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | End date for last updated | +| `updatedWithin` | `Duration` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601#Durations) | Returns TEIs not older than specified Duration | +| `enrollmentEnrolledAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Start date for enrollment in the given program | +| `enrollmentEnrolledBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | End date for enrollment in the given program | +| `enrollmentOccurredAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Start date for incident in the given program | +| `enrollmentOccurredBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | End date for incident in the given program | +| `trackedEntityType` | `String` | UID of tracked entity type | Only returns Tracked Entity Instances of given type | +| `trackedEntity` | `String` | semicolon-delimited list of tracked entity instance `UID` | Filter the result down to a limited set of tracked entities using explicit uids of the tracked entity instances by using `trackedEntity=id1;id2`. This parameter will, at the very least, create the outer boundary of the results, forming the list of all tracked entities using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | +| `assignedUserMode` | `String` | `CURRENT`|`PROVIDED`|`NONE`|`ANY` | Restricts result to tracked entities with events assigned based on the assigned user selection mode. See table below "Assigned user modes" for explanations. | +| `assignedUser` | `String` | Semicolon-delimited list of user UIDs to filter based on events assigned to the users. | Filter the result down to a limited set of tracked entities with events that are assigned to the given user IDs by using `assignedUser=id1;id2`.This parameter will only be considered if assignedUserMode is either `PROVIDED` or `null`. The API will error out, if for example, `assignedUserMode=CURRENT` and `assignedUser=someId` | +| `eventStatus` | `String` | `ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of any events in the specified program | +| `eventOccurredAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Start date for Event for the given Program | +| `eventOccurredBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | End date for Event for the given Program | +| `skipMeta` | `Boolean` | `true`|`false` | Indicates whether not to include metadata in the response. | +| `includeDeleted` | `Boolean` | `true`|`false` | Indicates whether to include soft-deleted elements | +| `includeAllAttributes` | `Boolean` | `true`|`false` | Indicates whether to include all TEI attributes | +| `attachment` | `String` | | The file name in case of exporting as a file | +| `potentialDuplicate` | `Boolean` | `true`|`false` | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not. | + +The available assigned user modes are explained in the following table. + +Table: Assigned user modes + +| Mode | Descripción | +| --- | --- | +| CURRENT | Includes events assigned to the current logged in user. | +| PROVIDED | Includes events assigned to the user provided in the request. | +| NONE | Includes unassigned events only. | +| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | + +The query is case insensitive. The following rules apply to the query parameters. + +- At least one organisation unit must be specified using the `orgUnit` parameter (one or many), or `ouMode=ALL` must be specified. + +- Only one of the `program` and `trackedEntity` parameters can be specified (zero or one). + +- If `programStatus` is specified, then `program` must also be specified. + +- If `followUp` is specified, then `program` must also be specified. + +- If `enrollmentEnrolledAfter` or `enrollmentEnrolledBefore` is specified then `program` must also be specified. + +- Filter items can only be specified once. + +##### Example requests { #example-requests } + +A query for all instances associated with a specific organisation unit can look like this: + + GET /api/tracker/trackedEntities?orgUnit=DiszpKrYNg8 + +To query for instances using one attribute with a filter and one attribute without a filter, with one organisation unit using the descendant organisation unit query mode: + + GET /api/tracker/trackedEntities?filter=zHXD5Ve1Efw:EQ:A + &attribure=AMpUYgxuCaE&orgUnit=DiszpKrYNg8;yMCshbaVExv + +A query for instances where attributes are included in the response and one attribute is used as a filter: + + GET /api/tracker/trackedEntities?filter=zHXD5Ve1Efw:EQ:A + &filter=AMpUYgxuCaE:LIKE:Road + &orgUnit=DiszpKrYNg8 + +A query where multiple operand and filters are specified for a filter item: + + GET /api/tracker/trackedEntities?orgUnit=DiszpKrYNg8 + &program=ur1Edk5Oe2n + &filter=lw1SqmMlnfh:GT:150 + &filter=lw1SqmMlnfh:LT:190 + +To query on an attribute using multiple values in an _IN_ filter: + + GET /api/tracker/trackedEntities?orgUnit=DiszpKrYNg8 + &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago + +To constrain the response to instances which are part of a specific program you can include a program query parameter: + + GET /api/tracker/trackedEntities?filter=zHXD5Ve1Efw:EQ:A + &orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS + &program=ur1Edk5Oe2n + +To specify program enrollment dates as part of the query: + + GET /API/tracker/trackedEntities? + &orgUnit=O6uvpzGd5pu&program=ur1Edk5Oe2n + &enrollmentEnrolledAfter=2013-01-01 + &enrollmentEnrolledBefore=2013-09-01 + +To constrain the response to instances of a specific tracked entity you can include a tracked entity query parameter: + + GET /api/tracker/trackedEntities?filter=zHXD5Ve1Efw:EQ:A + &orgUnit=O6uvpzGd5pu + &ouMode=DESCENDANTS + &trackedEntity=cyl5vuJ5ETQ + +By default the instances are returned in pages of size 50, to change this you can use the page and pageSize query parameters: + + GET /api/tracker/trackedEntities?filter=zHXD5Ve1Efw:EQ:A + &orgUnit=O6uvpzGd5pu + &ouMode=DESCENDANTS + &page=2&pageSize=3 + +You can use a range of operators for the filtering: + +| Operador | Descripción | +| -------- | ---------------------------------------------------- | +| `EQ` | Equal to | +| `GT` | Greater than | +| `GE` | Greater than or equal to | +| `LT` | Less than | +| `LE` | Less than or equal to | +| `NE` | Not equal to | +| `LIKE` | Like (free text match) | +| `IN` | Equal to one of the multiple values separated by ";" | + +##### Response format { #response-format } + +The `JSON` response can look like the following. + +Responses can be filtered on desired fields, see [Request parameter to filter responses](#webapi_nti_field_filter) + +```json +{ + "instances": [ + { + "trackedEntity": "IzHblRD2sDH", + "trackedEntityType": "nEenWmSyUEp", + "createdAt": "2014-03-26T15:40:36.669", + "createdAtClient": "2014-03-26T15:40:36.669", + "updatedAt": "2014-03-28T12:28:17.544", + "orgUnit": "g8upMTyEZGZ", + "inactive": false, + "deleted": false, + "relationships": [], + "attributes": [ + { + "attribute": "VqEFza8wbwA", + "code": "MMD_PER_ADR1", + "displayName": "Address", + "createdAt": "2016-01-12T00:00:00.000", + "updatedAt": "2016-01-12T00:00:00.000", + "valueType": "TEXT", + "value": "1061 Marconi St" + }, + { + "attribute": "RG7uGl4w5Jq", + "code": "Longitude", + "displayName": "Longitude", + "createdAt": "2016-01-12T00:00:00.000", + "updatedAt": "2016-01-12T00:00:00.000", + "valueType": "TEXT", + "value": "27.866613" + }, + ..., + ..., + ], + "enrollments": [], + "programOwners": [] + } + ], + "page": 1, + "total": 39, + "pageSize": 1 +} +``` + +#### Tracked Entities single object endpoint `GET /api/tracker/trackedEntities/{uid}` + +The purpose of this endpoint is to retrieve one tracked entity given its uid. + +##### Request syntax { #request-syntax } + +`GET /api/tracker/trackedEntities/{uid}?program={programUid}&fields={fields}` + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `uid` | `String` | `uid` | Return the Tracked Entity Instance with specified `uid` | +| `program` | `String` | `uid` | Include program attributes in the response (only the ones user has access to) | +| `fields` | `String` | Any valid field filter (default `*,!relationships,!enrollments,!events,!programOwners`) | Include specified sub-objects in the response | + +##### Example requests { #example-requests } + +A query for a Tracked Entity Instance: + + GET /api/tracker/trackedEntities/IzHblRD2sDH?program=ur1Edk5Oe2n&fields=* + +##### Response format { #response-format } + +This endpoint supports returning sub-objects when the `fields` request parameter is passed when json format is requested. In case of csv the `fields` request parameter has no effect and the response will always contain the same fields, which are: + +- trackedEntity (Identifier) +- trackedEntityType (Identifier) +- createdAt (Datetime) +- createdAtClient (Datetime) +- updatedAt (Datetime) +- updatedAtClient (Datetime) +- orgUnit (Identifier) +- inactive (boolean) +- deleted (boolean) +- potentialDuplicate (boolean) +- geometry (WKT, https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) +- storedBy (String) +- createdBy (Username of user) +- updatedBy (Username of user) +- attributes (each valid attribute listed as another column) + +An example of a json response: + +```json +{ + "trackedEntity": "IzHblRD2sDH", + "trackedEntityType": "nEenWmSyUEp", + "createdAt": "2014-03-26T15:40:36.669", + "updatedAt": "2014-03-28T12:28:17.544", + "orgUnit": "g8upMTyEZGZ", + "inactive": false, + "deleted": false, + "relationships": [], + "attributes": [ + { + "attribute": "w75KJ2mc4zz", + "code": "MMD_PER_NAM", + "displayName": "First name", + "createdAt": "2016-01-12T09:10:26.986", + "updatedAt": "2016-01-12T09:10:35.884", + "valueType": "TEXT", + "value": "Wegahta" + }, + { + "attribute": "zDhUuAYrxNC", + "displayName": "Last name", + "createdAt": "2016-01-12T09:10:26.986", + "updatedAt": "2016-01-12T09:10:35.884", + "valueType": "TEXT", + "value": "Goytiom" + } + ], + "enrollments": [ + { + "enrollment": "uT5ZysTES7j", + "createdAt": "2017-03-28T12:28:17.539", + "createdAtClient": "2016-03-28T12:28:17.539", + "updatedAt": "2017-03-28T12:28:17.544", + "trackedEntity": "IzHblRD2sDH", + "trackedEntityType": "nEenWmSyUEp", + "program": "ur1Edk5Oe2n", + "status": "ACTIVE", + "orgUnit": "g8upMTyEZGZ", + "orgUnitName": "Njandama MCHP", + "enrolledAt": "2020-11-10T12:28:17.532", + "occurredAt": "2020-10-12T12:28:17.532", + "followUp": false, + "deleted": false, + "events": [ + { + "event": "ixDYEGrNQeH", + "status": "ACTIVE", + "program": "ur1Edk5Oe2n", + "programStage": "ZkbAXlQUYJG", + "enrollment": "uT5ZysTES7j", + "enrollmentStatus": "ACTIVE", + "trackedEntity": "IzHblRD2sDH", + "relationships": [], + "scheduledAt": "2019-10-12T12:28:17.532", + "followup": false, + "deleted": false, + "createdAt": "2017-03-28T12:28:17.542", + "createdAtClient": "2016-03-28T12:28:17.542", + "updatedAt": "2017-03-28T12:28:17.542", + "attributeOptionCombo": "HllvX50cXC0", + "attributeCategoryOptions": "xYerKDKCefk", + "dataValues": [], + "notes": [] + } + ], + "relationships": [], + "attributes": [], + "notes": [] + } + ], + "programOwners": [ + { + "orgUnit": "g8upMTyEZGZ", + "trackedEntity": "IzHblRD2sDH", + "program": "ur1Edk5Oe2n" + } + ] +} +``` + +### Events (`GET /api/tracker/events`) { #events-get-apitrackerevents } + +Two endpoints are dedicated to events: + +- `GET /api/tracker/events` + - retrieves events matching given criteria +- `GET /api/tracker/events/{id}` + - retrieves an event given the provided id + +#### Events Collection endpoint `GET /api/tracker/events` { #events-collection-endpoint-get-apitrackerevents } + +Returns a list of events based on the provided filters. + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `program` | `String` | `uid` | Identifier of program | +| `programStage` | `String` | `uid` | Identifier of program stage | +| `programStatus` | `enum` | `ACTIVE`|`COMPLETED`|`CANCELLED` | Status of event in program | +| `filter` | `String` | Comma separated values of data element filters | Narrows response to events matching given filters. A filter is a colon separated property or data element UID with optional operator and value pairs. Example: `filter=fazCI2ygYkq:eq:PASSIVE` with operator starts with `eq` followed by a value. Multiple operator/value pairs for the same property/data element like `filter=qrur9Dvnyt5:gt:70:lt:80` are allowed. Repeating the same data element UID is not allowed. User needs access to the data element to filter on it. | +| `filterAttributes` | `String` | Comma separated values of attribute filters | Narrows response to TEIs matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it. | +| `followUp` | `boolean` | `true`|`false` | Whether event is considered for follow up in program. Defaults to `true` | +| `trackedEntityInstance` | `String` | `uid` | Identifier of tracked entity instance | +| `orgUnit` | `String` | `uid` | Identifier of organisation unit | +| `ouMode` see [ouModes](#Request-parameters-for-Organisational-Unit-selection-mode) | `String` | `SELECTED`|`CHILDREN`|`DESCENDANTS` | Org unit selection mode | +| `status` | `String` | `ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event | +| `occurredAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date. | +| `occurredBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred up until this date. | +| `scheduledAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which were scheduled after this date. | +| `scheduledBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which were scheduled before this date. | +| `updatedAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which were updated after this date. Cannot be used together with `updatedWithin`. | +| `updatedBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which were updated up until this date. Cannot be used together with `updatedWithin`. | +| `updatedWithin` | `Duration` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601#Durations) | Include only items which are updated within the given duration.

The format is [ISO-8601#Duration](https://en.wikipedia.org/wiki/ISO_8601#Durations) | +| `enrollmentEnrolledAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Start date for enrollment in the given program | +| `enrollmentEnrolledBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | End date for enrollment in the given program | +| `enrollmentOccurredAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Start date for incident in the given program | +| `enrollmentOccurredBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | End date for incident in the given program | +| `skipMeta` | `Boolean` | `true`|`false` | Exclude the meta data part of response (improves performance) | +| `dataElementIdScheme` | `String` | `UID`|`CODE`|`ATTRIBUTE:{ID}` | Data element ID scheme to use for export. | +| `categoryOptionComboIdScheme` | `String` | `UID`|`CODE`|`ATTRIBUTE:{ID}` | Category Option Combo ID scheme to use for export | +| `orgUnitIdScheme` | `String` | `UID`|`CODE`|`ATTRIBUTE:{ID}` | Organisation Unit ID scheme to use for export | +| `programIdScheme` | `String` | `UID`|`CODE`|`ATTRIBUTE:{ID}` | Program ID scheme to use for export | +| `programStageIdScheme` | `String` | `UID`|`CODE`|`ATTRIBUTE:{ID}` | Program Stage ID scheme to use for export | +| `idScheme` | `string` | `UID`|`CODE`|`ATTRIBUTE:{ID}` | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | +| `order` | `String` | comma-delimited list of property name, attribute or data element UID and sort direction pairs in format `propName:sortDirection`. | Sort the response based on given order values.

Example: `createdAt:desc` or `SzVk2KvkSSd:asc`

**Note:** `propName` is case sensitive, `sortDirection` is case insensitive. Supported are `storedBy, attributeCategoryOptions, dueDate, assignedUserUsername, createdAtClient, program, lastUpdated, event, assignedUser, programStage, programType, occurredAt, created, createdAt, orgUnit, completedDate, enrollment, trackedEntityInstance, followup, deleted, enrollmentStatus, attributeOptionCombo, assignedUserDisplayName, completedBy, orgUnitName, eventDate, lastUpdatedAtClient, status, enrolledAt`. | +| `event` | `String` | comma-delimited list of `uid` | Filter the result down to a limited set of IDs by using event=id1;id2. | +| `skipEventId` | `Boolean` | | Skips event identifiers in the response | +| `attributeCc` (see note) | `String` | Attribute category combo identifier (must be combined with attributeCos) | +| `attributeCos` (see note) | `String` | Attribute category option identifiers, separated with ; (must be combined with attributeCc) | +| `includeDeleted` | `Boolean` | | When true, soft deleted events will be included in your query result. | +| `assignedUserMode` | `String` | `CURRENT`|`PROVIDED`|`NONE`|`ANY` | Assigned user selection mode | +| `assignedUser` | `String` | comma-delimited list od `uid` | Filter the result down to a limited set of events that are assigned to the given user IDs by using `assignedUser=id1;id2`.

This parameter will be considered only if assignedUserMode is either `PROVIDED` or `null`.

The API will error out, if for example, `assignedUserMode=CURRENT` and `assignedUser=someId` | + +> **Note** +> +> If the query contains neither `attributeCC` nor `attributeCos`, the server returns events for all attribute option combos where the user has read access. + +##### Example requests { #example-requests } + +The query for all events with children of a particular organisation unit: + + GET /api/tracker/events?orgUnit=YuQRtpLP10I&ouMode=CHILDREN + +The query for all events with all descendants of a particular organisation unit, implying all organisation units in the sub-hierarchy: + + GET /api/tracker/events?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS + +Query for all events with a certain program and organisation unit: + + GET /api/tracker/events?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc + +Query for all events with a certain program and organisation unit, sorting by due date ascending: + + GET /api/tracker/events?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate + +Query for the 10 events with the newest event date in a certain program and organisation unit - by paging and ordering by due date descending: + + GET /api/tracker/events?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc + &order=eventDate:desc&pageSize=10&page=1 + +Query for all events with a certain program and organisation unit for a specific tracked entity instance: + + GET /api/tracker/events?orgUnit=DiszpKrYNg8 + &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m + +Query for all events with a certain program and organisation unit older or equal to 2014-02-03: + + GET /api/tracker/events?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 + +Query for all events with a certain program stage, organisation unit and tracked entity instance in the year 2014: + + GET /api/tracker/events?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc + &trackedEntityInstance=gfVxE3ALA9m&occurredAfter=2014-01-01&occurredBefore=2014-12-31 + +Retrieve events with specified Organisation unit and Program, and use `Attribute:Gq0oWTf2DtN` as identifier scheme + + GET /api/tracker/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN + +Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for organisation units, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as the identifier scheme for the rest of the metadata with assigned attributes. + + GET /api/tracker/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN + &orgUnitIdScheme=UID&programStageIdScheme=Code + +##### Response format { #response-format } + +The `JSON` response can look like the following. + +```json +{ + "instances": [ + { + "event": "rgWr86qs0sI", + "status": "ACTIVE", + "program": "kla3mAPgvCH", + "programStage": "aNLq9ZYoy9W", + "orgUnit": "DiszpKrYNg8", + "orgUnitName": "Ngelehun CHC", + "relationships": [], + "occurredAt": "2021-10-12T00:00:00.000", + "followup": false, + "deleted": false, + "createdAt": "2018-10-20T12:09:19.492", + "updatedAt": "2018-10-20T12:09:19.492", + "attributeOptionCombo": "amw2rQP6r6M", + "attributeCategoryOptions": "RkbOhHwiOgW", + "dataValues": [ + { + "createdAt": "2015-10-20T12:09:19.640", + "updatedAt": "2015-10-20T12:09:19.640", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "HyJL2Lt37jN", + "value": "12" + }, + ... + ], + "notes": [] + } + ], + "page": 1, + "pageSize": 1 +} +``` + +The `CSV` response can look like the following. + +``` +|event|status|program|programStage|enrollment|orgUnit|occurredAt|scheduledAt|dataElement|value|storedBy|providedElsewhere +|---|---|---|---|---|---|---|---|---|---|---|---| +|V1CerIi3sdL|COMPLETED|IpHINAT79UW|A03MvHHogjR|CCBLMntFuzb|DiszpKrYNg8|2020-02-26T23:00:00Z|2020-02-27T23:00:00Z|a3kGcGDCuk6|11|admin|false +|V1CerIi3sdL|COMPLETED|IpHINAT79UW|A03MvHHogjR|CCBLMntFuzb|DiszpKrYNg8|2020-02-26T23:00:00Z|2020-02-27T23:00:00Z|mB2QHw1tU96|[-11.566044,9.477801]|admin|false +``` + +#### Events single object endpoint `GET /api/tracker/events/{uid}` + +The purpose of this endpoint is to retrieve one Event given its uid. + +##### Request syntax { #request-syntax } + +`GET /api/tracker/events/{uid}?fields={fields}` + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `uid` | `String` | `uid` | Return the Event with specified `uid` | +| `fields` | `String` | Any valid field filter (default `*,!relationships`) | Include specified sub-objects in the response | + +##### Example requests { #example-requests } + +A query for an Event: + + GET /api/tracker/events/rgWr86qs0sI + +##### Response format { #response-format } + +```json +{ + "event": "rgWr86qs0sI", + "status": "ACTIVE", + "program": "kla3mAPgvCH", + "programStage": "aNLq9ZYoy9W", + "enrollment": "Lo3SHzCnMSm", + "enrollmentStatus": "ACTIVE", + "orgUnit": "DiszpKrYNg8", + "orgUnitName": "Ngelehun CHC", + "relationships": [], + "occurredAt": "2021-10-12T00:00:00.000", + "followup": false, + "deleted": false, + "createdAt": "2018-10-20T12:09:19.492", + "createdAtClient": "2017-10-20T12:09:19.492", + "updatedAt": "2018-10-20T12:09:19.492", + "attributeOptionCombo": "amw2rQP6r6M", + "attributeCategoryOptions": "RkbOhHwiOgW", + "dataValues": [ + { + "createdAt": "2015-10-20T12:09:19.640", + "updatedAt": "2015-10-20T12:09:19.640", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "HyJL2Lt37jN", + "value": "12" + }, + { + "createdAt": "2015-10-20T12:09:19.514", + "updatedAt": "2015-10-20T12:09:19.514", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "b6dOUjAarHD", + "value": "213" + }, + { + "createdAt": "2015-10-20T12:09:19.626", + "updatedAt": "2015-10-20T12:09:19.626", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "UwCXONyUtGs", + "value": "3" + }, + { + "createdAt": "2015-10-20T12:09:19.542", + "updatedAt": "2015-10-20T12:09:19.542", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "fqnXmRYo5Cz", + "value": "123" + }, + { + "createdAt": "2015-10-20T12:09:19.614", + "updatedAt": "2015-10-20T12:09:19.614", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "Qz3kfeKgLgL", + "value": "23" + }, + { + "createdAt": "2015-10-20T12:09:19.528", + "updatedAt": "2015-10-20T12:09:19.528", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "W7aC8jLASW8", + "value": "12" + }, + { + "createdAt": "2015-10-20T12:09:19.599", + "updatedAt": "2015-10-20T12:09:19.599", + "storedBy": "system", + "providedElsewhere": false, + "dataElement": "HrJmqlBqTFG", + "value": "3" + } + ], + "notes": [] +} +``` + +### Enrollments (`GET /api/tracker/enrollments`) { #enrollments-get-apitrackerenrollments } + +Two endpoints are dedicated to enrollments: + +- `GET /api/tracker/enrollments` + - retrieves enrollments matching given criteria +- `GET /api/tracker/enrollments/{id}` + - retrieves an enrollment given the provided id + +#### Enrollment Collection endpoint `GET /api/tracker/enrollments` { #enrollment-collection-endpoint-get-apitrackerenrollments } + +Returns a list of events based on filters. + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `orgUnit` | `String` | `uid` | Identifier of organisation unit | +| `ouMode` see [ouModes](#Request-parameters-for-Organisational-Unit-selection-mode) | `String` | `SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL | Org unit selection mode | +| `program` | `String` | `uid` | Identifier of program | +| `programStatus` | `enum` | `ACTIVE`|`COMPLETED`|`CANCELLED` | Program Status | +| `followUp` | `boolean` | `true`|`false` | Follow up status of the instance for the given program. Can be `true`|`false` or omitted. | +| `updatedAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Only enrollments updated after this date | +| `updatedWithin` | `Duration` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Only enrollments updated since given duration | +| `enrolledAfter` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Only enrollments newer than this date | +| `enrolledBefore` | `DateTime` | [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Only enrollments older than this date | +| `trackedEntityType` | `String` | `uid` | Identifier of tracked entity type | +| `trackedEntity` | `String` | `uid` | Identifier of tracked entity instance | +| `enrollment` | `String` | Comma-delimited list of `uid` | Filter the result down to a limited set of IDs by using enrollment=id1;id2. | +| `includeDeleted` | `Boolean` | | When true, soft deleted events will be included in your query result. | + +The query is case-insensitive. The following rules apply to the query parameters. + +- At least one organisation unit must be specified using the `orgUnit` parameter (one or many), or _ouMode=ALL_ must be specified. + +- Only one of the _program_ and _trackedEntity_ parameters can be specified (zero or one). + +- If _programStatus_ is specified, then _program_ must also be specified. + +- If _followUp_ is specified, then _program_ must also be specified. + +- If _enrolledAfter_ or _enrolledBefore_ is specified, then _program_ must also be specified. + +##### Example requests { #example-requests } + +A query for all enrollments associated with a specific organisation unit can look like this: + + GET /api/tracker/enrollments?orgUnit=DiszpKrYNg8 + +To constrain the response to enrollments which are part of a specific program you can include a program query parameter: + + GET /api/tracker/enrollments?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n + +To specify program enrollment dates as part of the query: + + GET /api/tracker/enrollments?&orgUnit=O6uvpzGd5pu&program=ur1Edk5Oe2n + &enrolledAfter=2013-01-01&enrolledBefore=2013-09-01 + +To constrain the response to enrollments of a specific tracked entity you can include a tracked entity query parameter: + + GET /api/tracker/enrollments?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ + +To constrain the response to enrollments of a specific tracked entity you can include a tracked entity instance query parameter, in In this case, we have restricted it to available enrollments viewable for current user: + + GET /API/tracker/enrollments?ouMode=ACCESSIBLE&trackedEntity=tphfdyIiVL6 + +##### Response format { #response-format } + +The `JSON` response can look like the following. + +```json +{ + "instances": [ + { + "enrollment": "iKaBMOyq7QQ", + "createdAt": "2017-03-28T12:28:19.812", + "createdAtClient": "2016-03-28T12:28:19.812", + "updatedAt": "2017-03-28T12:28:19.817", + "trackedEntity": "PpqV8ytvW5i", + "trackedEntityType": "nEenWmSyUEp", + "program": "ur1Edk5Oe2n", + "status": "ACTIVE", + "orgUnit": "NnQpISrLYWZ", + "orgUnitName": "Govt. Hosp. Bonthe", + "enrolledAt": "2020-10-23T12:28:19.805", + "occurredAt": "2020-10-07T12:28:19.805", + "followUp": false, + "deleted": false, + "events": [], + "relationships": [], + "attributes": [], + "notes": [] + } + ], + "page": 1, + "total": 1, + "pageSize": 5 +} +``` + +#### Enrollments single object endpoint `GET /api/tracker/enrollments/{uid}` + +The purpose of this endpoint is to retrieve one Enrollment given its uid. + +##### Request syntax { #request-syntax } + +`GET /api/tracker/enrollment/{uid}` + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `uid` | `String` | `uid` | Return the Enrollment with specified `uid` | +| `fields` | `String` | Any valid field filter (default `*,!relationships,!events,!attributes`) | Include specified sub-objects in the response | + +##### Example requests { #example-requests } + +A query for a Enrollment: + + GET /api/tracker/enrollments/iKaBMOyq7QQ + +##### Response format { #response-format } + +```json +{ + "enrollment": "iKaBMOyq7QQ", + "createdAt": "2017-03-28T12:28:19.812", + "createdAtClient": "2016-03-28T12:28:19.812", + "updatedAt": "2017-03-28T12:28:19.817", + "trackedEntity": "PpqV8ytvW5i", + "trackedEntityType": "nEenWmSyUEp", + "program": "ur1Edk5Oe2n", + "status": "ACTIVE", + "orgUnit": "NnQpISrLYWZ", + "orgUnitName": "Govt. Hosp. Bonthe", + "enrolledAt": "2020-10-23T12:28:19.805", + "occurredAt": "2020-10-07T12:28:19.805", + "followUp": false, + "deleted": false, + "events": [], + "relationships": [], + "attributes": [], + "notes": [] +} +``` + +### Relationships (`GET /api/tracker/relationships`) { #relationships-get-apitrackerrelationships } + +Relationships are links between two entities in the Tracker. These entities can be tracked entity instances, enrollments, and events. + +The purpose of this endpoint is to retrieve relationships between objects. + +Unlike other tracked objects endpoints, relationships only expose one endpoint: + +- `GET /api/tracker/relationships?[trackedEntity={trackedEntityUid}|enrollment={enrollmentUid}|event={eventUid}]&fields=[fields]` + +#### Request parameters { #request-parameters } + +| Request parameter | Tipo | Allowed values | Descripción | +| --- | --- | --- | --- | +| `trackedEntity` | `String` | `uid` | Identifier of a Tracked Entity Instance | +| `enrollment` | `String` | `uid` | Identifier of an Enrollment | +| `event` | `String` | `uid` | Identifier of an Event | +| `fields` | `String` | Any valid field filter (default `relationship,relationshipType,from[trackedEntity[trackedEntity],enrollment[enrollment],event[event]],to[trackedEntity[trackedEntity],enrollment[enrollment],event[event]]`) | Include specified sub-objects in the response | + +The following rules apply to the query parameters. + +- only one parameter among `trackedEntity`, `enrollment`, `event` can be passed + +> **NOTE** +> +> Using tracked entity, Enrollment or Event params, will return any relationship where the trackedEntity, enrollment or event is part of the relationship (either from or to). As long as user has access, that is. + +#### Example response { #example-response } + +```json +{ + "instances": [ + { + "relationship": "SSfIicJKbh5", + "relationshipType": "Mv8R4MPcNcX", + "from": { + "trackedEntity": { + "trackedEntity": "neR4cmMY22o" + } + }, + "to": { + "trackedEntity": { + "trackedEntity": "rEYUGH97Ssd" + } + } + }, + { + "relationship": "S9kZGYPKk3x", + "relationshipType": "Mv8R4MPcNcX", + "from": { + "trackedEntity": { + "trackedEntity": "neR4cmMY22o" + } + }, + "to": { + "trackedEntity": { + "trackedEntity": "k8TU70vWtnP" + } + } + } + ], + "page": 1, + "pageSize": 2 +} +``` + +## Tracker Access Control { #webapi_nti_access_control } + +Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. + +### Metadata Sharing { #webapi_nti_metadata_sharing } + +Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability to define who can see/do what. In general, there are five possible sharing configurations – no access, metadata read, metadata write, data read, and data write. These access configurations can be granted at user and/or user group level (for more flexibility). With a focus on Tracker, the following metadata and their sharing setting is of particular importance: Data Element, Category Option, Program, Program Stage, Tracked Entity Type, Tracked Entity Attribute as well as Tracker related Dashboards and Dashboard Items. + +How sharing setting works is straightforward – the settings are enforced during Tracker data import/export processes. To read value, one needs to have data read access. If a user is expected to modify data, he/she needs to have data write access. Similarly, if a user is expected to modify metadata, it is essential to grant metadata write access. + +One critical point with Tracker data is the need to have a holistic approach. For example, a user won’t be able to see the Data Element value by having read access to just the Data Element. The user needs to have data read to access the parent Program Stage and Program where this Data Element belongs. It is the same with the category option combination. In Tracker, the Event is related to AttributeOptionCombo, which is made up of a combination of Category Options. Therefore, for a user to read data of an Event, he/she needs to have data read access to all Category Options and corresponding Categories that constitute the AttributeOptionCombo of the Event in question. If a user lacks access to just one Category Option or Category, then the user has no access to the entire Event. + +When it comes to accessing Enrollment data, it is essential to have access to the Tracked Entity first. Access to a Tracked Entity is controlled through sharing setting of Program, Tracked Entity Type, and Tracked Entity Attribute. Once Enrollment is accessed, it is possible to access Event data, again depending on Program Stage and Data element sharing setting. + +Another vital point to consider is how to map out access to different Program Stages of a Program. Sometimes we could be in a situation where we need to grant access to a specific stage – for example, “Lab Result” – to a specific group of users (Lab Technicians). In this situation, we can provide data write access to "Lab Result" stage, probably data read to one or more stages just in case we want Lab Technicians to read other medical results or no access if we think it not necessary for the Lab Technicians to see data other than lab related. + +In summary, DHIS2 has a fine-grained sharing setting that we can use to implement access control mechanisms both at the data and metadata level. These sharing settings can be applied directly at the user level or user group level. How exactly to apply a sharing setting depends on the use-case at hand. + +For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). + +### Organisation Unit Scopes { #webapi_nti_ou_scope } + +Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that can be assigned to a user. These are data capture, data view, and tracker search. As the name implies, these organisation units define a scope under which a user is allowed to conduct the respective operations. + +However, to further fine-tune the scope, DHIS2 Tracker introduces a concept that we call **OrganisationUnitSelectionMode**. Such a mode is often used at the time exporting tracker objects. For example, given that a user has a particular tracker search scope, does it mean that we have to use this scope every time a user tries to search for a tracker, Enrollment, or Event object? Or is the user interested in limiting the searching just to the selected org unit, or the entire capture org unit scope, and so on. + +Users can do the fine-tuning by passing a specific value of ouMode in their API request: + +_api/tracker/trackedEntities?orgUnit=UID&ouMode=specific_organisation_unit_selection_mode_ + +Currently, there are six selection modes available: _SELECTED, CHILDREN, DESCENDANTS, CAPTURE, ACCESSIBLE, and ALL_. + +1. **SELECTED**: as the name implies, all operations intended by the requesting API narrow down to the selected organisation unit. +2. **CHILDREN**: under this mode, the organisation unit scope will be constructed using the selected organisation unit and its immediate children. +3. **DESCENDANTS**: here, the selected organisation unit and everything underneath it, not just the immediate children, constitute the data operation universe. +4. **CAPTURE**: as the name implies, organisation units assigned as the user's data capture constitute the universe. Note that, of the three organisation units that can be assigned to a user data capture is the mandatory one. If a user does not have data view and tracker search organisation units, the system will fall back to data capture. This way, we are always sure that a user has at least one universe. +5. **ACCESSIBLE**: technically, this is the same scope as the user's tracker search organisation units. +6. **ALL**: the name ALL makes perfect sense if we are dealing with a superuser. For super users, this scope means the entire organisation unit available in the system. However, for non-superusers, ALL boils down to ACCESSIBLE organisation units. + +It makes little sense to pass these modes at the time of tracker import operations. Because when writing tracker data, each of the objects needs to have a specific organisation unit attached to them. The system will then ensure if each of the mentioned organisation units falls under the CAPTURE scope. If not, the system will simply reject the write operation. + +Note that there is 4 type of organisation unit associations relevant for Tracker objects. A TrackedEntity has an organisation unit, commonly referred to as the Registration Organisation unit. Enrollments have an organisation unit associated with them. Events also have an organisation unit associated with them. There is also an Owner organisation unit for a TrackedEntity-Program combination. + +When fetching Tracker objects, depending on the context, the organisation unit scope is applied to one of the above four organisation unit associations. + +For example, when retrieving TrackedEntities without the context of a program, the organisation unit scope is applied to the registration organisation unit of the TrackedEntity. Whereas, when retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. + +- **Explain how they relate to ownership - Link to Program Ownership** + +### Tracker Program Ownership { #webapi_nti_ownership } + +A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured with access level _OPEN_ or _AUDITED_ , the Owner OrganisationUnit has to be in the user's search scope. For Programs that are configured with access level _PROTECTED_ or _CLOSED_ , the Owner OrganisationUnit has to be in the user's capture scope to be able to access the corresponding program data for the specific tracked entity. + +#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } + +It is possible to temporarily override this ownership privilege for a program that is configured with an access level of _PROTECTED_. Any user will be able to temporarily gain access to the Program related data if the user specifies a reason for accessing the TrackedEntity-Program data. This act of temporarily gaining access is termed as _breaking the glass_. Currently, temporary access is granted for 3 hours. DHIS2 audits breaking the glass along with the reason specified by the user. It is not possible to gain temporary access to a program that has been configured with an access level of _CLOSED_. To break the glass for a TrackedEntity-Program combination, the following POST request can be used: + + /API/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 + &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care + +#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } + +It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has Ownership access (or temporary access by breaking the glass) can transfer the ownership. To transfer ownership of a TrackedEntity-Program to another organisation unit, the following PUT request can be used: + + /API/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 + &program=eBAyeGv0exc&ou=EJNxP3WreNP + +### Access Level { #webapi_nti_access_level } + +DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional access level protection mechanisms. Currently, there are four access levels that can be configured for a Program: Open, Audited, Protected, and Closed. + +These access levels are only triggered when users try to interact with program data, namely Enrollments and Events data. The different Access Level configuration for Program is a degree of openness (or closedness) of program data. Note that all other sharing settings are still respected, and the access level is only an additional layer of access control. Here is a short description of the four access levels that can be configured for a Program. + +1. Open: This access level is the least restricted among the access levels. Data inside an OPEN program can be accessed and modified by users if the Owner organisation unit falls under the user's search scope. With this access level, accessing and modifying data outside the capture scope is possible without any justification or consequence. +2. Audited: This is the same as the Open access level. The difference here is that the system will automatically add an audit log entry on the data being accessed by the specific user. +3. Protected: This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass gains temporary access. +4. Closed: This is the most restricted access level. Data recorded under programs configured with access level CLOSED will not be accessible if the Owner Organisation Unit does not fall within the user's capture scope. It is also not possible to break the glass or gain temporary ownership in this configuration. Note that it is still possible to transfer the ownership to another organisation unit. Only a user who has access to the data can transfer the ownership of a TrackedEntity-Program combination to another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md index 8ee1fce9f..19e27f307 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Perfil de la unidad organizativa { #org_unit_profile } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index e4c1c3fd4..b932d3892 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index 5c2453845..634a4dc83 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/route.md" revision_date: '2024-05-15' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Route { #route } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index 3620a9a0a..28d95434f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Scheduling { #webapi_scheduling } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index 72c58b5b7..55ca6217e 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index 8171225ae..c0f751b36 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md @@ -2,11 +2,11 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- -# Sharing { #sharing } +# Compartir { #sharing } ## Sharing { #webapi_sharing } @@ -202,7 +202,7 @@ Puede eliminar un usuario de `sharing` así ## Cascade Sharing for Dashboard { #cascade-sharing-for-dashboard } -### Overview { #overview } +### Visión general { #overview } - `cascadeSharing` is available for Dashboards. This function copies the `userAccesses` and `userGroupAccesses` of a Dashboard to all of the objects in its `DashboardItems`, including `Map`, `EventReport`, `EventChart`, `Visualization`. - This function will not copy `METADATA_WRITE` access. The copied `UserAccess` and `UserGroupAccess` will **only** receive the `METADATA_READ` permission. @@ -302,7 +302,7 @@ curl -X PATCH -d @payload.json -H "Content-Type: application/json-patch+json" "h | atomic | falso | If this is set to true, then the batch function will stop and not updating any objects if there is an error
Otherwise, if this is false then the function will try to proceed with best effort mode. | -## Validation { #validation } +## Validación { #validation } - All object ID will be validated for existence. - Current User need to have metadata READ/WRITE permission on updating objects. - All existing validations from metadata import service will also be applied. diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index ce988a04b..527445670 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # SMS { #sms } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index b2fe303b9..10e60e9a2 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Sincronización { #webapi_synchronization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md index e9a2b8ebb..b14ee88c6 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md @@ -775,7 +775,7 @@ You can use a range of operators for the filtering: Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | @@ -1117,7 +1117,7 @@ You can use a range of operators for the filtering: Table: Filter operators -| Operator | Descripción | +| Operador | Descripción | |---|---| | EQ | Equal to | | GT | Greater than | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md index be6c152fb..f7a2f4f6f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-07-02' +revision_date: '2024-07-08' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Tracker { #webapi_tracker } @@ -1418,7 +1418,7 @@ The import will validate unique attributes at the time of import. That means as value is unique for the attribute in the whole system, it will pass. However, if the unique value is found to be used by any other tracked entity other than the one being imported, it will fail. -#### Configuration { #configuration } +#### Configuración { #configuration } The last part of validations in the importer are validations based on the user's configuration of relevant metadata. For more information about each configuration, check out the relevant sections. @@ -1874,7 +1874,7 @@ To query on an attribute using multiple values in an *IN* filter: You can use a range of operators for the filtering: -|Operator| Descripción| +|Operador| Descripción| |---|---| |`EQ`|Equal to| |`GE`|Greater than or equal to| @@ -2851,7 +2851,8 @@ Organisation units are one of the most fundamental objects in DHIS2. They define which a user is allowed to record and/or read data. There are three types of organisation units that can be assigned to a user. These are data capture, data view (not used in tracker), and tracker search. As the name implies, these organisation units define a scope under which a user is allowed -to conduct the respective operations. +to conduct the respective operations. A user can search for data in their search scope and capture +scope organisation units. However, to further fine-tune the scope, DHIS2 Tracker introduces a concept that we call **OrganisationUnitSelectionMode**. Such a mode is often used at the time exporting tracker objects. @@ -2927,14 +2928,19 @@ falls under the user's organisation unit scope (Search/Capture). For Programs th with access level *OPEN* or *AUDITED* , the Owner OrganisationUnit has to be in the user's search scope. For Programs that are configured with access level *PROTECTED* or *CLOSED* , the Owner OrganisationUnit has to be in the user's capture scope to be able to access the corresponding -program data for the specific tracked entity. Irrespective of the program access level, to access -Tracker objects, the requested organisation unit must always be within the user's search scope. A -user cannot request objects outside its search scope unless it's using the organisation unit mode -ALL and has enough privileges to use that mode. - -When requesting tracked entities without specifying a program, the response will include only tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and one of the following criteria: -- The tracked entity is enrolled in at least one program the user has data access to, and the user has access to the owner organisation unit. -- The tracked entity is not enrolled in any program the user has data access to, but the user has access to the tracked entity registering organisation unit. +program data for the specific tracked entity. Irrespective of the program access level, to access +Tracker objects, the requested organisation unit must always be within either the user's search +scope or capture scope. A user cannot request objects outside these two scopes unless they are +using the organisation unit mode ALL and have sufficient privileges to use that mode. + +When requesting tracked entities without specifying a program, the response will include only +tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and +one of the following criteria: + +* The tracked entity is enrolled in at least one program the user has data access to, and the user + has access to the owner organisation unit. +* The tracked entity is not enrolled in any program the user has data access to, but the user has + access to the tracked entity registering organisation unit. #### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index 892dc2444..af584cce8 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Users { #users } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index d685b2e94..8097b68c0 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- DHIS core version master - Desarrollar +- DHIS core version master --- # Visualizations { #visualizations } @@ -294,8 +294,8 @@ Table: Layout attributes | Atributo | Descripción | Tipo | |---|---|---| -| layout | This is the root object | Object | -| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Object | +| layout | This is the root object | Objeto | +| spacing | Defines the spacing for specific layout components. Currently, it supports columns and rows. | Objeto | | columns | Stores specific parameters related to columns (at the moment, index and span) | Array of objects | ## Visualization { #webapi_visualization } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__CHIS-IMPLEMENTATION__sustainability-and-governance-md b/projects/docs-full-site/es_419/IMPLEMENT__CHIS-IMPLEMENTATION__sustainability-and-governance-md new file mode 100644 index 000000000..d345aa95e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__CHIS-IMPLEMENTATION__sustainability-and-governance-md @@ -0,0 +1,574 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/chis_implementation/08_governance_sustainability.md" +revision_date: '2022-04-20' +tags: +- Implementar +--- + +# Sustainability and Governance { #sustainability-and-governance } + +## Introducción { #introduction } + +Ensuring sustainability, broadly concerning how the CHIS endures over time and space is one of the most difficult challenge that policy makers and implementers have to deal with. + +The key to long term sustainability rests with governance of data management, which is a cross-cutting issue that involves formal management structures, policies and procedures, staffing, and workforce development, monitoring and evaluation of the CHIS program. By the end of this chapter, readers should be able to: + +## What Do We Mean by Sustainability? { #what-do-we-mean-by-sustainability } + +Sustainability of HIS in general, and CHIS in particular, is one of the most significant challenges facing designers, implementers, and policy makers of CHIS. Sustainability is a "wicked" problem, implying that if you try to address one of its facets, other problems will arise elsewhere. For example, to address the problem of CHIS continuity, a donor may be approached for funding. However, this may lead to other dependencies that can further put pressure on sustainability. + +Some relevant characteristics of a sustainable CHIS include: + +1. The CHIS must be well integrated into existing organizational routines of work practices, budgeting, training, reporting, and infrastructure provision. +2. On one hand the CHIS has to be well institutionalized, on the other hand, it must remain flexible, so that it can continue to evolve with the changing informational needs of the health system. This often leads to a dilemma of ensuring both stability and change, which designers and implementers have to constantly engage with. +3. The CHIS must be integrated with other systems like the routine facility HIS to ensure it does not remain standalone and lead to double work for the CHWs. A standalone CHIS is a sure recipe for unsustainability. +4. The outputs of the CHIS must provide real value to the key stakeholders, particularly the CHWs and their supervisors, but also mid-level and senior system managers. + +## Ensuring CHIS Sustainability { #ensuring-chis-sustainability } + +To address sustainability the primary focus of CHIS design should be on strengthening the "demand side" conditions such as how the CHIS adds value to the CHW, how it is integrated with their everyday work practices, and their needs for ongoing technical and public health support, rather than the dominant "supply side" approach of merely providing computers, internet and training. + +To make a CHIS sustainable, planners need to address key technical, organizational and behavioral factors. These are explained in detail in the Performance of Routine Information Systems (PRISM) framework^[MEASURE Evaluation, “PRISM: Performance of Routine Information System Management Framework,” [https://www.measureevaluation.org/resources/prism.html](https://www.measureevaluation.org/resources/prism.html)] and shown schematically in Figure 6.1 below. + +![](resources/images/chis_figure39.png) + +*Figure 6.1:* The PRISM framework + +In this approach, CHIS inputs such as assessments, interventions and strategies need to be addressed by technical, organizational, and behavioral determinants in order to achieve the desired outputs of a sustainable system that produces good quality information used to improve overall health system performance. A few aspects focused specifically on CHIS sustainability are detailed below. + +1. **Technical Design** + + a. **Integrated CHIS**: There are a number of examples of CHIS developed as an integrated part of the overall HMIS, linked directly to other systems in the community, particularly the routine facility information systems. Using an architectural approach, the CHIS becomes part of the system, reducing CHW workload and adding value. + b. **Increasing ICT infrastructure**: MHealth projects are increasingly based on internet connectivity, which is increasing exponentially allowing the use of android devices and mobile phones. However, This infrastructure must be carefully assessed, ensuring that the CHIS projects use available connectivity to its maximum while becoming fully operational. + c. **Free open Source software (FOSS) systems**: Successful CHIS projects are developed based on free open source software such as DHIS2, ensuring interoperability with other systems. FOSS flexibility and iterative design processes allow ongoing changes required for the application. As a result, the CHIS can evolve with changing needs, constantly adapted to the needs of the end users. +2. **Human Behavior** + Human behavior is the most difficult aspect of implementing a sustainable CHIS, and this aspect needs consistent attention. This phenomenon is increasingly being addressed by dealing with common issues with CHIS such as: + + a. **Changing Facility Staff attitude to CHWs.** Many health workers do not understand the role of CHWs and look down on their work as being second class. Major effort needs to be put into encouraging facility level workers to support the community health services, the CHIS and providing CHWs with necessary feedback, support and supervision. Facility staff also need to be involved in addressing sustainable remuneration of CHWs, building this into the budgets, to increase motivation, reduce dropout, and minimize attrition. + b. **Providing targeted feedback.** CHIS stakeholders need to see the practical value of data and increase data use through regular, targeted feedback that demonstrates data driven actions based on data. This further increases local demand for and use of data, stimulates ownership and promotes a culture of information use, creating the virtuous data cycle. (see figure 3.1) + c. **CHIS provides added value to end users.** For the CHIS to add value to the CHWs, the system design must be integrated with their work practices, reduce their work burden and add value for them to perform their work. A CHIS that is designed for local use and program monitoring rather the surveillance needs of administrators, means that CHWs and stakeholders are motivated to use the system. + d. **Ongoing CHIS support and capacity strengthening**. CHIS should focus on ongoing training, and provide support to CHWs in the many challenges they face when they use the system, providing feedback and support rather than criticism. CHIS supervision needs to encourage CHWs to use the system and make it sustainable. +3. **Organization** + + a. **Strong Data governance:** Governance is key to sustainability of any CHIS. All community level stakeholders must agree to common data standards and high-level coordination based on accountability, transparency and local participation. Key to these standards, are common data collection formats that reduce the data burden of the CHW and minimise the fragmentation of the CHIS. These in the long run contribute to systems becoming sustainable and enduring. + b. **Plan for scaling up:** Many CHIS projects are initiated as pilots with a limited timeframe and funding, known as "pilotitis". This needs to be avoided and scaling up planned for from the beginning with adequate resources and support. CHIS is about bringing about long term institutional and human behavior change, and systems take a long time to mature, usually beyond the short term "project" timeframe. + +In summary, various reasons, technical, institutional, and human related, contribute to the CHIS becoming sustainable. Many of the reasons are inter-connected, requiring a holistic design and a health systems based approach to address sustainability. + +Unsustainable systems do not scale, do not add value to the administrators who want data on the entire catchment population and not just from pilot areas. This challenge has been called the "all or nothing" consideration in HIS. Because the CHIS are not able to surmount these challenges, they don't add value, and thus do not attract the required support from the administrators. This vicious cycle of unsustainable systems that do not scale and thus add limited or no value to users, leads to poor support and further adds to the unsustainability of the CHIS. + +## CHIS Governance { #chis-governance } + +Information systems are not what they used to be and are becoming more important as interdependence among systems increases and demands for social accountability increase. Health information systems are becoming more important as information and communication technology spreads and have a greater impact on health workers lives, with pressures growing for more and better quality data. This trend is occurring at the same time as other significant changes are taking place with demands for greater transparency, participation and accountability and a reduction in the "digital divide" between countries. The challenge to CHIS designers and implementers is to build relationships of trust between stakeholders and to deliver effective social accountability. + +The growing expectation that it is right to be involved in decisions that affect one's future and the increasing knowledge about what is going on in the health system are a powerful combination to pressure health managers to improve trust between different levels of the system. Civil society, health workers and other stakeholders are increasingly demanding participation in decisions that are made about them, insisting on transparency about allocation of resources and using the internet and social media to voice these demands. At the same time international organisations are insisting on accountability, demanding value for money for aid projects. + +These three concepts - participation, accountability and transparency - are the core principles of good governance and need to be applied to any development of a CHIS. + +***Participation*** in CHIS governance emphasizes the broad participation of stakeholders in the direction and operation of information systems to develop a degree of consensus around decision making rules and capacity development processes. Participation implies increased citizen participation and greater community representation than traditional systems, creating opportunities for stakeholders to make meaningful contributions to decision-making, and seeks to broaden the range of people who have access to such opportunities. Technology may provide important forces leading to empowerment in participatory models, though face to face meetings remain important + +***Transparency*** refers to the availability of information to the general public and clarity about government rules, regulations, and decisions. Transparent procedures include open meetings, financial disclosure statements, freedom of information legislation, budgetary review, and audits. Transparent CHIS governance, therefore, means not hiding things from community stakeholders, not engaging in shady deals and not making discretionary decisions. There should be clear guidelines to adhere upon, based on openness. + +**Accountability** in governance refers to the collective responsibility of officials to preserve the public's trust in government by delivering on policy outcomes and safeguarding public funds. Accountable governance of a CHIS involves systems and coordinated actions through which the MoH (with donors) ensures the effectiveness, efficiency and economy of expenditure. It relies on tools that promote value-for-money, integrity and transparency in government, such as external control, internal control, sanctions, and enforcement. These tools create an enabling environment for greater accountability and improved governance. + +### Governance implications for donors and government { #governance-implications-for-donors-and-government } + +While governance is ultimately the role of government, accountable governance is not the responsibility of one institution, but many entities and individuals across all levels, particularly local government for the CHIS. + +The donor community (development partners) has a distinct role in supporting government to develop and implement CHIS governance guidelines around transparency, accountability and accountability. The donors wield considerable influence over the availability of resources and need to support the design principles, harmonize CHIS and end pilotitis. + +### Governance of Data Management { #governance-of-data-management } + +Effective data governance is the key to sustainability and is essential to all forms of routine HIS, including CHIS. + +Data management governance is at the core of all information systems and is crucial for the sustainable functioning of a CHIS. This section is adapted from "Guidelines for Data Management Standards in Routine Health Information Systems"^[Heywood & Boone Guidelines for Data Management Standards in Routine Health Information Systems Measure evaluation 2013] and readers are encouraged to refer to that for further details. + +This section defines CHIS governance, provides an overview of governance of CHIS, and proposes standards for data management governance which, when applied, can strengthen CHIS performance. + +> *Governance in data management can be defined as:* The development and implementation of administrative policies, procedures, and processes that define workflow, program inputs and outputs, management structure and oversight functions, and the methods and frequency of performance evaluation. + +Data management governance dictates how the different components of the CHIS, at the same or different levels of the health system, work together to achieve a common goal - quality health data for decision making. For the purposes of this guideline, governance is applied largely to CHIS and is seen as a core function of high level management at all levels -that is, to monitor, assess, and strengthen these systems to facilitate improvements in service delivery + +Data management governance ensures that data is of high quality - current, correct, consistent, and complete - as well as readily available to stakeholders (i.e., ensuring access to consumers, or those who require health information to inform decision making). In practical terms, that means putting personnel, policies, procedures, and organizational structures in place to ensure that data is accurate, consistent, secure, and available. + +The process of data management governance for a CHIS should foster cross-organizational collaboration, facilitate structured policy making and balance ad hoc or narrow information needs with the interest of the Community health system. Interventions to improve governance should address the institutional, behavioral, and technical determinants of CHIS performance described above and focus on improving the desired CHIS output of good-quality data that is regularly used to improve service delivery. + +Good governance requires commitment at all levels. It is not enough to have good structures, policies and procedures at the top. They need to be implemented by a dedicated team of well-trained stakeholders at the lower levels who have the motivation and skills to monitor and evaluate the CHIS based on the principles of participation, accountability and transparency. + +![](resources/images/chis_figure40.png) + +*Figure 6.2* Governance of Data management + +This model brings together in one place a number of concepts dealt with in other places in this guideline including: + +- Formal governance structures such as SOPs and strategic planning and financial systems, as well as oversight mechanisms such as technical working groups (TWG). +- Workforce development, training, and supervision to identify best practices pertaining to CHIS staffing. (Chapter 5) +- Policies and procedures for data management, with particular regard to standard operating procedures, data and metadata stewardship. (Chapter 4) +- CHIS assessment, starting with general assessment questions and then exploring the Performance of Routine Information Systems (PRISM) model to see how CHIS converts inputs into appropriate outputs by influencing determinants of health outputs (organizational, behavioral, and technical) and their influence on overall health system performance.(Chapter 2) +- Ways to promote a culture of information use is the core theme of this manual. + +## Formal Governance Structures { #formal-governance-structures } + +CHIS governance is the oversight and monitoring function necessary to ensure that the CHIS functions as designed. Adequate governance allows the system to identify threats to performance and make necessary corrections, as well as to find opportunities to improve the CHIS and advance the aims of the system. + +Governance structures are the formal mechanisms through which this oversight and local management takes place, including organizational frameworks, TWG (Technical Working Groups), and boards of directors. Governance structures oversee the management functions and inputs to ensure optimal system functioning + +### Mission Statement { #mission-statement } + +A mission statement is a formal expression of the purpose of the CHIS and its reason for being. A good mission statement states the reason for the organization's existence and includes goals, names primary stakeholders, and articulates how the organization provides value to stakeholders. + +### Organizational Chart { #organizational-chart } + +An organizational chart is a diagram used to depict the CHIS structure and personnel. It helps organize personnel by identifying management control within the organization. + +An organizational chart is useful for planning, resolving disputes, and managing change. It can be used as a baseline for planning, budgeting, and workforce modeling as it gives a succinct overview of the organization. + +### Effective participation structures { #effective-participation-structures } + +CHIS oversight committees should be formed at each level of the system---that is, in each district and facility, to monitor CHIS system performance. The committee should be made up of CHIS stakeholders from health care institutions, implementing partners, local governments, and, where possible, civil society. These committees should facilitate the CHIS mission in their area of influence by monitoring performance, alerting CHIS management to strengths and weaknesses, and facilitating capacity building. + +Village Health Committees are crucial to spread participatory processes to the lowest levels and these need capacity development, funding and regular feedback to become effective + +The CHIS regulatory authority and data governance council (see policies and participation section) also need to have effective representation of community stakeholders + +### Reporting Structures { #reporting-structures } + +In a CHIS, data and information begin at the service delivery point in the community and then flow toward the center to be shared with stakeholders to ensure that relevant information, based on quality data is available to those who need it in timely fashion. + +Reporting structures include directives (SOPs) from CHIS management, which state who reports what and to whom, when reports are due, in what format and by which mechanisms. + +In the context of CHIS, reporting structures clearly define: + +- The source document for reporting---that is, the individual client record +- The standardized, aggregate, periodic report for reporting to the next level +- Reporting deadlines---the date reports of various types are due to the next level. +- Indicator calculation guidelines and compilation, and completing the forms +- Reporting Procedures for sending the data to the next level. +- Data quality review procedures +- Sanctions (if any) for failure to meet reporting obligations. +- Responsibilities of staff members to monitor reporting of performance and compliance, and enforcement of these standards? + +### Master Facilities List { #master-facilities-list } + +A master facilities list, in DHIS2, is a complete listing of all health service delivery sites in a country, including CHIS reporting units, with information about capacity and services available. It is dynamic and should be kept up to date as reporting units (CHWs) are added to or subtracted from the system. + +A master facilities list improves record keeping by improving transparency and reporting efficiency. It minimizes duplicate reporting and promotes analysis and synthesis of data to improve decision making and health system functioning. + +### Planning Structures { #planning-structures } + +Planning is critical to ensure that CHIS resources are targeted efficiently and according to need, so that maximal benefit is achieved from CHIS investments. Planning *structures* refers to mechanisms for planning, such as periodic program reviews and needs assessments, combined with financial reviews and budgeting. Setting targets and situational analyses are also aspects of regular planning. + +## Policies and Procedures for Data Management Governance { #policies-and-procedures-for-data-management-governance } + +The management of CHIS data should be standardized such that the steps performed in turning data into information are the same throughout the system---from one district or CHW to another. + +These policies and procedures are an integral part of governance and should be well defined, detailed, written down, and made accessible to all staff and other stakeholders in the data management process. Processes should be supported by policies that are well known and enforced, so that standards are applied uniformly across the system. The following are standards and best practices for data management policies and procedures. + +### CHIS Regulatory Authority { #chis-regulatory-authority } + +For a CHIS to function effectively, all community role-players should routinely report, using standard mechanisms, to the CHIS. Regulatory authority often takes the form of public institutions empowered to regulate public health practice according to government imposed standards. This is necessary to ensure complete reporting from all sources of health service delivery including CHWs. However, the MOH often has no formal influence over CHWs to ensure reporting, other than the regulatory authority provided through government. + +To efficiently target resources for disease control and prevention, CHIS managers need to understand where disease is occurring in the population and where services are being utilized. Without accurate targeting based on complete, reliable data, resources can be wasted by sending too much to areas that do not need it or too little to areas that do. + +### E- Health and Information and Communication Technology Policies { #e-health-and-information-and-communication-technology-policies } + +ICT governance is essential to ensure that there are rules and regulations guiding use of electronic tools for managing and transmitting data and information, such as computers (hardware and software), networks, tablets, personal data assistants (PDAs), flash media, and communication tools, such as cell phones, modems, e-mail, instant messaging, and social networking. + +A policy framework should be developed by the MOH to manage ICT resources in the system. What resources to acquire, how they should be used and by whom, when they should be upgraded or replaced, and how they are maintained should all be codified into the framework to ensure efficient stewardship of CHIS resources. + +Because CHIS personnel should not be expected to have knowledge of maintenance and repair of ICT hardware and software, outside resources can be utilized. Reputable, licensed computer hardware and software vendors and repair firms can be contracted to maintain the ICT resources in the CHIS, reducing the burden on HMIS personnel and allowing them to focus on data collection, analysis, and use for planning and management. + +### CHIS Data Governance Plan Based on Best International Practices { #chis-data-governance-plan-based-on-best-international-practices } + +A CHIS governance plan refers to roles and processes that serve as a guideline for fulfilling, sustaining, and extending CHIS planning. A governance plan crosses all organizational layers, including stakeholders, administration, maintenance, strategy, policy, and support.^[*Technopedia:* [Governance Plan](http://www.techopedia.com/definition/2910/governance-plan)] + +A CHIS governance plan should clearly state who does what, when, and how with regard to CHIS management, to management of data and information, and to decision making. A governance plan is useful in times of transition or change in the CHIS, since it provides a reference tool to clarify roles and settle disputes. + +### Data Standardization Policies, Framework, and Procedures { #data-standardization-policies-framework-and-procedures } + +Most countries still lack policies that bring together the various components of CHIS under a single unifying framework and provide clear lines of responsibility and functionality. CHIS management structures should be strengthened centrally and resources and authority decentralized to serve the specific needs of the people involved in implementing CHIS, particularly at the periphery. + +The CHIS framework in both national health policies and strategic plans should encapsulate an integrated CHIS as part of overall health systems strengthening and governance reform, with buy-in to the plan from local government, political authorities, the MOH, and donors. The framework should recommend the pooling of CHIS expertise and resources into "one plan, one framework and one funding mechanism."^[Paris Declaration on Aid effectiveness 2005] + +Countries also need a practical CHIS operational plan wherein all CHIS activities within the MOH are centrally guided, with clear lines of decentralized responsibilities in the spirit of administrative, financial, and operational decentralization toward districts. + +As defined in the CHIS framework, institutionalized mechanisms should be developed for integrated CHIS data quality assurance (as measured by its completeness, accuracy, timeliness, and consistency), with validation rules for electronic systems and a team approach to data quality. In addition, these policies should: + +1. Specify interoperability of CHIS subsystems. +2. Define human resource needs and capacity strengthening requirements. +3. Define responsibilities for data collection, information flow, and use. + +National policies should provide for a balanced, limited set of national CHIS indicators, which are regularly reviewed in a participative manner, with clearly defined numerators and denominators, data sources, baselines, and national targets. There should be a regular indicator review process in which program and subnational managers participate to ensure that the existing indicator set fulfills their needs. + +Most countries have policies, laws, and regulations governing health services that, if applied, would greatly improve health system functioning. Too often inadequate resources or a lack of incentives mean that these policies are not enforced. Their implementation could be strengthened by the application of SOPs. + +### Metadata stewardship { #metadata-stewardship } + +In CHIS, stewardship of metadata, or responsible planning and management of data about data, is needed to foster consistent use of data management resources and facilitate data mapping among computer systems. A data steward holds responsibility for maintaining a data element in a metadata registry. Data stewardship roles are common when organizations need to exchange data precisely and consistently among computer systems and to reuse data-related resources. + +A data steward ensures that each assigned data element: + +1. Has a clear and unambiguous definition. +2. Does not conflict with other data elements in the metadata registry. +3. Is being used and is being used consistently in all interlinked computer systems; unused data elements are removed. +4. Has adequate documentation on appropriate usage and notes. +5. Is documented with regard to its origin and sources of authority. + +Assignment of data elements to an individual promotes trust in systems where users can contact a specific staff member with questions on specific data elements. + +### Data Quality Assessment and Auditing { #data-quality-assessment-and-auditing } + +CHIS data quality should be assessed periodically to enhance confidence in data and promote use of the data for decision making. Data quality should be assessed routinely for high-priority indicators as a part of regular supervision, and less often for other indicators. A periodic assessment of CHIS performance should include a data quality assessment. + +### Data Standards { #data-standards } + +Governance refers to a process which outlines the process and mechanisms of how decisions are taken. In the CHIS case, the governance decisions concern how and why new systems are introduced, and their implications. As emphasized throughout this document, the CHIS is not a standalone system, but is linked by standards with other data collection processes and systems based on the six WHO building blocks. + +Data standards are multifaceted in nature, involving both technical and semantic standards: + +1. Technical (syntactic) standards such as data transfer protocols. +2. Semantic (nomenclature) aspects. Important semantic standards in the context of CHIS include metadata stewardship issues such as : + a. Meta data naming conventions for data elements, indicators, organizational units, shape files and others. + b. Reporting periods for different elements and the formats in which they are reported, that enable ease of compilation of data for the CHW. + +A universal governance problem is that donors and NGOs want to introduce their own parallel community systems and data collection formats without being accountable to other standards and systems in the community setting. This lack of governance adds to the workload of the CHWs since all data collection work converges on them, and magnifies the fragmentation. + +This situation is primarily due to the absence of a higher level mechanism for governance of data and standards. A typical governance mechanism is the establishment of a steering committee at the MoH level, and all proposals for the introduction of new systems should be approved by them. For example, they should need ensure that the new system being proposed is feasible, how it overlaps with other systems, what duplications are involved, the implications on data collection burden, compliance with laid out standards, and whether the required outputs can be met through existing systems. Such a systematic and thorough process of governance goes a long way to control duplications and redundancies and reducing the work burden of the CHW. However this governance needs to be enforced at lower levels, with responsibility and authority being given to districts and facilities to prevent parallel systems proliferating. + +These guiding principles generated a community driven framework of standards, as contrasted with those which are typically imposed from the top with most often sub-optimal results. A framework of standards which represent everyday work, and are bottom up driven are more likely to add value and be accepted by the CHWs. + +### Standard Operating Procedures (SOPs) { #standard-operating-procedures-sops } + +SOPs are the translation of policies and procedures into day to day life of the CHIS stakeholders. All stakeholders need their roles and responsibilities clearly defined in a set of SOPs that form part of the organizational culture of the CHIS. SOPs should describe clearly who should do what, when, and with what resources, to manage and maintain the CHIS. + +There are many ways to define SOPs, and the actual SOPs vary tremendously from country to country and project to project. The SOPs outlined below represent some very basic, practical SOPs that could serve as the foundation for country or program specific SOPs. + +#### Visión general { #overview } + +There are three, basic SOPs outlined in this manual: + +1. Reporting Guidelines in Chapter 4 +2. Training protocol in the Chapter 5 +3. Supervision protocol in Chapter 5 + +![](resources/images/chis_figure41.png) + + +*Figure 6.3:* Standard operating procedures outlined in this manual. + +#### SOP Best Practices { #sop-best-practices } + +1. **Harmonize multiple programs into a single protocol.** This is especially true for the data capture protocol described in this chapter and the training and supervision protocols in the training chapter. +2. **Develop SOPs for each individual community project** especially if multiple data flows exist from. +3. **Turn the SOP into illustrated posters** and have the facility staff post them on their walls for public viewing. +4. **Print SOPs and make sure all CHWs, facility staff, and district staff have copies** +5. **Stakeholders to sign the SOPs** at the completion of training. +6. **Stakeholder participation in the creation and approval of SOPs.** The SOPs must institutionalize the best practices and workflow of the actors in the CHIS. Include representation from all relevant stakeholders in the process of developing SOPs. +7. **Ensure all data elements and indicators are captured.** The project should have an M&E framework (see Chapter 3) that should clearly define all data elements and indicators. The CHWs should clearly understand the meaning, and measurement of each data element and indicator to remove ambiguity +8. **Use data capture guidelines at trainings.** To build accountability, CHWs and facility staff need to know they are part of a larger system. They need to know how their data is used for planning at higher levels and specific actions at lower levels. +9. **Have the CHWs explain the data capture guidelines.** This teach-back method is an effective adult learning practice. By explaining the data capture guidelines, this elevates the CHW's credibility with the health committee. +10. **Produce, simple-to-use, local language guidelines.** CHWs and facility staff need guides and instructions on what to do. Consider making posters or small laminated portable data capture guidelines for CHWs and facilities to put on the wall or carry with them that outline their role and responsibilities based upon the data capture guidelines. +11. **Have CHWs, facility, district staff and national staff sign guidelines.** This is a symbolic "commitment" measure. The aim is that they have read it, understand their reporting responsibilities as defined in the data capture guidelines, and will carry out these responsibilities. +12. **Produce simple videos or audio and upload them to phones.** Responsibilities and actions for every event are made easier with a simple, local-language videos or audio guides that facility staff and CHWs can refer to. + +## CHIS Staffing and Workforce Planning and Development { #chis-staffing-and-workforce-planning-and-development } + +People are the lifeblood of CHIS, and even the best system would generate no information products without the combined efforts of all CHIS staff. An entire chapter of these guidelines are dedicated to capacity development, but the topic outline is repeated here to reinforce its importance in CHIS governance. + +- Training needs to be carefully planned and costed, with the appropriate infrastructure, equipment and curriculum, trained teachers +- CHIS staff must have the training they need to perform the tasks expected and to produce the data and information necessary to monitor the community health system. +- Adequate numbers of staff is also necessary. A staff that is too small risks underperformance, while a staff that is too large wastes precious CHIS resources. +- The staff and its training should be organized, efficient and of high quality. +- Certain standard elements of CHIS staffing and training help ensure high quality output from the workforce while avoiding redundancy or wastage. + +Components of CHIS planning and development that should be covered by this planning and development process include + +**Training Infrastructure and staff:** + +- Costed training plan| +- Standardized training curriculum/materials| +- Equipped training institutions| +- Adequate numbers of competent, trained trainers | + +**Supportive Supervision and Mentoring:** + +- Guidelines for standardized, effective supervision +- Standardized supervisory checklists +- Targeted feedback mechanisms| +- Standardized supervision reports---tracking results and monitoring trends | + - Schedule of supervisory visits| +- Data quality checks + +## Monitoring and Evaluation { #monitoring-and-evaluation } + +Monitoring and evaluation (M&E) is the final, but crucial component of Data Governance and concerns maintaining data quality and ensuring quality of the overall CHIS as well as regular assessments of CHIS functionality. This is in addition to the standard programmatic M&E, which is not covered here. + +### Maintaining CHIS Quality { #maintaining-chis-quality } + +CHIS quality is essential and the determinants are similar to those already described for sustainability -technical, organizational, and behavioral factors that convert CHIS functions into the key outputs in the form of quality data that is regularly used so as to improve health system performance. (PRISM framework^[MEASURE Evaluation, “PRISM: Performance of Routine Information System Management Framework,” [https://www.measureevaluation.org/resources/prism.html](https://www.measureevaluation.org/resources/prism.html)]) + +#### Technical Determinants { #technical-determinants } + +These are the specialized know-how and technology to develop, manage, and improve CHIS processes and performance. Affecting CHIS performance both directly and via behavioral factors, they include: CHIS design, computer software, as well as the complexity of information technology, reporting forms and procedures. + +#### Organizational Determinants { #organizational-determinants } + +These relate to organizational structure, resources, procedures, support services, and work environment that promote a "culture of information"---the capacity and control to promote values and beliefs within the organization by collecting, analyzing, and using information to achieve the organization's goal and mission. Organizational factors include: governance, planning, resource availability, training and capacity development, supervision, finances, information distribution, and the culture of information. + +#### Behavioral Determinants { #behavioral-determinants } + +These include: the CHIS users' demand for data, data quality checking skills, competence and problem-solving skills for CHIS tasks, confidence levels in their ability to perform CHIS tasks, and motivation to perform at peak ability. These behavioral factors are influenced by both technical and organizational determinants (above). + +### Assessing CHIS Functionality { #assessing-chis-functionality } + +Assessment has been dealt extensively in Chapter 2 and is summarised here. + +A major test of the effectiveness of CHIS governance is regular participatory assessment to see whether CHIS is improving health program outputs and health impacts. Yet, surprisingly, this aspect of performance is rarely formally evaluated. + +CHIS impacts on health programs can be measured by four simple questions: + +- Is the information relevant? +- Is the information of good quality? (Is it timely, consistent, complete, and accurate?) +- Is the information presented in a user-friendly way? (Is it easy to access and easy to interpret?) +- Is there capacity to act on the information provided? +The answers to these questions need to be approached in a way that addresses the health systems framework and should be further elaborated by asking: +- Has the CHIS been decentralized, and have lower-level program managers contributed to decision making? +- Have the systems been integrated and contributed to broader program integration? +- Has CHIS contributed to evidence-based decision making and more effective health outcomes? + +### Assessment methods { #assessment-methods } + +Here we provide an overview of some of the popular methodologies to assess CHIS functionality, including: + +#### Decentralised Self-Assessment { #decentralised-self-assessment } + +To strengthen data management, countries should institutionalize regular self-assessment data use meetings, particularly at facility and district levels. Self-assessment should use local data to calculate indicators in order to review performance against targets for client, facility, and system indicators and to compare the results to those of similar institutions, other geographic areas, and national norms. Self-assessment meetings should be conducted at least quarterly and should be made part of routine SOPs for work and management procedures. + +#### Health Metrics Network Assessment Framework { #health-metrics-network-assessment-framework } + +This comprehensive assessment framework, considered the gold standard for HIS assessment, is the basis for the Macro-assessment described in chapter 2. The HMN framework deals with the holistic HIS (the CHIS being just one aspect) and is not discussed further here, but constitutes a valuable tool for evaluating overall HIS functionality, in which CHIS plays a significant role. + +The full HMN assessment asks stakeholders approximately 200 questions regarding all six HIS components---HIS resources, indicators, data sources, data management, information products, and data dissemination and use ---and scores the answers electronically, producing a series of graphs for each component. + +#### The PRISM Framework { #the-prism-framework } + +The PRISM framework and toolkit takes a holistic approach to CHIS monitoring and evaluation, seeking to assess system performance by investigating CHIS performance determinants (the technical, organizational, and behavioral factors described above). Performance, as assessed by the PRISM methodology, is measured by the level of data quality, the extent of data use for decision making, and the management capacity. + +PRISM assessments can be used to establish a baseline measurement of performance and can then be repeated after interventions to gauge their effectiveness. PRISM tools can also be used for routine monitoring of CHIS performance (such as conducting data quality checks as part of routine supervision). + +## Conclusión { #conclusion } + +Many of the governance issues dealt with above are illustrated in a case study from Zambia in which an NGO- initiated project transitioned to government ownership while achieving remarkable results for community sanitation. + +## Case Study: Community Led Total Sanitation from Zambia { #case-study-community-led-total-sanitation-from-zambia } + +This case study describes the development of an information system for Water and sanitation for Health (WASH) based on the DHIS2 platform. This system was built by Akros, an NGO, and were engaged with the challenge of sustainability after successful implementation of the system. The case illustrates the approach they adopted in transition the system from the NGO to the government in their bid to establish sustainability. This case is thus unique in illustrating the challenges of transitioning systems to establish robust government ownership. + +In 2013, DFID funded a Water and Sanitation for Health (WASH) program in Zambia. Community led total sanitation (CLTS) conducted by the Zambian Ministry of Local Government and Housing (MLGH), UNICEF, and an implementing partner. In response to concerns of poor data reporting and targets which were not being achieved, the team layered a unique mobile-to-web application (M2W) using DHIS2, over traditional paper based CLTS data collection methods, resulting in an innovative service delivery and monitoring system dubbed "CLTS M2W". CLTS M2W uses mobile feature phones, automated data feedback loops, and engagement of traditional leaders to provide communities with the ability to clearly see their progress towards sanitation goals. + +These tools require data collection at the community level by Sanitation Action Groups in each village, data entry onto phone by community champions, and the management of this process by local chiefs and at district level. CLTS M2W paved the way for unprecedented CLTS uptake in Zambia, facilitating the creation of over 1,500,000 new users of sanitation over 18 months. + +#### Government involvement and Ownership { #government-involvement-and-ownership } + +The leadership of the Ministry of Local Government and Housing was critical from the beginning of the project, but most important was the leadership of the local government in the districts and the traditional leadership of chiefs in the villages, where the intervention was ongoing. When a CLTS program is first introduced in a district, the intervention, technology, and supervision is initially led by the implementing partners with the goal of ultimately transitioning ownership of the program fully to the government. Though the initiation visits were led by the governments' partners, the following visits and all supervision visits were led by the district government officials with each subsequent visit involving less outside partner involvement than the prior. + +Focal Point Persons (FPP) are the local or national government employees who coordinate these activities and channel knowledge and communication for programs in the field and at the district level. To promote their ownership and engagement of the data, FPPs receive DHIS2 data analysis training during supervision visits. Long term sustainability requires fully trained ministry staff and community champions, who understand and can troubleshoot the system. + +#### Capacity Development { #capacity-development } + +Trainings were conducted by partner staff to district staff, who then trained community champions (CCs) and Sanitation action groups (SAGs) in a training of trainers approach. There were different trainings at every level of data collection and regular feedback to ensure that data collection tools were properly used and understood. + +- The Sanitation Action Groups required an understanding of the paper-based data collection tools, what was being monitored and why; +- Community Champions needed to operate feature phones for data reporting, understand the data being collected and the feedback loops they were receiving; +- Environmental Health Technicians (EHTs) required training to understand the mobile platform and how to troubleshoot minor problems. EHTs and other government officials also benefited from data use trainings. + +District Water Sanitation and Hygiene Education (DWASHE) committees were created in districts with staff from all government ministries to review sanitation progress at quarterly meetings. They are trained in the use of DHIS2, using specially developed dashboards and other visualization tools to enable them to inspect the sanitation state of the districts and make district WASH plans based on these data. + +#### Feedback to Stakeholders { #feedback-to-stakeholders } + +Custom-developed reports with DHIS2 data are sent to partners monthly, giving an overview of "open defecation free" (ODF) status, and reporting rates. There are several iterations of these html based reports, designed to communicate the necessary information to the receivers. + +- EHTs receive information on total reports received out of the total expected within their assigned catchment area. +- UNICEF and MLGH receive reports on sanitation progress of each data element per district. + +These reports were designed to help EHTs target their activities based on which CCs need help reporting, and respectively can help UNICEF and MLGH in resource allocation. + +#### Involvement of chiefs { #involvement-of-chiefs } + +After a few months of monitoring data and not seeing a dramatic effect on latrine construction, a program manager proposed incorporating the power of traditional leadership into the protocol design of CLTS. A tablet-based chiefdom widget was designed to enable chiefs to view relevant information without logging in to DHIS2 and requiring minimal mobile data to support. This information is presented in charts, tables, and graphics, that exist on the home screen of the tablets. + +![](resources/images/chis_figure42.png) + +*Figure 6.5:* Snapshot of the Chief's Visualization App active on a tablet home screen. + +![](resources/images/chis_figure43.png) + +*Figure 6.6:* Enlarged list of sanitation performance of individual villages of the chiefdom. + +Armed with this information, chiefs could compare the performance of their villages to their neighboring chiefdoms villages' performance, combining the power of community behavior changes, with the traditional authority chiefs must instigate that change. Following tablet distribution came positive change in open defecation free status, as chiefs used their influence to encourage their headman and villages to build more latrines (see figures 6.7 & 6.8). + +![](resources/images/chis_figure44.png) + +*Figure 6.7:* Figure illustrating the influence and process of chiefdom orientation + +![](resources/images/chis_figure45.png) + +*Figure 6.8:* Sanitation Uptake over Time. Ministry of Local Government Republic of Zambia + +#### CHIS Development { #chis-development } + +The development process benefited from a "boots-on-the-ground" approach at district level and below in Zambia. This local understanding combined with DHIS2 skills enabled an agile development approach that allowed for flexible platform creation and modification as needs and priorities shifted. This flexibility allowed the data collection process to mature as needs developed. As the program grew and donor interest expanded, data collection was able to expand to include monitoring of water access, face washing and environmental cleanliness. + +The paper tools themselves also changed: originally, paper sheets were printed on single-sided documents and distributed to SAGs, but as the program grew, notebooks were printed for SAGs to collect their monthly reports and share with the CC. The notebooks included helpful tools and guides for implementing CLTS in their communities on the front and back cover and prevented the loss of paper records. + +One key example of agility that the development approach facilitated was the selection of the most appropriate hardware for data collection. Smart phones were piloted in the first year, but were not working well due to the low literacy level of the CCs and the added costs associated with more expensive and fragile phones. The pilot approach allowed procurement and training strategies to shift to use simpler feature phones, a more fitting option for the data collection tool. + +The CHIS development strategy also relied heavily on the CHIS pillar that stressed balancing the reporting burden. Pushing against the tendency to collect more, do more, and learn more is tough work. As stakeholders learn of a successful program, they want to be involved. Keeping the reporting burden of village SAGs and CCs light enables reporting incentives to remain low, reporting rates high and training costs low. Nowhere was this more evident than in the roll out of water access monitoring. Initial requests had CCs collecting an additional 12 new data elements. It took months of negotiation, a pilot, and subsequent data collection revisions to keep the list of new data elements reasonable. + +Historically, a paper to Excel system was used for CLTS, requiring community facilitators to collect and aggregate hand-written reports for each village Sanitation Action Group (SAG). Environmental Health Technicians (EHTs) collected aggregated paper records from community facilitators and reported to the district to enter Microsoft Excel. These Excel records were submitted to the central level for manual aggregation into one master Excel file for data analysis. This process was error prone, extremely slow, and only offered basic analytical functions. + +![](resources/images/chis_figure46.png) + +*Figure 6.9:* Data flow of CLTS reports. Sanitation action groups (SAGs) in each village report data to community champions (CCs). CCs submit data to the DHIS2 via mobile phones. EHTs oversee CC cadres. + +The new system depicted above in Figure 3 was designed to maintain the paper-based village SAG forms containing 14 data elements on latrine construction. Data burden was reduced by reporting only data for a set of indicators developed with MLGH for performance of village-level sanitation. CC's were given mobile feature phones with a java app to report SAG data directly onto the DHIS2 database, minimizing reporting duplication. + +#### SOP Development { #sop-development } + +Strong protocol development and implementation also helped move the program towards sustainable success. These protocols (e.g. Supervision Visit Protocol, Surveillance Protocol, Event Protocol, Exit Protocol, and Final SV Checklist) were developed together with MLGH, based on improving existing practices and are the basis for activities that Surveillance Officers, Environmental Health Technicians, and traditional leaders undergo for successful implementation. + +A key protocol that ensured government engagement throughout all parts of the reporting process was the Event Protocol. This protocol provides a foundation for government transition support as well as structured approach to each necessary task that delineates for each event: who is responsible, when it should occur, why it should occur, and what the goal of that event is. Within the WASH program, these events are Community Mobilization, Mobile Surveillance Training, SAG Data Collection, CC Data Collection, EHT Feedback, District Monitoring, ODF Verification, Quarterly Ward Meetings, and Quarterly DWASHE Meetings. + +Two examples are given in Figures 6.10 and 6.11: + +> | Community Mobilization | | +> |:-|:-| +> | Responsible Person | Chief and/or Senior Headmen | +> | Periodicity | Ongoing| +> | Purpose | To continue building village-level awareness of and support for community-led total sanitation | +> | Outcome | Continued propagation of improved latrines | +> +> CLTS community mobilization includes any event that involves a SAG, CC, EHT, Headman and/or Chief pushing the CLTS agenda at the village-level. On a monthly basis, the SAG mobilizes each household in the village, fills out the CLTS Data Collection Sheet while monitoring latrine propagation and conducting sensitization. + +*Figure 6.10:* Table illustrating community mobilization. + +> | **ODF Verification**| | +> | :- | :- | +> | Responsible Person| District CLTS Focal Point Person| +> | Periodicity | When a village claims ODF status| +> | Purpose | To verify if villages are open defecation free| +> | Outcome | Villages that claim ODF are verified to be ODF or not | +> +> This process helps maintain data quality. When the District CLTS FPP logs into DHIS, he/she will see a notification on the Dashboard for any villages that claim ODF status. The notification will indicate the name of the village and prompt the District CLTS FPP to mobilize the verification team to conduct a field visit to the village. +> +> It is the EHT's responsibility to coordinate a verification team, acquire funds from the District Office and verify the village. After the verification visit, the EHT reports their findings through the DHIS2 mobile application's ODF Verification Form. +> +> Once a village has been verified for 3 months, a team of District Officers then visits the village to conduct a spot-check certification. Districts are able to monitor ODF progression through DHIS2 visualization tools. + +*Figure 6.11:* Table illustrating ODF verification. + +These protocols strengthen operations, and streamline reporting by standardizing expectations for all roles, and providing people with needed tools to meet these expectations. + +#### Lessons learned { #lessons-learned } + +1. Government sustainability was fostered from the very inception of the program as program implementers worked hand-in-hand with MLGH at all levels of the hierarchy. Surveillance visits always incorporated local government staff. +2. Visualization of data by key 'change agents', in this case local chiefs and traditional leaders creates ownership and motivation. These change agents were provided a means to understand the performance of their villages in relation to sanitation practices and not only had the data, but the leadership authority to encourage village level improvement. +3. Clear documentation through SOPs is essential for clear system functioning and management of all parties. +4. Multi-ministerial collaboration is important. In this case, Ministry of Chiefs and Traditional Affairs (MOCTA) and MLGH collaborated to ensure chiefs and traditional leaders were engaged in sanitation at local level. This was a success. + +A future goal is to better link data from MLGH with data from the Ministry of Health. Specifically, MLGH data (CLTS intervention data) is currently captured within an instance of DHIS2, with health-outcome data (e.g. diarrheal disease incidence) captured in a separate instance of DHIS2 (Ministry of Health). By linking the two systems, it will be easier to understand the impact of the CLTS program on health outcomes. + +## Case Study Liberia Community Based Information System (CBIS) { #case-study-liberia-community-based-information-system-cbis } + +### The National Community Health policy and programs { #the-national-community-health-policy-and-programs } + +In 2015, the national policy on Community Health Services was revised to fully reflect the community health components of the National Health Plan. The Revised National Community Health Services Policy aims to strengthen Liberia's health system and health services that were lost due to the Ebola Virus Disease (EVD) crisis, to provide health security by reducing risks due to epidemics and other health threats' to accelerate progress towards universal health coverage by improving access to safe and quality health services and to narrow the equity gap for Liberia's most vulnerable populations that live in the last mile. + +Community-based services are vital to the health and wellbeing of these communities. Additionally, the recent Ebola epidemic in Liberia and across West Africa highlighted the critical role that communities play in addressing their own health needs and changing their own health behaviors. + +A key feature of this revised policy is the institution of a new cadre of Community Health Assistants (CHAs), who are selected from and serve communities located more than a one-hour walk (more than 5km) from the nearest health facility. Through established criteria, CHAs are selected by their respective communities to undergo an integrated and standardized CHA training. Upon successful completion of the training, these individuals will be certified as CHAs. Throughout training and continuing after certification, CHAs will be supervised to deliver an integrated and standardized service delivery package---which includes curative, preventive, promotive, rehabilitative and palliative services as well as epidemic surveillance services---to households in their communities. + +#### Community Health Services Vision { #community-health-services-vision } + +*A coordinated national community health care system in which households have access to life-saving services and are empowered to mitigate potential health risks.* + +![](resources/images/chis_figure47.png) + +### Key figures in Liberia's CHA program structure { #key-figures-in-liberias-cha-program-structure } + +#### Community { #community } + +The Community Health Committee (CHC) is elected by the community with guidance from the catchment Health Facility. The CHC is to oversee and assist in the selection of CHAs and provide administrative support for health activities in the community. The committee shall comprise of a total number of 5 - 9 elected members depending on the size of the community. Every attempt should be made that at least 30 % of the members are women + +The Health Facility Development Committee's (HFDC) primary responsibility is to act as a governing body for all CHCs in the facility catchment area. The CHSS, in consultation with the OIC, shall serve as secretary to the HFDC. The HFDC is to meet monthly, providing a direct connection between community members and the District Health Team (DHT)/County Health Team (CHT), as well as local representatives and coordinating bodies of the Ministry of Internal Affairs + +#### Community Health Assistant (CHA) { #community-health-assistant-cha } + +CHAs is recruited by the community, trained and supervised the formal health system (Facility) to deliver an integrated and standardized service delivery package, which includes preventive, curative, promotive, rehabilitative and palliative services and epidemic surveillance to households located more than a one-hour walk (>5km) from the nearest health facility. CHAs will be responsible for recording information on individuals in each household during visits when conducted and services are provided. These data are reported into an aggregated monthly service report and sent to the facility at the end of each month. + +**Profile of CHAs** + +- Permanent resident in the community which s/he serves, between 18 and 50 years of age +- Involved in community project/s in the past, trustworthy and respected +- Able to read and write and to add, subtract and multiply +- A good mobilizer and communicator fluent in the village dialect + +#### Community Health Services Supervisor (CHSS) { #community-health-services-supervisor-chss } + +Community Health Services Supervisor (CHSS) is a clinically trained professional assigned to the health facility to supervise the CHAs. The CHSS shall provide field-based supervision to CHAs working in remote catchment communities of the health facility. One CHSS shall supervise up to 10 CHAs and is responsible to manage the CBIS system and serve as first point of contact for CHAs at facility level, provide leadership and clinical supervisions to CHAs, ensure logistics (forms, commodities, etc.) and to aggregate data from the CHAs and submit to the relevant facility. + +#### Officer in Charge (OIC) of the Facility { #officer-in-charge-oic-of-the-facility } + +The OIC is responsible for coordinating all health-related activities in all catchment communities for each health facility. He/she is responsible to supervise the CHSS and provide feedbacks to health facility development committee (HFDC) on which he/she serve as secretary. + +#### Community Health Services Focal Point (CHFP) { #community-health-services-focal-point-chfp } + +The Community Health Department of each CHT shall be responsible for integrating all community health activities into their county operational plan. The Community Health Focal Person (CHFP), assigned by the CHT, work under the supervision of the Community Health Department Director (CHDD) to coordinate all community health activities in the county. He/she work with the District Health Teams and facilities in the implementation of the community health programs. + +### The CBIS { #the-cbis } + +During the Ebola epidemic it became clear that the fragmentation of the current health information system made it impossible to have the "right information at the right time and in the right place". Many HIS subsystems were not interconnected, and stakeholders did not coordinate, contributing even further to the fragmentation by setting up separate reporting systems. After the Ebola crisis, strengthening the National Health Information System (HIS), and the Monitoring and Evaluation (M&E) system was recognized by the Ministry of Health of Liberia as one of the key interventions of the Investment Plan. + +In 2016 as the National Community Health Assistant (CHA) Program was created, the need for a CHIS became apparent. With the support of development partners, the MoH developed a comprehensive community-based information system (CBIS) as a subsystem within the HIS. These partners formed an M&E sub-group, which informed the system and development of tools to capture information from the CHA Program. + +The CBIS connects community-level health services with national health system, the lowest tier where service is provided. MOH attaches great importance to the preventive, curative, awareness, etc services provided by CHAs + +Data collection and reporting forms and ledgers were develop and built in the DHIS2 system. Future efforts include integrating CBHIS, LMIS and HRIS to improve management of community-based health services, produce supply chain efficiency gains and reduce stock-outs. + +#### Service Delivery Package and Data Sources { #service-delivery-package-and-data-sources } + +The ministry, with support from development partners, developed an integrated service delivery package for the Community Health Assistant (CHA) program, using modular packages. The CHA service package focuses on disease prevention, surveillance, reproductive, maternal, neonatal and child health, including integrated Community Case Management and its main approach is community mobilization, health education and health promotion. The goal is help residents realize that they are responsible to manage their own health matters; communities are empowered to create structures and identify and put together resources for health. + +#### Liberia Data Flow { #liberia-data-flow } + +Data collection tools from each of these module-based service delivery area were developed. Each of these service specific tools will be aggregated into the monthly service report each month at the level of the community health assistant (CHA) and at the level of the community health services supervisor (CHSS). The graphics illustrate this process. + +#### Reporting Timeline { #reporting-timeline } + +![](resources/images/chis_figure48.png) + +### Data Use { #data-use } + +CBIS was designed as a streamlined flexible system to allow for decentralized data entry and local use. + +#### Data Use at the CHA level { #data-use-at-the-cha-level } + +Data forms (ledgers) are kept in the community once completed, to keep an accurate record in the community of the work of the CHA. The CHA aggregates the ledgers into the CHA Monthly Service Report. This report is per community catchment area and can be entered into DHIS-2 to show indicators at the community level. For example, The CHA Monthly Service Report can be used in DHIS-2 to show a spike in the incidents of malaria in children under five in a given catchment area. + +#### Data Use at the CHSS (facility) level { #data-use-at-the-chss-facility-level } + +Each CHSS is responsible for analyzing CHA Forms to make informed decisions and targeted remedial supervision based on findings. For example: if the number of patients treated for malaria is much lower than the number of patients treated for malaria, the CHSS can coach the CHA on the value of routine visits and community education on malaria. Or if the number of home births is high compared to number of facility births the CHSS can coach the CHA to encourage facility delivery. + +The CHSS Monthly Service Report shows the aggregated indicators across all the CHAs, aggregated at the Health Facility level. They use this data to see the status of the communities around health facilities. For example, any maternal death in a CHSS catchment area is investigated. + +#### Data Use at County level { #data-use-at-county-level } + +The M&E Officer is responsible for providing information to various line managers, program supervisors and other stakeholders in the county. CBIS data should be analyzed and used in coordination and other management meetings. For example, the M&E Officer can provide data or help the stakeholders understand the data for the CHA program such as high numbers of diarrhea in certain facilities. + +#### Data Use at Central level { #data-use-at-central-level } + +The Central Level CBIS builds the capacity of the County Teams, training county level M&E staff how to create and run reports. He / She analyzes the data to troubleshoot and strategize for the programs. The data and reports should be accessible to the Ministry of Health and partners to use for decision making at all levels of the health system. + + +\[2\] "Paris Declaration on Aid Effectiveness: Ownership Harmonization, Alignment, Results and Mutual Accountability," in *The Paris Declaration on Aid Effectiveness and the Accra Agenda for Action* (Paris: Organization for Economic Co-operation and Development, n.d.), 4--13, [[http://www.oecd.org/dac/effectiveness/34428351.pdf]{.ul}](http://www.oecd.org/dac/effectiveness/34428351.pdf). + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-android-settings-web-app-md b/projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-android-settings-web-app-md new file mode 100644 index 000000000..1b1e7aa3e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-android-settings-web-app-md @@ -0,0 +1,182 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-android-capture-app/edit/master/docs/src/commonmark/en/content/capture-app/app-android-settings-configuration.md" +--- +# Android Settings Web App { #android-settings-web-app } + +## Visión general { #overview } + +This section focuses on the Android Settings Web App implementation. + +The Android Settings Web App allows admins to configure synchronization parameters for the DHIS2 Android Capture App, encrypt the local database of the android devices, and run tests on the size of data and metadata synchronized by a given android user. The configuration parameters defined within this web app will overwrite the settings of all android devices using the DHIS2 Android Capture App. + +Please note that in this version of the web app, only users with 'ALL' authority are able to define those parameters in the configuration. Other users having access to the web app can see the value of the parameters, but cannot edit them. + + +## General download sync settings { #general-download-sync-settings } + +Includes configurations such as how often the android app will synchronize metadata and data, number of reserved values to download per TEI, and encrypt the device database. + +![](../content/capture-app/resources/images/general-settings.png) + +**Metadata sync:** Admin users can choose how often the metadata will sync. e.g. Sync metadata every 24 hours. + +**Data sync:** Admin users can choose how often the data will sync. e.g. Syncing data every 6 hours. + +**SMS Gateway:** This section allows admin users to edit the SMS gateway phone number. + +**Reserved values:** This will specify the number of reserved values per TEI attribute to download in the devices. + +**Encrypt device database:** + +> **Warning** +> +> This is a critical action and will affect the local database of all android devices synchronizing with the server (it won't affect the server DHIS2 database). +> +> By default the android app database is not encrypted, but an admin can check the *Encrypt device database* to encrypt the metadata and data stored in every device. Encrypting the database will have an impact on the database volume and performance of the android app. Also note that at the moment of selecting or unselecting this option no data is lost (even if it hasn't been previously synchronized with the server) + + +**Disable all settings:** By clicking this button the user will remove all android confiuration settings, so no configuration will be applied to the Android Capture app (if this is the case the sync parameters applied are the ones defined in the Android Capture app). + + +## Program download sync settings { #program-download-sync-settings } + +It allows admin users to specify the sync parameters for Programs. This section has two parts, global and specific settings. + +### Global settings { #global-settings } + +Global settings apply to all programs that an android user has access to. + +![](../content/capture-app/resources/images/program-global-settings.png) + +**TEI to download:** Maximum number of TEIs to download from the server. + +**TEI download period:** It downloads the TEIs that have been updated within a period. e.g. TEIs that have been updated within last month + +**Event to download:** Maximum number of Events to download. + +**Event download period:** It downloads Events which event date belongs to a specific period. + +### Specific settings { #specific-settings } + +This section allows the admin users to specify the behaviour of a particular program/s when syncing the data. The specific configuration overwrites the general settings for the programs listed in this section. To add a setting for a specific program: + +- Click on *Add a Program-specific setting*, a Dialog will appear. +- Bellow "Values per Program" title a user can click and find a list of programs. +- Clicking on a program will show up the different parameters to configure. The number of parameters depends on the program type (with or without registration). + +**Settings for Program Without Registration** + +![](../content/capture-app/resources/images/program-specific-dialog-without_registration.png) + +**Settings for a Program With Registration** + +![](../content/capture-app/resources/images/program-specific-dialog-with_registration.png) + +In the case that any specific settings has been saved, a table will show up a summary with the specific configuration per program, and the options to edit or delete these settings. + +![](../content/capture-app/resources/images/program-specific-table.png) + +### Reset all values { #reset-all-values } + +By clicking on *Reset all values*, the admin user will restore the default settings values of the program section. Please note that in this case it means no specific settings per program. + +To save any configuration, the admin user needs to click on the *Save* button (this button is disabled for the users who doesn't have the 'ALL' authority) + + +## Data set download sync settings { #data-set-download-sync-settings } + +It allows admin users to specify the sync parameters for DataSets. It has two parts. + +### Global settings { #global-settings } + +The first part is for global settings that apply to all data sets an android user has access to. + +![](../content/capture-app/resources/images/dataset-global-settings.png) + +**Number of Periods:** Maximum number of periods to download. + +### Specific Settings { #specific-settings } + +To add a specific setting: + - Click on *Add a Data set specific setting*, the will find a dialog with a list of data sets, + - Click on a data set and this field will be autocompleted with the default value based on the dataset period type. + +![](../content/capture-app/resources/images/dataset-specific-dialog.png) + +![](../content/capture-app/resources/images/dataset-specific-table.png) + + +## User Sync Test { #user-sync-test } + +This section checks the amount of data and metadata a user would sync to his/her device. You can run this test on any user that you have access to. This test shows up the number of organisation units, data sets, program rules, programs, etc. that an android user has access to (so the resoruces that the android app will download) , and the metadata and data download size (approx estimation). Please note that a user doesn't need to have the 'ALL' authority to run this test. + +![](../content/capture-app/resources/images/user-sync-test.png) + +> **Note:** +> +> The values that are highlighted in red, are because the value is considered greater than the maximum recommended value. + + +## Instalación { #installation } + +A user can easily install the Android Settings Web App by logging into the DHIS2 and going to **App Management**. + +- Click on **App Store** +- Go to *Android Settings App* +- Click on *Install V1.0.0* + +![](../content/capture-app/resources/images/app-store-install.png) + + +## Log in and first time setup { #log-in-and-first-time-setup } + +After a user install and launch the Android Settings Web App for the first time, the web app will require to set and save the default values of the configuration. This will apply default settings to all android devices connected to the instance. + +![](../content/capture-app/resources/images/first-time-setup.png) + + +> **Warning** +> +> Only users will 'ALL' authority are able to *save or update* the configuration, but any user will have view access once it's created. + + +![](../content/capture-app/resources/images/first-setup-no-authorities.png) + + +## Enter and save configuration parameters { #enter-and-save-configuration-parameters } + +### Datastore { #datastore } + +Internally all settings are stored in [Datastore](https://docs.dhis2.org/master/en/developer/html/webapi_data_store.html) in JSON format. + +Datastore structure: + +| Item | Descripción | tipo de dato | +| ----------- | ----------- | --------- | +| Namespace | Namespace for organization of entries | Cadena | +| Key | Key for identification of values | Cadena | +| Value | Value holding the information for the entry | JSON | + +### Save configuration parameters { #save-configuration-parameters } + +At the form footer of all settings sections, admin users can find a *Save* button. + +![](../content/capture-app/resources/images/save_button.png) + +Only when an admin user clicks on this button all changes made on the current section are saved on the Datastore. These changes will apply to the Android Capture Apps when they synchronize their configuration. + +**Unsaved changes:** + +In case an admin user wants to go to another section when there are still some unsaved changes, an alert will be displayed before navigating away from the current section. In case the user accepts leaving the page, the unsaved changes will be lost. + +![](../content/capture-app/resources/images/unsaved-changes.png) + +#### Reset all values to default { #reset-all-values-to-default } + +An admin user can restore the settings at any time. There is a *Reset all values to default* button at the form footer of all settings sections. + +![](../content/capture-app/resources/images/reset-default.png) + +The default values will be only restored on Datastore and applied after clicking on *Save*. + + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-md b/projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-md new file mode 100644 index 000000000..31c18ced8 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__CONFIGURING-THE-ANDROID-APP__android-settings-web-app-md @@ -0,0 +1,182 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-android-capture-app/edit/master/docs/src/commonmark/en/content/capture-app/app-android-settings-configuration.md" +--- +# Android Settings Web App { #android-settings-web-app } + +## Visión general { #overview } + +This section focuses on the Android Settings Web App implementation. + +The Android Settings Web App allows admins to configure synchronization parameters for the DHIS2 Android Capture App, encrypt the local database of the android devices, and run tests on the size of data and metadata synchronized by a given android user. The configuration parameters defined within this web app will overwrite the settings of all android devices using the DHIS2 Android Capture App. + +Please note that in this version of the web app, only users with 'ALL' authority are able to define those parameters in the configuration. Other users having access to the web app can see the value of the parameters, but cannot edit them. + + +## General download sync settings { #general-download-sync-settings } + +Includes configurations such as how often the android app will synchronize metadata and data, number of reserved values to download per TEI, and encrypt the device database. + +![](../content/capture-app/resources/images/general-settings.png) + +**Metadata sync:** Admin users can choose how often the metadata will sync. e.g. Sync metadata every 24 hours. + +**Data sync:** Admin users can choose how often the data will sync. e.g. Syncing data every 6 hours. + +**SMS Gateway:** This section allows admin users to edit the SMS gateway phone number. + +**Reserved values:** This will specify the number of reserved values per TEI attribute to download in the devices. + +**Encrypt device database:** + +> **Warning** +> +> This is a critical action and will affect the local database of all android devices synchronizing with the server (it won't affect the server DHIS2 database). +> +> By default the android app database is not encrypted, but an admin can check the *Encrypt device database* to encrypt the metadata and data stored in every device. Encrypting the database will have an impact on the database volume and performance of the android app. Also note that at the moment of selecting or unselecting this option no data is lost (even if it hasn't been previously synchronized with the server) + + +**Disable all settings:** By clicking this button the user will remove all android confiuration settings, so no configuration will be applied to the Android Capture app (if this is the case the sync parameters applied are the ones defined in the Android Capture app). + + +## Program download sync settings { #program-download-sync-settings } + +It allows admin users to specify the sync parameters for Programs. This section has two parts, global and specific settings. + +### Global settings { #global-settings } + +Global settings apply to all programs that an android user has access to. + +![](../content/capture-app/resources/images/program-global-settings.png) + +**TEI to download:** Maximum number of TEIs to download from the server. + +**TEI download period:** It downloads the TEIs that have been updated within a period. e.g. TEIs that have been updated within last month + +**Event to download:** Maximum number of Events to download. + +**Event download period:** It downloads Events which event date belongs to a specific period. + +### Specific settings { #specific-settings } + +This section allows the admin users to specify the behaviour of a particular program/s when syncing the data. The specific configuration overwrites the general settings for the programs listed in this section. To add a setting for a specific program: + +- Click on *Add a Program-specific setting*, a Dialog will appear. +- Bellow "Values per Program" title a user can click and find a list of programs. +- Clicking on a program will show up the different parameters to configure. The number of parameters depends on the program type (with or without registration). + +**Settings for Program Without Registration** + +![](../content/capture-app/resources/images/program-specific-dialog-without_registration.png) + +**Settings for a Program With Registration** + +![](../content/capture-app/resources/images/program-specific-dialog-with_registration.png) + +In the case that any specific settings has been saved, a table will show up a summary with the specific configuration per program, and the options to edit or delete these settings. + +![](../content/capture-app/resources/images/program-specific-table.png) + +### Reset all values { #reset-all-values } + +By clicking on *Reset all values*, the admin user will restore the default settings values of the program section. Please note that in this case it means no specific settings per program. + +To save any configuration, the admin user needs to click on the *Save* button (this button is disabled for the users who doesn't have the 'ALL' authority) + + +## Data set download sync settings { #data-set-download-sync-settings } + +It allows admin users to specify the sync parameters for DataSets. It has two parts. + +### Global settings { #global-settings } + +The first part is for global settings that apply to all data sets an android user has access to. + +![](../content/capture-app/resources/images/dataset-global-settings.png) + +**Number of Periods:** Maximum number of periods to download. + +### Specific Settings { #specific-settings } + +To add a specific setting: + - Click on *Add a Data set specific setting*, the will find a dialog with a list of data sets, + - Click on a data set and this field will be autocompleted with the default value based on the dataset period type. + +![](../content/capture-app/resources/images/dataset-specific-dialog.png) + +![](../content/capture-app/resources/images/dataset-specific-table.png) + + +## User Sync Test { #user-sync-test } + +This section checks the amount of data and metadata a user would sync to his/her device. You can run this test on any user that you have access to. This test shows up the number of organisation units, data sets, program rules, programs, etc. that an android user has access to (so the resoruces that the android app will download) , and the metadata and data download size (approx estimation). Please note that a user doesn't need to have the 'ALL' authority to run this test. + +![](../content/capture-app/resources/images/user-sync-test.png) + +> **Note:** +> +> The values that are highlighted in red, are because the value is considered greater than the maximum recommended value. + + +## Instalación { #installation } + +A user can easily install the Android Settings Web App by logging into the DHIS2 and going to **App Management**. + +- Click on **App Store** +- Go to *Android Settings App* +- Click on *Install V1.0.0* + +![](../content/capture-app/resources/images/app-store-install.png) + + +## Log in and first time setup { #log-in-and-first-time-setup } + +After a user install and launch the Android Settings Web App for the first time, the web app will require to set and save the default values of the configuration. This will apply default settings to all android devices connected to the instance. + +![](../content/capture-app/resources/images/first-time-setup.png) + + +> **Warning** +> +> Only users will 'ALL' authority are able to *save or update* the configuration, but any user will have view access once it's created. + + +![](../content/capture-app/resources/images/first-setup-no-authorities.png) + + +## Enter and save configuration parameters { #enter-and-save-configuration-parameters } + +### Datastore { #datastore } + +Internally all settings are stored in [Datastore](https://docs.dhis2.org/master/en/developer/html/webapi_data_store.html) in JSON format. + +Datastore structure: + +| Item | Descripción | tipo de dato | +| ----------- | ----------- | --------- | +| Namespace | Namespace for organization of entries | Cadena | +| Key | Key for identification of values | Cadena | +| Value | Value holding the information for the entry | JSON | + +### Save configuration parameters { #save-configuration-parameters } + +At the form footer of all settings sections, admin users can find a *Save* button. + +![](../content/capture-app/resources/images/save_button.png) + +Only when an admin user clicks on this button all changes made on the current section are saved on the Datastore. These changes will apply to the Android Capture Apps when they synchronize their configuration. + +**Unsaved changes:** + +In case an admin user wants to go to another section when there are still some unsaved changes, an alert will be displayed before navigating away from the current section. In case the user accepts leaving the page, the unsaved changes will be lost. + +![](../content/capture-app/resources/images/unsaved-changes.png) + +#### Reset all values to default { #reset-all-values-to-default } + +An admin user can restore the settings at any time. There is a *Reset all values to default* button at the form footer of all settings sections. + +![](../content/capture-app/resources/images/reset-default.png) + +The default values will be only restored on Datastore and applied after clicking on *Save*. + + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__AGGREGATE-SYSTEM-DESIGN__indicators-md b/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__AGGREGATE-SYSTEM-DESIGN__indicators-md new file mode 100644 index 000000000..76bea3450 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__AGGREGATE-SYSTEM-DESIGN__indicators-md @@ -0,0 +1,97 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/database_design/indicators.md" +revision_date: '2021-09-15' +tags: +- Implementar +--- + +# Indicators { #indicators } + +This chapter covers the following topics: + + - What is an indicator + + - Purposes of indicators + + - Indicator-driven data collection + + - Managing indicators in DHIS2 + +The following describes these topics in greater detail. + +## What is an indicator? { #what-is-an-indicator } + +In DHIS2, the indicator is a core element of data analysis. An indicator +is a calculated formula based on a combination of data elements, +category options, possibly constants and a factor. There are two foms of +indicators, those with a denominator and those which do not have a +denominator. Calculated totals, which may be composed of multiple data +elements do not have denominators. Coverage indicators (ratios, +percentages, etc) are composed of two formulas of data elements, one +representing the numerator and another representing the denominator. + +Indicators are thus made up of formulas of data elements and other +components and are always multiplied by a factor (e.g. 1, 100, 100, 100 +000). The factor is essentially a number which is multiplied by the +result of the numerator divided by denominator. As a concrete example, +the indicator "BCG coverage <1 year" is defined by a formula with a +factor 100 (in order to obtain a percentage), a numerator ("BCG doses +given to children under 1 year") and a denominator ("Target population +under 1 year"). The indicator "DPT1 to DPT3 drop out rate" is a formula +of 100 % x ("DPT1 doses given"- "DPT3 doses given") / ("DPT1 doses +given"). + + + +Table: Indicator examples + +| Indicador | Formula | Numerador | Denominador | Factor | +|---|---|---|---|---| +| Fully immunized <1 year coverage | Fully immunized/Population < 1 year x 100 | Fully immunized | Population < 1 | 100 (Percentage) | +| Maternal Mortality Rate | Maternal deaths/Live births x 100 000 | Maternal deaths | Live births | 100 000 (MMR is measured per 100 000) | +| Cumulative number of people Enrolled in Care | Cumulative number of people Enrolled in Care x 1 | Cumulative number Enrolled in Care (Male, Age<18) +Cumulative number Enrolled in Care (Male, Age18+) +Cumulative number Enrolled in Care (Female, Age<18) +Cumulative number Enrolled in Care (Female, Age18+) | Ninguno | 1 | + +## Purpose of indicators { #purpose-of-indicators } + +Indicators which are defined with both numerators and denominators are +typically more useful for analysis. Because they are proportions, they +are comparable across time and space, which is very important since +units of analysis and comparison, such as districts, vary in size and +change over time. A district with population of 1000 people may have +fewer cases of a given disease than a district with a population of +10,000. However, the incidence values of a given disease will be +comparable between the two districts because of the use of the +respective populations for each district. + +Indicators thus allow comparison, and are the prime tool for data +analysis. DHIS2 should provide relevant indicators for analysis for all +health programs, not just the raw data. Most report modules in DHIS2 +support both data elements and indicators and you can also combine these +in custom reports. + +## Indicator-driven data collection { #indicator-driven-data-collection } + +Since indicators are more suited for analysis compared to data elements, +the calculation of indicators should be the main driving force for +collection of data. A usual situation is that much data is collected but +never used in any indicator, which significantly reduces the usability +of the data. Either the captured data elements should be included in +indicators used for management or they should probably not be collected +at all. + +For implementation purposes, a list of indicators used for management +should be defined and implemented in DHIS2. For analysis, training +should focus on the use of indicators and why these are better suited +than data elements for this purpose. + +## Managing indicators { #managing-indicators } + +Indicators can be added, deleted, or modified at any time in DHIS2 +without affecting the data. Indicators are not stored as values in +DHIS2, but as formulas, which are calculated whenever the user needs +them. Thus a change in the formulas will only lead to different data +elements being called for when using the indicator for analysis, without +any changes to the underlying data values taking place. For information +how to manage indicators, please refer to the chapter on indicators in +the DHIS2 user documentation. + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__TRACKER-SYSTEM-DESIGN__tracker-analytics-md b/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__TRACKER-SYSTEM-DESIGN__tracker-analytics-md index 3e4776f80..f5ece2221 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__TRACKER-SYSTEM-DESIGN__tracker-analytics-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__TRACKER-SYSTEM-DESIGN__tracker-analytics-md @@ -84,7 +84,7 @@ There are five components of program indicators that define how the value is cal |--- |--- |--- | |1|Unidad Organizativa|For event type it is the org unit of the event. For enrollment type it is enrollment org unit, even if some events in an enrollment were entered elsewhere.| |2|Período|Defined by analytics period boundaries. Depending on the PI type, it defaults to the enrollment date or event date falling between start and end of the reporting period.| -|3|Filter|Create a value filter for the event or enrollment. Include tracked entity instance attribute values, or any data elements within a specific program stage (event type), or any data elements within any program stages. A variety of [functions and variables are available](#program_indicator_functions_variables_operators) for additional operations, like filtering for TEIs where the number of years between the enrollment date and the date of birth is more than 18.| +|3|Filtro|Create a value filter for the event or enrollment. Include tracked entity instance attribute values, or any data elements within a specific program stage (event type), or any data elements within any program stages. A variety of [functions and variables are available](#program_indicator_functions_variables_operators) for additional operations, like filtering for TEIs where the number of years between the enrollment date and the date of birth is more than 18.| |4|Expression|The criteria above define which enrollments (or event) to include. The expression is the value that is applied to each enrollment (or event). Usually it will be event_count, enrollment_count, or tei_count, but can also be a data element value or more complex expression.| |5|Aggregation Type|How to aggregate up the expression applied to each enrollment (or event). Usually “count” or “average”.| diff --git a/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__organisation-units-md b/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__organisation-units-md new file mode 100644 index 000000000..4c7d496d0 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__DATABASE-DESIGN__organisation-units-md @@ -0,0 +1,163 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/database_design/organisation-units.md" +revision_date: '2021-09-15' +tags: +- Implementar +--- + +# Unidades organizativas { #organisation-units } + +In DHIS2 the location of the data, the geographical context, is +represented as organisational units. Organisational units can be either +a health facility or department/sub-unit providing services or an +administrative unit representing a geographical area (e.g. a health +district). + +Organisation units are located within a hierarchy, also referred to as a +tree. The hierarchy will reflect the health administrative structure and +its levels. Typical levels in such a hierarchy are the national, +province, district and facility levels. In DHIS2 there is a single +organisational hierarchy so the way this is defined and mapped to the +reality needs careful consideration. Which geographical areas and levels +are defined in the main organisational hierarchy will have major impact +on the usability and performance of the application. Additionally, there +are ways of addressing alternative hierarchies and levels as explained +in the section called Organisation unit groups and group sets further +down. + +## Organisation unit hierarchy design { #organisation-unit-hierarchy-design } + +The process of designing a sensible organisation unit hierarchy has many +aspects: + + - *Include all reporting health facilities:* All health facilities + which contribute to the national data collection should be included + in the system. Facilities of all kinds of ownership should be + incorporated, including private, public, NGO and faith-oriented + facilities. Often private facilities constitute half of the total + number of facilities in a country and have policies for data + reporting imposed on them, which means that incorporating data from + such facilities are necessary to get realistic, national aggregate + figures. + + - *Emphasize the health administrative hierarchy:* A country typically + has multiple administrative hierarchies which are often not well + coordinated nor harmonized. When considering what to emphasize when + designing the DHIS2 database one should keep in mind what areas are + most interesting and will be most frequently requested for data + analysis. DHIS2 is primarily managing health data and performing + analysis based on the health administrative structure. This implies + that even if adjustments might be made to cater for areas such as + finance and local government, the point of departure for the DHIS2 + organisation unit hierarchy should be the health administrative + areas. + + + + - *Limit the number of organisation unit hierarchy levels:* To cater + for analysis requirements coming from various organisational bodies + such as local government and the treasury, it is tempting to include + all of these areas as organisation units in the DHIS2 database. + However, due to performance considerations one should try to limit + the organisation unit hierarchy levels to the smallest possible + number. The hierarchy is used as the basis for aggregation of data + to be presented in any of the reporting tools, so when producing + aggregate data for the higher levels, the DHIS2 application must + search for and add together data registered for all organisation + units located further down the hierarchy. Increasing the number of + organisation units will hence negatively impact the performance of + the application and an excessively large number might become a + significant problem in that regard. + + In addition, a central part in most of the analysis tools in DHIS2 + is based around dynamically selecting the “parent” organisation unit + of those which are intended to be included. For instance, one would + want to select a province and have the districts belonging to that + province included in the report. If the district level is the most + interesting level from an analysis point of view and several + hierarchy levels exist between this and the province level, this + kind of report will be rendered unusable. When building up the + hierarchy, one should focus on the levels that will be used + frequently in reports and data analysis and leave out levels that + are rarely or never used as this will have an impact on both the + performance and usability of the application. + + - *Avoid one-to-one relationships:* Another guiding principle for + designing the hierarchy is to avoid connecting levels that have near + one-to-one parent-child ratios, meaning that for instance a district + (parent) should have on average more than one local council (child) + at the level below before it make sense to add a local council level + to the hierarchy. Parent-child ratios from 1:4 or more are much more + useful for data analysis purposes as one can start to look at e.g. + how a district’s data is distributed in the different sub-areas and + how these vary. Such drill-down exercises are not very useful when + the level below has the same target population and the same serving + health facilities as the parent. + + Skipping geographical levels when mapping the reality to the DHIS2 + organisation unit hierarchy can be difficult and can easily lead to + resistance among certain stakeholders, but one should have in mind + that there are actually ways of producing reports based on + geographical levels that are not part of the organisational + hierarchy in DHIS2, as will be explained in the next section. + +## Organisation unit groups and group sets { #organisation-unit-groups-and-group-sets } + +In DHIS2, organisation units can be grouped in organisation unit groups, +and these groups can be further organised into group sets. Together they +can mimic an alternative organisational hierarchy which can be used when +creating reports and other data output. In addition to representing +alternative geographical locations not part of the main hierarchy, these +groups are useful for assigning classification schemes to health +facilities, e.g. based on the type or ownership of the facilities. Any +number of group sets and groups can be defined in the application +through the user interface, and all these are defined locally for each +DHIS2 database. + +An example illustrates this best: Typically one would want to provide +analysis based on the ownership of the facilities. In that case one +would create a group for each ownership type, for instance “MoH”, +“Private” and “NGO”. All facilities in the database must then be +classified and assigned to one and only one of these three groups. Next +one would create a group set called “Ownership” to which the three +groups above are assigned, as illustrated in the figure +below. + +![](resources/images/organisation_unit_hiearchy.png) + +In a similar way one can create a group set for an additional +administrative level, e.g. local councils. All local councils must be +defined as organisation unit groups and then assigned to a group set +called “Local Council”. The final step is then to assign all health +facilities to one and only one of the local council groups. This enables +the DHIS2 to produce aggregate reports by each local council (adding +together data for all assigned health facilities) without having to +include the local council level in the main organisational hierarchy. +The same approach can be followed for any additional administrative or +geographical level that is needed, with one group set per additional +level. Before going ahead and designing this in DHIS2, a mapping between +the areas of the additional geographical level and the health facilities +in each area is needed. + +A key property of the group set concept in DHIS2 to understand is +*exclusivity*, which implies that an organisation unit can be member of +exactly one of the groups in a group set. A violation of this rule would +lead to duplication of data when aggregating health facility data by the +different groups, as a facility assigned to two groups in the same group +set would be counted twice. + +With this structure in place, DHIS2 can provide aggregated data for each +of the organisation unit ownership types through the “Organisation unit +group set report” in “Reporting” module or through the Excel pivot table +third-party tool. For instance one can view and compare utilisation +rates aggregated by the different types of ownership (e.g. MoH, Private, +NGO). In addition, DHIS2 can provide statistics of the distribution of +facilities in “Organisation unit distribution report” in “Reporting” +module. For instance one can view how many facilities exist under any +given organisation unit in the hierarchy for each of the various +ownership types. In the GIS module, given that health facility +coordinates have been registered in the system, one can view the +locations of the different types of health facilities (with different +symbols for each type), and also combine this information with another +map layer showing indicators e.g. by district. + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md index 6ae08470d..f92bfd9b9 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2-metadata/AH_EBS/blob/master/docs/ah_ebs-design.md" -revision_date: '2024-06-05' +revision_date: '2024-07-01' tags: - Implementar --- @@ -100,7 +100,7 @@ The tracker program structure is as follows, favoring simplicity in the number o | Laboratory | The stage collects information on the laboratory that is analysing the sample, sample identification and test details. A unique lab ID is included in this stage to allow the linkage of samples and results. **The stage is repeatable** because multiple samples can be taken, and multiple lab tests and results can be available for a given sample. | | Measures and treatment | The stage collects information on the treatment provided in the health event and the control measures implemented. **The stage is non-repeatable** as it is intended to include all response measures provided for the animal health event. | -### Tipo de entidad Tracked { #tracked-entity-type } +### Tipo de entidad Tracked { #tracked-entity-type } The DHIS2 Animal Health surveillance tracker program allows for the enrollment of a tracked entity type (TET) ‘Health event’. We have made this conceptualization based on CDC’s definition and the overall flow of the early wearing system. In this context, an event is a manifestation of disease or an occurrence that creates a potential for disease, which can include infectious, zoonotic, food safety, chemical, radiological, or nuclear in origin and may be transmitted by persons, vectors, animals, goods, or through the environment [CDC](https://www.cdc.gov/globalhealth/healthprotection/gddopscenter/event-based-surveillance.html). @@ -220,18 +220,18 @@ All data elements configured for the Tracker domain are also included in the Dat Within the program stages for ‘Epidemiology’ and ‘Measures and treatment’, there are a number of data elements that are cloned to allow the selection of multiple options for a given concept, sharing the same option set. This design is implemented as follows: -- Cloning of data elements eligible for multi-option choice -- The number of clone of the data element must be the same as the number of options present in the related option set -- Each cloned data element has its own UID, name and code +- Clonación de elementos de datos elegibles para elección de opciones múltiples +- El número de clones del elemento de datos debe ser el mismo que el número de opciones presentes en el set de opciones relacionado +- Cada elemento de datos clonado tiene su propio UID, nombre y código - Reglas de programa -- Hide the consequent Data Elements if the previous have not been selected -- Show error in case the same Option has been selected more than once in the same group of Data Elements +- Ocultar los elementos de datos consecuentes si los anteriores no han sido seleccionados +- Mostrar error en caso de que la misma Opción haya sido seleccionada más de una vez en el mismo grupo de Elementos de Datos ![Multi-select](resources/images/multioption_selection.gif) ## Analytics { #analytics } -An animal surveillance dashboard has been developed based on experience gathered from countries implementations and reports used by international actors such as FAO and WOAH. Dashboards are primarily represented using program indicators, which have been configured to aggregate numbers based on conditions recorded in the tracker program. +An animal surveillance [dashboard](https://demos.dhis2.org/hmis/dhis-web-dashboard/#/FHh9NTsTjQY) has been developed based on experience gathered from countries implementations and reports used by international actors such as FAO and WOAH. Dashboards are primarily represented using program indicators, which have been configured to aggregate numbers based on conditions recorded in the tracker program. ### Summary of events, cases, deaths reported by time and geographical distribution { #summary-of-events-cases-deaths-reported-by-time-and-geographical-distribution } @@ -249,13 +249,13 @@ An animal surveillance dashboard has been developed based on experience gathered ![dashboard3](resources/images/dashboard_3.png) -## User Groups { #user-groups } +## Grupos de Usuarios { #user-groups } The following user groups are included in the downloadable metadata file: -| **User group** | **Metadata** | **Data** | +| **User group** | **Metadatos** | **Data** | | --------------------- | ----------------- | -------------------- | -| AH_EBS - Admin | Puede editar y visualizar | No Access | +| AH_EBS - Admin | Puede editar y visualizar | Sin acceso | | AH_EBS - Access | Solo lectura | Solo lectura | | AH_EBS - Data Capture | Solo lectura | Puede capturar y visualizar | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__installation-md index 585234106..c2d656aa6 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__installation-md @@ -9,11 +9,11 @@ tags: Package Version 1.0.0 -System default language: English +Idioma predeterminado del sistema: Inglés ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -23,17 +23,17 @@ Installation of the module consists of several steps: It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](http://dhis2.org/documentation). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section [Importing a metadata file into DHIS2](#importing-metadata) -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension (if applicable) { #default-data-dimension-if-applicable } @@ -41,79 +41,79 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:----------------------------|:------------|:----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into , the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. **_Note that this search and replace operation must be done with a plain text editor_**, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-----------|:------------|:-------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | -| Numerator only (number) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| +| Sólo numerador (número) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| -### Tipo de entidad Tracked { #tracked-entity-type } +### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-------|:------------|:-------------------------------------------------------| | Health Event | DnxQe1mgmlp | `../api/trackedEntityTypes.json?filter=name:eq:Event` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. Some visualizations and maps may contain references to organisation unit levels. Maps that consist of several map views may contain various Organisation unit level references based on the configuration of the map layer. Adjust the organisation unit level references in the metadata json file to match the organisation unit structure in the target instance before importing the metadata file. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/master/en/user/html/import_export.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } > NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to conflict with. Follow the instructions to import the metadata then please proceed to the “[Configuration](#configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -126,46 +126,46 @@ A metadata package usually contains several user groups: By default, the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | AH_EBS - Access | AH_EBS - Admin | AH_EBS - Data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/master/en/dhis2_user_manual_en/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. ## Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__adolescant-health-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__adolescant-health-md new file mode 100644 index 000000000..af57302c5 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__adolescant-health-md @@ -0,0 +1,334 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_ah-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Adolescent Health { #chis-agg-ah-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Adolescent Health (AH) module includes: + +1. A **monthly dataset** with key data elements for adolescent health +2. A **yearly dataset** for the follow up of key annual information on adolescent health +3. **Core indicators** for both datasets +4. A predefined **“CH - Adolescent Health” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +## 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the AH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the AH module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH027a - Adolescents seeking FP services | Adolescents and young people seeking family planning services from CHW | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH027b - Adolescents seeking FP methods tested for HIV | Adolescents and young people seeking family planning services who were tested for HIV by CHW | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH041a - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/ MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041b - People with possible MNS symptoms | People with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041c - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/mental health conditions by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041d - People with possible MNS symptoms | People with possible symptoms of MNS conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041e - Women assessed for MNS disorders/ MH conditions | Women and adolescent girls assessed for MNS disorders / MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041f - Women with possible MNS symptoms | Women and adolescent girls with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042a - People with MNS disorders referred | People with MNS disorders referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042b - People with MNS disorders referred by type | People with MNS disorders referred by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042c - Women with MNS disorders referred | Women and adolescent girls with MNS disorders/mental health conditions referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH060a - People receiving deworming preventive chemotherapy | People receiving a dose of preventive chemotherapy for deworming | CH - Adolescent Health (Monthly), CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Adolescent Health, CH - Nutrition, CH - Child Health | +| CH060b - People targeted for deworming preventive chemotherapy | People targeted for preventive chemotherapy for deworming | CH - Adolescent Health (Monthly), CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Adolescent Health, CH - Nutrition, CH - Child Health | +| CH060c - People receiving deworming preventive chemotherapy | People receiving a dose of preventive chemotherapy for deworming by drug | CH - Adolescent Health (Monthly), CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Adolescent Health, CH - Nutrition, CH - Child Health | +| CH092a - People with suicidal ideation or plan | People with suicidal ideation or plan | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH092b - People assessed for suicidal ideation or plan | People assessed for suicidal ideation or plan | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH093a - People who reported attempting suicide | People who reported attempting suicide | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH093b - People assessed for attempting suicide | People assessed for attempting suicide | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH028a - HIV positive tests returned | HIV tests conducted in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028b - HIV tests returned | HIV tests returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028c - HIV positive tests returned to key population | HIV tests conducted amongst key population in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028d - HIV tests returned to key population | HIV tests performed amongst key population where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028e - HIV positive tests returned to TB patients | HIV tests conducted amongst TB in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028f - HIV tests returned to TB patients | HIV tests performed amongst TB where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH043a - People with MNS disorders receiving services | People with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043b - People assessed for MNS disorders | People assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043c - People with MNS disorders receiving services - MH awareness | People with MNS disorders/mental health conditions receiving services - mental health awareness | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043d - People with MNS disorders receiving services - MH HP | People with MNS disorders/mental health conditions receiving services - mental health promotion and prevention | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043e - People with MNS disorders receiving services - MH support | People with MNS disorders/mental health conditions receiving services - support for people with mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043f - People with MNS disorders receiving services - recovery/rehab | People with MNS disorders/mental health conditions receiving services - recovery and rehabilitation | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043g - Women with MNS disorders receiving services | Women and adolescent girls with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043h - Women assessed for MNS disorders | Women and adolescent girls assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH069a - Children (5-19 y) overweight and obese | Children and adolescents aged 5-19 years who are overweight | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH069b - Children (5-19 y) weighted | Children and adolescents aged 5-19 years who were measured | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH082 - Young adolescent deaths (10-14 years old) | Young adolescent deaths (10-14 years old) | CH - Adolescent Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Adolescent Health | +| CH083 - Older adolescent deaths (15-19 years) | Older adolescent deaths (15-19 years) | CH - Adolescent Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Adolescent Health | +| CH084a - Women receiving anaemia-preventing iron supplements | Adolescent girls and menstruating women who received anaemia-preventing iron supplements | CH - Adolescent Health (Yearly), CH - Nutrition (Yearly) | CH - Nutrition, CH - Adolescent Health | +| CH084b - Consultations with adolescent girls and menstruating women | Number of menstruating women and young adolescent girls who have received a consultation | CH - Adolescent Health (Yearly), CH - Nutrition (Yearly) | CH - Nutrition, CH - Adolescent Health | +| CH085a - Women underweight | Non-pregnant women and adolescent girls with low BMI | CH - Adolescent Health (Yearly), CH - Nutrition (Yearly) | CH - Nutrition, CH - Adolescent Health | +| CH085b - Consultations with non-pregnant women | Consultations non-pregnant women and adolescent girls | CH - Adolescent Health (Yearly), CH - Nutrition (Yearly) | CH - Nutrition, CH - Adolescent Health | +| CH086 - Adolescents with insufficient physical activity | Adolescents with insufficient physical activity | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087a - Adolescent current tobacco users - smoked | Adolescent current tobacco users - smoked | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087b - Adolescent current tobacco users - smokeless | Adolescent current tobacco users - smokeless | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087c - Adolescent current tobacco users - daily users | Adolescent current tobacco users - daily users | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087d - Adolescent current tobacco users - non-daily users | Adolescent current tobacco users - non-daily users | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH088a - People reporting using alcohol | People reporting using alcohol | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH088b - People assessed for alcohol use | People assessed for alcohol use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH088c - Women reporting using alcohol | Women and adolescent girls reported using alcohol | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH088d - Women assessed for alcohol use | Women and adolescent girls assessed for alcohol use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH089a - People with heavy episodic drinking | People with heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089b - People assessed for heavy episodic drinking | People assessed for heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089c - Women with heavy episodic drinking | Women and adolescent girls with heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089d - Women assessed for heavy episodic drinking | Women and adolescent girls assessed for heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH090a - People reporting use of any psychoactive drugs | People reporting use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090b - People assessed for use of any psychoactive drugs | People assessed for use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090c - People reporting the use of psychoactive drugs | People who report use of any psychoactive drugs by type | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090d - Women reporting use of any psychoactive drugs | Women and adolescent girls who use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090e - Women assessed for use of any psychoactive drugs | Women and adolescent girls assessed for use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091a - People reporting use of injection drugs | People reporting use of injection drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091b - People assessed for injection drug use | People assessed for injection drug use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091c - Women reporting use of injection drugs | Women and adolescent girls injecting drug use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091d - Women assessed for injection drug use | Women and adolescent girls assessed for injecting drug use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH094a - Leisure screen time during the week | Amount of time usually spent on a typical weekday dedicated to screen time for leisure activities | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH094b - Leisure screen time during the weekend | Amount of time usually spent on a typical weekend day dedicated to screen time for leisure activities | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH094c - People assessed on leisure screen time | People assessed on screen time for leisure activities | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +## 2. Datasets Details { #2-datasets-details } + +### 2.1. Monthly Adolescent Health Dataset { #21-monthly-adolescent-health-dataset } + +In both the monthly and the yearly datasets the category combinations for the age groups have age groups that go beyond the [WHO definition of adolescents](https://www.who.int/southeastasia/health-topics/adolescent-health) “WHO defines 'Adolescents' as individuals in the 10-19 years age group and 'Youth' as the 15-24 year age group. While 'Young People' covers the age range 10-24 years” , and the definition of adolescent reported in the [CHIS guidelines](https://www.healthdatacollaborative.org/fileadmin/uploads/hdc/Documents/Working_Groups/Community_Data/210128_UNICEF_NY_Community_Health_Workers_Guidance_EN.pdf) “Adolescents are defined as persons aged 10–19 years. Young adolescent refers to 10–14-year-olds, while older adolescent refers to 15–19-year-olds”.This has been done to avoid creating ad hoc age groups for each and every dataset. The age groups above the definition of Adolescent/Youth have been greyed-out and therefore blocked for data entry. Countries should nonetheless edit and apply the age categories that better reflect the local context and guidelines. + +#### 2.1.1. Family Planning { #211-family-planning } + +The section is set to collect the total number of adolescents and young people seeking family planning methods by age groups (10-14y, 15-19y). + +![Family planning](resources/images/chis-ado-m-001.png) + +#### 2.1.2. Family Planning & HIV Testing { #212-family-planning-hiv-testing } + +The section is set to collect the total number of adolescents tested for HIV (by age groups - 10-14y, 15-19y-) and the results of the test (positive, negative, indeterminate). + +![Family planning HIV test](resources/images/chis-ado-m-001b.png) + +#### 2.1.3. Deworming { #213-deworming } + +The first part of the section is set to give an overview of the target population for the activity (by age groups -10-14y, 15-19y and unknown age - and by sex - male, female, other, unknown sex -) and the number of reached people (same disaggregation). The second part of the section divides the reached people by type of preventive chemotherapy (Albendazole and Mebendazole). The used drugs can be adapted locally based on availability and national guidelines. + +![Deworming chemotherapy](resources/images/chis-ado-m-002.png) + +#### 2.1.4. Mental Health Disorders and Conditions - All { #214-mental-health-disorders-and-conditions-all } + +The section focuses on all adolescents by age groups (10-14y and 15-19y) and sex (male, female, other, unknown sex). + +![MNS Disorders](resources/images/chis-ado-m-003.png) + +#### 2.1.5. Mental Health Disorders and Conditions - By Type { #215-mental-health-disorders-and-conditions-by-type } + +The table separates the total number of assessments, the number of people with potential MH conditions, and the number of referrals of the first by type of mental health disorder/conditions (Depression, psychoses, child and adolescent mental and behavioural conditions, dementia, substance use, suicide/self harm). + +![MNS Disorders by type](resources/images/chis-ado-m-003b.png) + +#### 2.1.6. Mental Health Disorders and Conditions - Pregnant and Postpartum { #216-mental-health-disorders-and-conditions-pregnant-and-postpartum } + +The table collects data on the MH assessments carried among pregnant and postpartum women. + +![MNS Disorders Pregnancy Postpartum](resources/images/chis-ado-m-003c.png) + +#### 2.1.7. Suicide Attempts { #217-suicide-attempts } + +The section provides an overview on the beneficiaries at risk of suicide and of suicide preventive and reactive assessments by age groups (10-14y and 15-19y) and sex (male, female, other, unknown sex). + +![Suicide attempts](resources/images/chis-ado-m-004.png) + +### 2.2. Yearly Adolescent Health Dataset { #22-yearly-adolescent-health-dataset } + +#### 2.2.1. HIV Tests - All { #221-hiv-tests-all } + +The section reports core information on HIV-related activities. +The table gives an overview of the number of performed tests and positive results among all people tested and this disaggregated by age groups (10-14y, 15-19y, unknown age) and sex (male, female, other, unknonw sex). + +![HIV Tests - All](resources/images/chis-ado-y-001.png) + +#### 2.2.2. HIV Tests - TB Cases { #222-hiv-tests-tb-cases } + +The table gives the information among TB-confirmed and -presumptive patients. + +![HIV tests - TB case](resources/images/chis-ado-y-001b.png) + +#### 2.2.3. HIV Tests - Key Population { #223-hiv-tests-key-population } + +The table captures data for the key population groups at risk (MSM, SW, Prisoners, IDU, TG, Other). The categories should be adapted locally to better mirror the contexts and the activities. + +![HIV tests - Key Population](resources/images/chis-ado-y-001c.png) + +#### 2.2.4. Death { #224-death } + +The section provides a very simple overview of the number of deaths by sex ( male, female, other, unknonw sex) among adolescents. + +![Death](resources/images/chis-ado-y-002.png) + +#### 2.2.5. Iron Supplement { #225-iron-supplement } + +The section provides a simple overview of the iron supplement for adolescent girls activities conducted in the community by age group (10-14y and 15-19y). + +![Iron supplement](resources/images/chis-ado-y-003.png) + +#### 2.2.6. Body Weight and BMI { #226-body-weight-and-bmi } + +The section collects data on the two ends of the spectrum among measured adolescents: those with high BMI and those with low BMI by age group (10-14y, 15-17y, 18-19y, unknown age). + +![Body weight - BMI](resources/images/chis-ado-y-004.png) + +#### 2.2.7. Physical Activity and Screen Time { #227-physical-activity-and-screen-time } + +The section provides information on the time spent during the week and weekend in front of the screen and the level of physical activity of the screened adolescents by age (10-14y and 15-19y, unknown age) and by sex (male, female, other, unknown sex). + +![Physical activity and screen time](resources/images/chis-ado-y-005.png) + +#### 2.2.8. Tobacco Use { #228-tobacco-use } + +This section shows the patterns of tobacco use among the targeted adolescent population in the community by age (10-14y and 15-19y, unknown age) and by sex (male, female, other, unknown sex). + +![Tobacco use](resources/images/chis-ado-y-006.png) + +#### 2.2.9. Alcohol Use - All { #229-alcohol-use-all } + +The section provides specific information on the use of alcohol among adolescents by age (10-14y and 15-19y, unknown age) and by sex (male, female, other, unknown sex). + +![Alcohol use - all](resources/images/chis-ado-y-007.png) + +#### 2.2.10. Alcohol Use - All { #2210-alcohol-use-all } + +The table further categorises the information on alcohol use among adolescent girls by pregnancy status (pregnant or postpartum). + +![Alcohol use - all B](resources/images/chis-ado-y-007b.png) + +#### 2.2.11. Drug Use- All { #2211-drug-use-all } + +The table collects the information for all adolescent drug users by age groups (10-14y and 15-19y) and sex (male, female, other, unknown sex) + +![Drug use - all](resources/images/chis-ado-y-008.png) + +#### 2.2.12. Drug Use- By Type { #2212-drug-use-by-type } + +The table disaggregates the users by type of the abused substance (Cannabis, opioids, cocaine, amphetamine-type stimulants). + +![Drug use - by type](resources/images/chis-ado-y-008b.png) + +#### 2.2.13. Drug Use- By Type { #2213-drug-use-by-type } + +The table further categorises the data on adolescent drug users by pregnant or postpartum. + +![Drug use - by type C](resources/images/chis-ado-y-008c.png) + +#### 2.2.14. Mental Health Disorders and Conditions - All { #2214-mental-health-disorders-and-conditions-all } + +The table collects the information on all the adolescents assessed for their MH status by age groups (10-14y and 15-19y) and sex (male, female, other, unknown sex). + +![MNS Disorders - conditions - all](resources/images/chis-ado-y-009.png) + +#### 2.2.15. Mental Health Disorders and Conditions - Pregnant and Postpartum { #2215-mental-health-disorders-and-conditions-pregnant-and-postpartum } + +The table collects the relevant data for the MH evaluations among pregnant and postpartum adolescent girls. + +![MNS Disorders - pregnant and postpartum](resources/images/chis-ado-y-009b.png) + +#### 2.2.16. Mental Health Disorders and Conditions - Awareness and Support { #2216-mental-health-disorders-and-conditions-awareness-and-support } + +The section collects the totals on people with MNS disorders and which of services and/supports they have received in the community. + +![MNS Disorders - awareness and support](resources/images/chis-ado-y-009c.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Adolescent health datasets: + +| name | instruction | operator | leftSide description | rightSide description | +|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|---------------------------------------------------| +| CH - AG and menstruating women who received Vs Consultations with AG and menstruating women | AG and menstruating women who received should be less than or equal to Consultations with AG and menstruating women | menor_que_o_igual_que | AG and menstruating women who received | Consultations with AG and menstruating women | +| CH - AGW assessed for heavy episodic drinking Vs People assessed for heavy episodic drinking | AGW assessed for heavy episodic drinking should be less than or equal to People assessed for heavy episodic drinking | menor_que_o_igual_que | AGW assessed for heavy episodic drinking | People assessed for heavy episodic drinking | +| CH - AGW assessed for injecting drug use Vs People assessed for injecting drug use | AGW assessed for injecting drug use should be less than or equal to People assessed for injecting drug use | menor_que_o_igual_que | AGW assessed for injecting drug use | People assessed for injecting drug use | +| CH - AGW assessed for MNS disorders Vs AGW with a possible MNS symptoms | AGW assessed for MNS disorders should be less than or equal to AGW with a possible MNS symptoms | menor_que_o_igual_que | AGW assessed for MNS disorders | AGW with a possible MNS symptoms | +| CH - AGW assessed for use of any psychoactive drugs Vs People assessed for use of any psychoactive drugs | AGW assessed for use of any psychoactive drugs should be less than or equal to People assessed for use of any psychoactive drugs | menor_que_o_igual_que | AGW assessed for use of any psychoactive drugs | People assessed for use of any psychoactive drugs | +| CH - AGW who use of any psychoactive drugs Vs People who report use of any psychoactive drugs | AGW who use of any psychoactive drugs should be less than or equal to People who report use of any psychoactive drugs | menor_que_o_igual_que | AGW who use of any psychoactive drugs | People who report use of any psychoactive drugs | +| CH - AGW with heavy episodic drinking Vs People with heavy episodic drinking | AGW with heavy episodic drinking should be less than or equal to People with heavy episodic drinking | menor_que_o_igual_que | AGW with heavy episodic drinking | People with heavy episodic drinking | +| CH - AGW with MNS disorders/receiving Vs AGW assessed for MNS MH disorders | AGW with MNS disorders/receiving should be less than or equal to AGW assessed for MNS MH disorders | menor_que_o_igual_que | AGW with MNS disorders/receiving | AGW assessed for MNS MH disorders | +| CH - AGW with MNS disorders/receiving Vs People with MNS disorders/receiving | AGW with MNS disorders/receiving should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | AGW with MNS disorders/receiving | People with MNS disorders/receiving | +| CH - Assessed for MNS disorders conditions by type Vs People with a possible MNS symptoms by type | Assessed for MNS disorders conditions by type should be less than or equal to People with a possible MNS symptoms by type | menor_que_o_igual_que | Assessed for MNS disorders conditions by type | People with a possible MNS symptoms by type | +| CH - AYP seeking FP services tested for HIV by CHW Vs AYP seeking family planning services from CHW | AYP seeking FP services tested for HIV by CHW should be less than or equal to AYP seeking family planning services from CHW | menor_que_o_igual_que | AYP seeking FP services tested for HIV by CHW | AYP seeking family planning services from CHW | +| CH - Children and adolescents 5-19 years overweight Vs Children and adolescents 5-19 years measured | Children and adolescents 5-19 years overweight should be less than or equal to Children and adolescents 5-19 years measured | menor_que_o_igual_que | Children and adolescents 5-19 years overweight | Children and adolescents 5-19 years measured | +| CH - HIV tests performed amongst KP & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst KP & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst KP & results returned | HIV tests performed where results were returned | +| CH - HIV tests performed amongst TB & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst TB & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst TB & results returned | HIV tests performed where results were returned | +| CH - MNS disorders receiving - recovery & rehab Vs People with MNS disorders/receiving | MNS disorders receiving - recovery & rehab should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - recovery & rehab | People with MNS disorders/receiving | +| CH - MNS disorders receiving - support for MH Vs People with MNS disorders/receiving | MNS disorders receiving - support for MH should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - support for MH | People with MNS disorders/receiving | +| CH - New HIV-positive result or diagnosis was returned Vs HIV tests performed where results were returned | New HIV-positive result or diagnosis was returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | +| CH - New HIV-positive result returned for KP Vs HIV tests performed amongst KP & results returned | New HIV-positive result returned for KP should be less than or equal to HIV tests performed amongst KP & results returned | menor_que_o_igual_que | New HIV-positive result returned for KP | HIV tests performed amongst KP & results returned | +| CH - New HIV-positive result returned for KP Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for KP should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for KP | New HIV-positive result or diagnosis was returned | +| CH - New HIV-positive result returned for TB Vs HIV tests performed amongst TB & results returned | New HIV-positive result returned for TB should be less than or equal to HIV tests performed amongst TB & results returned | menor_que_o_igual_que | New HIV-positive result returned for TB | HIV tests performed amongst TB & results returned | +| CH - New HIV-positive result returned for TB Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for TB should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for TB | New HIV-positive result or diagnosis was returned | +| CH - Non-pregnant AGW with low BMI Vs Consultations non-pregnant AGW | Non-pregnant AGW with low BMI should be less than or equal to Consultations non-pregnant AGW | menor_que_o_igual_que | Non-pregnant AGW with low BMI | Consultations non-pregnant AGW | +| CH - People assessed for MNS disorders conditions Vs Assessed for MNS disorders conditions by type | People assessed for MNS disorders conditions should be less than or equal to Assessed for MNS disorders conditions by type | menor_que_o_igual_que | People assessed for MNS disorders conditions | Assessed for MNS disorders conditions by type | +| CH - People assessed for MNS disorders conditions Vs People with a possible MNS symptoms | People assessed for MNS disorders conditions should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People assessed for MNS disorders conditions | People with a possible MNS symptoms | +| CH - People reported using alcohol Vs Number people assessed for alcohol use | People reported using alcohol should be less than or equal to Number people assessed for alcohol use | menor_que_o_igual_que | People reported using alcohol | Number people assessed for alcohol use | +| CH - People who reported attempting suicide Vs People assessed for attempting suicide | People who reported attempting suicide should be less than or equal to People assessed for attempting suicide | menor_que_o_igual_que | People who reported attempting suicide | People assessed for attempting suicide | +| CH - People who report injecting drug use Vs People assessed for injecting drug use | People who report injecting drug use should be less than or equal to People assessed for injecting drug use | menor_que_o_igual_que | People who report injecting drug use | People assessed for injecting drug use | +| CH - People who report use of any psychoactive drugs Vs People assessed for use of any psychoactive drugs | People who report use of any psychoactive drugs should be less than or equal to People assessed for use of any psychoactive drugs | menor_que_o_igual_que | People who report use of any psychoactive drugs | People assessed for use of any psychoactive drugs | +| CH - People with a possible MNS symptoms by type Vs People with a possible MNS symptoms | People with a possible MNS symptoms by type should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People with a possible MNS symptoms by type | People with a possible MNS symptoms | +| CH - People with heavy episodic drinking Vs People assessed for heavy episodic drinking | People with heavy episodic drinking should be less than or equal to People assessed for heavy episodic drinking | menor_que_o_igual_que | People with heavy episodic drinking | People assessed for heavy episodic drinking | +| CH - People with MNS disorders - MH promotion and prev Vs People with MNS disorders/receiving | People with MNS disorders - MH promotion and prev should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders - MH promotion and prev | People with MNS disorders/receiving | +| CH - People with MNS disorders receiving - MH awareness Vs People with MNS disorders/receiving | People with MNS disorders receiving - MH awareness should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders receiving - MH awareness | People with MNS disorders/receiving | +| CH - People with MNS disorders/receiving Vs People assessed for MNS disorders | People with MNS disorders/receiving should be less than or equal to People assessed for MNS disorders | menor_que_o_igual_que | People with MNS disorders/receiving | People assessed for MNS disorders | +| CH - People with MNS disorders referred Vs People assessed for MNS disorders conditions | People with MNS disorders referred should be less than or equal to People assessed for MNS disorders conditions | menor_que_o_igual_que | People with MNS disorders referred | People assessed for MNS disorders conditions | +| CH - People with suicidal ideation or plan Vs People assessed for suicidal ideation or plan | People with suicidal ideation or plan should be less than or equal to People assessed for suicidal ideation or plan | menor_que_o_igual_que | People with suicidal ideation or plan | People assessed for suicidal ideation or plan | +| CH - Receiving a dose of PC for deworming by drug Vs Receiving a dose of PC for deworming | Receiving a dose of PC for deworming by drug should be less than or equal to Receiving a dose of PC for deworming | menor_que_o_igual_que | Receiving a dose of PC for deworming by drug | Receiving a dose of PC for deworming | +| CH - Receiving a dose of PC for deworming Vs People targeted for PC for deworming | Receiving a dose of PC for deworming should be less than or equal to People targeted for PC for deworming | menor_que_o_igual_que | Receiving a dose of PC for deworming | People targeted for PC for deworming | +| CH - Reported use of any psychoactive drugs type Vs People who report use of any psychoactive drugs | Reported use of any psychoactive drugs type should be less than or equal to People who report use of any psychoactive drugs | menor_que_o_igual_que | Reported use of any psychoactive drugs type | People who report use of any psychoactive drugs | +| CH - Women and adolescent girls injecting drug use Vs People who report injecting drug use | Women and adolescent girls injecting drug use should be less than or equal to People who report injecting drug use | menor_que_o_igual_que | Women and adolescent girls injecting drug use | People who report injecting drug use | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the AH indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH027 - Adolescents seeking FP methods | Number of adolescents and young people seeking contraception/family planning who received an HIV test | AYP seeking FP services | 1 | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH027 - Adolescents seeking FP methods tested for HIV (%) | Proportion of adolescents and young people seeking contraception/family planning who received an HIV test | AYP seeking FP services tested for HIV by CHW | AYP seeking family planning services from CHW | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH028a - HIV tests with returned results | Number of HIV tests conducted and results returned | HIV tests performed where results were returned | 1 | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH028b - HIV +ve tests returned to people (%) | Proportion of HIV tests performed that were positive and results returned to people | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH041m - Women assessed for MNS disorders | Number of Women assessed for mental, neurological and substance use (MNS) disorders | Women assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH041 - People assessed for MNS disorders | Number of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health | +| CH041 - People assessed for MNS disorders (%) | Proportion of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | People with a possible MNS symptoms | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042b - Women referred for MNS disorders (%) | Proportion of Women with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | Women assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042 - People referred for MNS disorders (%) | Proportion of people with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH043 - People with MNS disorders receiving services (%) | Proportion of people with mental, neurologic and substance use (MNS) disorders receiving services | People with MNS disorders/receiving | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH060 - People receiving deworming preventive chemotherapy (%) | Proportion of people receiving preventive chemotherapy for deworming | Receiving a dose of PC for deworming | People targeted for PC for deworming | CH - Nutrition, CH - Child Health, CH - Adolescent Health | +| CH069 - Overweight and obese children (5-19 y) (%) | Proportion of overweight and obesity in school-age children and adolescents 5-19 years | Children and adolescents 5-19 years overweight | Children and adolescents 5-19 years measured | CH - Nutrition, CH - Child Health, CH - Adolescent Health, CH - Noncommunicable diseases | +| CH082 - Young adolescent deaths (10-14 years old) | Number of new young adolescent deaths (10-14 years old) | New young adolescent aged 10-14 years deaths | 1 | CH - Adolescent Health, CH - Civil registration and vital statistics | +| CH083 - Older adolescent deaths (15-19 years) | Number of new older adolescent deaths (15-19 years) | New older adolescent aged 15-19 years deaths | 1 | CH - Adolescent Health, CH - Civil registration and vital statistics | +| CH084 - Women receiving anaemia-preventing iron supplements (%) | Proportion of adolescent girls and women of reproductive age given iron-containing supplements for anaemia prevention | AG and menstruating women who received | Consultations with AG and menstruating women | CH - Nutrition, CH - Adolescent Health | +| CH085 - Underweight women (%) | Proportion of Women and adolescent girls who are underweight | Non-pregnant AGW with low BMI | Consultations non-pregnant AGW | CH - Nutrition, CH - Adolescent Health | +| CH086 - Adolescents with insufficient physical activity (%) | Proportion of adolescents with insufficient physical activity | Adolescents insufficient physical activity | Adolescents in the catchment area | CH - Adolescent Health, CH - Noncommunicable diseases | +| CH087 - Adolescents currently using tobacco (%) | Proportion of adolescents currently using tobacco | Adolescents currently using tobacco | Adolescents in the catchment area | CH - Adolescent Health, CH - Noncommunicable diseases | +| CH088 - Alcohol consumers (%) | Proportion of people reporting consuming alcohol | People reported using alcohol | Number people assessed for alcohol use | CH - Adolescent Health, CH - Mental health | +| CH089 - People with heavy episodic drinking (%) | Proportion of people with heavy episodic drinking | People with heavy episodic drinking | People assessed for heavy episodic drinking | CH - Adolescent Health, CH - Mental health, CH - Noncommunicable diseases | +| CH090 - People using psychoactive drugs (%) | Proportion of people who reporting psychoactive drugs | People who report use of any psychoactive drugs | People assessed for use of any psychoactive drugs | CH - Adolescent Health, CH - Mental health | +| CH091 - People injecting psychoactive drugs (%) | Proportion of people who report injecting psychoactive drugs | People who report injecting drug use | People assessed for injecting drug use | CH - Adolescent Health, CH - Mental health | +| CH092 - People with suicidal plan | Number of people with suicidal ideation or plan | People with suicidal ideation or plan | 1 | CH - Adolescent Health, CH - Mental health | +| CH093 - People with suicide attempts | Number of People who reported attempting suicide | People who reported attempting suicide | 1 | CH - Adolescent Health, CH - Mental health | +| CH094a - Average time of screen time as leisure activity (week) | Average time on weekdays dedicated to screen time for leisure activities | Weekday screen time for leisure activities | 1 | CH - Adolescent Health, CH - Mental health | +| CH094b - Average time of screen time as leisure activity (weekend) | Average time on weekend days dedicated to screen time for leisure activities | Weekend screen time for leisure activities | 1 | CH - Adolescent Health, CH - Mental health | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Adolescent Health”. +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data on FP, deworming, drug use, and suicide, but the content should be adapted based in the local activities. + +![Dashboard](resources/images/chis-ado-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-ado-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-health-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-health-md new file mode 100644 index 000000000..89866b4e1 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-health-md @@ -0,0 +1,306 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_ch-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Child Health { #chis-agg-ch-design } + +## 1.Datasets { #1datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Child Health (ChH) module includes: + +1. A **monthly dataset** with key data elements for child health +2. A **yearly dataset** for the follow up of key annual information on child health +3. **Core indicators** for both datasets +4. A predefined **“CH - Child Health” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +## 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the ChH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the ChH module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| CH060a - People receiving deworming preventive chemotherapy | People receiving a dose of preventive chemotherapy for deworming | CH - Adolescent Health (Monthly), CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Adolescent Health, CH - Nutrition, CH - Child Health | +| CH060b - People targeted for deworming preventive chemotherapy | People targeted for preventive chemotherapy for deworming | CH - Adolescent Health (Monthly), CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Adolescent Health, CH - Nutrition, CH - Child Health | +| CH060c - People receiving deworming preventive chemotherapy | People receiving a dose of preventive chemotherapy for deworming by drug | CH - Adolescent Health (Monthly), CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Adolescent Health, CH - Nutrition, CH - Child Health | +| CH028a - HIV positive tests returned | HIV tests conducted in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028b - HIV tests returned | HIV tests returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028c - HIV positive tests returned to key population | HIV tests conducted amongst key population in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028d - HIV tests returned to key population | HIV tests performed amongst key population where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028e - HIV positive tests returned to TB patients | HIV tests conducted amongst TB in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028f - HIV tests returned to TB patients | HIV tests performed amongst TB where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH069a - Children (5-19 y) overweight and obese | Children and adolescents aged 5-19 years who are overweight | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH069b - Children (5-19 y) weighted | Children and adolescents aged 5-19 years who were measured | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH052a - Newborns and children with danger signs | Newborns and children with danger signs in the community | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH052b - Newborns and children with danger signs referred | Newborns and children with danger signs referred | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH052c - Newborns and children consultations in the community | Newborns and children consultations in the community | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH058a - Consultations for children (0-5 m) with feeding counselling | Consultations with a CHW for an infant aged 0-5 months providing any counselling on appropriate infant and young child feeding | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH058b - Consultations for children (0-5 m) with CHW | Consultations for children (0-5 m) with CHW | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH059a - Consultations for children (6-23 m) with feeding counselling | Consultations with a CHW for children aged 6-23 months providing any counselling on appropriate complementary feeding | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH059b - Consultations for children (6-23 m) with CHW | Consultations for children (6-23 m) with CHW | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061a - Children (6-59m) given Vit A in semester 1 - routine | Children aged 6-59 months who received vitamin a via routine contacts with CHW in semester 1 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061b - Children (6-59m) given Vit A in semester 2 routine | Children aged 6-59 months who received vitamin a via routine contacts with CHW in semester 2 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061c - Children (6-59m) with CHW contact in semester 1 routine | Children aged 6-59 months with at least one community contact in semester 1 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061d - Children (6-59m) with CHW contact in semester 2 routine | Children aged 6-59 months with at least one community contact in semester 2 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061e - Children (6-59m) given Vit A by CHW in semester 1 event | Children aged 6-59 months who received vitamin a by CHW via event in semester 1 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061f - Children (6-59m) given Vit A by CHW in semester 2 event | Children aged 6-59 months who received vitamin a by CHW via event in semester 2 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061g - Children (6-59m) attending Vit A event in semester 1 | Children aged 6-59 months attending events with vitamin A supplementation distributed via CHW in semester 1 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH061h - Children (6-59m) attending Vit A event in semester 2 | Children aged 6-59 months attending events with vitamin A supplementation distributed via CHW in semester 2 | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH062a - Children (6-59m) assessed using MUAC or WHZ or bilateral pitting oedema | Children (6-59m) assessed using MUAC or WHZ or bilateral pitting oedema | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH062b - Children (6-59m) in the community | Children (6-59m) in the community | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH063a - Children (6-59m) with SAM | Children aged 6-59 months with severe acute malnutrition | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH063b - Children (6-59m) assessed for SAM | Children aged 6-59 months screened for severe acute malnutrition | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH063c - Children (6-59m) with SAM referred | Children aged 6-59 months with severe acute malnutrition referred | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH064 - Children (0-4 y) weight measured | Children aged <5 years visited by a CHW whose weight was assessed | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH066a - Children (6-59m) wasting or with bilateral pitting oedema | Children aged 6-59 months wasting or bilateral pitting oedema | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH066b - Children (6-59m) wasting or with bilateral pitting oedema referred | Children (6-59m) wasting or with bilateral pitting oedema referred | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH067a - Children (0-4 y) with height measured | Children aged 0-4 years visited by a CHW whose height/length was measured | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH067b - Children (0-4 y) consulted by a CHW | Children (0-4 y) consulted by a CHW | CH - Child Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH070a - Children (0-9 y) treated for diarrhoea | Children aged 0-9 years presenting with diarrhoea who received treatment | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH070b - Children (0-9 y) assessed for diarrhoea | Children aged 0-9 years presenting with diarrhoea assessed by CHW | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH071a - Children with fast breathing and/or chest indrawing | Children with fast breathing and/or chest indrawing | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH071b - Children with fast breathing and/or chest indrawing referred | Children with fast breathing and/or chest indrawing referred | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH071c - Children screened for fast breathing and/or chest indrawing | Children screened for fast breathing and/or chest indrawing | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH072 - Children with fast breathing and/or chest indrawing given ABX | Children presenting with fast breathing and/or chest indrawing who received antibiotic treatment from CHW | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH073 - Infants (0-59 days) with pre-referral treatment for bacterial infection | Young infants 0-59 days old who received pre-referral treatment by CHW for signs of possible serious bacterial infection | CH - Child Health (Monthly) | CH - Child Health | +| CH074a - Caregivers receiving information on early identification of danger signs | Caregivers receiving information on early identification of danger signs | CH - Child Health (Monthly) | CH - Child Health | +| CH074b - Caregivers of consulted children | Caregivers of consulted children | CH - Child Health (Monthly) | CH - Child Health | +| CH075a - Children (0-4 y) monitored for early signs of developmental delays | Children aged 0-4 years monitored for early signs of developmental delays | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH075b - Children (0-4 y) monitored for early signs of developmental delays referred | Children (0-4 y) monitored for early signs of developmental delays referred | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH076a - Children with suspected developmental disabilities referred | Children with suspected developmental disabilities referred | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH076b - Children assessed for development monitoring | Children who were assessed for their developmental monitoring | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH077a - Caregivers counselled on responsive caregiving and learning activities | Caregivers receiving counselling on responsive caregiving and early learning activities | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH077b - Caregivers of children consulting for developmental delays | Caregivers of children consulting for developmental delays | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH078a - Children with developmental disability whose caregiver received parenting info | Children with suspected developmental disorders and disabilities whose caregivers receive information on parenting | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH078b - Children (0-4 y) assessed for developmental delays - last 12 months | Children who were assessed for their developmental disorders and disabilities in the past 12 months | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH055 - Infant deaths (0-11 m) | Infant deaths (0-11 m) | CH - Child Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Child Health | +| CH056 - Child deaths (1-4 years) | Child deaths (1-4 years) | CH - Child Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Child Health | +| CH057 - Child deaths (5-9 years) | Child deaths (5-9 years) | CH - Child Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Child Health | +| CH065 - Children (0-4 y) underweight | Number of children aged 0-5 years with weight for height > +2 SD from the median of the WHO Child Growth Standards | CH - Child Health (Yearly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Child Health | +| CH068a - Children (0-4 y) overweight | Children aged 0-4 years visited by CHW and overweight | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH068b - Children (0-4 y) weighted | Children aged 0-4 years whose weight were measured | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH079a - People (>18 m) referred for HIV testing | People (>18 m) referred for HIV testing | CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly) | CH - HIV, CH - ICCM, CH - Child Health | +| CH079b - People (>18 m) in the catchment area | People (>18 m) in the catchment area | CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly) | CH - HIV, CH - ICCM, CH - Child Health | +| CH080 - Children (0-4 y) with insufficient physical activity | Children aged 0-4 years not meeting who recommendations on physical activity for their age group | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Child Health | +| CH081 - Children (5-9 y) with insufficient physical activity | Children (5-9 y) with insufficient physical activity | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Child Health | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly Child Health Dataset { #21-monthly-child-health-dataset } + +The [United Nations Convention on the Rights of the Child](https://www.savethechildren.org.uk/content/dam/gb/reports/humanitarian/uncrc19-summary2.pdf) defines a child as every human being **below the age of 18 years**, unless under the law applicable to the child, majority is attained earlier. **This module focuses more specifically on children between the age of 29 days and 9 years**. In both the monthly and the yearly datasets the category combinations for the age groups have age groups that go beyond the definition. This has been done to avoid creating *ad hoc* age groups for each and every dataset. The age groups above the definition of Child have been greyed-out and therefore blocked for data entry. Countries should nonetheless edit and apply the age categories that better reflect the local context and guidelines. + +#### 2.1.1. Infant Feeding { #211-infant-feeding } + +The section is set to collect the number of CHWs consultations to infants and about appropriate feeding. + +![Infant feeding](resources/images/chis-cdh-m-001.png) + +#### 2.1.2. Deworming { #212-deworming } + +The first part of the section is set to give an overview of the target population for the activity by age group (1-4Y, 5-9Y, 140-14Y, 15-19Y, unknown age) and by sex (male, female, other, unknown sex), and the number of reached people (same disaggregation). The second part of the section divides the reached people by type of preventive chemotherapy (Albendazole and Mebendazole). The used drugs can be adapted locally based on availability and national guidelines. + +![Deworming](resources/images/chis-cdh-m-002.png) + +#### 2.1.3. Vitamin A Supplement - Routine { #213-vitamin-a-supplement-routine } + +This section of the monthly dataset focuses only on routine activities dedicated to the distribution of Vit A supplements to children during the first and second semester of the year. This has two subsections with the first focusing on routine vitamin A supplementation with children by age groups (6-11m and 12-59m) and by age and the administered IUs (100000 IU and 200000 IU). + +![Vitamin A Supplement - Routine](resources/images/chis-cdh-m-003.png) + +#### 2.1.4. Vitamin A Supplement - Events { #214-vitamin-a-supplement-events } + +The other section on Vitamin A supplementation is dedicated exclusively to mass distributions that are conducted during one-shot interventions organized to reach the maximum number of children at once. + +![Vitamin A Supplement - Events](resources/images/chis-cdh-m-003b.png) + +#### 2.1.5. Severe Acute Malnutrition (SAM) { #215-severe-acute-malnutrition-sam } + +The section provides a simple overview of the core information to be collected during the nutritional assessment in the community by age group (6-11m and 12-59m). + +![SAM](resources/images/chis-cdh-m-004.png) + +#### 2.1.6.Body weight { #216body-weight } + +The section the total number of weighted children by age (0-11m, 1-4y) and by sex (male, female, other, unknown sex). + +![Body weight](resources/images/chis-cdh-m-005.png) + +#### 2.1.7. Wasting { #217-wasting } + +The section is dedicated to the assessment of the nutritional status of children under the age of five by age groups (0-11m and 12-59m) via MUAC or bilateral pitting oedema. + +![Wasting](resources/images/chis-cdh-m-005b.png) + +#### 2.1.8. Body Height { #218-body-height } + +The section collects data on the number of assessed children and on how many among them have had their height measured during the consultation. + +![Body Height](resources/images/chis-cdh-m-005c.png) + +#### 2.1.9. Diarrhoea { #219-diarrhoea } + +The section collects the information on diarrhoea treatment (ORS, Zinc, both)among children aged 0-4 and 5-9 years. + +![Diarrhoea](resources/images/chis-cdh-m-006.png) + +#### 2.1.10. Bacterial Infections { #2110-bacterial-infections } + +The section collects data on administered treatments against bacterial infections by age group (0-6d, 7-28d, 29-59d, unknown age) and by ABX (Amoxicillin, Gentamicin, Other); and, in particular, how many among these were to treat chest problems by age group (0-11m, 1-4y, 5-9y, unknown age) and by symptoms (fast breathing, chest indrawing, both). + +![Bacterial Infections](resources/images/chis-cdh-m-008.png) + +#### 2.1.11. Breathing and Chest Problems { #2111-breathing-and-chest-problems } + +The section provides a simple overview of the screened children by age group (0-11m, 1-4y, 5-9y, unknown age) and by symptoms (fast breathing, chest indrawing, both); and on how many among them have been identified for chest problems and eventually referred. + +![Breathing and Chest Problems](resources/images/chis-cdh-m-007.png) + +#### 2.1.12. Danger Signs Among Children { #2112-danger-signs-among-children } + +The section collects data on danger signs among newborns and young children by age group (0-27d, 28d-11m, 1-4y, 5-9y, unknown age); and provides information on the sessions given to their caregivers on the identifications of such danger signs by se of the caregiver (male, female, other, unknown sex). + +![Danger Signs Children](resources/images/chis-cdh-m-009.png) + +#### 2.1.13. Developmental Delays - Monitored For Early Signs { #2113-developmental-delays-monitored-for-early-signs } + +The section collects data on children under five years of age who have been screened for early signs of developmental delays and how many have been referred for a better follow-up by age groups (0-11m and 1-4y) and by sex (male, female, other, unknown sex). + +![Developmental Delays - Monitored Early Signs](resources/images/chis-cdh-m-010.png) + +#### 2.1.14.Developmental Delays - Caregivers Receiving Parenting Info { #2114developmental-delays-caregivers-receiving-parenting-info } + +The section also focuses on children under five years of age by age groups (0-11m and 1-4y) and by sex (male, female, other, unknown sex) and their caregivers. + +![Developmental Delays - Caregivers Receiving Parenting Info](resources/images/chis-cdh-m-010c.png) + +#### 2.1.15. Developmental Delays - Suspects Referred { #2115-developmental-delays-suspects-referred } + +This section focuses on children up to 17 years of age by age groups (0-11m, 1-4y, 5-9y, 10-14y, 15-17y, unknown age) and by sex (male, female, other, unknown sex). + +![Developmental Delays - Suspects Referred](resources/images/chis-cdh-m-010b.png) + +#### 2.1.16. Developmental Delays - Counselled Caregivers { #2116-developmental-delays-counselled-caregivers } + +The section provides information on the counseling sessions for the caregivers by sex of the caregiver (male, female, other, unknown sex). + +![Developmental Delays - Counselled Caregivers](resources/images/chis-cdh-m-010d.png) + +### 2.2. Yearly Child Health Dataset { #22-yearly-child-health-dataset } + +#### 2.2.1. HIV - All { #221-hiv-all } + +The section collects the core information on the number of tests returned to people and the positive results among them. The information is disaggregated by age groups (0-4y 5-9y, 10-14, 15-19y, unknown age) and sex (male, female, other, unknown sex). + +![HIV - All](resources/images/chis-cdh-y-001.png) + +#### 2.2.2. HIV - Key Population { #222-hiv-key-population } + +The table gives an overview of the number of returned tests and positive results among key population groups at risk (MSM, SW, Prisoners, IDU, TG, Other - the groups can be adapted to better mirror the local context). + +![Key Population](resources/images/chis-cdh-y-001b.png) + +#### 2.2.3. HIV - TB Cases { #223-hiv-tb-cases } + +The section provides the relevant information on HIV testing among presumptive and confirmed TB patients. + +![HIV - TB Cases](resources/images/chis-cdh-y-001c.png) + +#### 2.2.4. Child Death { #224-child-death } + +The section provides a very simple overview of the number of deaths by sex (male, female, other, unknown sex) among children. + +![Child Death](resources/images/chis-cdh-y-002.png) + +#### 2.2.5. Body Weight { #225-body-weight } + +The section collects data on the two ends of the spectrum among measured children: those with high BMI and those with low BMI by age group (5-9y, 10-14y, 15-17y, 18-19y, unknown age), and by age group (0-11m, 1-4y) and by sex (male, female, other, unknown sex) . + +![Body Weight](resources/images/chis-cdh-y-003.png) + +#### 2.2.6. Physical Activity { #226-physical-activity } + +The section provides info on the levels of physical activities of the screened children. Children between the ages of 5 and 9 years are disaggregated by sex (male, female, other, unknown sex), while the chilndren between the ages of 0 and 4 years are disagrgegated by age groups (0-11m, 1-4y) and by sex (male, female, other, unknown sex). + +![Physical Activity](resources/images/chis-cdh-y-004.png) + +#### 2.2.7. HTS Referral { #227-hts-referral } +This section collects data on children >18 months at risk of HIV and therefore referred for further testing. The data are disaggregated by age (0-4y, 5-9y, 10-14y, 15-19y) and by sex (male, female, other, unknown sex). + +![HTS Referral](resources/images/chis-cdh-y-005.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Child Health datasets: + +| name | instruction | operator | leftSide description | rightSide description | +|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|----------------------------------------------------| +| CH - Caregivers receiving info on danger signs Vs Caregivers of children consulting | Caregivers receiving info on danger signs should be less than or equal to Caregivers of children consulting | menor_que_o_igual_que | Caregivers receiving info on danger signs | Caregivers of children consulting | +| CH - Children presenting fast breathing/chest indrawing Vs Children screened for fast breathing/ indrawing | Children presenting fast breathing/chest indrawing should be less than or equal to Children screened for fast breathing/ indrawing | menor_que_o_igual_que | Children presenting fast breathing/chest indrawing | Children screened for fast breathing/ indrawing | +| CH - Children with fast breathing/indrawing referred Vs Children presenting fast breathing/chest indrawing | Children with fast breathing/indrawing referred should be less than or equal to Children presenting fast breathing/chest indrawing | menor_que_o_igual_que | Children with fast breathing/indrawing referred | Children presenting fast breathing/chest indrawing | +| CH - Fast breathing/chest indrawing given antibiotic TX Vs Children presenting fast breathing/chest indrawing | Fast breathing/chest indrawing given antibiotic TX should be less than or equal to Children presenting fast breathing/chest indrawing | menor_que_o_igual_que | Fast breathing/chest indrawing given antibiotic TX | Children presenting fast breathing/chest indrawing | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the ChH indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| CH028a - HIV tests with returned results | Number of HIV tests conducted and results returned | HIV tests performed where results were returned | 1 | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH028b - HIV +ve tests returned to people (%) | Proportion of HIV tests performed that were positive and results returned to people | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH052e - Newborns and children with danger signs | Number of newborns and children with danger signs | Newborns and children with danger signs | 1 | CH - Child Health, CH - Newborn Health, CH - ICCM | +| CH055 - Infant deaths (0-11 m) | Number of new infant deaths (0-11 m) | New infant deaths (0-11 m) | 1 | CH - Child Health, CH - Civil registration and vital statistics | +| CH056 - Child deaths (1-4 years) | Number of new child deaths (1-4 years) | New child deaths aged 1-4 years | 1 | CH - Child Health, CH - Civil registration and vital statistics | +| CH057 - Child deaths (5-9 years) | Number of new child deaths (5-9 years) | New child deaths aged 5-9 years | 1 | CH - Child Health, CH - Civil registration and vital statistics | +| CH058 - Consultations for children (0-5 m) | Number of consultations for infants under 6 months with CHW | Consultation for children 0-5 mos | 1 | CH - Nutrition, CH - Child Health | +| CH058 - Consultations for children (0-5 m) with feeding counselling (%) | Proportion of consultations for infants under 6 months providing counselling on appropriate infant and young child feeding | Consultation for children 0-5 m & infant feeding | Consultations with a CHW for an infant 0-5 months | CH - Nutrition, CH - Child Health | +| CH059 - Consultations for children (6-23 m) | Number of consultations for children 6-23 months with CHW | Consultation for children 6-23 mos | 1 | CH - Nutrition, CH - Child Health | +| CH059 - Consultations for children (6-23 m) with feeding counselling (%) | Proportion of consultations for children 6-23 months providing counselling on appropriate complementary feeding | Consultation for children 6-23 mos & comp feeding | Consultations with a CHW for children 6-23 months | CH - Nutrition, CH - Child Health | +| CH05x - Deaths children (0-11 m) | Number of new children deaths(0-11 m) | New infant deaths (0-11 m) | 1 | CH - Child Health | +| CH060 - People receiving deworming preventive chemotherapy (%) | Proportion of people receiving preventive chemotherapy for deworming | Receiving a dose of PC for deworming | People targeted for PC for deworming | CH - Nutrition, CH - Child Health, CH - Adolescent Health | +| CH061b - Children (6-59m) given Vit A each semester event(%) | Proportion of children 6-59 months given a dose of vitamin A through event CHW contacts in each semester | Children 6-59 months given vitamin A event | Contacts with children 6-59 months through event CHW contacts for Vitamin A | CH - Nutrition, CH - Child Health | +| CH062 - Children (6-59 m) assessed for wasting (%) | Proportion of children aged 6-59 months assessed for wasting | Children aged 6-59 months assessed for wasting | Children aged 6-59 months in the community | CH - Nutrition, CH - Child Health | +| CH062 - Children (6-59 m) wasting | Number of children aged 6-59 months with signs and symptoms of wasting | Children aged 6-59 wasting | 1 | CH - Nutrition, CH - Child Health | +| CH063 - Children (6-59 m) assessed for SAM (%) | Proportion of children 6-59 months with severe acute malnutrition (SAM) | Children 6-59 months with SAM | Children 6-59 months screened for SAM | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH063 - Children (6-59 m) with SAM | Number of children 6-59 months with severe acute malnutrition (SAM) | Children 6-59 months with SAM | 1 | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH064 - Children (6-59 m) weighted | Number of children under 5 years (6-59 months) who had their weight assessed | Children 6-59 months with weight assessed | 1 | CH - Nutrition, CH - Child Health | +| CH065 - Children (0-4 y) underweight (%) | Proportion of children under 5 years who are underweight | Children aged 0-4 years visited by a CHW and underweight | Children weighed | CH - Nutrition, CH - Child Health | +| CH066 - Children (6-59m) wasting (%) | Proportion of children (6-59m) wasting | Children 6-59 months wasting | Children (6-59m) assessed using MUAC or WHZ or bilateral pitting oedema | CH - Nutrition, CH - Child Health | +| CH067 - Children (0-4 y) with measured height (%) | Proportion of children under 5 years who had their height/length measured | Children 0-4 years whose height was measured | Children aged 0-4 years consulted by a CHW | CH - Nutrition, CH - Child Health | +| CH068 - Overweight children (0-4 y) (%) | Proportion of overweight among children under 5 years of age | Children 0-4 years visited by CHW and overweight | Children aged 0-4 years that were measured | CH - Nutrition, CH - Child Health, CH - Noncommunicable diseases | +| CH069 - Overweight and obese children (5-19 y) (%) | Proportion of overweight and obesity in school-age children and adolescents 5-19 years | Children and adolescents 5-19 years overweight | Children and adolescents 5-19 years measured | CH - Nutrition, CH - Child Health, CH - Adolescent Health, CH - Noncommunicable diseases | +| CH070b - Children (0-9 y) assessed for diarrhoea | Children (0-9 y) assessed for diarrhoea | Children (0-9 y) assessed for diarrhoea | 1 | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH070 - Children (0-9 y) treated for diarrhoea (%) | Proportion of children (0-9 years)who received treatment for diarrhoea | Children 0-9 years with diarrhoea who received tx | Children 0-9 yrs presenting diarrhoea assessed | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH071 - Children with fast breathing and/or chest in-drawing (%) | Proportion of children presenting fast breathing and/or chest indrawing | Children presenting fast breathing/chest indrawing | Children screened for fast breathing/ indrawing | CH - Child Health, CH - ICCM | +| CH072 - Children receiving antibiotics for fast breathing and/or chest in-drawing (%) | Proportion of children receiving antibiotic treatment for fast breathing and/or chest indrawing | Fast breathing/chest indrawing given antibiotic TX | Children presenting fast breathing/chest indrawing | CH - Child Health, CH - ICCM | +| CH073 - Infants (0-59 days) with pre-referral treatment for bacterial infection | Number of young infants, 0-59 days old who received pre-referral treatment for signs of possible serious bacterial infection | Infants 0-59 days tx for bacterial infection | 1 | CH - Child Health | +| CH074 - Caregivers receiving info on early identification of danger signs (%) | Proportion of caregivers receiving information on early identification of danger signs | Caregivers receiving info on danger signs | Caregivers of children consulting | CH - Child Health | +| CH075 - Children (0-4 y) monitored for developmental delays (%) | Proportion of children aged 0-4 years monitored for early signs of developmental delays | Children 0-4 yrs monitored for signs of dev delays | Children aged 0-4 years in the catchment area | CH - Child Health, CH - Mental health | +| CH076 - Children (0-4 y) referred for developmental disabilities (%) | Proportion of children aged 0-4 years with suspected developmental disabilities referred | Children with suspected dev disabilities referred | Children assessed for their dev monitoring | CH - Child Health, CH - Mental health | +| CH077 - Caregivers counselled on responsive care giving and learning activities (%) | Proportion of caregivers counselled on responsive caregiving and early learning activities | Counselled on caregiving & early learning | Caregivers of children consulting for dev delays | CH - Child Health, CH - Mental health | +| CH078 - Caregivers of children with developmental disability receiving parenting info (%) | Proportion of children with suspected developmental disorders and disabilities whose caregivers receive parenting information | Caregivers who received info on parenting | Children assessed for dev disorders & disabilities | CH - Child Health, CH - Mental health | +| CH079 - People (>18 m) referred for HIV testing | Number of people above 18 months referred for HIV testing | People >18 months who were referred for HIV test | 1 | CH - HIV, CH - Child Health, CH - ICCM | +| CH080 - Children (0-4 y) with insufficient physical activity (%) | Proportion of children aged 0-4 years with insufficient physical activity | Children 0-4 years not meeting required activity | Children aged 0-4 years in the catchment area | CH - Child Health, CH - Noncommunicable diseases | +| CH081 - Children (5-9 y) with insufficient physical activity (%) | Proportion of children aged 5-9years with insufficient physical activity | Children 5-9 years with insufficient activity | Children aged 5-9 years in the catchment area | CH - Child Health, CH - Noncommunicable diseases | +| CH08x - Children (0-9 y) with insufficient physical activity (%) | Proportion of children (0-9 y)with insufficient physical activity | Children (0-9 y) not meeting required activity | Children (0-9 y) in the catchment area | CH - Child Health | +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Child Health”. +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-cdh-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-cdh-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-protection-and-interpersonal-violence-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-protection-and-interpersonal-violence-md new file mode 100644 index 000000000..dfb391223 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__child-protection-and-interpersonal-violence-md @@ -0,0 +1,107 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_cpiv-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Child Protection and Interpersonal Violence { #chis-agg-cpiv-design } + +## 1. Dataset Configuration { #1-dataset-configuration } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Child Protection and Interpersonal Violence (CPIPV) module includes: + +1. A **monthly dataset** with key data elements for child protection and interpersonal violence +2. A **yearly dataset** for the follow up of key annual information on child protection and interpersonal violence +3. **Core indicators** for both datasets +4. A predefined **“CH - Child Protection and Interpersonal Violence” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the CPIPV module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the CPIPV module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| CH154a - Referrals of women for GBV or SV | Referrals made to health or other essential services for women and girls who disclose intimate partner violence or sexual violence | CH - Child protection & interpersonal violence (Monthly) | CH - Child protection & interpersonal violence | +| CH154b - Referrals of women for GBV / SV | Referrals made to health or other essential services for women and girls who disclose intimate partner violence or sexual violence by service | CH - Child protection & interpersonal violence (Monthly) | CH - Child protection & interpersonal violence | +| CH157 - Households with referrals to family services by CHW | Households where CHW provided referrals to family services | CH - Child protection & interpersonal violence (Monthly) | CH - Child protection & interpersonal violence | +| CH034a - Women (15-49 years) with FGM | Women aged 15-49 years who have undergone FGM | CH - Child protection & interpersonal violence (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - Sexual and Reproductive Health, CH - Child protection & interpersonal violence | +| CH034b - Women (15-49 years) in the catchment area | Women (15-49 years) in the catchment area | CH - Child protection & interpersonal violence (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - Sexual and Reproductive Health, CH - Child protection & interpersonal violence | +| CH153 - Households reached by GBV HP messages | Households reached with health promotion messages about the impacts of violence against women and where to seek help | CH - Child protection & interpersonal violence (Yearly) | CH - Child protection & interpersonal violence | +| CH155a - Girls (0-14 years) who have undergone FGM | Girls (0-14 years) who have undergone FGM | CH - Child protection & interpersonal violence (Yearly) | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | +| CH155b - Girls (0-14 years) not undergone FGM | Girls (0-14 years) who have NOT undergone FGM | CH - Child protection & interpersonal violence (Yearly) | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | +| CH155c - Girls (0-14 years) in the catchment area | Girls (0-14 years) in the catchment area | CH - Child protection & interpersonal violence (Yearly) | CH - Child protection & interpersonal violence | +| CH156 - Households reached by positive parenting messages | Households where CHW raised awareness of positive parenting | CH - Child protection & interpersonal violence (Yearly) | CH - Child protection & interpersonal violence | + +## 2.Dataset Details { #2dataset-details } + +### 2.1. Monthly Child Protection and Interpersonal Violence Dataset { #21-monthly-child-protection-and-interpersonal-violence-dataset } + +#### 2.1.1. Service Referral { #211-service-referral } + +The section is set to collect the information necessary to identify the causes of intervention (child maltreatment, MH status of caregiver, alcohol use by caregiver, drugs use by caregiver, other) and the services of referral (health facility, psychological support, legl, shelter, other). The categories can be edited to better mirror the local context. + +![Service Referral](resources/images/chis-cpiv-m-001.png) + +## 2.2. Yearly Child Protection and Interpersonal Violence Dataset { #22-yearly-child-protection-and-interpersonal-violence-dataset } + +### 2.2.1. FGM { #221-fgm } + +The section reports the core information on FGM practices in the community. The data are disaggregated by age groups depending on the target population (15-19y, 20-49y, unknown age; or 0-4y, 5-9y, 10-14y, unknown age). + +![FGM](resources/images/chis-cpiv-y-001.png) + +### 2.2.2. Health Promotion { #222-health-promotion } + +The section provides a very simple overview of the Health promotion sessions among GBV survivors. + +![Health Promotion](resources/images/chis-cpiv-y-002.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the CPIV datasets: +| name | instruction | operator | leftSide description | rightSide description | Groups | +|----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------|----------------------------------------------|-------------------------------------------------------------------------------------| +| CH - Girls aged 0-14 y who have NOT undergone FGM Vs Girls 0-14 y | Girls aged 0-14 y who have NOT undergone FGM should be less than or equal to Girls aged 0-14 y | less_than_or_equal_to | Girls aged 0-14 y who have NOT undergone FGM | Girls aged 0-14 y | CH - Child protection & interpersonal violence | +| CH - Girls aged 0-14 y who have undergone FGM Vs Girls 0-14 y | Girls aged 0-14 y who have undergone FGM should be less than or equal to Girls aged 0-14 y | less_than_or_equal_to | Girls aged 0-14 y who have undergone FGM | Girls aged 0-14 y | CH - Child protection & interpersonal violence | +| CH - Referrals of women and girls on GBV by service Vs Referrals of women and girls on GBV | Referrals of women and girls on GBV by service should be less than or equal to Referrals of women and girls on GBV | less_than_or_equal_to | Referrals of women and girls on GBV by service | Referrals of women and girls on GBV | CH - Child protection & interpersonal violence | +| CH - Women aged 15-49 years who have undergone FGM Vs Women aged 15-49 years in the catchment area | Women aged 15-49 years who have undergone FGM should be less than or equal to Women aged 15-49 years in the catchment area | less_than_or_equal_to | Women aged 15-49 years who have undergone FGM | Women aged 15-49 years in the catchment area | CH - Sexual and Reproductive Health; CH - Child protection & interpersonal violence | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the CPIV indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|----------------------------------------------|-------------------------------------------------------------------------------------| +| CH034b - Women (15-49 years) with FGM | Number of women aged 15-49 years old who have undergone female genital mutilation | Women aged 15-49 years who have undergone FGM | 1 | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | +| CH034 - Women (15-49 years) with FGM (%) | Proportion of women aged 15-49 years old who have undergone female genital mutilation | Women aged 15-49 years who have undergone FGM | Women aged 15-49 years in the catchment area | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | +| CH153 - Households reached by GBV HP messages (%) | Proportion of households reached with health promotion messages about the impacts of violence against women and where to seek help | HHs reached with health promotion on GBV | Households in the catchment area | CH - Child protection & interpersonal violence | +| CH154 - Women referred for GBV or SV | Number of referrals made to health or other essential services for women and girls who disclose intimate partner violence or sexual violence | Referrals of women and girls on GBV | 1 | CH - Child protection & interpersonal violence | +| CH155 - Girls (0-14 y) who have undergone FGM (%) | Proportion of girls (0-14 y)who have undergone female genital mutilation (FGM) or are at risk of FGM | Girls (0-14 y) who have undergone FGM | Girls (0-14 y) | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | +| CH156 - Households reached by positive parenting messages (%) | Proportion of households where CHW raised awareness of positive parenting | HHs CHW raised awareness of positive parenting | Households in the catchment area | CH - Child protection & interpersonal violence | +| CH157b - Households with referrals to family services - Child maltreatment | Proportion of households where CHW provided referrals to family services due to child maltreatment | HH with child maltreatment | 1 | CH - Child protection & interpersonal violence | +| CH157c - Households with referrals to family services - MH caregiver | Proportion of households where CHW provided referrals to family services due to the MH status of the caregiver | HH with MH unstable status of caregiver | 1 | CH - Child protection & interpersonal violence | +| CH157d - Households with referrals to family services - Alcohol abuse | Proportion of households where CHW provided referrals to family services due to alcohol abuse by the caregiver | Alcohol abuse | 1 | CH - Child protection & interpersonal violence | +| CH157e - Households with referrals to family services - Drug abuse | Proportion of households where CHW provided referrals to family services due to drug abuse by the caregiver | Drug abuse | 1 | CH - Child protection & interpersonal violence | +| CH157f - Households with referrals to family services - Other reason | Proportion of households where CHW provided referrals to family services due to other reasons | Other reason of referral | 1 | CH - Child protection & interpersonal violence | +| CH157 - Households with referrals to family services by CHW (%) | Proportion of households where CHW provided referrals to family services | HHs referred to family services by CHW | Households in the catchment area | CH - Child protection & interpersonal violence | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Child Protection and Interpersonal Violence”. +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-cpiv-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-cpiv-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__chis-general-design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__chis-general-design-md index 9be918615..b3bc9af39 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__chis-general-design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__chis-general-design-md @@ -98,7 +98,7 @@ The types of services that community health workers provide in communities are h ![CHIS workflow](resources/images/chis-workflow.png) -### Usuarios previstos { #intended-users } +### Usuarios objetivo { #intended-users } The package has been developed with the following user profiles in mind: @@ -129,7 +129,7 @@ Below are some of the examples to learn from and create additional composite ind Table 1: Examples of possible composite indicators for some the programs in CHIS. -| Programa | Facility + Community = Numerator | Denominator | Example of Composite indicators | +| Programa | Facility + Community = Numerator | Denominador | Example of Composite indicators | |---------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-------------------------------------------------------------------| | TB | [New, relapse and cases with unknown treatment history]
+
[CH128b - Notified TB cases] in the catchment area] | N/A | Notified TB case at facility and community | | VIH | [HIV - HIV tests performed]
+
[CH028b - HIV tests returned] | N/A | HIV tests performed at facility and community | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__civil-registration-and-vital-statistics-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__civil-registration-and-vital-statistics-md new file mode 100644 index 000000000..540cccd03 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__civil-registration-and-vital-statistics-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_crvs-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Civil Registration and Vital Statistics (CRVS) { #chis-agg-crvs-design } + +## 1. Datasets { #1-datasets } + +## 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - CRVS module includes: + +1. A **monthly dataset** with key data elements for CRVS +2. A **yearly dataset** for the follow up of key annual information on CRVS +3. **Core indicators** for both datasets +4. A predefined **“CH - Civil registration and vital statistics” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the CRVS module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the CRVS module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| CH082 - Young adolescent deaths (10-14 years old) | Young adolescent deaths (10-14 years old) | CH - Adolescent Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Adolescent Health | +| CH083 - Older adolescent deaths (15-19 years) | Older adolescent deaths (15-19 years) | CH - Adolescent Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Adolescent Health | +| CH055 - Infant deaths (0-11 m) | Infant deaths (0-11 m) | CH - Child Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Child Health | +| CH056 - Child deaths (1-4 years) | Child deaths (1-4 years) | CH - Child Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Child Health | +| CH057 - Child deaths (5-9 years) | Child deaths (5-9 years) | CH - Child Health (Yearly), CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics, CH - Child Health | +| CH161a - Unregistered live births with submitted notification | Live births not registered for which notification was submitted by CHW to local authorities in the reporting period | CH - Civil registration and vital statistics (Monthly) | CH - Civil registration and vital statistics | +| CH161b - Unregistered live births | Unregistered live births | CH - Civil registration and vital statistics (Monthly) | CH - Civil registration and vital statistics | +| CH162a - Unregistered deaths with submitted notification | Deaths that were not registered for which notification was submitted by CHW to local authorities | CH - Civil registration and vital statistics (Monthly) | CH - Civil registration and vital statistics | +| CH162b - Unregistered deaths | Unregistered deaths | CH - Civil registration and vital statistics (Monthly) | CH - Civil registration and vital statistics | +| CH002a - Live births delivered in the community | Live births delivered in the community | CH - Civil registration and vital statistics (Yearly), CH - Population composition (Yearly) | CH - Population composition, CH - Newborn Health, CH - Civil registration and vital statistics | +| CH002b - Live births delivered in the community (by mother's age) | Live births delivered in the community by age of mother | CH - Civil registration and vital statistics (Yearly), CH - Population composition (Yearly) | CH - Civil registration and vital statistics, CH - Population composition | +| CH044a - Deaths pregnancy-related - during pregnancy | Deaths pregnancy-related - during pregnancy | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH044b - Deaths pregnancy-related - facility delivery | New pregnancy-related deaths during childbirth at facility | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH044c - Deaths pregnancy-related - community delivery | New pregnancy-related deaths during childbirth at community | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH044d - Deaths pregnancy-related - 2m pre/post delivery | New pregnancy-related deaths within two months of delivery or end of pregnancy | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH045 - Stillbirths (late fetal deaths) | Stillbirths (late fetal deaths) | CH - Civil registration and vital statistics (Yearly), CH - Newborn Health (Yearly) | CH - Civil registration and vital statistics, CH - Newborn Health | +| CH046 - Neonatal deaths (0-27 days) | Neonatal deaths (0-27 days) | CH - Civil registration and vital statistics (Yearly), CH - Newborn Health (Yearly) | CH - Civil registration and vital statistics, CH - Newborn Health | +| CH158a - New adult deaths in the reporting period | New adult deaths in the reporting period | CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics | +| CH159 - Deaths due to road traffic crashes | Deaths due to road traffic crashes | CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics | +| CH160a - Deaths due to drowning | Deaths due to drowning | CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics | +| CH163a - Children (0-4 y) registered birth | Children aged 0-4 years whose births are registered with the civil authority | CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics | +| CH163b - Children (0-4 y) screened for registration | Children (0-4 y) screened for registration | CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics | +| CH164a - Households with death certificates | Households with death certificates | CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics | +| CH164b - Households with death reported | Households with death reported | CH - Civil registration and vital statistics (Yearly) | CH - Civil registration and vital statistics | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly CRVS Dataset { #21-monthly-crvs-dataset } + +#### 2.1.1. Birth and Death Registration { #211-birth-and-death-registration } + +The section is set to collect the information necessary to identify births and deaths in the community on a monthly basis by sex (male, female, other, unknown sex). + +![Birth and Death Registration](resources/images/chis-crvs-m-001.png) + +## 2.2. Yearly CRVS Dataset { #22-yearly-crvs-dataset } + +### 2.2.1. Live Births { #221-live-births } + +The section reports the core information on deliveries in the community. The data are disaggregated by age of the mother (10-14y, 15-19y, 20+y, unknown age) and by sex of the child (male, female, other, unknown sex). + +![Live Births](resources/images/chis-crvs-y-001.png) + +### 2.2.2. Pregnancy-related Deaths { #222-pregnancy-related-deaths } + +The section provides an overview of the women’s deaths during pregnancy and delivery by the age of the mother (10-14y, 15-19y, 20+y, unknown age). + +![Pregnancy-related Deaths](resources/images/chis-crvs-y-002.png) + +### 2.2.3. Stillbirths and Neonatal Deaths { #223-stillbirths-and-neonatal-deaths } + +The section collects the data on neonatal deaths (occurring before the 28th day from birth) by age group (0-6d, 7-27d, unknown age) and by sex (male, female, other, unknown sex); and on stillbirths by gestational week (22-37w, 38-41w, 42+w, unknown age). The lower limit for the stillbirth gestational age has been set at 22 weeks as per international standards. If any other national guidelines have different thresholds (e.g. 20 weeks) the lower threshold can be changed accordingly. + +![Stillbirths and Neonatal Deaths](resources/images/chis-crvs-y-003.png) + +### 2.2.4. Child Deaths { #224-child-deaths } + +The section collects the data the deaths of children under up tp nine years of age by sex (male, female, other, unknown sex). + +![Child Deaths](resources/images/chis-crvs-y-004.png) + +### 2.2.5. Adolescent Deaths { #225-adolescent-deaths } + +The section collects the data on the deaths of adolescent by sex (male, female, other, unknown sex). + +![Adolescent Deaths](resources/images/chis-crvs-y-005.png) + +### 2.2.6. Adult Deaths { #226-adult-deaths } + +The section collects the data on the number of adult deaths by age groups (20-29y, 30-39y, 40-49y, 50-59y, 60-69y, 70-79y, 80+y, unknown age) and by sex (male, female, other, unknown sex). + +![Adult Deaths](resources/images/chis-crvs-y-005b.png) + +### 2.2.7. Deaths Due to Accidents { #227-deaths-due-to-accidents } + +The adult deaths can also be collected by cause in case there is the need to put the accent on accident-related deaths. The data can be disaggregated by age groups (20-29y, 30-39y, 40-49y, 50-59y, 60-69y, 70-79y, 80+y, unknown age) and by sex (male, female, other, unknown sex). +The causes can be adapted locally to better reflect the context and its leading causes. + +![Deaths Due to Accidents](resources/images/chis-crvs-y-005c.png) + +### 2.2.8. Birth and Death Registration { #228-birth-and-death-registration } + +The reports the numbers of births that have been reported and registered in the national CRVS by age (0-11m, 1-4y) and sex (male, female, other, unknown sex). The section also includes the totals for deaths reported and certified. + +![Birth and Death Registration](resources/images/chis-crvs-y-006.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the CRVS datasets: + +| name | instruction | operator | leftSide description | rightSide description | | +|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|---------------------------------------------------|---| +| CH - Children 0-4 y whose births are registered Vs Children 0-4 y screened for registration | Children 0-4 y whose births are registered should be less than or equal to Children 0-4 y screened | menor_que_o_igual_que | Children 0-4 y whose births are registered | Children aged 0-4 y screened birth registration | | +| CH - Deaths not registered notified local authorities Vs Deaths that were not registered | Deaths not registered notified local authorities should be less than or equal to Deaths that were not registered | menor_que_o_igual_que | Deaths not registered notified local authorities | Deaths that were not registered | | +| CH - Households with a death certificate for deaths Vs Households with death reported | Households with a death certificate for deaths should be less than or equal to Households with death reported | menor_que_o_igual_que | Households with a death certificate for deaths | Households with death reported | | +| CH - Live births delivered by age of mother Vs Live births delivered in the community | Live births delivered by age of mother should be less than or equal to Live births delivered in the community | menor_que_o_igual_que | Live births delivered by age of mother | Live births delivered in the community | | +| CH - Live births not reg but notified local authorities Vs Live births that were not registered | Live births not reg but notified local authorities should be less than or equal to Live births that were not registered | menor_que_o_igual_que | Live births not reg but notified local authorities | Live births that were not registered | | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the CRVS indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|--------------------------------------|---------------------------------------------------------------------------| +| CH002 - Live births delivered in the community | Number of live births | Live births delivered in the community | 1 | CH - Population composition, CH - Civil registration and vital statistics | +| CH044 - Pregnancy-related deaths | Number of pregnancy-related deaths | Pregnancy-related deaths | 1 | CH - Maternal Health, CH - Civil registration and vital statistics | +| CH045 - Stillbirths (late fetal deaths) | Number of stillbirths (late fetal deaths) in the community | Stillbirths | 1 | CH - Newborn Health, CH - Civil registration and vital statistics | +| CH046 - Neonatal deaths (0-27 days) | Number of neonatal deaths (0-27 days) in the community | Neonatal deaths (0-27 days) | 1 | CH - Newborn Health, CH - Civil registration and vital statistics | +| CH055 - Infant deaths (0-11 m) | Number of new infant deaths (0-11 m) | New infant deaths (0-11 m) | 1 | CH - Child Health, CH - Civil registration and vital statistics | +| CH056 - Child deaths (1-4 years) | Number of new child deaths (1-4 years) | New child deaths aged 1-4 years | 1 | CH - Child Health, CH - Civil registration and vital statistics | +| CH057 - Child deaths (5-9 years) | Number of new child deaths (5-9 years) | New child deaths aged 5-9 years | 1 | CH - Child Health, CH - Civil registration and vital statistics | +| CH082 - Young adolescent deaths (10-14 years old) | Number of new young adolescent deaths (10-14 years old) | New young adolescent aged 10-14 years deaths | 1 | CH - Adolescent Health, CH - Civil registration and vital statistics | +| CH083 - Older adolescent deaths (15-19 years) | Number of new older adolescent deaths (15-19 years) | New older adolescent aged 15-19 years deaths | 1 | CH - Adolescent Health, CH - Civil registration and vital statistics | +| CH158 - New adult deaths in the reporting period | Number of adult deaths | New adult deaths in the reporting period | 1 | CH - Civil registration and vital statistics | +| CH159 - Deaths due to road traffic crashes | Number of deaths due to road traffic crashes | Deaths due to road traffic crashes | 1 | CH - Civil registration and vital statistics | +| CH160 - Deaths due to drowning | Number of deaths due to drowning | Deaths due to drowning | 1 | CH - Civil registration and vital statistics | +| CH161b - Live births unregistered | Number of unregistered live births | Live births not reg | 1 | CH - Civil registration and vital statistics | +| CH161 - Live births with submitted notification unregistered (%) | Proportion of live births not registered for which notification was submitted by CHW to local authorities in the reporting period | Live births not reg but notified local authorities | Live births that were not registered | CH - Civil registration and vital statistics | +| CH162b - Deaths unregistered | Number of unregistered deaths | Deaths not registered | 1 | CH - Civil registration and vital statistics | +| CH162 - Deaths with submitted notification unregistered (%) | Proportion of deaths that were not registered for which notification was submitted by CHW to local authorities | Deaths not registered notified local authorities | Deaths that were not registered | CH - Civil registration and vital statistics | +| CH163 - Births (0-4 y) registered (%) | Proportion of children 0-4 yrs whose births are registered with the civil authority | Children (0-4 y) whose births are registered | Children (0-4 y) screened | CH - Civil registration and vital statistics | +| CH164 - Households with death certificates (%) | Proportion of deaths that were registered in a timely manner over the reporting period | Households with a death certificate for deaths | Households with death reported | CH - Civil registration and vital statistics | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Civil registration and vital statistics”. +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-crvs-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-crvs-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__clean-energy-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__clean-energy-md new file mode 100644 index 000000000..0f6ca3433 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__clean-energy-md @@ -0,0 +1,82 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_ene-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Clean Energy { #chis-agg-ene-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Clean energy (CE) module includes: + +1. A yearly dataset for the follow up of key annual information on Clean Energy +2. Core indicators for the dataset +3. A predefined “CH - Clean energy” dashboard + +It is recommended that the datasets get assigned to Organisation Units at the lowest level of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the CE module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the CE module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|---------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------|--------------------------------------------------| +| CH021 - Households relying on clean energy for cooking | Households with primary reliance on clean fuels and technologies for cooking | CH - Clean energy (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Clean energy | +| CH022 - Households relying on clean energy for lighting | Households with primary reliance on clean fuels and technologies for lighting | CH - Clean energy (Yearly) | CH - Clean energy | +| CH023 - Households relying on clean energy for heating | Households with primary reliance on clean fuels and technologies for heating | CH - Clean energy (Yearly) | CH - Clean energy | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Clean Energy { #21-clean-energy } + +The section is set to collect the information necessary to identify the different sources of energy used in the surveyed households for cooking, heating, and lighting. The cooking data are disaggregated by source (solar, electric stove, piped natural gas, biogas, LPG/cooking gas, liquid fuel, other). The heating data are disaggregated by type (central heating, cookstove, heat pump, other). The lighting data are disaggregated by source of power (electricity, solar power, rechargeable flashlight, mobile, torch/lantern, battery powered flashlight, biogas lamp, LPG lamp, other). + +![Clean Energy](resources/images/chis-ene-y-001.png) + +## 3. Validation Rules { #3-validation-rules } + +There are no validation rules configured for the Clean Energy module. + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the CE indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------|--------------------------------------------------| +| CH021b - Households relying on clean energy for cooking - Solar | Proportion of households with primary reliance on clean fuels and technologies for cooking - solar energy | HHs cooking with solar | 1 | CH - Clean energy | +| CH021c - Households relying on clean energy for cooking - Electric stove | Proportion of households with primary reliance on clean fuels and technologies for cooking - electric stove | HHs cooking with electric stove | 1 | CH - Clean energy | +| CH021d - Households relying on clean energy for cooking - Piped natural gas | Proportion of households with primary reliance on clean fuels and technologies for cooking - Piped natural gas | HHs cooking with Piped natural gas | 1 | CH - Clean energy | +| CH021e - Households relying on clean energy for cooking - Biogas | Proportion of households with primary reliance on clean fuels and technologies for cooking - Biogas | HHs cooking with Biogas | 1 | CH - Clean energy | +| CH021f - Households relying on clean energy for cooking - LPG | Proportion of households with primary reliance on clean fuels and technologies for cooking - LPG / cooking gas | HHs cooking with LPG | 1 | CH - Clean energy | +| CH021g - Households relying on clean energy for cooking - Liquid fuel | Proportion of households with primary reliance on clean fuels and technologies for cooking - Liquid fuel (not kerosene) | HHs cooking with Liquid fuel | 1 | CH - Clean energy | +| CH021h - Households relying on clean energy for cooking - Other | Proportion of households with primary reliance on clean fuels and technologies for cooking - Other | HHs cooking with other | 1 | CH - Clean energy | +| CH021 - Households relying on clean energy for cooking (%) | Proportion of households with primary reliance on clean fuels and technologies for cooking | HHs that rely on clean fuels and tech for cooking | Households in the catchment area | CH - Clean energy, CH - Noncommunicable diseases | +| CH022b - Households relying on clean energy for lighting - Electricity | Proportion of households with primary reliance on clean fuels and technologies for lighting - Electricity | HHs that rely on clean fuels and tech for lighting Electricity | 1 | CH - Clean energy | +| CH022c - Households relying on clean energy for lighting - Solar power | Proportion of households with primary reliance on clean fuels and technologies for lighting - Solar power | HHs that rely on clean fuels and tech for lighting Solar power | 1 | CH - Clean energy | +| CH022d - Households relying on clean energy for lighting - Rechargeable flashlight | Proportion of households with primary reliance on clean fuels and technologies for lighting - Rechargeable flashlight | HHs that rely on clean fuels and tech for lighting Rechargeable flashlight | 1 | CH - Clean energy | +| CH022e - Households relying on clean energy for lighting - Mobile | Proportion of households with primary reliance on clean fuels and technologies for lighting - Mobile | HHs that rely on clean fuels and tech for lighting Mobile | 1 | CH - Clean energy | +| CH022f - Households relying on clean energy for lighting - Torch or lantern | Proportion of households with primary reliance on clean fuels and technologies for lighting - Torch or lantern | HHs that rely on clean fuels and tech for lighting Torch or lantern | 1 | CH - Clean energy | +| CH022g - Households relying on clean energy for lighting - Battery-powered flashlight | Proportion of households with primary reliance on clean fuels and technologies for lighting - Battery-powered flashlight | HHs that rely on clean fuels and tech for lighting Battery-powered flashlight | 1 | CH - Clean energy | +| CH022h - Households relying on clean energy for lighting - Biogas lamp | Proportion of households with primary reliance on clean fuels and technologies for lighting - Biogas lamp | HHs that rely on clean fuels and tech for lighting Biogas lamp | 1 | CH - Clean energy | +| CH022 - Households relying on clean energy for lighting (%) | Proportion of households with primary reliance on clean fuels and technologies for lighting | HHs that rely on clean fuels and tech for lighting | Households in the catchment area | CH - Clean energy | +| CH022i - Households relying on clean energy for lighting - LPG lamp | Proportion of households with primary reliance on clean fuels and technologies for lighting - LPG lamp | HHs that rely on clean fuels and tech for lighting LPG lamp | 1 | CH - Clean energy | +| CH022l - Households relying on clean energy for lighting - Other | Proportion of households with primary reliance on clean fuels and technologies for lighting - Other | HHs that rely on clean fuels and tech for lighting Other | 1 | CH - Clean energy | +| CH023b - Households relying on clean energy for heating - Central heating | Number of households with primary reliance on clean fuels and technologies for heating - Central heating | HHs that rely on clean fuels and tech for heating - Central heating | 1 | CH - Clean energy | +| CH023c - Households relying on clean energy for heating - Stove | Number of households with primary reliance on clean fuels and technologies for heating - Stove | HHs that rely on clean fuels and tech for heating - stove | 1 | CH - Clean energy | +| CH023d - Households relying on clean energy for heating - Heat pump | Number of households with primary reliance on clean fuels and technologies for heating - Heat pump | HHs that rely on clean fuels and tech for heating -Heat pump | 1 | CH - Clean energy | +| CH023e - Households relying on clean energy for heating - Other | Number of households with primary reliance on clean fuels and technologies for heating - Other | HHs that rely on clean fuels and tech for heating -other | 1 | CH - Clean energy | +| CH023 - Households relying on clean energy for heating (%) | Proportion of households with primary reliance on clean fuels and technologies for heating | HHs that rely on clean fuels and tech for heating | Households in the catchment area | CH - Clean energy | +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Clean energy”. + +The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-ene-db-001.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__community-based-surveillance-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__community-based-surveillance-md new file mode 100644 index 000000000..790362794 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__community-based-surveillance-md @@ -0,0 +1,75 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_cbs-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Community-based surveillance (CBS) { #chis-agg-cbs-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Community-based surveillance module includes: + +1. A **monthly dataset** with key data elements for CBS +2. **Core indicators** for the dataset +3. A predefined **“CH - Community-based surveillance” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +## 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the CBS module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. In this case, the CBS DEs are not shared with any other module. + +All the DEs in the CBS module are used in the build up of indicators. + +| Nombre | Descripción | Disaggregation | Data Sets | Data Element Groups | | +|----------------------------------------------|-----------------------------------------------------------------------------------------------|----------------|---------------------------------------------|-----------------------------------|---| +| CH173a - Events/alert case detected | Events/alert case detected | default | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | | +| CH173b - Events/alert case detected referred | Events/alert case detected referred | default | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | | +| CH174a - CBS alerts with timely response | CBS alerts responded to within 24 hours or within specified time period from the CBS protocol | default | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | | +| CH174b - CBS alerts | CBS alerts | default | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | | +| CH175a - Communities in action after alerts | Communities in which action was taken following an alert (per month) | default | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | | +| CH175b - Communities with alert(s) | Communities in which there was at least an alert (per month) | default | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | | + +## 2. Datasets Details { #2-datasets-details } + +### 2.1. CBS Dataset { #21-cbs-dataset } + +The section is set to collect the information necessary to monitor the knowledge and reactivity of the community for alerts and events. + +![CBS](resources/images/chis-cbs-m-001.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the CBS datasets: + +| Nombre | Descripción | Datasets | DE groups | +|----------------------------------------------|-----------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------| +| CH173a - Events/alert case detected | Events/alert case detected | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | +| CH173b - Events/alert case detected referred | Events/alert case detected referred | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | +| CH174a - CBS alerts with timely response | CBS alerts responded to within 24 hours or within specified time period from the CBS protocol | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | +| CH174b - CBS alerts | CBS alerts | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | +| CH175a - Communities in action after alerts | Communities in which action was taken following an alert (per month) | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | +| CH175b - Communities with alert(s) | Communities in which there was at least an alert (per month) | CH - Community-based surveillance (Monthly) | CH - Community-based surveillance | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the CBS indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------------------------|---------------------------------------|-----------------------------------| +| CH173 - Events/alert case detected | Number of events/alert case detected | Events/alert case detected | 1 | CH - Community-based surveillance | +| CH174b - CBS alerts | Number of CBS alerts | Alerts | 1 | CH - Community-based surveillance | +| CH175b - Communities with alerts | Number of communities with alerts | Communities with alerts | 1 | CH - Community-based surveillance | +| CH175 - Communities in action after alerts (%) | Proportion of communities in which action was taken following an alert (per month) | Communities with action was taken after an alert | Communities with 1+ alert (per month) | CH - Community-based surveillance | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Community-based surveillance”. + +The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. +![Dashboard](resources/images/chis-cbs-db-001.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__immunization-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__immunization-md new file mode 100644 index 000000000..65783ab70 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__immunization-md @@ -0,0 +1,116 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_epi-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Immunization { #chis-agg-epi-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Immunization module includes: + +1. A **monthly dataset** with key data elements for Immunization +2. A **yearly dataset** for the follow up of key annual information on Immunization activities +3. **Core indicators** for both datasets +4. A predefined **“CH - Immunization” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +## 1.2. Data elements { #12-data-elements } + +The table below summarizes the data elements present in the Immunization module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the Immunization module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|------------------------------| +| CH095a - People not up to date with vaccinations referred | Persons who are not up to date with immunizations and referred | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH095b - People checked for vaccination | People checked for vaccination for vaccination completion | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH095c - Women not up to date with vaccinations referred | Women not up to date with vaccinations referred | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH095d - Pregnant women checked for vaccination | Pregnant women checked for vaccination completion | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH096a - Unvaccinated children (0-4 y) referred | Children 0-4 years whose parents state they have never been vaccinated, and who are referred | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH096b - Children (0-4 y) checked for vaccination | Children (0-4 y) checked for vaccination completion | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH100a - Children (0-23 m) with Polio vaccination | Eligible children 0-23 mears who received routine requested doses of polio vaccine according to national schedule | CH - ICCM (Monthly), CH - Immunization (Monthly) | CH - Immunization, CH - ICCM | +| CH100b - Children (0-23 m) eligible for OPV in the target population | Children (0-23 m) eligible for OPV in the target population | CH - ICCM (Monthly), CH - Immunization (Monthly) | CH - Immunization, CH - ICCM | +| CH097a - Neonates with signs and symptoms of tetanus | Neonates with signs and symptoms of tetanus | CH - Immunization (Monthly) | CH - Immunization | +| CH097b - Neonates with confirmed signs and symptoms of tetanus | Neonates with confirmed signs and symptoms of tetanus | CH - Immunization (Monthly) | CH - Immunization | +| CH098a - Children (0-14 y) suspected of AFP | Children < 15 years of age with suspicion of acute flaccid paralysis | CH - Immunization (Monthly) | CH - Immunization | +| CH098b - Children (0-14 y) suspected of AFP referred | Children < 15 years of age with suspicion of acute flaccid paralysis referred | CH - Immunization (Monthly) | CH - Immunization | +| CH099a - People with signs and symptoms of measles or rubella | People with signs and symptoms of measles or measles rubella | CH - Immunization (Monthly) | CH - Immunization | +| CH099b - People with signs of measles or rubella referred | People with signs of measles or rubella referred | CH - Immunization (Monthly) | CH - Immunization | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly Immunization Dataset { #21-monthly-immunization-dataset } + +#### 2.1.1. Neonatal Tetanus { #211-neonatal-tetanus } + +The section is set to collect the basic information on newborns showing danger signs of NNT by outcome (dead or alive). + +![Neonatal Tetanus](resources/images/chis-epi-m-001.png) + +#### 2.1.2. Measles and Rubella { #212-measles-and-rubella } + +The section is set to collect the basic information on children <15 years of age suffering from danger signs of measles and/or rubella by age groups (0-4y. 5-9y, 10-14y, unknown age). + +![Measles and Rubella](resources/images/chis-epi-m-002.png) + +#### 2.1.3. Acute Flaccid Paralysis { #213-acute-flaccid-paralysis } + +The section collects data on signs of AFP among children under the age of 15 years by age groups (0-4y. 5-9y, 10-14y, unknown age). + +![Acute Flaccid Paralysis](resources/images/chis-epi-m-003.png) + +#### 2.1.4. OPV { #214-opv } + +The section collects data on the type of polio vaccine and the doses administered to eligible children under the age of 2 by type of OPV and dose (0 to 4). + +![OPV](resources/images/chis-epi-m-004.png) + +### 2.2.Yearly Immunization Dataset { #22yearly-immunization-dataset } + +#### 2.2.1. Incomplete Immunization Schedule { #221-incomplete-immunization-schedule } + +The section collects the data on children under 5 years of age (0-11m, 1-4y), people above the age of 5, and pregnant women whose vaccination schedule is not up to date according to their national guideline. + +![OPV](resources/images/chis-epi-y-001.png) + +## 3. Validation Rules { #3-validation-rules } + +There are no validation rules set up for the Immunization datasets. + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the Immunization indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|--------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|---------------------------------------------------------|------------------------------------------------| +| CH003 - Infants aged 0-11 months in the catchment area | Number of infants in the catchment area (0 to less than 1 year old) | Infants aged 0-11 months in the catchment area | 1 | CH - Immunization, CH - Population composition | +| CH004 - Children aged 1-4 years in the catchment area | Number of children in the catchment area (1 to less than 5 years old) | Children aged 1-4 years in the catchment area | 1 | CH - Immunization, CH - Population composition | +| CH095 - Referred people not up to date with vaccinations (%) | Proportion of persons who are not up to date with immunizations and are referred | Not up to date with immunizations and referred | Persons who have been checked | CH - Immunization, CH - ICCM | +| CH096b - Children (0-4 y) unvaccinated | Number of Children (0-4 y) whose parents state they have never been vaccinated | Children (0-4 y) never vaccinated | 1 | CH - Immunization | +| CH096 - Children (0-4 y) unvaccinated referred (%) | Proportion of Children 0-4 yrs whose parents state they have never been vaccinated, and who are referred | Children (0-4 y) never vaccinated and referred | Children (0-4 y) who have been checked for vaccination | CH - Immunization, CH - ICCM | +| CH097 - Neonates with signs and symptoms of tetanus | Detection and reporting of neonatal tetanus | Neonates with signs and symptoms of tetanus | 1 | CH - Immunization | +| CH098 - Children (0-14 y) suspected of AFP | Detection and reporting of acute flaccid paralysis among children (0-4 y) | Children (0-14 y) with signs of AFP | 1 | CH - Immunization | +| CH099 - People with signs and symptoms of measles / rubella | Detection and reporting of rash and fever for measles or measles/rubella | Persons with signs of measles or measles rubella | 1 | CH - Immunization | +| CH100b - Children (0-23 y) eligible for Polio vaccine | Number of eligible children 0-23 y for polio vaccine according to national schedule | Children 0-23 m | 1 | CH - Immunization | +| CH100 - Children (0-59 m) vaccinated for polio (%) | Proportion of eligible children (0-59 m) who received routine requested doses of polio vaccine according to national schedule | Children (0-59 m) who given routine doses of polio | Children (0-59 m) in the target population | CH - Immunization, CH - ICCM | + +## 6. Dashboards { #6-dashboards } + +The module includes a predefined dashboard called “CH - Immunization”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-epi-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined items analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-epi-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__integrated-community-case-management-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__integrated-community-case-management-md new file mode 100644 index 000000000..81195d04d --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__integrated-community-case-management-md @@ -0,0 +1,243 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_iccm-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Integrated community case management (ICCM) { #chis-agg--iccm-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - ICCM module includes: + +1. A **monthly dataset** with key data elements for ICCM +2. **Core indicators** for both datasets +3. A predefined **“CH - ICCM” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the ICCM module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the ICCM module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| CH028a - HIV positive tests returned | HIV tests conducted in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028b - HIV tests returned | HIV tests returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028c - HIV positive tests returned to key population | HIV tests conducted amongst key population in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028d - HIV tests returned to key population | HIV tests performed amongst key population where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028e - HIV positive tests returned to TB patients | HIV tests conducted amongst TB in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028f - HIV tests returned to TB patients | HIV tests performed amongst TB where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH052a - Newborns and children with danger signs | Newborns and children with danger signs in the community | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH052b - Newborns and children with danger signs referred | Newborns and children with danger signs referred | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH052c - Newborns and children consultations in the community | Newborns and children consultations in the community | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH063a - Children (6-59m) with SAM | Children aged 6-59 months with severe acute malnutrition | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH063b - Children (6-59m) assessed for SAM | Children aged 6-59 months screened for severe acute malnutrition | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH063c - Children (6-59m) with SAM referred | Children aged 6-59 months with severe acute malnutrition referred | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH070a - Children (0-9 y) treated for diarrhoea | Children aged 0-9 years presenting with diarrhoea who received treatment | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH070b - Children (0-9 y) assessed for diarrhoea | Children aged 0-9 years presenting with diarrhoea assessed by CHW | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Nutrition (Monthly) | CH - ICCM, CH - Nutrition, CH - Child Health | +| CH071a - Children with fast breathing and/or chest indrawing | Children with fast breathing and/or chest indrawing | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH071b - Children with fast breathing and/or chest indrawing referred | Children with fast breathing and/or chest indrawing referred | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH071c - Children screened for fast breathing and/or chest indrawing | Children screened for fast breathing and/or chest indrawing | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH072 - Children with fast breathing and/or chest indrawing given ABX | Children presenting with fast breathing and/or chest indrawing who received antibiotic treatment from CHW | CH - Child Health (Monthly), CH - ICCM (Monthly) | CH - Child Health, CH - ICCM | +| CH079a - People (>18 m) referred for HIV testing | People (>18 m) referred for HIV testing | CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly) | CH - HIV, CH - ICCM, CH - Child Health | +| CH079b - People (>18 m) in the catchment area | People (>18 m) in the catchment area | CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly) | CH - HIV, CH - ICCM, CH - Child Health | +| CH095a - People not up to date with vaccinations referred | Persons who are not up to date with immunizations and referred | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH095b - People checked for vaccination | People checked for vaccination for vaccination completion | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH095c - Women not up to date with vaccinations referred | Women not up to date with vaccinations referred | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH095d - Pregnant women checked for vaccination | Pregnant women checked for vaccination completion | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH096a - Unvaccinated children (0-4 y) referred | Children 0-4 years whose parents state they have never been vaccinated, and who are referred | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH096b - Children (0-4 y) checked for vaccination | Children (0-4 y) checked for vaccination completion | CH - ICCM (Monthly), CH - Immunization (Yearly) | CH - Immunization, CH - ICCM | +| CH100a - Children (0-23 m) with Polio vaccination | Eligible children 0-23 mears who received routine requested doses of polio vaccine according to national schedule | CH - ICCM (Monthly), CH - Immunization (Monthly) | CH - Immunization, CH - ICCM | +| CH100b - Children (0-23 m) eligible for OPV in the target population | Children (0-23 m) eligible for OPV in the target population | CH - ICCM (Monthly), CH - Immunization (Monthly) | CH - Immunization, CH - ICCM | +| CH119a - Febrile cased tested by RDT | Febrile cases who received a RDT | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH119b - Febrile cases of malaria | Febrile cases of malaria | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH120a - Suspected cases tested by RDT | Suspected cases tested by RDT | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH120b - Suspected cases of malaria | Suspected cases of malaria | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH121c - Confirmed malaria cases by parasite | Confirmed malaria cases by parasite | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH121 - Confirmed malaria cases | Confirmed malaria cases | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH121d - Febrile cased tested by RDT by parasite | Febrile cased tested by RDT by parasite | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH122a - Malaria cases receiving first line anti-malarial | Patients with malaria who received first-line antimalarial treatment according to national policy | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH122b - Patients with malaria | Patients with malaria | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH123a - Children with confirmed malaria and danger signs referred | Children with confirmed malaria and danger signs referred | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH123b - Children with confirmed malaria and danger signs | Children with confirmed malaria and danger signs | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH124a - Children with malaria danger signs referred after administration of rectal artesunate | Children with malaria danger signs referred after administration of rectal artesunate | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH124b - Children with malaria danger signs | Children with malaria danger signs | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Child Health - Newborn { #21-child-health-newborn } + +The section is set to collect the information necessary to have a snapshot of the health of the children in the community. The table collects data on danger signs and the reactivity of the community upon those signs by age groups (0-27d, 28d-11m, 1-4y,5-9y unknown age). + +![Child Health - Newborn](resources/images/chis-iccm-m-001.png) + +### 2.2. Child Health - Nutrition { #22-child-health-nutrition } + +The section collects data on malnutrition by age groups (6-11m and 12-59m). + +![Child Health - Nutrition](resources/images/chis-iccm-m-002.png) + +### 2.3. Child Health - Diarrhoea { #23-child-health-diarrhoea } + +The section focuses on diarrhoea and rehydration by age group (0-4y, 5-9y) and its treatment (ORS, Zinc, both). + +![Child Health - Diarrhoea](resources/images/chis-iccm-m-003.png) + +### 2.4. Child Health - Fast Breathing { #24-child-health-fast-breathing } + +The section collects info on possible chest infections and respiratory problems by age groups (0-11m, 1-4y, 5-9y, unknown age) and symptoms (fast breathing, chest indrawing, both). + +![Child Health - Fast Breathing](resources/images/chis-iccm-m-004.png) + +### 2.5. Malaria - Suspected Cases Tested { #25-malaria-suspected-cases-tested } + +The section focuses on suspected and tested cases in the community by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age). + +![Suspected Cases Tested](resources/images/chis-iccm-m-005.png) + +### 2.6. Malaria - Febrile Cases Tested { #26-malaria-febrile-cases-tested } + +The section collects data about suspected febrile cases, tested cases, and confirmed cases of malaria. The info is disaggregated by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age). + +![Suspected Cases Tested](resources/images/chis-iccm-m-006.png) + +### 2.7. Malaria - Cases by Parasite { #27-malaria-cases-by-parasite } + +The malaria section could also be set up as the tables below, where the data are collected by Plasmodium spp. + +![Malaria - Cases by Parasite](resources/images/chis-iccm-m-007.png) + +### 2.8. Malaria - Treatment { #28-malaria-treatment } + +The cases in this table are tallied by type of case vs. treatment with first line antimalarials( combination of age groups - 0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age - and result - confirmed with RDT, suspected, febrile not confirmed). + +![Malaria - Treatment](resources/images/chis-iccm-m-008.png) + +### 2.9. Malaria - Danger Signs { #29-malaria-danger-signs } + +In this table there is a focus on children in the second table with danger signs and referrals of children up to the age of 9 years by age groups (0-11m, 1-4y, 5-9y, unknown age). + +![Malaria - Danger Signs](resources/images/chis-iccm-m-009.png) + +### 2.10. Immunization - Never Vaccinated { #210-immunization-never-vaccinated } + +The section focuses on children up to four years of age and on how many among the screened ones are completely unvaccinated. + +![Immunization - Never Vaccinated](resources/images/chis-iccm-m-010.png) + +### 2.11. Immunization - Not Up to Date { #211-immunization-not-up-to-date } + +The section collects the data for people and women who are not up to date with the vaccination calendar according to their stage of life and pregnancy. + +![Immunization - Not Up to Date](resources/images/chis-iccm-m-011.png) + +### 2.12. Immunization - Polio { #212-immunization-polio } + +The section monitors children up to 23 months and their Polio vaccinations status by OPV and dose (0 to 4). + +![Immunization - Polio](resources/images/chis-iccm-m-012.png) + +### 2.13. HIV Test - All { #213-hiv-test-all } + +The section reports core information on HIV-related activities. +The table gives an overview of the number of performed tests and positive results among all people tested. The data are disaggregated by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and sex (male, female, other, unknonw sex). + +![HIV Test - All](resources/images/chis-iccm-m-013.png) + +### 2.14. HIV Test - Key Population { #214-hiv-test-key-population } + +The table captures data for the key population groups at risk (MSM, SW, Prisoners, IDU, TG, Other). The categories should be adapted locally to better mirror the contexts and the activities. + +![HIV Test - Key Population](resources/images/chis-iccm-m-014.png) + +### 2.15. HIV Test - TB Cases { #215-hiv-test-tb-cases } + +The table gives the information among TB-confirmed and -presumptive patients. + +![HIV Test - TB Cases](resources/images/chis-iccm-m-015.png) + +### 2.16. HIV Test - Referrals { #216-hiv-test-referrals } + +The section focuses on all people above 18 months of age who are referred for HIV testing. The data are disaggregated by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and sex (male, female, other, unknonw sex). + +![HIV Test - Referrals](resources/images/chis-iccm-m-016.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the ICCM dataset. + +| name | instruction | operator | leftSide description | rightSide description | | +|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|------------------------------------------------------|---| +| CH - New HIV-positive result returned for TB Vs HIV tests performed amongst TB & results returned | New HIV-positive result returned for TB should be less than or equal to HIV tests performed amongst TB & results returned | menor_que_o_igual_que | New HIV-positive result returned for TB | HIV tests performed amongst TB & results returned | | +| CH - Children presenting fast breathing/chest indrawing Vs Children screened for fast breathing/ indrawing | Children presenting fast breathing/chest indrawing should be less than or equal to Children screened for fast breathing/ indrawing | menor_que_o_igual_que | Children presenting fast breathing/chest indrawing | Children screened for fast breathing/ indrawing | | +| CH - Received first-line antimalarial Tx Vs Patients with malaria | Received first-line antimalarial Tx should be less than or equal to Patients with malaria | menor_que_o_igual_que | Received first-line antimalarial Tx | Patients with malaria | | +| CH - Children 6-59 months with SAM referred Vs Children 6-59 months screened for SAM | Children 6-59 months with SAM referred should be less than or equal to Children 6-59 months screened for SAM | menor_que_o_igual_que | Children 6-59 months with SAM referred | Children 6-59 months screened for SAM | | +| CH - Given rectal artesunate and referred Vs Children with malaria danger signs | Given rectal artesunate and referred should be less than or equal to Children with malaria danger signs | menor_que_o_igual_que | Given rectal artesunate and referred | Children with malaria danger signs | | +| CH - PG not up to date with immunizations and referred Vs Not up to date with immunizations and referred | PG not up to date with immunizations and referred should be less than or equal to Not up to date with immunizations and referred | menor_que_o_igual_que | PG not up to date with immunizations and referred | Not up to date with immunizations and referred | | +| CH - New HIV-positive result returned for KP Vs HIV tests performed amongst KP & results returned | New HIV-positive result returned for KP should be less than or equal to HIV tests performed amongst KP & results returned | menor_que_o_igual_que | New HIV-positive result returned for KP | HIV tests performed amongst KP & results returned | | +| CH - Children with fast breathing/indrawing referred Vs Children presenting fast breathing/chest indrawing | Children with fast breathing/indrawing referred should be less than or equal to Children presenting fast breathing/chest indrawing | menor_que_o_igual_que | Children with fast breathing/indrawing referred | Children presenting fast breathing/chest indrawing | | +| CH - Not up to date with immunizations and referred Vs Persons who have been checked | Not up to date with immunizations and referred should be less than or equal to Persons who have been checked | menor_que_o_igual_que | Not up to date with immunizations and referred | Persons who have been checked | | +| CH - People >18 months who were referred for HIV test Vs People >18 months in the catchment area | People >18 months who were referred for HIV test should be less than or equal to People >18 months in the catchment area | menor_que_o_igual_que | People >18 months who were referred for HIV test | People >18 months in the catchment area | | +| CH - Children 6-59 months with SAM Vs Children 6-59 months screened for SAM | Children 6-59 months with SAM should be less than or equal to Children 6-59 months screened for SAM | menor_que_o_igual_que | Children 6-59 months with SAM | Children 6-59 months screened for SAM | | +| CH - Suspected cases who received a RDT Vs Suspected cases of malaria | Suspected cases who received a RDT should be less than or equal to Suspected cases of malaria | menor_que_o_igual_que | Suspected cases who received a RDT | Suspected cases of malaria | | +| CH - Children 0-23m who given routine doses of polio Vs Eligible children 0-23m in the target population | Children 0-23m who given routine doses of polio should be less than or equal to Eligible children 0-23m in the target population | menor_que_o_igual_que | Children 0-23m who given routine doses of polio | Children 0-23m eligible in the target population | | +| CH - Children with conf malaria & danger signs referred Vs Children with confirmed malaria and danger signs | Children with conf malaria & danger signs referred should be less than or equal to Children with confirmed malaria and danger signs | menor_que_o_igual_que | Children with conf malaria & danger signs referred | Children with confirmed malaria and danger signs | | +| CH - Newborns and children with danger signs referred Vs Newborns and children with danger signs | Newborns and children with danger signs referred should be less than or equal to Newborns and children with danger signs | menor_que_o_igual_que | Newborns and children with danger signs referred | Newborns and children with danger signs | | +| CH - HIV tests performed amongst TB & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst TB & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst TB & results returned | HIV tests performed where results were returned | | +| CH - Febrile cases who received a RDT Vs Febrile cases of malaria | Febrile cases who received a RDT should be less than or equal to Febrile cases of malaria | menor_que_o_igual_que | Febrile cases who received a RDT | Febrile cases of malaria | | +| CH - HIV tests performed amongst KP & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst KP & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst KP & results returned | HIV tests performed where results were returned | | +| CH - New HIV-positive result returned for TB Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for TB should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for TB | New HIV-positive result or diagnosis was returned | | +| CH - New HIV-positive result returned for KP Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for KP should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for KP | New HIV-positive result or diagnosis was returned | | +| CH - Newborns and children with danger signs Vs Newborns and children consultations in the community | Newborns and children with danger signs should be less than or equal to Newborns and children consultations in the community | menor_que_o_igual_que | Newborns and children with danger signs | Newborns and children consultations in the community | | +| CH - Children 0-9 years with diarrhoea who received tx Vs Children 0-9 y presenting diarrhoea assessed | Children 0-9 years with diarrhoea who received tx should be less than or equal to Children 0-9 y presenting diarrhoea assessed | menor_que_o_igual_que | Children 0-9 years with diarrhoea who received tx | Children 0-9 y presenting diarrhoea assessed | | +| CH - New HIV-positive result or diagnosis was returned Vs HIV tests performed where results were returned | New HIV-positive result or diagnosis was returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | | +| CH - Children 0-4 y never vaccinated and referred Vs Children 0-4 y who have been checked | Children 0-4 y never vaccinated and referred should be less than or equal to Children 0-4 y who have been checked | menor_que_o_igual_que | Children 0-4 y never vaccinated and referred | Children 0-4 y who have been checked for vaccination | | +| CH - Confirmed malaria cases by parasite Vs Confirmed malaria cases | Confirmed malaria cases by parasite should be less than or equal to Confirmed malaria cases | menor_que_o_igual_que | Confirmed malaria cases by parasite | Confirmed malaria cases | | +| CH - Confirmed malaria cases Vs Febrile cases who received a RDT by parasite | Confirmed malaria cases should be less than or equal to Febrile cases who received a RDT by parasite | menor_que_o_igual_que | Confirmed malaria cases | Febrile cases who received a RDT by parasite | | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the ICCM indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| CH028a - HIV tests with returned results | Number of HIV tests conducted and results returned | HIV tests performed where results were returned | 1 | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH028b - HIV +ve tests returned to people (%) | Proportion of HIV tests performed that were positive and results returned to people | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH052a - Newborns and children with danger signs referred (%) | Proportion of newborns and children referred with danger signs | Newborns and children with danger signs referred | Newborns and children with danger signs | CH - Newborn Health, CH - ICCM | +| CH052b - Newborns and children with danger signs (%) | Proportion of newborns and children with danger signs | Newborns and children with danger signs | Newborns and children consultations in the community | CH - Newborn Health, CH - ICCM | +| CH052c - Newborns and children consultations in the community | Newborns and children consultations in the community | Newborns and children consultations | 1 | CH - Newborn Health, CH - ICCM | +| CH052d - Newborns and children referred with danger signs | Number of newborns and children referred with danger signs | Newborns and children with danger signs referred | 1 | CH - Newborn Health, CH - ICCM | +| CH052e - Newborns and children with danger signs | Number of newborns and children with danger signs | Newborns and children with danger signs | 1 | CH - Child Health, CH - Newborn Health, CH - ICCM | +| CH063 - Children (6-59 m) assessed for SAM (%) | Proportion of children 6-59 months with severe acute malnutrition (SAM) | Children 6-59 months with SAM | Children 6-59 months screened for SAM | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH063 - Children (6-59 m) with SAM | Number of children 6-59 months with severe acute malnutrition (SAM) | Children 6-59 months with SAM | 1 | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH070b - Children (0-9 y) assessed for diarrhoea | Children (0-9 y) assessed for diarrhoea | Children (0-9 y) assessed for diarrhoea | 1 | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH070 - Children (0-9 y) treated for diarrhoea (%) | Proportion of children (0-9 years)who received treatment for diarrhoea | Children 0-9 years with diarrhoea who received tx | Children 0-9 yrs presenting diarrhoea assessed | CH - Nutrition, CH - Child Health, CH - ICCM | +| CH071 - Children with fast breathing and/or chest in-drawing (%) | Proportion of children presenting fast breathing and/or chest indrawing | Children presenting fast breathing/chest indrawing | Children screened for fast breathing/ indrawing | CH - Child Health, CH - ICCM | +| CH072 - Children receiving antibiotics for fast breathing and/or chest in-drawing (%) | Proportion of children receiving antibiotic treatment for fast breathing and/or chest indrawing | Fast breathing/chest indrawing given antibiotic TX | Children presenting fast breathing/chest indrawing | CH - Child Health, CH - ICCM | +| CH079 - People (>18 m) referred for HIV testing | Number of people above 18 months referred for HIV testing | People >18 months who were referred for HIV test | 1 | CH - HIV, CH - Child Health, CH - ICCM | +| CH095 - Referred people not up to date with vaccinations (%) | Proportion of persons who are not up to date with immunizations and are referred | Not up to date with immunizations and referred | Persons who have been checked | CH - Immunization, CH - ICCM | +| CH096 - Children (0-4 y) unvaccinated referred (%) | Proportion of Children 0-4 yrs whose parents state they have never been vaccinated, and who are referred | Children (0-4 y) never vaccinated and referred | Children (0-4 y) who have been checked for vaccination | CH - Immunization, CH - ICCM | +| CH100 - Children (0-59 m) vaccinated for polio (%) | Proportion of eligible children (0-59 m) who received routine requested doses of polio vaccine according to national schedule | Children (0-59 m) who given routine doses of polio | Children (0-59 m) in the target population | CH - Immunization, CH - ICCM | +| CH119b - Febrile cases of malaria | Febrile cases of malaria | Febrile cases | 1 | CH - ICCM, CH - Malaria | +| CH119 - Febrile cased tested by RDT (%) | Proportion of febrile cases who received a rapid diagnostic test (RDT) | Febrile cases who received a RDT | Febrile cases of malaria | CH - ICCM, CH - Malaria | +| CH120b - Suspected cases of malaria | Suspected cases of malaria | Suspected cases | 1 | CH - ICCM, CH - Malaria | +| CH120 - Suspected cases tested by RDT (%) | Proportion of suspected cases who received a RDT | Suspected cases who received a RDT | Suspected cases of malaria | CH - ICCM, CH - Malaria | +| CH121b - Confirmed malaria cases | Number of confirmed malaria cases | Confirmed malaria cases | 1 | CH - ICCM, CH - Malaria | +| CH121 - Malaria RDT positivity rate(%) | Malaria RDT positivity rate | Confirmed malaria cases | Febrile cased tested by RDT | CH - ICCM, CH - Malaria | +| CH122 - Malaria cases receiving first line anti-malarial (%) | Proportion of patients with malaria who received first-line antimalarial treatment according to national policy | Received first-line antimalarial Tx | Patients with malaria | CH - ICCM, CH - Malaria | +| CH123 - Children referred with danger signs (%) | Proportion of children with confirmed malaria and danger signs who are referred | Children with conf malaria & danger signs referred | Children with confirmed malaria and danger signs | CH - ICCM, CH - Malaria | +| CH124 - Suspected children referred after rectal Artesunate (%) | Proportion of children with malaria danger signs referred after administration of rectal artesunate | Given rectal artesunate and referred | Children with malaria danger signs | CH - ICCM, CH - Malaria | +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - ICCM”. + +The predefined items analyse and visualize the main areas of the dataset by section, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-iccm-db-001.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__malaria-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__malaria-md new file mode 100644 index 000000000..59818408e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__malaria-md @@ -0,0 +1,176 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_mal-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Malaria { #chis-agg-mal-design } + +## 1.Datasets { #1datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Malaria module includes: + +1. A **monthly dataset** with key data elements for malaria +2. A **yearly dataset** for the follow up of key annual information on malaria +3. **Core indicators** for both datasets +4. A predefined **“CH - Malaria” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the Malaria module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the Malaria module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|---------------------------------------------|-------------------------| +| CH119a - Febrile cased tested by RDT | Febrile cases who received a RDT | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH119b - Febrile cases of malaria | Febrile cases of malaria | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH120a - Suspected cases tested by RDT | Suspected cases tested by RDT | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH120b - Suspected cases of malaria | Suspected cases of malaria | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH121c - Confirmed malaria cases by parasite | Confirmed malaria cases by parasite | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH121 - Confirmed malaria cases | Confirmed malaria cases | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH121d - Febrile cased tested by RDT by parasite | Febrile cased tested by RDT by parasite | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH122a - Malaria cases receiving first line anti-malarial | Patients with malaria who received first-line antimalarial treatment according to national policy | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH122b - Patients with malaria | Patients with malaria | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH123a - Children with confirmed malaria and danger signs referred | Children with confirmed malaria and danger signs referred | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH123b - Children with confirmed malaria and danger signs | Children with confirmed malaria and danger signs | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH124a - Children with malaria danger signs referred after administration of rectal artesunate | Children with malaria danger signs referred after administration of rectal artesunate | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH124b - Children with malaria danger signs | Children with malaria danger signs | CH - ICCM (Monthly), CH - Malaria (Monthly) | CH - Malaria, CH - ICCM | +| CH125 - Pregnant women having received IPTp | Pregnant women having received IPTp | CH - Malaria (Monthly) | CH - Malaria | +| CH113a - Children (0-4 y) reporting fever in the last two weeks | Children (0-4 y) reporting fever in the last two weeks | CH - Malaria (Yearly) | CH - Malaria | +| CH114 - Households with at least one ITN | Households with at least one ITN | CH - Malaria (Yearly) | CH - Malaria | +| CH115a - Households with at least one ITN for every two persons | Households with at least one ITN for every two persons | CH - Malaria (Yearly) | CH - Malaria | +| CH115b - Total individuals who live in the household | Total individuals who live in the household | CH - Malaria (Yearly) | CH - Malaria | +| CH116a - People sleeping under an ITN the previous night | Individuals stating they slept under an ITN the previous night | CH - Malaria (Yearly) | CH - Malaria | +| CH116b - Individuals sleeping in the household | Individuals sleeping in the household | CH - Malaria (Yearly) | CH - Malaria | +| CH117 - People living in an IRS-sprayed house | Individuals stating they live in a house sprayed by IRS in the previous 12 months | CH - Malaria (Yearly) | CH - Malaria | +| CH118 - ITNs distributed | ITNs distributed | CH - Malaria (Yearly) | CH - Malaria | +| CH126 - Children (3-59 m) given SMC in transmission season | Children aged 3-59 months who received courses of SMC in a transmission season | CH - Malaria (Yearly) | CH - Malaria | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly Malaria Dataset { #21-monthly-malaria-dataset } + +#### 2.1.1. Suspected Cases Tested { #211-suspected-cases-tested } + +This section provides a summary of the data on suspected and tested cases in the community by age group (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age). + +![Suspected Cases Tested](resources/images/chis-mal-m-001.png) + +#### 2.1.2. Febrile Cases Tested { #212-febrile-cases-tested } + +The section reports the febrile cases and those tested for malaria by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age). + +![Febrile Cases Tested](resources/images/chis-mal-m-001b.png) + +#### 2.1.3. Cases by Parasite { #213-cases-by-parasite } + +The section collects the data on tested and confirmed cases by Plasmodium spp. + +![Cases by Parasite](resources/images/chis-mal-m-001c.png) + +#### 2.1.4. Treatment { #214-treatment } + +The section collects the cases of the patients who received a first-line treatment. The data are disaggregated with combination of age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age) and result (confirmed with RDT, suspected, febrile not confirmed). + +![Treatment](resources/images/chis-mal-m-001d.png) + +#### 2.1.5. Confirmed Cases { #215-confirmed-cases } + +The section presents the total numbers of confirmed cases by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age). + +![Confirmed Cases](resources/images/chis-mal-m-001e.png) + +#### 2.1.6. Danger Signs { #216-danger-signs } + +The section collects data on danger signs among children up to 9 years of age by age groups (0-11m, 1-4y, 5-9y unknown age). + +![Danger Signs](resources/images/chis-mal-m-002.png) + +#### 2.1.7. IPTp for Pregnant Women { #217-iptp-for-pregnant-women } + +A quick data collection tally for pregnant women receiving preventing chemoprophylaxis by age groups (10-14y, 15-19y, 20+, unknown age) and doses (0 to 4). + +![Danger Signs](resources/images/chis-mal-m-003.png) + +### 2.2. Yearly Malaria Dataset { #22-yearly-malaria-dataset } + +#### 2.2.1. Fever { #221-fever } + +A simple count of children with fever in the past two weeks by age groups (0-11 months and 1-4 years) + +![Fever](resources/images/chis-mal-y-001.png) + +#### 2.2.2. Insecticide treated net (ITN) { #222-insecticide-treated-net-itn } + +The section provides a general overview of the availability and the use of ITNs in the community. + +![Insecticide treated net (ITN)](resources/images/chis-mal-y-002.png) + +#### 2.2.3. Seasonal Malaria Chemoprevention { #223-seasonal-malaria-chemoprevention } + +The section tallies the number of children under the age of 5 years to whom the SMC has been distributed. The data is disaggregated by dose (0 to 4). + +![Seasonal Malaria Chemoprevention](resources/images/chis-mal-y-003.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Malaria datasets: + +| Nombre | Instrucción | Operador | Left side | Right side | +|:-----------------------------------------------------------------------------------------------------------:|:-----------------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:--------------------------------------------------:|:------------------------------------------------:| +| CH - Children with conf malaria & danger signs referred Vs Children with confirmed malaria and danger signs | Children with conf malaria & danger signs referred should be less than or equal to Children with confirmed malaria and danger signs | menor_que_o_igual_que | Children with conf malaria & danger signs referred | Children with confirmed malaria and danger signs | +| CH - Confirmed malaria cases by parasite Vs Confirmed malaria cases | Confirmed malaria cases by parasite should be less than or equal to Confirmed malaria cases | menor_que_o_igual_que | Confirmed malaria cases by parasite | Confirmed malaria cases | +| CH - Confirmed malaria cases Vs Febrile cases who received a RDT by parasite | Confirmed malaria cases should be less than or equal to Febrile cases who received a RDT by parasite | menor_que_o_igual_que | Confirmed malaria cases | Febrile cases who received a RDT by parasite | +| CH - Febrile cases who received a RDT Vs Febrile cases of malaria | Febrile cases who received a RDT should be less than or equal to Febrile cases of malaria | menor_que_o_igual_que | Febrile cases who received a RDT | Febrile cases of malaria | +| CH - Given rectal artesunate and referred Vs Children with malaria danger signs | Given rectal artesunate and referred should be less than or equal to Children with malaria danger signs | menor_que_o_igual_que | Given rectal artesunate and referred | Children with malaria danger signs | +| CH - HHs with at least one ITN for every two persons Vs Individuals who live in the household | HHs with at least one ITN for every two persons should be less than or equal to Individuals who live in the household | menor_que_o_igual_que | HHs with at least one ITN for every two persons | Individuals who live in the household | +| CH - People who live in a house sprayed by IRS Vs Individuals who live in the household | People who live in a house sprayed by IRS should be less than or equal to Individuals who live in the household | menor_que_o_igual_que | People who live in a house sprayed by IRS | Individuals who live in the household | +| CH - Received first-line antimalarial Tx Vs Patients with malaria | Received first-line antimalarial Tx should be less than or equal to Patients with malaria | menor_que_o_igual_que | Received first-line antimalarial Tx | Patients with malaria | +| CH - Slept under an ITN the previous night Vs Individuals in the households visited | Slept under an ITN the previous night should be less than or equal to Individuals in the households visited | menor_que_o_igual_que | Slept under an ITN the previous night | Individuals in the households visited | +| CH - Suspected cases who received a RDT Vs Suspected cases of malaria | Suspected cases who received a RDT should be less than or equal to Suspected cases of malaria | menor_que_o_igual_que | Suspected cases who received a RDT | Suspected cases of malaria | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the malaria indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|--------------------------------------------------|-------------------------| +| CH113a - Children (0-4 y) reporting fever in the last two weeks (%) | Proportion of children 0-4 yrs who had fever in the last two weeks | Children (0-4 y) had fever in the last two weeks | Children (0-4 y) in the catchment area | CH - Malaria | +| CH113b - Children (0-4 y) reporting fever in the last two weeks | Number of children under 5 who had fever in the last two weeks | Children <5 years had fever in the last two weeks | 1 | CH - Malaria | +| CH114 - Households with at least one ITN (%) | Proportion of households with at least one insecticide-treated nets (ITN) | Households with at least one ITN | Households in the catchment area | CH - Malaria | +| CH115 - Households with at least one ITN for every two persons (%) | Proportion of households with at least one ITN for every two persons | HHs with at least one ITN for every two persons | Totalindividuals who live in the household | CH - Malaria | +| CH116 - People sleeping under an ITN the previous night (%) | Proportion of population who slept under an ITN the previous night | Slept under an ITN the previous night | Individuals in the households visited | CH - Malaria | +| CH117 - People living in an IRS-sprayed house (%) | Proportion of population living in a house sprayed by IRS in the previous 12 months | People who live in a house sprayed by IRS | Total individuals who live in the household | CH - Malaria | +| CH118 - ITNs distributed | Number of ITNs distributed by CHWs | ITNs distributed | 1 | CH - Malaria | +| CH119b - Febrile cases of malaria | Febrile cases of malaria | Febrile cases | 1 | CH - ICCM, CH - Malaria | +| CH119 - Febrile cased tested by RDT (%) | Proportion of febrile cases who received a rapid diagnostic test (RDT) | Febrile cases who received a RDT | Febrile cases of malaria | CH - ICCM, CH - Malaria | +| CH120b - Suspected cases of malaria | Suspected cases of malaria | Suspected cases | 1 | CH - ICCM, CH - Malaria | +| CH120 - Suspected cases tested by RDT (%) | Proportion of suspected cases who received a RDT | Suspected cases who received a RDT | Suspected cases of malaria | CH - ICCM, CH - Malaria | +| CH121b - Confirmed malaria cases | Number of confirmed malaria cases | Confirmed malaria cases | 1 | CH - ICCM, CH - Malaria | +| CH121 - Malaria RDT positivity rate(%) | Malaria RDT positivity rate | Confirmed malaria cases | Febrile cased tested by RDT | CH - ICCM, CH - Malaria | +| CH122 - Malaria cases receiving first line anti-malarial (%) | Proportion of patients with malaria who received first-line antimalarial treatment according to national policy | Received first-line antimalarial Tx | Patients with malaria | CH - ICCM, CH - Malaria | +| CH123 - Children referred with danger signs (%) | Proportion of children with confirmed malaria and danger signs who are referred | Children with conf malaria & danger signs referred | Children with confirmed malaria and danger signs | CH - ICCM, CH - Malaria | +| CH124 - Suspected children referred after rectal Artesunate (%) | Proportion of children with malaria danger signs referred after administration of rectal artesunate | Given rectal artesunate and referred | Children with malaria danger signs | CH - ICCM, CH - Malaria | +| CH125 - Pregnant women having received IPTp | Number of pregnant women who have received zero/one/two/three or more doses of intermittent preventive treatment of malaria in pregnancy (IPTp) | Pregnant women who have received doses of IPTp | 1 | CH - Malaria | +| CH126 - Children (3-59 m) given SMC in transmission season | Number of children aged 3-59 months who received zero/one/two/three/four or more courses of seasonal malaria chemoprevention (SMC) in a transmission season | Children 3-59 mos given SMC in a transm season | 1 | CH - Malaria | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Malaria”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data the activities present in the different sections of the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-mal-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-mal-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__maternal-health-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__maternal-health-md new file mode 100644 index 000000000..d2da76b68 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__maternal-health-md @@ -0,0 +1,248 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_mat-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Maternal Health { #chis-agg-mat-design } + +## 1.Datasets { #1datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Maternal Health (MatH) module includes: + +1. A **monthly dataset** with key data elements for adolescent health +2. A **yearly dataset** for the follow up of key annual information on adolescent health +3. **Core indicators** for both datasets +4. A predefined **“CH - Maternal Health”** dashboard + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +## 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the MatH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the MatH module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH041a - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/ MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041b - People with possible MNS symptoms | People with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041c - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/mental health conditions by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041d - People with possible MNS symptoms | People with possible symptoms of MNS conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041e - Women assessed for MNS disorders/ MH conditions | Women and adolescent girls assessed for MNS disorders / MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041f - Women with possible MNS symptoms | Women and adolescent girls with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042a - People with MNS disorders referred | People with MNS disorders referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042b - People with MNS disorders referred by type | People with MNS disorders referred by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042c - Women with MNS disorders referred | Women and adolescent girls with MNS disorders/mental health conditions referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH028a - HIV positive tests returned | HIV tests conducted in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028b - HIV tests returned | HIV tests returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028c - HIV positive tests returned to key population | HIV tests conducted amongst key population in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028d - HIV tests returned to key population | HIV tests performed amongst key population where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028e - HIV positive tests returned to TB patients | HIV tests conducted amongst TB in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028f - HIV tests returned to TB patients | HIV tests performed amongst TB where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH043a - People with MNS disorders receiving services | People with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043b - People assessed for MNS disorders | People assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043c - People with MNS disorders receiving services - MH awareness | People with MNS disorders/mental health conditions receiving services - mental health awareness | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043d - People with MNS disorders receiving services - MH HP | People with MNS disorders/mental health conditions receiving services - mental health promotion and prevention | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043e - People with MNS disorders receiving services - MH support | People with MNS disorders/mental health conditions receiving services - support for people with mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043f - People with MNS disorders receiving services - recovery/rehab | People with MNS disorders/mental health conditions receiving services - recovery and rehabilitation | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043g - Women with MNS disorders receiving services | Women and adolescent girls with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043h - Women assessed for MNS disorders | Women and adolescent girls assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH044a - Deaths pregnancy-related - during pregnancy | Deaths pregnancy-related - during pregnancy | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH044b - Deaths pregnancy-related - facility delivery | New pregnancy-related deaths during childbirth at facility | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH044c - Deaths pregnancy-related - community delivery | New pregnancy-related deaths during childbirth at community | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH044d - Deaths pregnancy-related - 2m pre/post delivery | New pregnancy-related deaths within two months of delivery or end of pregnancy | CH - Civil registration and vital statistics (Yearly), CH - Maternal Health (Yearly) | CH - Civil registration and vital statistics, CH - Maternal Health | +| CH030a - Women tested for syphilis - 1st ANC | Women attending 1st ANC visit provided by CHW who were tested for syphilis | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH030b - Women tested for syphilis by CHW - 1st ANC | Women tested for syphilis by CHW - 1st ANC | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH030c - Women tested for syphilis - 2nd+ ANC | Women attending other ANC visits provided by CHW who were tested for syphilis | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH030d - Women tested for syphilis by CHW - 2nd+ ANC | Women attending other ANC visits provided by CHW | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH035a - Pregnant women who have 1st ANC contact with CHW during first trimester | Pregnant women who have 1st ANC contact with CHW during first trimester | CH - Maternal Health (Monthly) | CH - Maternal Health | +| CH035b - Women with at least one ANC CHW visit | Pregnant women who have had at least one ANC contact with CHW | CH - Maternal Health (Monthly) | CH - Maternal Health | +| CH036a - Community ANC contacts | Community ANC contacts | CH - Maternal Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Maternal Health | +| CH036b - Pregnant women counseled on breastfeeding during ANC contact | Community ANC contacts where pregnant women received any breastfeeding counselling | CH - Maternal Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Maternal Health | +| CH037 - Women given iron supplements during ANC | Community ANC contacts during which pregnant women were given/prescribed iron-containing supplements | CH - Maternal Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Maternal Health | +| CH039a - Pregnant women referred for maternal complications during ANC | Women and adolescent girls referred for maternal complications during antenatal care | CH - Maternal Health (Monthly) | CH - Maternal Health | +| CH039b - Pregnant women referred for maternal complications during labour/delivery | Women and adolescent girls referred for maternal complications during labour and delivery | CH - Maternal Health (Monthly) | CH - Maternal Health | +| CH039c - Pregnant women referred for maternal complications during postpartum | Women and adolescent girls referred for maternal complications during postpartum care | CH - Maternal Health (Monthly) | CH - Maternal Health | +| CH040a - Women given postpartum uteronic after delivery without SBA | Women and adolescent girls who gave birth in the community without SBA and given immediate oral postpartum uterotonic | CH - Maternal Health (Monthly) | CH - Maternal Health | +| CH038a - People with measured raised blood pressure | People with measured raised blood pressure | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | +| CH038b - Women with measured raised blood pressure - ANC | Women and adolescent girls with measured raised blood pressure during antenatal care | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | +| CH038c - Women with measured raised blood pressure - delivery | Women and adolescent girls with measured raised blood pressure during labour and delivery | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | +| CH038d - Women with high blood pressure - postpartum | Women and adolescent girls with measured raised blood pressure during postpartum care | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly Maternal Health Dataset { #21-monthly-maternal-health-dataset } + +#### 2.1.1. Syphilis Screening at ANC { #211-syphilis-screening-at-anc } + +The section collects data on syphilis screening during ANC visits (first or subsequents). The disaggregation is by age groups (10-14 y, 15-19 y, 20+ y and unknown age) + +![Syphilis Screening at ANC](resources/images/chis-mat-m-001.png) + +#### 2.1.2. ANC Contacts { #212-anc-contacts } + +The section collects data on the degree of contacts with mothers-to-be for general ANC visits, breastfeeding counselling, and Fe prescriptions. The disaggregation of the data on ANC visits is by age groups (10-14 y, 15-19 y, 20+ y and unknown age). + +![ANC Contacts](resources/images/chis-mat-m-002.png) + +#### 2.1.3. Maternal Complications { #213-maternal-complications } + +The data collected in this section are a simple overview of maternal complications. Firstly is about women receiving uteronics by age groups (10-14 y, 15-19 y, 20+ y and unknown age) and by uteronic (Misoprostol or other - this should be adapted locally depending on the used products), and on the pregnancy stage when the complication arises by age groups (10-14 y, 15-19 y, 20-24y, 25-29y, 30-49y, 50+y). + +![Maternal Complications](resources/images/chis-mat-m-003.png) + +#### 2.1.4. Mental Health Disorders and Conditions - All { #214-mental-health-disorders-and-conditions-all } + +The section focuses on all the women benefiting from MH assessments and referrals. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown sex). + +![Mental Health Disorders and Conditions - All](resources/images/chis-mat-m-004.png) + +#### 2.1.5. Mental Health Disorders and Conditions - by Type { #215-mental-health-disorders-and-conditions-by-type } + +The information collected on the general female population (section 2.1.4.) can also be disaggregated by type of condition (depression, psychoses, behavioural conditions, dementia, substance use, suicide/self harm) - the conditions should be edited and adapted to the local context. + +![Mental Health Disorders and Conditions - by Type](resources/images/chis-mat-m-005.png) + +#### 2.1.6. Mental Health Disorders and Conditions - Pregnant and Postpartum { #216-mental-health-disorders-and-conditions-pregnant-and-postpartum } + +This section collects the same variables as the other two sections on MH, but it focuses specifically on pregnant and postpartum women. + +![Mental Health Disorders and Conditions - by Type](resources/images/chis-mat-m-006.png) + +### 2.2. Yearly Maternal Health Dataset { #22-yearly-maternal-health-dataset } + +#### 2.2.1. HIV Tests - All { #221-hiv-tests-all } + +The section collects the info on returned and positive HIV tests among the general population benefiting from the Maternal health services. The data are collected by age (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and sex (female, other). + +![HIV Tests - All](resources/images/chis-mat-y-001.png) + +#### 2.2.2. HIV Tests - TB Case { #222-hiv-tests-tb-case } + +THe section collects the same information as the previous section, though among presumptive and confirmed TB cases. + +![HIV Tests - TB Case](resources/images/chis-mat-y-001b.png) + +#### 2.2.3. HIV Tests - Key Population { #223-hiv-tests-key-population } + +The section provides the information on the key population by type of key population groups (SW, Prisoners, IDU, TG, Other - these can be adapted to better mirror the local context). + +![HIV Tests - Key Population](resources/images/chis-mat-y-001c.png) + +#### 2.2.4. Blood Pressure { #224-blood-pressure } + +The section reports the measurement of high blood pressure by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (female, other), and the pregnancy stage during which the HBP appears by age (10-14 y, 15-19 y, 20-24y, 25-29y, 30-49y, 50+y). + +![Blood Pressure](resources/images/chis-mat-y-002.png) + +#### 2.2.5. Mental Health Conditions and Disorders - All { #225-mental-health-conditions-and-disorders-all } + +The section focuses on all the women benefiting from MH assessments and referrals. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (female, other). + +![Mental Health Conditions and Disorders - All](resources/images/chis-mat-y-003.png) + +#### 2.2.6. Mental Health Conditions and Disorders - Pregnant and Postpartum { #226-mental-health-conditions-and-disorders-pregnant-and-postpartum } + +This section collects the same variables as the other section on MH, but it focuses specifically on pregnant and postpartum women. + +![Mental Health Conditions and Disorders - Pregnant and Postpartum](resources/images/chis-mat-y-003b.png) + +#### 2.2.7. Mental Health Conditions and Disorders - Awareness and Support { #227-mental-health-conditions-and-disorders-awareness-and-support } + +The section collects the number of women accessing MH-relates services and support activities. + +![Mental Health Conditions and Disorders - Awareness and Support](resources/images/chis-mat-y-003c.png) + +#### 2.2.8. Pregnancy-related Deaths { #228-pregnancy-related-deaths } + +The DEs in the section show the stages of pregnancy during which the deaths could occur. The data are disaggregated by age (10-14y, 15-19y, 20+y and unknown age). + +![Pregnancy-related Deaths](resources/images/chis-mat-y-004.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Maternal health datasets: + +| Nombre | Instrucción | Operador | Left side | Right side | +|:---------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:--------------------------------------------------:|:-------------------------------------------------:| +| CH - AGW assessed for MNS disorders Vs AGW with a possible MNS symptoms | AGW assessed for MNS disorders should be less than or equal to AGW with a possible MNS symptoms | menor_que_o_igual_que | AGW assessed for MNS disorders | AGW with a possible MNS symptoms | +| CH - AGW with MNS disorders/receiving Vs AGW assessed for MNS MH disorders | AGW with MNS disorders/receiving should be less than or equal to AGW assessed for MNS MH disorders | menor_que_o_igual_que | AGW with MNS disorders/receiving | AGW assessed for MNS MH disorders | +| CH - AGW with MNS disorders/receiving Vs People with MNS disorders/receiving | AGW with MNS disorders/receiving should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | AGW with MNS disorders/receiving | People with MNS disorders/receiving | +| CH - Assessed for MNS disorders conditions by type Vs People with a possible MNS symptoms by type | Assessed for MNS disorders conditions by type should be less than or equal to People with a possible MNS symptoms by type | menor_que_o_igual_que | Assessed for MNS disorders conditions by type | People with a possible MNS symptoms by type | +| CH - MNS disorders receiving - recovery & rehab Vs People with MNS disorders/receiving | MNS disorders receiving - recovery & rehab should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - recovery & rehab | People with MNS disorders/receiving | +| CH - MNS disorders receiving - support for MH Vs People with MNS disorders/receiving | MNS disorders receiving - support for MH should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - support for MH | People with MNS disorders/receiving | +| CH - People assessed for MNS disorders conditions Vs Assessed for MNS disorders conditions by type | People assessed for MNS disorders conditions should be less than or equal to Assessed for MNS disorders conditions by type | menor_que_o_igual_que | People assessed for MNS disorders conditions | Assessed for MNS disorders conditions by type | +| CH - People assessed for MNS disorders conditions Vs People with a possible MNS symptoms | People assessed for MNS disorders conditions should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People assessed for MNS disorders conditions | People with a possible MNS symptoms | +| CH - People with a possible MNS symptoms by type Vs People with a possible MNS symptoms | People with a possible MNS symptoms by type should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People with a possible MNS symptoms by type | People with a possible MNS symptoms | +| CH - People with MNS disorders - MH promotion and prev Vs People with MNS disorders/receiving | People with MNS disorders - MH promotion and prev should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders - MH promotion and prev | People with MNS disorders/receiving | +| CH - People with MNS disorders receiving - MH awareness Vs People with MNS disorders/receiving | People with MNS disorders receiving - MH awareness should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders receiving - MH awareness | People with MNS disorders/receiving | +| CH - People with MNS disorders/receiving Vs People assessed for MNS disorders | People with MNS disorders/receiving should be less than or equal to People assessed for MNS disorders | menor_que_o_igual_que | People with MNS disorders/receiving | People assessed for MNS disorders | +| CH - People with MNS disorders referred Vs People assessed for MNS disorders conditions | People with MNS disorders referred should be less than or equal to People assessed for MNS disorders conditions | menor_que_o_igual_que | People with MNS disorders referred | People assessed for MNS disorders conditions | +| CH - HIV tests performed amongst KP & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst KP & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst KP & results returned | HIV tests performed where results were returned | +| CH - HIV tests performed amongst TB & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst TB & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst TB & results returned | HIV tests performed where results were returned | +| CH - New HIV-positive result or diagnosis was returned Vs HIV tests performed where results were returned | New HIV-positive result or diagnosis was returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | +| CH - New HIV-positive result returned for KP Vs HIV tests performed amongst KP & results returned | New HIV-positive result returned for KP should be less than or equal to HIV tests performed amongst KP & results returned | menor_que_o_igual_que | New HIV-positive result returned for KP | HIV tests performed amongst KP & results returned | +| CH - New HIV-positive result returned for KP Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for KP should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for KP | New HIV-positive result or diagnosis was returned | +| CH - New HIV-positive result returned for TB Vs HIV tests performed amongst TB & results returned | New HIV-positive result returned for TB should be less than or equal to HIV tests performed amongst TB & results returned | menor_que_o_igual_que | New HIV-positive result returned for TB | HIV tests performed amongst TB & results returned | +| CH - New HIV-positive result returned for TB Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for TB should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for TB | New HIV-positive result or diagnosis was returned | +| CH - Women attending 1st ANC visit provided by CHW Vs Attending 1st ANC visit & tested for syphilis | Women attending 1st ANC visit provided by CHW should be less than or equal to Attending 1st ANC visit & tested for syphilis | menor_que_o_igual_que | Women attending 1st ANC visit provided by CHW | Attending 1st ANC visit & tested for syphilis | +| CH - Women attending other ANC visits provided by CHW Vs Other ANC visits tested for syphilis | Women attending other ANC visits provided by CHW should be less than or equal to Other ANC visits tested for syphilis | menor_que_o_igual_que | Women attending other ANC visits provided by CHW | Other ANC visits tested for syphilis | +| CH - AGW with measured raised BP during ANC Vs People with measured raised blood pressure | AGW with measured raised BP during ANC should be less than or equal to People with measured raised blood pressure | menor_que_o_igual_que | AGW with measured raised BP during ANC | People with measured raised blood pressure | +| CH - AGW with measured raised BP during postpartum care Vs People with measured raised blood pressure | AGW with measured raised BP during postpartum care should be less than or equal to People with measured raised blood pressure | menor_que_o_igual_que | AGW with measured raised BP during postpartum care | People with measured raised blood pressure | +| CH - AGW with raised BP during labor and delivery Vs People with measured raised blood pressure | AGW with raised BP during labor and delivery should be less than or equal to People with measured raised blood pressure | menor_que_o_igual_que | AGW with raised BP during labor and delivery | People with measured raised blood pressure | +| CH - ANC contacts given/prescribed iron supplements Vs Community ANC contacts | ANC contacts given/prescribed iron supplements should be less than or equal to Community ANC contacts | menor_que_o_igual_que | ANC contacts given/prescribed iron supplements | Community ANC contacts | +| CH - ANC contacts received breastfeeding counselling Vs Community ANC contacts | ANC contacts received breastfeeding counselling should be less than or equal to Community ANC contacts | menor_que_o_igual_que | ANC contacts received breastfeeding counselling | Community ANC contacts | +| CH - 1st ANC contact with CHW during 1st trimester Vs Pregnant women who had at least one ANC with CHW | 1st ANC contact with CHW during 1st trimester should be less than or equal to Pregnant women who had at least one ANC with CHW | menor_que_o_igual_que | 1st ANC contact with CHW during 1st trimester | Pregnant women who had at least one ANC with CHW | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the MatH indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH028a - HIV tests with returned results | Number of HIV tests conducted and results returned | HIV tests performed where results were returned | 1 | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH028b - HIV +ve tests returned to people (%) | Proportion of HIV tests performed that were positive and results returned to people | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH030 - Antenatal care attendees tested for syphilis (%) | Proportion of antenatal care attendees tested for syphilis | Women attending ANC & tested for syphilis | Women attending ANC provided by CHW | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH035 - Pregnant women with 1st ANC visit during 1st trimester (%) | Proportion of pregnant women who have first antenatal care (ANC) contact with a CHW during the first trimester of pregnancy | 1st ANC contact with CHW during 1st trimester | Pregnant women who had at least one ANC with CHW | CH - Maternal Health | +| CH036 - ANC visits with breastfeeding counselling (%) | Proportion of antenatal care contacts during which women received breastfeeding counselling | ANC contacts received breastfeeding counselling | Community ANC contacts | CH - Nutrition, CH - Maternal Health | +| CH036b - Community ANC visits | Number of antenatal care contacts in the community | ANC contacts | 1 | CH - Nutrition, CH - Maternal Health | +| CH037 - Women given/prescribed iron supplements during ANC (%) | Proportion of community antenatal care contacts given/prescribed iron-containing supplements | ANC contacts given/prescribed iron supplements | Community ANC contacts | CH - Nutrition, CH - Maternal Health | +| CH038b - Females with measured raised blood pressure (%) | Proportion of females with raised blood pressure measured by CHW | Females with measured raised blood pressure | Females 10+ years in the catchment area | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038c - Women with measured raised blood pressure - ANC | Number of Women with measured raised blood pressure - ANC | Women with measured raised blood pressure - ANC | 1 | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038d - Women with measured raised blood pressure - Delivery | Number of Women with measured raised blood pressure - Delivery | Women with measured raised blood pressure - Delivery | 1 | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038e - Women with measured raised blood pressure - Postpartum | Number of Women with measured raised blood pressure - Postpartum | Women with measured raised blood pressure - Postpartum | 1 | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038 - People with measured raised blood pressure (%) | Proportion of people with raised blood pressure measured by CHW | People with measured raised blood pressure | People 10+ years in the catchment area | CH - Maternal Health, CH - Noncommunicable diseases | +| CH039b - Pregnant women referred for maternal complications - ANC | Number of pregnant women referred for maternal complications - ANC | Women referred for maternal complications | 1 | CH - Maternal Health | +| CH039c - Pregnant women referred for maternal complications - Labour/delivery | Number of pregnant women referred for maternal complications - Labour/Delivery | Women referred for maternal complications | 1 | CH - Maternal Health | +| CH039d - Pregnant women referred for maternal complications - Postpartum | Number of pregnant women referred for maternal complications - Postpartum | Women referred for maternal complications | 1 | CH - Maternal Health | +| CH039 - Pregnant women referred for maternal complications | Number of pregnant women referred for maternal complications | Women referred for maternal complications | 1 | CH - Maternal Health | +| CH040 - Women given postpartum uteronic after delivery without SBA (%) | Proportion of women who delivered without a skilled birth attendant (SBA) and who were administered oral immediate postpartum uterotonic | AGW without SBA and given postpartum uterotonic | Live births delivered in the community | CH - Maternal Health | +| CH041m - Women assessed for MNS disorders | Number of Women assessed for mental, neurological and substance use (MNS) disorders | Women assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH041 - People assessed for MNS disorders | Number of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health | +| CH041 - People assessed for MNS disorders (%) | Proportion of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | People with a possible MNS symptoms | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042b - Women referred for MNS disorders (%) | Proportion of Women with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | Women assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042 - People referred for MNS disorders (%) | Proportion of people with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH043 - People with MNS disorders receiving services (%) | Proportion of people with mental, neurologic and substance use (MNS) disorders receiving services | People with MNS disorders/receiving | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH044b - Pregnancy-related deaths - during pregnancy | Number of pregnancy-related deaths - during pregnancy | Pregnancy-related deaths - During pregnancy | 1 | CH - Maternal Health | +| CH044c - Pregnancy-related deaths - delivery at facility | Number of pregnancy-related deaths - delivery at facility | Pregnancy-related deaths - delivery at facility | 1 | CH - Maternal Health | +| CH044d - Pregnancy-related deaths - delivery in community | Number of pregnancy-related deaths - delivery in community | Pregnancy-related deaths - delivery community | 1 | CH - Maternal Health | +| CH044e - Pregnancy-related deaths - 2 months pre/post delivery | Number of pregnancy-related deaths - 2 months pre/post delivery | Pregnancy-related deaths - 2 months pre/post delivery | 1 | CH - Maternal Health | +| CH044 - Pregnancy-related deaths | Number of pregnancy-related deaths | Pregnancy-related deaths | 1 | CH - Maternal Health, CH - Civil registration and vital statistics | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Maternal Health”. + +The dashboard is divided in two based on the periodicity of the datasets. +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-mat-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-mat-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__mental-health-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__mental-health-md new file mode 100644 index 000000000..b34e4a8d4 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__mental-health-md @@ -0,0 +1,272 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_men-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Mental Health { #chis-agg-men-design } + +## 1. Dataset Configuration { #1-dataset-configuration } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Adolescent Health (MH) module includes: + +1. A **monthly dataset** with key data elements for MH +2. A **yearly dataset** for the follow up of key annual information on MH +3. **Core indicators** for both datasets +4. A predefined **“CH - Mental Health”** dashboard + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +## 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the MH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the MH module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH041a - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/ MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041b - People with possible MNS symptoms | People with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041c - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/mental health conditions by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041d - People with possible MNS symptoms | People with possible symptoms of MNS conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041e - Women assessed for MNS disorders/ MH conditions | Women and adolescent girls assessed for MNS disorders / MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041f - Women with possible MNS symptoms | Women and adolescent girls with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042a - People with MNS disorders referred | People with MNS disorders referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042b - People with MNS disorders referred by type | People with MNS disorders referred by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042c - Women with MNS disorders referred | Women and adolescent girls with MNS disorders/mental health conditions referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH092a - People with suicidal ideation or plan | People with suicidal ideation or plan | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH092b - People assessed for suicidal ideation or plan | People assessed for suicidal ideation or plan | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH093a - People who reported attempting suicide | People who reported attempting suicide | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH093b - People assessed for attempting suicide | People assessed for attempting suicide | CH - Adolescent Health (Monthly), CH - Mental health (Monthly) | CH - Mental health, CH - Adolescent Health | +| CH043a - People with MNS disorders receiving services | People with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043b - People assessed for MNS disorders | People assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043c - People with MNS disorders receiving services - MH awareness | People with MNS disorders/mental health conditions receiving services - mental health awareness | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043d - People with MNS disorders receiving services - MH HP | People with MNS disorders/mental health conditions receiving services - mental health promotion and prevention | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043e - People with MNS disorders receiving services - MH support | People with MNS disorders/mental health conditions receiving services - support for people with mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043f - People with MNS disorders receiving services - recovery/rehab | People with MNS disorders/mental health conditions receiving services - recovery and rehabilitation | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043g - Women with MNS disorders receiving services | Women and adolescent girls with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043h - Women assessed for MNS disorders | Women and adolescent girls assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH088a - People reporting using alcohol | People reporting using alcohol | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH088b - People assessed for alcohol use | People assessed for alcohol use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH088c - Women reporting using alcohol | Women and adolescent girls reported using alcohol | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH088d - Women assessed for alcohol use | Women and adolescent girls assessed for alcohol use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH089a - People with heavy episodic drinking | People with heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089b - People assessed for heavy episodic drinking | People assessed for heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089c - Women with heavy episodic drinking | Women and adolescent girls with heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089d - Women assessed for heavy episodic drinking | Women and adolescent girls assessed for heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH090a - People reporting use of any psychoactive drugs | People reporting use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090b - People assessed for use of any psychoactive drugs | People assessed for use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090c - People reporting the use of psychoactive drugs | People who report use of any psychoactive drugs by type | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090d - Women reporting use of any psychoactive drugs | Women and adolescent girls who use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH090e - Women assessed for use of any psychoactive drugs | Women and adolescent girls assessed for use of any psychoactive drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091a - People reporting use of injection drugs | People reporting use of injection drugs | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091b - People assessed for injection drug use | People assessed for injection drug use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091c - Women reporting use of injection drugs | Women and adolescent girls injecting drug use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH091d - Women assessed for injection drug use | Women and adolescent girls assessed for injecting drug use | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH094a - Leisure screen time during the week | Amount of time usually spent on a typical weekday dedicated to screen time for leisure activities | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH094b - Leisure screen time during the weekend | Amount of time usually spent on a typical weekend day dedicated to screen time for leisure activities | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH094c - People assessed on leisure screen time | People assessed on screen time for leisure activities | CH - Adolescent Health (Yearly), CH - Mental health (Yearly) | CH - Mental health, CH - Adolescent Health | +| CH075a - Children (0-4 y) monitored for early signs of developmental delays | Children aged 0-4 years monitored for early signs of developmental delays | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH075b - Children (0-4 y) monitored for early signs of developmental delays referred | Children (0-4 y) monitored for early signs of developmental delays referred | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH076a - Children with suspected developmental disabilities referred | Children with suspected developmental disabilities referred | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH076b - Children assessed for development monitoring | Children who were assessed for their developmental monitoring | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH077a - Caregivers counselled on responsive caregiving and learning activities | Caregivers receiving counselling on responsive caregiving and early learning activities | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH077b - Caregivers of children consulting for developmental delays | Caregivers of children consulting for developmental delays | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH078a - Children with developmental disability whose caregiver received parenting info | Children with suspected developmental disorders and disabilities whose caregivers receive information on parenting | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH078b - Children (0-4 y) assessed for developmental delays - last 12 months | Children who were assessed for their developmental disorders and disabilities in the past 12 months | CH - Child Health (Monthly), CH - Mental health (Monthly) | CH - Child Health, CH - Mental health | +| CH170a - Deaths due to drug overdose | Persons who died from drug overdose deaths in the past 12 months | CH - Mental health (Yearly) | CH - Mental health | +| CH170b - Deaths due to drug overdose by type | Persons who died from drug overdose deaths in the past 12 months by type | CH - Mental health (Yearly) | CH - Mental health | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly Mental Health Dataset { #21-monthly-mental-health-dataset } + +#### 2.1.1. Mental Health Disorders and Conditions - All { #211-mental-health-disorders-and-conditions-all } + +The section focuses on all the people benefiting from MH assessments and referrals. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Mental Health Disorders and Conditions - All](resources/images/chis-men-m-001.png) + +#### 2.1.2. Mental Health Disorders and Conditions - by Type { #212-mental-health-disorders-and-conditions-by-type } + +The information collected on the general population (section 2.1.1.) can also be disaggregated by type of condition (depression, psychoses, behavioural conditions, dementia, substance use, suicide/self harm) - the conditions should be edited and adapted to the local context. + +![Mental Health Disorders and Conditions - by Type](resources/images/chis-men-m-002.png) + +#### 2.1.3. Mental Health Disorders and Conditions - Pregnant and Postpartum { #213-mental-health-disorders-and-conditions-pregnant-and-postpartum } + +This section collects the same variables as the other two sections on MH, but it focuses specifically on pregnant and postpartum women benefiting from MH community activities. + +![Mental Health Disorders and Conditions - Pregnant and Postpartum](resources/images/chis-men-m-003.png) + +#### 2.1.4. Developmental Delays - Monitored for Early Signs { #214-developmental-delays-monitored-for-early-signs } + +The section collects the information related to the assessment of early developmental disabilities among children under 5 years of age by age groups (0-11m and 1-4y) and sex (male, female, other, unknown sex). + +![Developmental Delays - Monitored for Early Signs](resources/images/chis-men-m-004.png) + +#### 2.1.5. Developmental Delays - Suspects Referred { #215-developmental-delays-suspects-referred } + +The section collects the information related to the assessment of developmental disabilities among children as per WHO definition (up to 18 years). The data are disaggregated by age groups (0-11m, 1-4y, 5-9y, 10-14y, 15-17y, unknown) and sex (male, female, other, unknown). + +![Developmental Delays - Suspects Referred](resources/images/chis-men-m-005.png) + +#### 2.1.6. Developmental Delays - Caregivers Counselled { #216-developmental-delays-caregivers-counselled } + +The section collects data on sensibilization activities given to caregivers of children with developmental disabilities. The data are disaggregated by sex of the caregiver (male, female, other, unknown). + +![Developmental Delays - Caregivers Counselled](resources/images/chis-men-m-006.png) + +#### 2.1.7. Developmental Delays - Caregivers Receiving Parenting Info { #217-developmental-delays-caregivers-receiving-parenting-info } + +The section summarizes the data collected during parenting information sessions among caregivers of children assessed for developmental delays during the past 12 months. + +![Developmental Delays - Caregivers Receiving Parenting Info](resources/images/chis-men-m-007.png) + +#### 2.1.8. Suicide Attempts { #218-suicide-attempts } + +The section collects information on the risk of suicide (ideation, attempted, or reported) in the community. The data are collected by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+y, unknown age) and sex (male, female, other, unknown sex). + +![Suicide Attempts](resources/images/chis-men-m-008.png) + +### 2.2. Yearly Mental Health Dataset { #22-yearly-mental-health-dataset } + +#### 2.2.1. Mental Health Conditions and Disorders - All { #221-mental-health-conditions-and-disorders-all } + +The section focuses on all the people benefiting from MH assessments and referrals. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Mental Health Conditions and Disorders - All](resources/images/chis-men-y-001.png) + +#### 2.2.2. Mental Health conditions and Disorders - Pregnant and Postpartum { #222-mental-health-conditions-and-disorders-pregnant-and-postpartum } + +This section collects the same variables as the other section on MH, but it focuses specifically on pregnant and postpartum women. + +![Mental Health conditions and Disorders - Pregnant and Postpartum](resources/images/chis-men-y-002.png) + +#### 2.2.3. Mental Health Conditions and Disorders - Awareness and Support { #223-mental-health-conditions-and-disorders-awareness-and-support } + +The section collects the number of people accessing MH-related services and support activities. + +![Mental Health Conditions and Disorders - Awareness and Support](resources/images/chis-men-y-003.png) + +#### 2.2.4. Alcohol Use - All { #224-alcohol-use-all } + +The section reports the data on the alcohol use assessment carried in the community. The data are disaggregated by age groups (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Alcohol Use - All](resources/images/chis-men-y-004.png) + +#### 2.2.5. Alcohol Use - Pregnant and Postpartum { #225-alcohol-use-pregnant-and-postpartum } + +The section on alcohol use is focused on the assessment carried out among the pregnant and postpartum women in the community. + +![Alcohol Use - Pregnant and Postpartum](resources/images/chis-men-y-005.png) + +#### 2.2.6. Drug Use - All { #226-drug-use-all } + +The section reports the data on the assessment on drug use carried out among the general population. The data are disaggregated by age groups (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Drug Use - All](resources/images/chis-men-y-006.png) + +#### 2.2.7. Drug Use - by Type { #227-drug-use-by-type } + +The data collected in section 2.2.6. can also be disaggregated by the type of consumed drug. Currently the data re disaggregated by cannabis, opioids, cocaine, amphetamine, other, but the categories should be modified according to the local context. + +![Drug Use - by Type](resources/images/chis-men-y-007.png) + +#### 2.2.8. Drug Use - Pregnant and Postpartum { #228-drug-use-pregnant-and-postpartum } + +The section reports the data coming from the assessment on drug use among pregnant and postpartum women in the community. + +![Drug Use - Pregnant and Postpartum](resources/images/chis-men-y-008.png) + +#### 2.2.9. Drug Overdoses { #229-drug-overdoses } + +The section collects the number of deaths due to drug overdoses. The first table reports teh data byage groups (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown); whereas the second table reports the same information by the type of drug that caused the overdose (opioids, non-opioid, other, unknown drug). + +![Drug Overdoses](resources/images/chis-men-y-009.png) + +#### 2.2.10. Screen Time { #2210-screen-time } + +The information reported in the section provides the necessary info to get an estimate of the times spent in front of a screen during people’s spare time during the week and the weekend. The data are disaggregated by age groups (<1y, 1-2y, 3-4y, 5-12y, 13-17y, 18-24y, 25-29y, 30+y, unknown) and by sex (male, female, other unknown). + +![Screen Time](resources/images/chis-men-y-010.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Adolescent health datasets: + +| name | instruction | operator | leftSide description | rightSide description | | +|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|----------------------------------------------------|---| +| CH - AGW assessed for heavy episodic drinking Vs People assessed for heavy episodic drinking | AGW assessed for heavy episodic drinking should be less than or equal to People assessed for heavy episodic drinking | menor_que_o_igual_que | AGW assessed for heavy episodic drinking | People assessed for heavy episodic drinking | | +| CH - AGW assessed for injecting drug use Vs People assessed for injecting drug use | AGW assessed for injecting drug use should be less than or equal to People assessed for injecting drug use | menor_que_o_igual_que | AGW assessed for injecting drug use | People assessed for injecting drug use | | +| CH - AGW assessed for MNS disorders Vs AGW with a possible MNS symptoms | AGW assessed for MNS disorders should be less than or equal to AGW with a possible MNS symptoms | menor_que_o_igual_que | AGW assessed for MNS disorders | AGW with a possible MNS symptoms | | +| CH - AGW assessed for use of any psychoactive drugs Vs People assessed for use of any psychoactive drugs | AGW assessed for use of any psychoactive drugs should be less than or equal to People assessed for use of any psychoactive drugs | menor_que_o_igual_que | AGW assessed for use of any psychoactive drugs | People assessed for use of any psychoactive drugs | | +| CH - AGW who use of any psychoactive drugs Vs People who report use of any psychoactive drugs | AGW who use of any psychoactive drugs should be less than or equal to People who report use of any psychoactive drugs | menor_que_o_igual_que | AGW who use of any psychoactive drugs | People who report use of any psychoactive drugs | | +| CH - AGW with heavy episodic drinking Vs People with heavy episodic drinking | AGW with heavy episodic drinking should be less than or equal to People with heavy episodic drinking | menor_que_o_igual_que | AGW with heavy episodic drinking | People with heavy episodic drinking | | +| CH - AGW with MNS disorders/receiving Vs AGW assessed for MNS MH disorders | AGW with MNS disorders/receiving should be less than or equal to AGW assessed for MNS MH disorders | menor_que_o_igual_que | AGW with MNS disorders/receiving | AGW assessed for MNS MH disorders | | +| CH - AGW with MNS disorders/receiving Vs People with MNS disorders/receiving | AGW with MNS disorders/receiving should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | AGW with MNS disorders/receiving | People with MNS disorders/receiving | | +| CH - Assessed for MNS disorders conditions by type Vs People with a possible MNS symptoms by type | Assessed for MNS disorders conditions by type should be less than or equal to People with a possible MNS symptoms by type | menor_que_o_igual_que | Assessed for MNS disorders conditions by type | People with a possible MNS symptoms by type | | +| CH - Caregivers who received info on parenting Vs Children assessed for dev disorders & disabilities | Caregivers who received info on parenting should be less than or equal to Children assessed for dev disorders & disabilities | menor_que_o_igual_que | Caregivers who received info on parenting | Children assessed for dev disorders & disabilities | | +| CH - Children 0-4 years with dev delays referred Vs Children 0-4 y monitored for signs of dev delays | Children 0-4 years with dev delays referred should be less than or equal to Children 0-4 y monitored for signs of dev delays | menor_que_o_igual_que | Children 0-4 years with dev delays referred | Children 0-4 y monitored for signs of dev delays | | +| CH - Children with suspected dev disabilities referred Vs Children assessed for their dev monitoring | Children with suspected dev disabilities referred should be less than or equal to Children assessed for their dev monitoring | menor_que_o_igual_que | Children with suspected dev disabilities referred | Children assessed for their dev monitoring | | +| CH - Counselled on caregiving & early learning Vs Caregivers of children consulting for dev delays | Counselled on caregiving & early learning should be less than or equal to Caregivers of children consulting for dev delays | menor_que_o_igual_que | Counselled on caregiving & early learning | Caregivers of children consulting for dev delays | | +| CH - Died from drug overdose deaths by type Vs Died from drug overdose deaths | Died from drug overdose deaths by type should be less than or equal to Died from drug overdose deaths | menor_que_o_igual_que | Deaths due to overdose by type | Deaths due to overdose | | +| CH - MNS disorders receiving - recovery & rehab Vs People with MNS disorders/receiving | MNS disorders receiving - recovery & rehab should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - recovery & rehab | People with MNS disorders/receiving | | +| CH - MNS disorders receiving - support for MH Vs People with MNS disorders/receiving | MNS disorders receiving - support for MH should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - support for MH | People with MNS disorders/receiving | | +| CH - People assessed for MNS disorders conditions Vs Assessed for MNS disorders conditions by type | People assessed for MNS disorders conditions should be less than or equal to Assessed for MNS disorders conditions by type | menor_que_o_igual_que | People assessed for MNS disorders conditions | Assessed for MNS disorders conditions by type | | +| CH - People assessed for MNS disorders conditions Vs People with a possible MNS symptoms | People assessed for MNS disorders conditions should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People assessed for MNS disorders conditions | People with a possible MNS symptoms | | +| CH - People reported using alcohol Vs Number people assessed for alcohol use | People reported using alcohol should be less than or equal to Number people assessed for alcohol use | menor_que_o_igual_que | People reported using alcohol | Number people assessed for alcohol use | | +| CH - People who reported attempting suicide Vs People assessed for attempting suicide | People who reported attempting suicide should be less than or equal to People assessed for attempting suicide | menor_que_o_igual_que | People who reported attempting suicide | People assessed for attempting suicide | | +| CH - People who report injecting drug use Vs People assessed for injecting drug use | People who report injecting drug use should be less than or equal to People assessed for injecting drug use | menor_que_o_igual_que | People who report injecting drug use | People assessed for injecting drug use | | +| CH - People who report use of any psychoactive drugs Vs People assessed for use of any psychoactive drugs | People who report use of any psychoactive drugs should be less than or equal to People assessed for use of any psychoactive drugs | menor_que_o_igual_que | People who report use of any psychoactive drugs | People assessed for use of any psychoactive drugs | | +| CH - People with a possible MNS symptoms by type Vs People with a possible MNS symptoms | People with a possible MNS symptoms by type should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People with a possible MNS symptoms by type | People with a possible MNS symptoms | | +| CH - People with heavy episodic drinking Vs People assessed for heavy episodic drinking | People with heavy episodic drinking should be less than or equal to People assessed for heavy episodic drinking | menor_que_o_igual_que | People with heavy episodic drinking | People assessed for heavy episodic drinking | | +| CH - People with MNS disorders - MH promotion and prev Vs People with MNS disorders/receiving | People with MNS disorders - MH promotion and prev should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders - MH promotion and prev | People with MNS disorders/receiving | | +| CH - People with MNS disorders receiving - MH awareness Vs People with MNS disorders/receiving | People with MNS disorders receiving - MH awareness should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders receiving - MH awareness | People with MNS disorders/receiving | | +| CH - People with MNS disorders/receiving Vs People assessed for MNS disorders | People with MNS disorders/receiving should be less than or equal to People assessed for MNS disorders | menor_que_o_igual_que | People with MNS disorders/receiving | People assessed for MNS disorders | | +| CH - People with MNS disorders referred Vs People assessed for MNS disorders conditions | People with MNS disorders referred should be less than or equal to People assessed for MNS disorders conditions | menor_que_o_igual_que | People with MNS disorders referred | People assessed for MNS disorders conditions | | +| CH - People with suicidal ideation or plan Vs People assessed for suicidal ideation or plan | People with suicidal ideation or plan should be less than or equal to People assessed for suicidal ideation or plan | menor_que_o_igual_que | People with suicidal ideation or plan | People assessed for suicidal ideation or plan | | +| CH - Reported use of any psychoactive drugs type Vs People who report use of any psychoactive drugs | Reported use of any psychoactive drugs type should be less than or equal to People who report use of any psychoactive drugs | menor_que_o_igual_que | Reported use of any psychoactive drugs type | People who report use of any psychoactive drugs | | +| CH - Women and adolescent girls injecting drug use Vs People who report injecting drug use | Women and adolescent girls injecting drug use should be less than or equal to People who report injecting drug use | menor_que_o_igual_que | Women and adolescent girls injecting drug use | People who report injecting drug use | | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the MH indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH041m - Women assessed for MNS disorders | Number of Women assessed for mental, neurological and substance use (MNS) disorders | Women assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH041 - People assessed for MNS disorders (%) | Proportion of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | People with a possible MNS symptoms | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042b - Women referred for MNS disorders (%) | Proportion of Women with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | Women assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042 - People referred for MNS disorders (%) | Proportion of people with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH043 - People with MNS disorders receiving services (%) | Proportion of people with mental, neurologic and substance use (MNS) disorders receiving services | People with MNS disorders/receiving | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH075 - Children (0-4 y) monitored for developmental delays (%) | Proportion of children aged 0-4 years monitored for early signs of developmental delays | Children 0-4 yrs monitored for signs of dev delays | Children aged 0-4 years in the catchment area | CH - Child Health, CH - Mental health | +| CH076 - Children (0-4 y) referred for developmental disabilities (%) | Proportion of children aged 0-4 years with suspected developmental disabilities referred | Children with suspected dev disabilities referred | Children assessed for their dev monitoring | CH - Child Health, CH - Mental health | +| CH077 - Caregivers counselled on responsive care giving and learning activities (%) | Proportion of caregivers counselled on responsive caregiving and early learning activities | Counselled on caregiving & early learning | Caregivers of children consulting for dev delays | CH - Child Health, CH - Mental health | +| CH078 - Caregivers of children with developmental disability receiving parenting info (%) | Proportion of children with suspected developmental disorders and disabilities whose caregivers receive parenting information | Caregivers who received info on parenting | Children assessed for dev disorders & disabilities | CH - Child Health, CH - Mental health | +| CH088 - Alcohol consumers (%) | Proportion of people reporting consuming alcohol | People reported using alcohol | Number people assessed for alcohol use | CH - Adolescent Health, CH - Mental health | +| CH089 - People with heavy episodic drinking (%) | Proportion of people with heavy episodic drinking | People with heavy episodic drinking | People assessed for heavy episodic drinking | CH - Adolescent Health, CH - Mental health, CH - Noncommunicable diseases | +| CH090 - People using psychoactive drugs (%) | Proportion of people who reporting psychoactive drugs | People who report use of any psychoactive drugs | People assessed for use of any psychoactive drugs | CH - Adolescent Health, CH - Mental health | +| CH091 - People injecting psychoactive drugs (%) | Proportion of people who report injecting psychoactive drugs | People who report injecting drug use | People assessed for injecting drug use | CH - Adolescent Health, CH - Mental health | +| CH092 - People with suicidal plan | Number of people with suicidal ideation or plan | People with suicidal ideation or plan | 1 | CH - Adolescent Health, CH - Mental health | +| CH093 - People with suicide attempts | Number of People who reported attempting suicide | People who reported attempting suicide | 1 | CH - Adolescent Health, CH - Mental health | +| CH094a - Average time of screen time as leisure activity (week) | Average time on weekdays dedicated to screen time for leisure activities | Weekday screen time for leisure activities | 1 | CH - Adolescent Health, CH - Mental health | +| CH094b - Average time of screen time as leisure activity (weekend) | Average time on weekend days dedicated to screen time for leisure activities | Weekend screen time for leisure activities | 1 | CH - Adolescent Health, CH - Mental health | +| CH170 - Deaths due to drug overdose (%) | Proportion of drug overdose deaths | Deaths due to drug overdose | People 15+ years | CH - Mental health | +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Mental Health”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboards](resources/images/chis-men-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboards](resources/images/chis-men-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__neglected-tropical-diseases-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__neglected-tropical-diseases-md new file mode 100644 index 000000000..c04f5ab5a --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__neglected-tropical-diseases-md @@ -0,0 +1,267 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_ntd-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Neglected Tropical Diseases (NTDs) { #chis-agg-ntd-design } + +## 1.Datasets { #1datasets } + +### 1.1. Configuration summary { #11-configuration-summary } + +The aggregate CH - Neglected tropical diseases (NTDs) module includes: + +1. A **monthly dataset** with key data elements for NTDs +2. A **yearly dataset** for the follow up of key annual information on adolescent health +3. **Core indicators** for both datasets +4. A predefined **“CH - NTDs” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the NTDs module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the NTDs module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH041a - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/ MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041b - People with possible MNS symptoms | People with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041c - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/mental health conditions by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041d - People with possible MNS symptoms | People with possible symptoms of MNS conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041e - Women assessed for MNS disorders/ MH conditions | Women and adolescent girls assessed for MNS disorders / MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041f - Women with possible MNS symptoms | Women and adolescent girls with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042a - People with MNS disorders referred | People with MNS disorders referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042b - People with MNS disorders referred by type | People with MNS disorders referred by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042c - Women with MNS disorders referred | Women and adolescent girls with MNS disorders/mental health conditions referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043a - People with MNS disorders receiving services | People with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043b - People assessed for MNS disorders | People assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043c - People with MNS disorders receiving services - MH awareness | People with MNS disorders/mental health conditions receiving services - mental health awareness | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043d - People with MNS disorders receiving services - MH HP | People with MNS disorders/mental health conditions receiving services - mental health promotion and prevention | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043e - People with MNS disorders receiving services - MH support | People with MNS disorders/mental health conditions receiving services - support for people with mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043f - People with MNS disorders receiving services - recovery/rehab | People with MNS disorders/mental health conditions receiving services - recovery and rehabilitation | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043g - Women with MNS disorders receiving services | Women and adolescent girls with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043h - Women assessed for MNS disorders | Women and adolescent girls assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH135 - Suspected NTD cases reported | Suspected NTD cases reported | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH136 - Reported rumours of guinea worm disease/dracunculiasis cases | Rumours of guinea worm disease/dracunculiasis cases reported | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH137 - Reported rumours of yaws cases | Reported rumours of yaws cases | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH138 - People with NTDs referred | People referred to health centre for diagnosis or treatment of NTDs | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH139a - Communities receiving NTDs PC | Communities/villages/localities receiving PC against NTDs | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH139b - Communities in need of NTDs PC | Communities/villages/localities requiring PC against NTDs | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH140a - People receiving a dose of NTDs PC | People receiving a dose of NTDs PC | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH140b - People targeted for PC against NTDs | People targeted for PC against NTDs | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH140c - People receiving a dose of NTDs PC by disease | People receiving a dose of NTDs PC by disease | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH140d - People targeted for PC against NTDs by disease | People targeted for PC against NTDs by disease | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141a - Households receiving messages on NTDs - case management | Households that received social mobilization campaigns on NTDs - case management | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141b - Households receiving messages on NTDs - OneHealth | Households that received social mobilization campaigns on NTDs - one health approach | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141c - Households receiving messages on NTDs - PC | Households that received social mobilization campaigns on NTDs - PC | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141d - Households receiving messages on NTDs - VC | Households that received social mobilization campaigns on NTDs - vector control | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141e - Households targeted for messages on NTDs - case management | Households targeted for social mobilization campaigns on NTDs - case management | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141f - Households targeted for messages on NTDs - OneHealth | Households targeted for social mobilization campaigns on NTDs - one health approach | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141g - Househoulds targeted for messages on NTDs - PC | Households targeted for social mobilization campaigns on NTDs - PC | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH141h - Households targeted for messages on NTDs - VC | Households targeted for social mobilization campaigns on NTDs - vector control | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH142a - People with animal bites | People with animal bites | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH142b - People with animal bites by animal | People with animal bites by animal | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH143a - Deaths within three months from a snakebite | Deaths in the community occurring within three months after a snakebite | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH143b - Deaths within three months from a dog bite | Deaths within three months from a dog bite | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH144a - People screened for skin NTDs | People screened for skin NTDs | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH144b - Population targeted for skin NTD screening | Population targeted for skin NTD screening | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH145a - NTD cases with adequate wound case | NTD cases who received adequate/recommended wound care | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH145b - NTD cases presenting with wound(s) | NTD cases presenting with wound(s) | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH146 - People screened for VL and/or PKDL | People screened for signs and symptoms of VL and/or PKDL in the catchment area | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH147a - People with visible haematuria or +ve micro-haematuria dipstick | Individuals reporting visible hematuria or with positive dipstick for micro-hematuria | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH147b - People screened for micro-hematuria | People screened for micro-hematuria | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH148a - People with NTD-linked disability receiving rehab support | People suffering from physical disability related to NTDs who receive rehabilitation support | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH148b - People with NTD-linked disability | People suffering from physical disability related to NTDs | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH149a - NTD cases having received self-care instructions | NTD cases who received instructions for self-care for relevant NTDs | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH149b - NTD cases relevant for self-care | NTD cases relevant for self-care | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH150a - Houses with implemented vector reduction measure | Houses where some domiciliary vector reduction measures were implemented | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH150b - Houses targeted for vector reduction measure | Houses targeted for domiciliary vector reduction measures | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH151a - Surface water bodies enumerated and mapped | Surface water bodies enumerated and mapped | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH152a - Households with covered water containers | Households with all containers covered and protected with lids | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | +| CH152b - Households visited in the catchment area | Households visited in the catchment area | CH - Neglected tropical diseases (Yearly) | CH - Neglected tropical diseases | + +## 2.Dataset Details { #2dataset-details } + +### 2.1. Monthly NTDs Dataset { #21-monthly-ntds-dataset } + +#### 2.1.1. Mental Health Disorders and Conditions - All { #211-mental-health-disorders-and-conditions-all } + +The section focuses on all the people benefiting from MH assessments and referrals. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Mental Health Disorders and Conditions - All](resources/images/chis-ntd-m-001.png) + +#### 2.1.2. Mental Health Disorders and Conditions - by Type { #212-mental-health-disorders-and-conditions-by-type } + +The information collected on the general population (section 2.1.1.) can also be disaggregated by type of condition (depression, psychoses, behavioural conditions, dementia, substance use, suicide/self harm) - the conditions should be edited and adapted to the local context. + +![Mental Health Disorders and Conditions - by type](resources/images/chis-ntd-m-001b.png) + +#### 2.1.3. Mental Health Disorders and Conditions - Pregnant and Postpartum { #213-mental-health-disorders-and-conditions-pregnant-and-postpartum } + +This section collects the same variables as the other two sections on MH, but it focuses specifically on pregnant and postpartum women benefiting from MH community activities. + +![Mental Health Disorders and Conditions - pregnant and postpartum](resources/images/chis-ntd-m-001c.png) + +### 2.2. Yearly NTDs Dataset { #22-yearly-ntds-dataset } + +#### 2.2.1. Mental Health Conditions and Disorders - All { #221-mental-health-conditions-and-disorders-all } + +The section focuses on all the people benefiting from MH assessments and referrals. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Mental Health Conditions and Disorders - All](resources/images/chis-ntd-y-001.png) + +#### 2.2.2. Mental Health Conditions and Disorders - Awareness and Support { #222-mental-health-conditions-and-disorders-awareness-and-support } + +The section collects the number of people accessing MH-related services and support activities. + +![Mental Health Conditions and Disorders - Awareness and Support](resources/images/chis-ntd-y-001b.png) + +#### 2.2.3. Mental Health Conditions and Disorders - Pregnant and Postpartum { #223-mental-health-conditions-and-disorders-pregnant-and-postpartum } + +This section collects the same variables as the other section on MH, but it focuses specifically on pregnant and postpartum women. + +![Mental Health Conditions and Disorders - Pregnant and Postpartum](resources/images/chis-ntd-y-001c.png) + +#### 2.2.4. NTDs and PC { #224-ntds-and-pc } + +The section collects the information about rumours on Guinea worms and Yaws cases and on PC in the community. The data are aggregated by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age) and sex (male, female, other, unknown sex). The same disaggregation is applied to the reported cases (third table). + +The second table collects the totals on PC activities but with more information on the specific targeted disease - The diseases in the cat combo at the moment are: Lymphatic filariasis, Onchocerciasis, Schistosomiasis, Soil-transmitted helminths, Taeniasis, Trachomas, Yaws, and Others. The specified diseases should be edited and better adapted to mirror the local context. + +![NTDs and PC](resources/images/chis-ntd-y-002.png) + +#### 2.2.3. Mobilization/Awareness Campaigns { #223-mobilizationawareness-campaigns } + +The section gathers the total on households receiving specific messages on different aspects of NTDs. + +![Mobilization/Awareness Campaigns](resources/images/chis-ntd-y-003.png) + +#### 2.2.4. Animal Bites { #224-animal-bites } + +This section gathers information on general animal bites as much as specific information on snake and dog bites. The collected data are disaggregated by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age) and sex (male, female, other, unknown sex). + +![Animal Bites](resources/images/chis-ntd-y-004.png) + +#### 2.2.5. Skin NTDs { #225-skin-ntds } + +This is a simple collection of data on people screened for skin NTDs. + +![Skin NTDs](resources/images/chis-ntd-y-005.png) + +#### 2.2.6. Wound Care { #226-wound-care } + +This collects data on people who required and received adequate wound care for the wounds caused by NTDs. + +![Wound Care](resources/images/chis-ntd-y-006.png) + +#### 2.2.7. VL and Micro-Haematuria { #227-vl-and-micro-haematuria } + +The section collects data on VL and patients with either evident presence of blood in their urine or with positive results from the micro-haematuria dipstick. The data are disaggregated by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age) and sex (male, female, other, unknown sex). + +![VL and Micro-Haematuria](resources/images/chis-ntd-y-007.png) + +#### 2.2.8. Vector Reduction Measures { #228-vector-reduction-measures } + +This section gathers info on VC activities in the community and the targeted houses. + +![Vector Reduction Measures](resources/images/chis-ntd-y-008.png) + +#### 2.2.9. Physical Disability and Self-care { #229-physical-disability-and-self-care } + +The section collects the information on patients’ access to support activities and to the degree of people self-caring for their NTD-correlated symptoms and signs. + +The data is disaggregated by age groups (0-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age) and sex (male, female, other, unknown sex). + +![Physical Disability and Self-care](resources/images/chis-ntd-y-009.png) + +#### 2.2.10. Water Sources { #2210-water-sources } + +This aggregates teh basic information required to have an overview of safe water storage and the number mapped water sources in the community. + +![Water Sources](resources/images/chis-ntd-y-010.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the NTDs datasets: + +| name | instruction | operator | leftSide description | rightSide description | +|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|----------------------------------------------------| +| CH - AGW assessed for MNS disorders Vs AGW with a possible MNS symptoms | AGW assessed for MNS disorders should be less than or equal to AGW with a possible MNS symptoms | menor_que_o_igual_que | AGW assessed for MNS disorders | AGW with a possible MNS symptoms | +| CH - AGW with MNS disorders/receiving Vs AGW assessed for MNS MH disorders | AGW with MNS disorders/receiving should be less than or equal to AGW assessed for MNS MH disorders | menor_que_o_igual_que | AGW with MNS disorders/receiving | AGW assessed for MNS MH disorders | +| CH - AGW with MNS disorders/receiving Vs People with MNS disorders/receiving | AGW with MNS disorders/receiving should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | AGW with MNS disorders/receiving | People with MNS disorders/receiving | +| CH - Assessed for MNS disorders conditions by type Vs People with a possible MNS symptoms by type | Assessed for MNS disorders conditions by type should be less than or equal to People with a possible MNS symptoms by type | menor_que_o_igual_que | Assessed for MNS disorders conditions by type | People with a possible MNS symptoms by type | +| CH - Deaths within three months after a dog bite Vs People bitten by an animal in the community | Deaths within three months after a dog bite should be less than or equal to People bitten by an animal in the community | menor_que_o_igual_que | Deaths within three months after a dog bite | People bitten by an animal in the community | +| CH - Deaths within three months after a snakebite Vs People bitten by an animal in the community | Deaths within three months after a snakebite should be less than or equal to People bitten by an animal in the community | menor_que_o_igual_que | Deaths within three months after a snakebite | People bitten by an animal in the community | +| CH - HHs all containers covered and protected with lids Vs Households visited in the catchment area | HHs all containers covered and protected with lids should be less than or equal to Households visited in the catchment area | menor_que_o_igual_que | HHs all containers covered and protected with lids | Households visited in the catchment area | +| CH - HHs received campaigns on NTDs - one health appr Vs HHs targeted campaigns on NTDs - one health appr | HHs received campaigns on NTDs - one health appr should be less than or equal to HHs targeted campaigns on NTDs - one health appr | menor_que_o_igual_que | HHs received campaigns on NTDs - one health appr | HHs targeted campaigns on NTDs - one health appr | +| CH - HHs that received campaigns on NTDs - case mgt Vs HHs targeted campaigns on NTDs - case management | HHs that received campaigns on NTDs - case mgt should be less than or equal to HHs targeted campaigns on NTDs - case management | menor_que_o_igual_que | HHs that received campaigns on NTDs - case mgt | HHs targeted campaigns on NTDs - case management | +| CH - HHs that received campaigns on NTDs - PC Vs HHs targeted campaigns on NTDs - PC | HHs that received campaigns on NTDs - PC should be less than or equal to HHs targeted campaigns on NTDs - PC | menor_que_o_igual_que | HHs that received campaigns on NTDs - PC | HHs targeted campaigns on NTDs - PC | +| CH - HHs that received campaigns on NTDs - vector contr Vs HHs targeted campaigns on NTDs - vector control | HHs that received campaigns on NTDs - vector contr should be less than or equal to HHs targeted campaigns on NTDs - vector control | menor_que_o_igual_que | HHs that received campaigns on NTDs - vector contr | HHs targeted campaigns on NTDs - vector control | +| CH - Houses where vector reduction were implemented Vs Houses targeted for domiciliary vector reduction | Houses where vector reduction were implemented should be less than or equal to Houses targeted for domiciliary vector reduction | menor_que_o_igual_que | Houses where vector reduction were implemented | Houses targeted for domiciliary vector reduction | +| CH - MNS disorders receiving - recovery & rehab Vs People with MNS disorders/receiving | MNS disorders receiving - recovery & rehab should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - recovery & rehab | People with MNS disorders/receiving | +| CH - MNS disorders receiving - support for MH Vs People with MNS disorders/receiving | MNS disorders receiving - support for MH should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - support for MH | People with MNS disorders/receiving | +| CH - NTD cases who received adequate wound care Vs NTD cases presenting wound requiring care | NTD cases who received adequate wound care should be less than or equal to NTD cases presenting wound requiring care | menor_que_o_igual_que | NTD cases who received adequate wound care | NTD cases presenting wound requiring care | +| CH - NTD cases who received instructions for self-care Vs NTD cases relevant for self-care | NTD cases who received instructions for self-care should be less than or equal to NTD cases relevant for self-care | menor_que_o_igual_que | NTD cases who received instructions for self-care | NTD cases relevant for self-care | +| CH - People assessed for MNS disorders conditions Vs Assessed for MNS disorders conditions by type | People assessed for MNS disorders conditions should be less than or equal to Assessed for MNS disorders conditions by type | menor_que_o_igual_que | People assessed for MNS disorders conditions | Assessed for MNS disorders conditions by type | +| CH - People assessed for MNS disorders conditions Vs People with a possible MNS symptoms | People assessed for MNS disorders conditions should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People assessed for MNS disorders conditions | People with a possible MNS symptoms | +| CH - People bitten by an animal in the community Vs People bitten by animal in the community by animal | People bitten by an animal in the community should be less than or equal to People bitten by animal in the community by animal | menor_que_o_igual_que | People bitten by an animal in the community | People bitten by animal in the community by animal | +| CH - People receiving a dose of PC against NTDs Vs People targeted for PC against NTDs | People receiving a dose of PC against NTDs should be less than or equal to People targeted for PC against NTDs | menor_que_o_igual_que | People receiving a dose of PC against NTDs | People targeted for PC against NTDs | +| CH - People screened for skin NTDs Vs Population targeted for skin NTD screening | People screened for skin NTDs should be less than or equal to Population targeted for skin NTD screening | menor_que_o_igual_que | People screened for skin NTDs | Population targeted for skin NTD screening | +| CH - People with a possible MNS symptoms by type Vs People with a possible MNS symptoms | People with a possible MNS symptoms by type should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People with a possible MNS symptoms by type | People with a possible MNS symptoms | +| CH - People with MNS disorders - MH promotion and prev Vs People with MNS disorders/receiving | People with MNS disorders - MH promotion and prev should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders - MH promotion and prev | People with MNS disorders/receiving | +| CH - People with MNS disorders receiving - MH awareness Vs People with MNS disorders/receiving | People with MNS disorders receiving - MH awareness should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders receiving - MH awareness | People with MNS disorders/receiving | +| CH - People with MNS disorders/receiving Vs People assessed for MNS disorders | People with MNS disorders/receiving should be less than or equal to People assessed for MNS disorders | menor_que_o_igual_que | People with MNS disorders/receiving | People assessed for MNS disorders | +| CH - People with MNS disorders referred Vs People assessed for MNS disorders conditions | People with MNS disorders referred should be less than or equal to People assessed for MNS disorders conditions | menor_que_o_igual_que | People with MNS disorders referred | People assessed for MNS disorders conditions | +| CH - People with visible hematuria or with +ve dipstick Vs Individuals screened for micro-hematuria | People with visible hematuria or with +ve dipstick should be less than or equal to Individuals screened for micro-hematuria | menor_que_o_igual_que | People with visible hematuria or with +ve dipstick | Individuals screened for micro-hematuria | +| CH - Villages receiving PC against NTDs Vs Villages requiring PC against NTDs | Villages receiving PC against NTDs should be less than or equal to Villages requiring PC against NTDs | menor_que_o_igual_que | Villages receiving PC against NTDs | Villages requiring PC against NTDs | +| CH - With disability related to NTDs who receive rehab Vs Suffering from physical disability related to NTDs | With disability related to NTDs who receive rehab should be less than or equal to Suffering from physical disability related to NTDs | menor_que_o_igual_que | With disability related to NTDs who receive rehab | Suffering from physical disability related to NTDs | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the NTDs indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH041m - Women assessed for MNS disorders | Number of Women assessed for mental, neurological and substance use (MNS) disorders | Women assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH041 - People assessed for MNS disorders | Number of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health | +| CH041 - People assessed for MNS disorders (%) | Proportion of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | People with a possible MNS symptoms | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042b - Women referred for MNS disorders (%) | Proportion of Women with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | Women assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042 - People referred for MNS disorders (%) | Proportion of people with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH043 - People with MNS disorders receiving services (%) | Proportion of people with mental, neurologic and substance use (MNS) disorders receiving services | People with MNS disorders/receiving | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH135 - Suspected NTD cases reported | Number of suspected neglected tropical disease (NTD) cases reported | Suspected NTD cases reported | 1 | CH - Neglected tropical diseases | +| CH136 - Reported rumours of guinea worm disease/dracunculiasis cases | Number of reported rumours of guinea worm disease/dracunculiasis cases | Rumours of guinea worm disease cases reported | 1 | CH - Neglected tropical diseases | +| CH137 - Reported rumours of yaws cases | Number of reported rumoured yaws cases | Rumoured yaws cases reported | 1 | CH - Neglected tropical diseases | +| CH138 - People referred for NTDs | Number of people referred to health centre for diagnosis or treatment of NTDs | Referred for diagnosis or Tx of NTDs | 1 | CH - Neglected tropical diseases | +| CH139 - Communities receiving NTDs PC | Proportion of Communities/villages/localities receiving PC against NTDs | Villages receiving PC against NTDs | Villages requiring PC against NTDs | CH - Neglected tropical diseases | +| CH140 - People receiving a dose of NTDs PC (%) | Proportion of people having received a dose of chemo-prophylaxis for any targeted NTD | People receiving a dose of PC against NTDs | People targeted for PC against NTDs | CH - Neglected tropical diseases | +| CH141b - Households receiving NTD messages - CM | Proportion of households in the targeted communities that received social mobilization/awareness campaigns on NTDs - case management | Receiving NTD messages - CM | 1 | CH - Neglected tropical diseases | +| CH141c - Households receiving NTD messages - OneHealth | Proportion of households in the targeted communities that received social mobilization/awareness campaigns on NTDs - OneHealth | Receiving NTD messages - OneHealth | 1 | CH - Neglected tropical diseases | +| CH141d - Households receiving NTD messages - PC | Proportion of households in the targeted communities that received social mobilization/awareness campaigns on NTDs - PC | Receiving NTD messages - PC | 1 | CH - Neglected tropical diseases | +| CH141e - Households receiving NTD messages - VC | Proportion of households in the targeted communities that received social mobilization/awareness campaigns on NTDs - VC | Receiving NTD messages - VC | 1 | CH - Neglected tropical diseases | +| CH141 - Households having received social mobilization campaigns on NTDs (%) | Proportion of households in the targeted communities that received social mobilization/awareness campaigns on NTDs | HHs that received campaigns on NTDs - case mgt | HHs received campaigns on NTDs - one health appr | CH - Neglected tropical diseases | +| CH142 - People with animal bites | Number of people bitten by an animal (animal bite cases) in the community, by animal | People bitten by an animal in the community | 1 | CH - Neglected tropical diseases | +| CH143 - Deaths within three months from a snakebite | Number of deaths in the community occurring within three months after a snakebite or a dog bite | Deaths within three months after a snakebite | 1 | CH - Neglected tropical diseases | +| CH144 - People screened for skin NTDs (%) | Proportion of people screened for skin lesions consistent with NTDs (and population coverage) | People screened for skin NTDs | Population targeted for skin NTD screening | CH - Neglected tropical diseases | +| CH145 - NTD cases with adequate wound case (%) | Proportion of NTD cases that received adequate/recommended wound care | NTD cases who received adequate wound care | NTD cases presenting wound requiring care | CH - Neglected tropical diseases | +| CH146b - People presenting with wounds | Number of People presenting with wounds | People presenting with wounds | 1 | CH - Neglected tropical diseases | +| CH146 - People screened for VL and/or PKDL | Number of people screened for signs and symptoms of visceral leishmaniasis (VL) and/or PKDL (and population coverage) | Screened for signs of VL and/or PKDL | 1 | CH - Neglected tropical diseases | +| CH147 - People with visible haematuria or +ve micro-haematuria dipstick (%) | Proportion of people presenting hematuria, either visible hematuria reported by the patient or micro-hematuria detected by a positive dipstick | People with visible hematuria or with +ve dipstick | Individuals screened for micro-hematuria | CH - Neglected tropical diseases | +| CH148 - People with NTD-linked disability receiving rehab support (%) | Proportion of people suffering from physical disability related to NTDs who receive rehabilitation support | With disability related to NTDs who receive rehab | Suffering from physical disability related to NTDs | CH - Neglected tropical diseases | +| CH149 - NTD cases having received self-care instructions (%) | Proportion of NTD cases who received instructions for self-care for relevant NTDs | NTD cases who received instructions for self-care | NTD cases relevant for self-care | CH - Neglected tropical diseases | +| CH150 - Houses with implemented vector reduction measure (%) | Proportion of targeted houses covered by domiciliary vector reduction measures | Houses where vector reduction were implemented | Houses targeted for domiciliary vector reduction | CH - Neglected tropical diseases | +| CH151 - Surface water bodies enumerated and mapped | Number of surface water bodies enumerated and mapped | Surface water bodies enumerated and mapped | 1 | CH - Neglected tropical diseases | +| CH152b - Households visited in catchment area | Households visited in catchment area | HH in area | 1 | CH - Neglected tropical diseases | +| CH152 - Households with covered water containers (%) | Proportion of households with all water storage containers covered and protected | HHs all containers covered and protected with lids | Households visited in the catchment area | CH - Neglected tropical diseases | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - NTDs”. + +The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-ntd-db-001.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__newborn-health-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__newborn-health-md new file mode 100644 index 000000000..b5bb07cb6 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__newborn-health-md @@ -0,0 +1,143 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_nbh-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Newborn Health { #chis-agg-nbh-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration { #11-configuration } + +The aggregate CH - Newborn Health module includes: + +1. A **monthly dataset** with key data elements for newborn health +2. A **yearly dataset** for the follow up of key annual information on newborn health +3. **Core indicators** for both datasets +4. A predefined **“CH - Newborn Health”** dashboard + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the Newborn health module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the Newborn Health module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| CH052a - Newborns and children with danger signs | Newborns and children with danger signs in the community | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH052b - Newborns and children with danger signs referred | Newborns and children with danger signs referred | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH052c - Newborns and children consultations in the community | Newborns and children consultations in the community | CH - Child Health (Monthly), CH - ICCM (Monthly), CH - Newborn Health (Monthly) | CH - Newborn Health, CH - ICCM, CH - Child Health | +| CH045 - Stillbirths (late fetal deaths) | Stillbirths (late fetal deaths) | CH - Civil registration and vital statistics (Yearly), CH - Newborn Health (Yearly) | CH - Civil registration and vital statistics, CH - Newborn Health | +| CH046 - Neonatal deaths (0-27 days) | Neonatal deaths (0-27 days) | CH - Civil registration and vital statistics (Yearly), CH - Newborn Health (Yearly) | CH - Civil registration and vital statistics, CH - Newborn Health | +| CH047 - Newborns delivered in the community and put to breast within the first hour of birth | Newborns delivered in the community and put to breast within the first hour of birth | CH - Newborn Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Newborn Health | +| CH048 - Newborns with documented birth weight | Newborns delivered in the community with documented birthweight | CH - Newborn Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Newborn Health | +| CH049 - Newborns with low birth weight delivered in the community | Newborns with low birthweight delivered in the community | CH - Newborn Health (Monthly), CH - Nutrition (Monthly) | CH - Nutrition, CH - Newborn Health | +| CH050 - Newborn preterm discharged with CHW KMC follow-up | Preterm newborns discharged from facility that received follow-up on KMC by CHW | CH - Newborn Health (Monthly) | CH - Newborn Health | +| CH051 - Newborns preterm delivered in the community | Newborns preterm delivered in the community | CH - Newborn Health (Monthly) | CH - Newborn Health | +| CH053a - Newborns on skin-to-skin contact immediately after birth | Newborns initiated on skin-to-skin contact immediately after birth in community | CH - Newborn Health (Monthly) | CH - Newborn Health | +| CH053b - Preterms on skin-to-skin contact immediately after birth | Preterms on skin-to-skin contact immediately after birth | CH - Newborn Health (Monthly) | CH - Newborn Health | +| CH054 - Newborns with umbilical cord cut with sterile instrument | Newborns born in the community who had their umbilical cord cut with a new blade or boiled instrument | CH - Newborn Health (Monthly) | CH - Newborn Health | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly Newborn Health Dataset { #21-monthly-newborn-health-dataset } + +#### 2.1.1. Live Births { #211-live-births } + +This section is a simple agrgegation of the number of live births in the community by sex (male, female, other, unknown sex). + +![Live Births](resources/images/chis-nbh-m-001.png) + +#### 2.1.2. Breastfeeding and Birth Weight { #212-breastfeeding-and-birth-weight } + +This section collects the basic information needed to get an overview of the weight and breastfeeding habits upon birth. + +![Breastfeeding and Birth Weight](resources/images/chis-nbh-m-002.png) + +#### 2.1.3. Preterm Delivery { #213-preterm-delivery } + +The section gathers data on preterm deliveries and the use of KMC in the community. The data is disaggregated by age of the mother (10-14y, 15-19y, 20+y, unknown age) in the case of KMC, and by sex in the case of preterm babies (male, female, other, unknown sex). + +![Preterm Delivery](resources/images/chis-nbh-m-003.png) + +#### 2.1.4. Newborns and Children with Danger Signs { #214-newborns-and-children-with-danger-signs } + +The section gathers information on danger signs identified among newborn babies and children in the community. The information is disaggregated by age groups (0-27d, 28d-11m, 1-4y, 5-9y, unknown age). + +![Newborns and Children with Danger Signs](resources/images/chis-nbh-m-004.png) + +#### 2.1.5. Skin-to-skin Contact { #215-skin-to-skin-contact } + +This provides the space to report the simple aggregate on the number of newborns and preterm babies put to skin-to-skin contact after birth. + +![Skin-to-skin Contact](resources/images/chis-nbh-m-005.png) + +#### 2.1.6. Cutting the Umbilical Cord { #216-cutting-the-umbilical-cord } + +This provides the space to report the simple aggregate on the number of umbilical cord cutting procedures carried out with clean or sterile instruments. + +The information is disaggregated by the type of person performing the cut (lay person, CHW) - the options should be modified locally to better mirror the context. + +![Skin-to-skin Contact](resources/images/chis-nbh-m-006.png) + +### 2.2. Yearly Newborn Health Dataset { #22-yearly-newborn-health-dataset } + +#### 2.2.1. Stillbirths and Neonatal Deaths { #221-stillbirths-and-neonatal-deaths } + +This section gathers data on neonatal deaths disaggregated by age (0-6d, 7-27d, unknown age) and sex (male, female, other, unknown sex); and on stillbirths by gestational age (22-37w, 38-41w, 42+w, unknown age). + +![Skin-to-skin Contact](resources/images/chis-nbh-y-001.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Adolescent health datasets: + +| Nombre | Instrucción | Operador | Left side | Right side | +|:----------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:------------------------------------------------:|:----------------------------------------------------:| +| CH - Newborns and children with danger signs <= Newborns and children consultations in the community | Newborns and children with danger signs should be less than or equal to Newborns and children consultations in the community | menor_que_o_igual_que | Newborns and children with danger signs | Newborns and children consultations in the community | +| CH - Newborns and children with danger signs referred <= Newborns and children with danger signs | Newborns and children with danger signs referred should be less than or equal to Newborns and children with danger signs | menor_que_o_igual_que | Newborns and children with danger signs referred | Newborns and children with danger signs | +| CH - Newborns with low birth weight <= Newborns with documented birth weight | Newborns with low birthweight should be less than or equal to Newborns with documented birth weight | menor_que_o_igual_que | Newborns with low birthweight | Newborns with documented birth weight | +| CH - Preterm started on skin-to-skin immediately <= Preterm newborns | Preterm started on skin-to-skin immediately should be less than or equal to Preterm newborns | menor_que_o_igual_que | Preterm started on skin-to-skin immediately | Preterm newborns | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the aH indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|------------------------------------------------------|-------------------------------------------------------------------| +| CH002a - Live birth delivered in the community | Live birth delivered in the community | Livebirth | 1 | CH - Nutrition, CH - Newborn Health | +| CH045 - Stillbirths (late fetal deaths) | Number of stillbirths (late fetal deaths) in the community | Stillbirths | 1 | CH - Newborn Health, CH - Civil registration and vital statistics | +| CH046 - Neonatal deaths (0-27 days) | Number of neonatal deaths (0-27 days) in the community | Neonatal deaths (0-27 days) | 1 | CH - Newborn Health, CH - Civil registration and vital statistics | +| CH047 - Newborns breastfed within the 1st hour (%) | Proportion of newborns delivered in the community who were put to breast within the first hour of birth | Newborns delivered in the community put to breast within one hour of birth | Livebirth | CH - Nutrition, CH - Newborn Health | +| CH048 - Newborns with documented birth weight (%) | Proportion of newborns delivered in the community with documented birth weight | Newborns with documented birthweight | Livebirth | CH - Nutrition, CH - Newborn Health | +| CH049 - Low birth weight among newborns delivered in the community (%) | Prevalence of low birthweight among newborns delivered in the community | Newborns with low birthweight | Newborns with documented birthweight | CH - Nutrition, CH - Newborn Health | +| CH050 - Newborn preterm discharged with CHW KMC follow-up | Number of preterm-newborns discharged from facility who received follow-up on KMC by CHW | Preterm that received follow-up on KMC by CHW | 1 | CH - Newborn Health | +| CH051a - Preterm-newborns delivered in the community | Preterm-newborns delivered in the community | Preterm newborns | 1 | CH - Newborn Health | +| CH051 - Preterm-newborns delivered in the community (%) | Proportion of preterm-newborns delivered in the community | Preterm newborns | Livebirth | CH - Newborn Health | +| CH052a - Newborns and children with danger signs referred (%) | Proportion of newborns and children referred with danger signs | Newborns and children with danger signs referred | Newborns and children with danger signs | CH - Newborn Health, CH - ICCM | +| CH052b - Newborns and children with danger signs (%) | Proportion of newborns and children with danger signs | Newborns and children with danger signs | Newborns and children consultations in the community | CH - Newborn Health, CH - ICCM | +| CH052c - Newborns and children consultations in the community | Newborns and children consultations in the community | Newborns and children consultations | 1 | CH - Newborn Health, CH - ICCM | +| CH052d - Newborns and children referred with danger signs | Number of newborns and children referred with danger signs | Newborns and children with danger signs referred | 1 | CH - Newborn Health, CH - ICCM | +| CH052e - Newborns and children with danger signs | Number of newborns and children with danger signs | Newborns and children with danger signs | 1 | CH - Child Health, CH - Newborn Health, CH - ICCM | +| CH053a - Newborn preterm initiated on skin-to-skin contact immediately after birth (%) | Proportion of preterm-newborns delivered in the community initiated on skin-to-skin contact immediately after birth | Preterm started on skin-to-skin immediately | Preterm newborns | CH - Newborn Health | +| CH053b - Newborns initiated on skin-to-skin contact immediately after birth (%) | Proportion of newborns delivered in the community initiated on skin-to-skin contact immediately after birth | Newborns started on skin-to-skin immediately | Livebirth | CH - Newborn Health | +| CH054 - Newborns with umbilical cord cut with a new blade or boiled instrument | Number of newborns born in the community who had their umbilical cord cut with a new blade or boiled instrument | Umbilical cord cut with a new or boiled instrument | 1 | CH - Newborn Health | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Newborn Health”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-nbh-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-nbh-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__non-communicable-diseases-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__non-communicable-diseases-md new file mode 100644 index 000000000..1f38fd6df --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__non-communicable-diseases-md @@ -0,0 +1,183 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_ncd-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Non-communicable diseases { #chis-agg-ncd-design } + +## 1.Datasets { #1datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Non-communicable diseases (NCDs) module includes: + +1. A **monthly dataset** with key data elements for NCDs +2. A **yearly dataset** for the follow up of key annual information on NCDs +3. **Core indicators** for both datasets +4. A predefined **“CH - Non-communicable diseases”** dashboard + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the AH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the NCD module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| CH069a - Children (5-19 y) overweight and obese | Children and adolescents aged 5-19 years who are overweight | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH069b - Children (5-19 y) weighted | Children and adolescents aged 5-19 years who were measured | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH086 - Adolescents with insufficient physical activity | Adolescents with insufficient physical activity | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087a - Adolescent current tobacco users - smoked | Adolescent current tobacco users - smoked | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087b - Adolescent current tobacco users - smokeless | Adolescent current tobacco users - smokeless | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087c - Adolescent current tobacco users - daily users | Adolescent current tobacco users - daily users | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH087d - Adolescent current tobacco users - non-daily users | Adolescent current tobacco users - non-daily users | CH - Adolescent Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Adolescent Health | +| CH089a - People with heavy episodic drinking | People with heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089b - People assessed for heavy episodic drinking | People assessed for heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089c - Women with heavy episodic drinking | Women and adolescent girls with heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH089d - Women assessed for heavy episodic drinking | Women and adolescent girls assessed for heavy episodic drinking | CH - Adolescent Health (Yearly), CH - Mental health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Adolescent Health, CH - Noncommunicable diseases, CH - Mental health | +| CH068a - Children (0-4 y) overweight | Children aged 0-4 years visited by CHW and overweight | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH068b - Children (0-4 y) weighted | Children aged 0-4 years whose weight were measured | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly), CH - Nutrition (Yearly) | CH - Noncommunicable diseases, CH - Nutrition, CH - Child Health | +| CH080 - Children (0-4 y) with insufficient physical activity | Children aged 0-4 years not meeting who recommendations on physical activity for their age group | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Child Health | +| CH081 - Children (5-9 y) with insufficient physical activity | Children (5-9 y) with insufficient physical activity | CH - Child Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Child Health | +| CH021 - Households relying on clean energy for cooking | Households with primary reliance on clean fuels and technologies for cooking | CH - Clean energy (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Clean energy | +| CH031a - Women screened for cervical cancer | Women screened for cervical cancer | CH - HIV (Yearly), CH - Noncommunicable diseases (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Noncommunicable diseases, CH - Sexual and Reproductive Health | +| CH031b - Women who should have had a screening test for cervical cancer | Women who should have had a screening test for cervical cancer | CH - HIV (Yearly), CH - Noncommunicable diseases (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Noncommunicable diseases, CH - Sexual and Reproductive Health | +| CH038a - People with measured raised blood pressure | People with measured raised blood pressure | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | +| CH038b - Women with measured raised blood pressure - ANC | Women and adolescent girls with measured raised blood pressure during antenatal care | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | +| CH038c - Women with measured raised blood pressure - delivery | Women and adolescent girls with measured raised blood pressure during labour and delivery | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | +| CH038d - Women with high blood pressure - postpartum | Women and adolescent girls with measured raised blood pressure during postpartum care | CH - Maternal Health (Yearly), CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases, CH - Maternal Health | +| CH169a - People provided with heart attack and stroke support | Persons to whom heart attacks and stroke preventive and curative therapy support/follow-up was provided | CH - Noncommunicable diseases (Monthly) | CH - Noncommunicable diseases | +| CH169b - Adults (40+ y) with cardiovascular diseases and risk factors | Adults 40+ years with cardiovascular disease, or who are smoking, have high blood pressure, high cholesterol, or diabetes | CH - Noncommunicable diseases (Monthly) | CH - Noncommunicable diseases | +| CH165a - Current tobacco users (15+ years) - smoked | Current tobacco users (> 15 years) - smoked | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH165b - Current tobacco users (15+ years) - smokeless | Current tobacco users (> 15 years) - smokeless | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH165c - Current tobacco users (15+ years) - daily users | Current tobacco users (> 15 years) - daily users | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH165d - Current tobacco users (15+ years) - non-daily users | Current tobacco users (> 15 years) - non-daily users | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH166 - Adults with insufficient physical activity | Adults with insufficient physical activity | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH167a - Adults overweight | Adults overweight | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH167b - Adults assessed for overweight and obese | Adults assessed for overweight and obese | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH168a - Asymptomatic diabetic adults (40+ y) with BMI >= 25 | Asymptomatic adults aged 40+ years with a BMI >= 25 with diabetes measured by CHW | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH168b - Asymptomatic diabetic adults (40+ y) with BMI >= 25 on treatment | Asymptomatic adults aged 40+ years with a BMI >= 25 with diabetes measured by CHW and on medication | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | +| CH168c - Asymptomatic diabetic adults (40+ y) with BMI >= 25 in catchment area | Asymptomatic adults aged 40+ years with a BMI >= 25 in the catchment area | CH - Noncommunicable diseases (Yearly) | CH - Noncommunicable diseases | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly NCDs Dataset { #21-monthly-ncds-dataset } + +#### 2.1.1. Heart Attack and Stroke { #211-heart-attack-and-stroke } + +The section gathers the data related to adults older than 40 years at risk of cardiovascular diseases and to patients receiving support. The data are disaggregated by age (40-49y, 50-59y, 60-69y, 70-79y, 80+y, unknown age) and by sex (male, female, other, unknown sex). + +![Heart Attack and Stroke](resources/images/chis-ncd-m-001.png) + +### 2.2. Yearly NCDs Dataset { #22-yearly-ncds-dataset } + +#### 2.2.1. Clean Energy { #221-clean-energy } + +This is a simple overview of the number of households relying on clean energy for cooking. The options in the disaggregation should be edited according to the local context. + +![Clean Energy](resources/images/chis-ncd-y-001.png) + +#### 2.2.2. Cervical Cancer Screening { #222-cervical-cancer-screening } + +The section provides the information on the women in the community and whether they have been or should have been screened. + +![Cervical Cancer Screening](resources/images/chis-ncd-y-002.png) + +#### 2.2.3. Blood Pressure { #223-blood-pressure } + +The information collected in this section relates to raised blood pressure measurements either among the general population or among women during ANC visits or during delivery. In the former the disaggregation is by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+y, unknown age) and sex (male, female, other, unknown sex), while in the latter is by age (10-14y, 15-19y, 20-24y, 25-29y, 30-49y, 50+y, unknown age). + +![Blood Pressure](resources/images/chis-ncd-y-003.png) + +#### 2.2.4. Body Weight { #224-body-weight } + +The data in this section screens for overweight children. In the first section the disaggregation is by age (5-9y, 10-14y, 15-17y, 18-19y, unknown age) , while in the second is by age (0-11m, 1-4y) and sex (male, female, other, unknown sex). + +![Body Weight](resources/images/chis-ncd-y-004.png) + +#### 2.2.5. Physical Activity { #225-physical-activity } + +The section provides an overview of the levels of inefficient physical activity in the community. The info for children 0-4 years are disaggregated by age (0-11m and 1-4y) and sex (male, female, other, unknown sex). The info for adults is disaggregated by age (20-39y, 40-49y, 50-59y, 60-69y, 70+yn unknown age) and sex (male, female, other, unknown sex). Being the children between the age of 5 and 9 years belonging to what normally is a standardized age group, the disaggregation of the table is just by sex. + +![Physical Activity](resources/images/chis-ncd-y-005.png) + +#### 2.2.6. Tobacco Use { #226-tobacco-use } + +The data collected give an overview of the use of tobacco among adolescents and among people above 15 years of age. + +![Tobacco Use](resources/images/chis-ncd-y-006.png) + +#### 2.2.7. Overweight { #227-overweight } + +The collected data provide an overview of the data on 40+ years suffering from diabetes while being overweight (BMI>=25). The data is disaggregated by age (40-49y, 50-59y, 60-69y, 70+y, unknown age) and by sex (male, female, other, unknonw sex). The section also provides information on screening for overweight adults. The data is disaggregated by age (20-39y, 40-49y, 50-59y, 60-69y, 70+y, unknown age) and sex (male, female, other, unknonw sex). + +![Overweight](resources/images/chis-ncd-y-007.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the NCD health datasets: + +| name | instruction | operator | leftSide description | rightSide description | | +|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------|----------------------------------------------------|---| +| CH - Adults who are overweight Vs Adults who were measured | Adults who are overweight should be less than or equal to Adults who were measured | menor_que_o_igual_que | Adults who are overweight | Adults who were measured | | +| CH - Adults with BMI <= 25 and diabetes on medication Vs Adults with BMI<=25 and diabetic | Adults with BMI <= 25 and diabetes on medication should be less than or equal to Adults with BMI<=25 and diabetic | menor_que_o_igual_que | Adults with BMI <= 25 and diabetes on medication | Adults with BMI<=25 and diabetic | | +| CH - Adults with BMI<=25 and diabetic Vs Asymptomatic adults aged 40+ years with BMI <=25 | Adults with BMI<=25 and diabetic should be less than or equal to Asymptomatic adults aged 40+ years with BMI <=25 | menor_que_o_igual_que | Adults with BMI<=25 and diabetic | Asymptomatic adults aged 40+ years with BMI <=25 | | +| CH - Adults with insufficient physical activity Vs Adults aged 20+ years in the catchment area | Adults with insufficient physical activity should be less than or equal to Adults aged 20+ years in the catchment area | menor_que_o_igual_que | Adults with insufficient physical activity | Adults aged 20+ years in the catchment area | | +| CH - AGW assessed for heavy episodic drinking Vs People assessed for heavy episodic drinking | AGW assessed for heavy episodic drinking should be less than or equal to People assessed for heavy episodic drinking | menor_que_o_igual_que | AGW assessed for heavy episodic drinking | People assessed for heavy episodic drinking | | +| CH - AGW with heavy episodic drinking Vs People with heavy episodic drinking | AGW with heavy episodic drinking should be less than or equal to People with heavy episodic drinking | menor_que_o_igual_que | AGW with heavy episodic drinking | People with heavy episodic drinking | | +| CH - AGW with measured raised BP during ANC Vs People with measured raised blood pressure | AGW with measured raised BP during ANC should be less than or equal to People with measured raised blood pressure | menor_que_o_igual_que | AGW with measured raised BP during ANC | People with measured raised blood pressure | | +| CH - AGW with measured raised BP during postpartum care Vs People with measured raised blood pressure | AGW with measured raised BP during postpartum care should be less than or equal to People with measured raised blood pressure | menor_que_o_igual_que | AGW with measured raised BP during postpartum care | People with measured raised blood pressure | | +| CH - AGW with raised BP during labor and delivery Vs People with measured raised blood pressure | AGW with raised BP during labor and delivery should be less than or equal to People with measured raised blood pressure | menor_que_o_igual_que | AGW with raised BP during labor and delivery | People with measured raised blood pressure | | +| CH - Children 0-4 years visited by CHW and overweight Vs Children aged 0-4 years that were measured | Children 0-4 years visited by CHW and overweight should be less than or equal to Children aged 0-4 years that were measured | menor_que_o_igual_que | Children 0-4 years visited by CHW and overweight | Children aged 0-4 years that were measured | | +| CH - Children and adolescents 5-19 years overweight Vs Children and adolescents 5-19 years measured | Children and adolescents 5-19 years overweight should be less than or equal to Children and adolescents 5-19 years measured | menor_que_o_igual_que | Children and adolescents 5-19 years overweight | Children and adolescents 5-19 years measured | | +| CH - People with heavy episodic drinking Vs People assessed for heavy episodic drinking | People with heavy episodic drinking should be less than or equal to People assessed for heavy episodic drinking | menor_que_o_igual_que | People with heavy episodic drinking | People assessed for heavy episodic drinking | | +| CH - Provided heart attacks, stroke and cure support Vs Adults with HD, smokes, high BP, obese or diabetic | Provided heart attacks, stroke and cure support should be less than or equal to Adults with HD, smokes, high BP, obese or diabetic | menor_que_o_igual_que | Provided heart attacks, stroke and cure support | Adults with HD, smokes, high BP, obese or diabetic | | +| CH - Women who had a screening test for cervical cancer Vs Women who should have screened for cervical cancer | Women who had a screening test for cervical cancer should be less than or equal to Women who should have screened for cervical cancer | menor_que_o_igual_que | Women who had a screening test for cervical cancer | Women who should have screened for cervical cancer | | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the NCD indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|----------------------------------------------------|------------------------------------------------------------------------------------------| +| CH021 - Households relying on clean energy for cooking (%) | Proportion of households with primary reliance on clean fuels and technologies for cooking | HHs that rely on clean fuels and tech for cooking | Households in the catchment area | CH - Clean energy, CH - Noncommunicable diseases | +| CH031 - Women screened for cervical cancer (%) | Proportion of women who have been screened for cervical cancer | Women who had a screening test for cervical cancer | Women who should have screened for cervical cancer | CH - HIV, CH - Noncommunicable diseases, CH - Sexual and Reproductive Health | +| CH038b - Females with measured raised blood pressure (%) | Proportion of females with raised blood pressure measured by CHW | Females with measured raised blood pressure | Females 10+ years in the catchment area | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038c - Women with measured raised blood pressure - ANC | Number of Women with measured raised blood pressure - ANC | Women with measured raised blood pressure - ANC | 1 | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038d - Women with measured raised blood pressure - Delivery | Number of Women with measured raised blood pressure - Delivery | Women with measured raised blood pressure - Delivery | 1 | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038e - Women with measured raised blood pressure - Postpartum | Number of Women with measured raised blood pressure - Postpartum | Women with measured raised blood pressure - Postpartum | 1 | CH - Maternal Health, CH - Noncommunicable diseases | +| CH038 - People with measured raised blood pressure (%) | Proportion of people with raised blood pressure measured by CHW | People with measured raised blood pressure | People 10+ years in the catchment area | CH - Maternal Health, CH - Noncommunicable diseases | +| CH068 - Overweight children (0-4 y) (%) | Proportion of overweight among children under 5 years of age | Children 0-4 years visited by CHW and overweight | Children aged 0-4 years that were measured | CH - Nutrition, CH - Child Health, CH - Noncommunicable diseases | +| CH069 - Overweight and obese children (5-19 y) (%) | Proportion of overweight and obesity in school-age children and adolescents 5-19 years | Children and adolescents 5-19 years overweight | Children and adolescents 5-19 years measured | CH - Nutrition, CH - Child Health, CH - Adolescent Health, CH - Noncommunicable diseases | +| CH080 - Children (0-4 y) with insufficient physical activity (%) | Proportion of children aged 0-4 years with insufficient physical activity | Children 0-4 years not meeting required activity | Children aged 0-4 years in the catchment area | CH - Child Health, CH - Noncommunicable diseases | +| CH081 - Children (5-9 y) with insufficient physical activity (%) | Proportion of children aged 5-9years with insufficient physical activity | Children 5-9 years with insufficient activity | Children aged 5-9 years in the catchment area | CH - Child Health, CH - Noncommunicable diseases | +| CH086 - Adolescents with insufficient physical activity (%) | Proportion of adolescents with insufficient physical activity | Adolescents insufficient physical activity | Adolescents in the catchment area | CH - Adolescent Health, CH - Noncommunicable diseases | +| CH087 - Adolescents currently using tobacco (%) | Proportion of adolescents currently using tobacco | Adolescents currently using tobacco | Adolescents in the catchment area | CH - Adolescent Health, CH - Noncommunicable diseases | +| CH089 - People with heavy episodic drinking (%) | Proportion of people with heavy episodic drinking | People with heavy episodic drinking | People assessed for heavy episodic drinking | CH - Adolescent Health, CH - Mental health, CH - Noncommunicable diseases | +| CH165 - Current tobacco users (> 15 years) (%) | Proportion of current tobacco users above the age of 15 | Current tobacco users aged 15 years and over | People 15+ years | CH - Noncommunicable diseases | +| CH166 - Adults with insufficient physical activity (%) | Proportion of adults with insufficient physical activity | Adults with insufficient physical activity | Adults aged 20+ years in the catchment area | CH - Noncommunicable diseases | +| CH167 - Adults overweight (%) | Proportion of overweight and obesity in adults | Adults who are overweight | Adults who were measured | CH - Noncommunicable diseases | +| CH168 - Adults (40+ y) asymptomatic diabetic BMI >= 25 (%) | Proportion of asymptomatic adults older than 40 with a BMI>=25 who have raised blood glucose/diabetes as per CHW measurements | Adults with BMI>=25 and diabetic | Asymptomatic adults aged 40+ years with BMI>=25 | CH - Noncommunicable diseases | +| CH168b - Adults (40+ y) asymptomatic diabetic BMI >= 25 | Number of asymptomatic adults older than 40 with a BMI>=25 who have raised blood glucose/diabetes as per CHW measurements | Adults with BMI>=25 and diabetic | 1 | CH - Noncommunicable diseases | +| CH168c - Adults (40+ y) asymptomatic diabetic BMI >= 25 on treatment (%) | Proportion of asymptomatic adults older than 40 with a BMI>=25 who have raised blood glucose/diabetes as per CHW measurements and are on treatment | Adults with BMI>=25 and diabetic on treatment | Asymptomatic adults aged 40+ years with BMI>=25 | CH - Noncommunicable diseases | +| CH169b - Adults (40+ y) with cardiovascular diseases | Adults (40+ y) with cardiovascular diseases | Adults (40+ y) with cardiovascular diseases | 1 | CH - Noncommunicable diseases | +| CH169 - People provided with heart attack and stroke support (%) | Proportion of Persons to whom heart attacks and stroke preventive and curative therapy support/follow-up was provided | Provided heart attacks, stroke and cure support | Adults with HD, smokes, high BP, obese or diabetic | CH - Noncommunicable diseases | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - NCDs”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-ncd-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-ncd-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__nutrition-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__nutrition-md new file mode 100644 index 000000000..bb2da38b3 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__nutrition-md @@ -0,0 +1,251 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_nut-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Nutrition { #chis-agg-nut-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Nutrition (NUT) module includes: + +1. A **monthly dataset** with key data elements for nutrition +2. A **yearly dataset** for the follow up of key annual information on nutrition +3. **Core indicators** for both datasets +4. A predefined **“CH - Nutrition” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the NUT module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the NUT module are used in the build up of indicators. + +| Nombre | Descripción | Disaggregation | Data Sets | Data Element Groups | | +|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---| +| CH002a - Live births delivered in the community | Live births delivered in the community | Sex (Other/Unk) | CH - Population composition (Yearly); CH - Civil registration and vital statistics (Yearly) | CH - Nutrition; CH - Population composition; CH - Civil registration and vital statistics | | +| CH036a - Community ANC contacts | Community ANC contacts | default | CH - Maternal Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Maternal Health | | +| CH036b - Pregnant women counseled on breastfeeding during ANC contact | Community ANC contacts where pregnant women received any breastfeeding counselling | default | CH - Nutrition (Monthly); CH - Maternal Health (Monthly) | CH - Nutrition; CH - Maternal Health | | +| CH037 - Women given iron supplements during ANC | Community ANC contacts during which pregnant women were given/prescribed iron-containing supplements | default | CH - Nutrition (Monthly); CH - Maternal Health (Monthly) | CH - Nutrition; CH - Maternal Health | | +| CH047 - Newborns delivered in the community and put to breast within the first hour of birth | Newborns delivered in the community and put to breast within the first hour of birth | default | CH - Nutrition (Monthly); CH - Newborn Health (Monthly) | CH - Newborn Health; CH - Nutrition | | +| CH048 - Newborns with documented birth weight | Newborns delivered in the community with documented birthweight | default | CH - Newborn Health (Monthly); CH - Nutrition (Monthly) | CH - Newborn Health; CH - Nutrition | | +| CH049 - Newborns with low birth weight delivered in the community | Newborns with low birthweight delivered in the community | default | CH - Nutrition (Monthly); CH - Newborn Health (Monthly) | CH - Newborn Health; CH - Nutrition | | +| CH058a - Consultations for children (0-5 m) with feeding counselling | Consultations with a CHW for an infant aged 0-5 months providing any counselling on appropriate infant and young child feeding | default | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH058b - Consultations for children (0-5 m) with CHW | Consultations for children (0-5 m) with CHW | default | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH059a - Consultations for children (6-23 m) with feeding counselling | Consultations with a CHW for children aged 6-23 months providing any counselling on appropriate complementary feeding | default | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| CH059b - Consultations for children (6-23 m) with CHW | Consultations for children (6-23 m) with CHW | default | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH060a - People receiving deworming preventive chemotherapy | People receiving a dose of preventive chemotherapy for deworming | Age (1-20+years)/Sex (Other/Unk) | CH - Adolescent Health (Monthly); CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Adolescent Health; CH - Child Health | | +| CH060b -People targeted for deworming preventive chemotherapy | People targeted for preventive chemotherapy for deworming | Age (1-20+years)/Sex (Other/Unk) | CH - Child Health (Monthly); CH - Adolescent Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Adolescent Health; CH - Child Health | | +| CH060c - People receiving deworming preventive chemotherapy | People receiving a dose of preventive chemotherapy for deworming by drug | Deworming drugs | CH - Nutrition (Monthly); CH - Child Health (Monthly); CH - Adolescent Health (Monthly) | CH - Nutrition; CH - Adolescent Health; CH - Child Health | | +| CH061a - Children (6-59m) given Vit A in semester 1 - routine | Children aged 6-59 months who received vitamin a via routine contacts with CHW in semester 1 | Age (6-59 months)/Vitamin A supplement | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| CH061b - Children (6-59m) given Vit A in semester 2 routine | Children aged 6-59 months who received vitamin a via routine contacts with CHW in semester 2 | Age (6-59 months)/Vitamin A supplement | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH061c - Children (6-59m) with CHW contact in semester 1 routine | Children aged 6-59 months with at least one community contact in semester 1 | Age (6-59 months) | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| CH061d - Children (6-59m) with CHW contact in semester 2 routine | Children aged 6-59 months with at least one community contact in semester 2 | Age (6-59 months) | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| CH061e - Children (6-59m) given Vit A by CHW in semester 1 event | Children aged 6-59 months who received vitamin a by CHW via event in semester 1 | default | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH061f - Children (6-59m) given Vit A by CHW in semester 2 event | Children aged 6-59 months who received vitamin a by CHW via event in semester 2 | default | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH061g - Children (6-59m) attending Vit A event in semester 1 | Children aged 6-59 months attending events with vitamin A supplementation distributed via CHW in semester 1 | default | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| CH061h - Children (6-59m) attending Vit A event in semester 2 | Children aged 6-59 months attending events with vitamin A supplementation distributed via CHW in semester 2 | default | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH062a - Children (6-59m) assessed using MUAC or WHZ or bilateral pitting oedema | Children (6-59m) assessed using MUAC or WHZ or bilateral pitting oedema | Age (6-59 months) | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH062b - Children (6-59m) in the community | Children (6-59m) in the community | Age (6-59 months) | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| _CH062c - Children (6-59m) assessed for wasting referred | Children (6-59m) assessed for wasting referred | Age (6-59 months) | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| CH063a - Children (6-59m) with SAM | Children aged 6-59 months with severe acute malnutrition | Age (6-59 months) | CH - ICCM (Monthly); CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - ICCM; CH - Child Health | | +| CH063b - Children (6-59m) assessed for SAM | Children aged 6-59 months screened for severe acute malnutrition | Age (6-59 months) | CH - Child Health (Monthly); CH - Nutrition (Monthly); CH - ICCM (Monthly) | CH - Nutrition; CH - ICCM; CH - Child Health | | +| CH063c - Children (6-59m) with SAM referred | Children aged 6-59 months with severe acute malnutrition referred | Age (6-59 months) | CH - Child Health (Monthly); CH - ICCM (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - ICCM; CH - Child Health | | +| CH064 - Children (0-4 y) weight measured | Children aged <5 years visited by a CHW whose weight was assessed | Age (<5 years)/Sex (Other/Unk) | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH065 - Children (0-4 y) underweight | Number of children aged 0‚Äö√Ñ√ ̈5 years with weight for height > +2 SD from the median of the WHO Child Growth Standards | Age (<5 years)/Sex (Other/Unk) | CH - Child Health (Yearly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH066a - Children (6-59m) wasting or with bilateral pitting oedema | Children aged 6-59 months wasting or bilateral pitting oedema | Age (6-59 months)/Sex (Other/Unk) | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH066b - Children (6-59m) wasting or with bilateral pitting oedema referred | Children (6-59m) wasting or with bilateral pitting oedema referred | Age (6-59 months)/Sex (Other/Unk) | CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - Child Health | | +| _CH066c - Children (6-59m) assessed for wasting | Children (6-59m) assessed for wasting | Age (6-59 months)/Sex (Other/Unk) | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH067a - Children (0-4 y) with height measured | Children aged 0-4 years visited by a CHW whose height/length was measured | Age (<5 years)/Sex (Other/Unk) | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH067b - Children (0-4 y) consulted by a CHW | Children (0-4 y) consulted by a CHW | Age (<5 years)/Sex (Other/Unk) | CH - Child Health (Monthly); CH - Nutrition (Monthly) | CH - Nutrition; CH - Child Health | | +| CH068a - Children (0-4 y) overweight | Children aged 0-4 years visited by CHW and overweight | Age (<5 years)/Sex (Other/Unk) | CH - Child Health (Yearly); CH - Nutrition (Yearly); CH - Noncommunicable diseases (Yearly) | CH - Nutrition; CH - Child Health; CH - Noncommunicable diseases | | +| CH068b - Children (0-4 y) weighted | Children aged 0-4 years whose weight were measured | Age (<5 years)/Sex (Other/Unk) | CH - Noncommunicable diseases (Yearly); CH - Nutrition (Yearly); CH - Child Health (Yearly) | CH - Nutrition; CH - Child Health; CH - Noncommunicable diseases | | +| CH069a - Children (5-19 y) overweight and obese | Children and adolescents aged 5-19 years who are overweight | Age (5-19 years) | CH - Nutrition (Yearly); CH - Noncommunicable diseases (Yearly); CH - Child Health (Yearly); CH - Adolescent Health (Yearly) | CH - Nutrition; CH - Adolescent Health; CH - Child Health; CH - Noncommunicable diseases | | +| CH069b - Children (5-19 y) weighted | Children and adolescents aged 5-19 years who were measured | Age (5-19 years) | CH - Noncommunicable diseases (Yearly); CH - Child Health (Yearly); CH - Adolescent Health (Yearly); CH - Nutrition (Yearly) | CH - Nutrition; CH - Adolescent Health; CH - Child Health; CH - Noncommunicable diseases | | +| CH070a - Children (0-9 y) treated for diarrhoea | Children aged 0-9 years presenting with diarrhoea who received treatment | Age (0-9 years)/Diarrhoea treatment | CH - ICCM (Monthly); CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - ICCM; CH - Child Health | | +| CH070b - Children (0-9 y) assessed for diarrhoea | Children aged 0-9 years presenting with diarrhoea assessed by CHW | Age (0-9 years) | CH - ICCM (Monthly); CH - Nutrition (Monthly); CH - Child Health (Monthly) | CH - Nutrition; CH - ICCM; CH - Child Health | | +| CH084a - Women receiving anaemia-preventing iron supplements | Adolescent girls and menstruating women who received anaemia-preventing iron supplements | Age (10-20+years) | CH - Nutrition (Yearly); CH - Adolescent Health (Yearly) | CH - Nutrition; CH - Adolescent Health | | +| CH084b - Consultations with adolescent girls and menstruating women | Number of menstruating women and young adolescent girls who have received a consultation | Age (10-20+years) | CH - Nutrition (Yearly); CH - Adolescent Health (Yearly) | CH - Nutrition; CH - Adolescent Health | | +| CH085a - Women underweight | Non-pregnant women and adolescent girls with low bmi | Age (10-19 years) | CH - Nutrition (Yearly); CH - Adolescent Health (Yearly) | CH - Nutrition; CH - Adolescent Health | | +| CH085b - Consultations with non-pregnant women | Consultations non-pregnant women and adolescent girls | Age (10-19 years) | CH - Nutrition (Yearly); CH - Adolescent Health (Yearly) | CH - Nutrition; CH - Adolescent Health | | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1.Monthly NUT Dataset { #21monthly-nut-dataset } + +#### 2.1.1. ANC Contacts { #211-anc-contacts } + +The section gives an overview of the ANC contacts with women in the community and the activities carried out during those contacts (FE supplements distribution and breastfeeding counseling). + +![ANC Contacts](resources/images/chis-nut-m-001.png) + +#### 2.1.2. Breastfeeding and Birth Weight { #212-breastfeeding-and-birth-weight } + +This section collects the basic information needed to get an overview of the weight and breastfeeding habits upon birth. + +![Breastfeeding and Birth Weight](resources/images/chis-nut-m-002.png) + +#### 2.1.3. Infant Feeding { #213-infant-feeding } + +The section collects data on feeding counselling for children 0-5 months and for children 6-23 months. + +![Infant Feeding](resources/images/chis-nut-m-003.png) + +#### 2.1.4. Deworming { #214-deworming } + +The data collected provides the info on deworming PC. The info is disaggregated by age (1-4y, 5-9y, 10-14y, 15-19y, 20+y, unknown age) and sex (male, female, other, unknown sex). The data on people receiving PC is disaggregated by type of medication (Albendazole and Mebedazole). This disaggregation should be adapted according to local availability of PC drugs. + +![Deworming](resources/images/chis-nut-m-004.png) + +#### 2.1.5. Vitamin A Supplementation - Routine { #215-vitamin-a-supplementation-routine } + +The section focuses on routine vitamin A supplementation with children by age groups (6-11m and 12-59m) and by age and the administered IUs (100000 IU and 200000 IU). + +![Vitamin A Supplementation - Routine](resources/images/chis-nut-m-005.png) + +#### 2.1.6. Vitamin A Supplementation - Events { #216-vitamin-a-supplementation-events } + +The section focuses on the attendance to Vitamin A distribution one shot events. There is no disaggregation of data, though the collected info refer only to children aged 6-59 months. + +![Vitamin A Supplementation - Events](resources/images/chis-nut-m-005b.png) + +#### 2.1.7. Body Height { #217-body-height } + +The section reports the number of children who have been measured in height out of all the consultations. The data are disaggregated by age (0-11m and 1-4y) and by sex (male, female, other, unknown). + +![Body Height](resources/images/chis-nut-m-006.png) + +#### 2.1.8. Body Weight { #218-body-weight } + +This is a very simple reporting of the number of weighted children by age(0-11m and 1-4y) and by sex (male, female, other, unknown). + +![Body Weight](resources/images/chis-nut-m-007.png) + +#### 2.1.9. Severe Acute Malnutrition (SAM) { #219-severe-acute-malnutrition-sam } + +The data collected in this section focus on screenings for SAM among children under 5 years of age. The data is disaggregated by age (0-11m and 1-4y). + +![Severe Acute Malnutrition (SAM)](resources/images/chis-nut-m-008.png) + +#### 2.1.10. Wasting { #2110-wasting } + +The section collects data on the screening for wasting (MUAC, WHZ, bilateral pitting oedema) among children under the age of five years in the community. The data are disaggregated by age (6-11m, 12-59m) and by sex for the oedema (mala, female, other, unknown). + +![Wasting](resources/images/chis-nut-m-009.png) + +#### 2.1.11. Underweight Children { #2111-underweight-children } + +The section is a simple aggregation of the information on screened children and on those who have been found to be underweight. + +![Underweight Children](resources/images/chis-nut-m-010.png) + +#### 2.1.12. Diarrhoea { #2112-diarrhoea } + +The section provides data on children (0-9y) screened and treated for diarrhoea. The data is disaggregated by age (0-4y, and 5-9y) and by rehydration approach (Zinc, ORS, both). + +![Diarrhoea](resources/images/chis-nut-m-011.png) + +### 2.2. Yearly NUT Dataset { #22-yearly-nut-dataset } + +#### 2.2.1. Overweight (0-4 y) { #221-overweight-0-4-y } + +The section provides info on children between the age of 0 and 4 years and their weight assessment to monitor for overweight children by age (0-11 and 1-4y) and sex (male, female, other, unknown sex). + +![Overweight (0-4 y)](resources/images/chis-nut-y-001.png) + +#### 2.2.2. Obesity (5-19 y) { #222-obesity-5-19-y } + +The section focuses on the nutritional assessment of obese children in the community. The table disaggregates the data by age (5-9y, 10-14y, 15-17y, 18-19y, unknown age). + +![Obesity (5-19 y)](resources/images/chis-nut-y-002.png) + +#### 2.2.3. Underweight Women { #223-underweight-women } + +The section focuses on the weight assessment of women who are not pregnant. The table disaggregates the data by age (10-14y, 15-19y, 20+, unknown age). + +![Underweight Women](resources/images/chis-nut-y-003.png) + +#### 2.2.4. Iron Supplement { #224-iron-supplement } + +The section provides info on Iron supplementation among menstruating women. The data is disaggregated by age (10-14y, 15-19y, 20+y, unknown age). + +![Underweight Women](resources/images/chis-nut-y-004.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Nutrition datasets: + +| name | instruction | operator | leftSide description | rightSide description | +|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|---------------------------------------------------| +| CH - AG and menstruating women who received Vs Consultations with AG and menstruating women | AG and menstruating women who received should be less than or equal to Consultations with AG and menstruating women | menor_que_o_igual_que | AG and menstruating women who received | Consultations with AG and menstruating women | +| CH - ANC contacts given/prescribed iron supplements Vs Community ANC contacts | ANC contacts given/prescribed iron supplements should be less than or equal to Community ANC contacts | menor_que_o_igual_que | ANC contacts given/prescribed iron supplements | Community ANC contacts | +| CH - ANC contacts received breastfeeding counselling Vs Community ANC contacts | ANC contacts received breastfeeding counselling should be less than or equal to Community ANC contacts | menor_que_o_igual_que | ANC contacts received breastfeeding counselling | Community ANC contacts | +| CH - Children 0-4 years visited by CHW and overweight Vs Children aged 0-4 years that were measured | Children 0-4 years visited by CHW and overweight should be less than or equal to Children aged 0-4 years that were measured | menor_que_o_igual_que | Children 0-4 years visited by CHW and overweight | Children aged 0-4 years that were measured | +| CH - Children 0-4 years whose height was measured Vs Children aged 0-4 years consulted by a CHW | Children 0-4 years whose height was measured should be less than or equal to Children aged 0-4 years consulted by a CHW | menor_que_o_igual_que | Children 0-4 years whose height was measured | Children aged 0-4 years consulted by a CHW | +| CH - Children 0-9 years with diarrhoea who received tx Vs Children 0-9 y presenting diarrhoea assessed | Children 0-9 years with diarrhoea who received tx should be less than or equal to Children 0-9 y presenting diarrhoea assessed | menor_que_o_igual_que | Children 0-9 years with diarrhoea who received tx | Children 0-9 y presenting diarrhoea assessed | +| CH - Children 6-59 months visited by CHW & underweight Vs Children aged 6-59 months visited by a CHW | Children 6-59 months visited by CHW & underweight should be less than or equal to Children aged 6-59 months visited by a CHW | menor_que_o_igual_que | Children 6-59 months visited by CHW & underweight | Children aged 6-59 months visited by a CHW | +| CH - Children 6-59 months wasting referred Vs Children 6-59 months wasting | Children 6-59 months wasting referred should be less than or equal to Children 6-59 months wasting | menor_que_o_igual_que | Children 6-59 months wasting referred | Children 6-59 months wasting | +| CH - Children 6-59 months wasting Vs Children aged 6-59 months that were measured | Children 6-59 months wasting should be less than or equal to Children aged 6-59 months that were measured | menor_que_o_igual_que | Children 6-59 months wasting | Children aged 6-59 months that were measured | +| CH - Children 6-59 months with SAM referred Vs Children 6-59 months screened for SAM | Children 6-59 months with SAM referred should be less than or equal to Children 6-59 months screened for SAM | menor_que_o_igual_que | Children 6-59 months with SAM referred | Children 6-59 months screened for SAM | +| CH - Children 6-59 months with SAM Vs Children 6-59 months screened for SAM | Children 6-59 months with SAM should be less than or equal to Children 6-59 months screened for SAM | menor_que_o_igual_que | Children 6-59 months with SAM | Children 6-59 months screened for SAM | +| CH - Children 6-59 months with weight assessed Vs Children aged 6-59 months in the community | Children 6-59 months with weight assessed should be less than or equal to Children aged 6-59 months in the community | menor_que_o_igual_que | Children 6-59 months with weight assessed | Children aged 6-59 months in the community | +| CH - Children 6-59 mo received vit A by event in sem 1 Vs Children 6-59 mo attending vit A event in sem 1 | Children 6-59 mo received vit A by event in sem 1 should be less than or equal to Children 6-59 mo attending vit A event in sem 1 | menor_que_o_igual_que | Children 6-59 mo received vit A by event in sem 1 | Children 6-59 mo attending vit A event in sem 1 | +| CH - Children 6-59 mo received vit A by event in sem 2 Vs Children 6-59 mo attending vit A event in sem 2 | Children 6-59 mo received vit A by event in sem 2 should be less than or equal to Children 6-59 mo attending vit A event in sem 2 | menor_que_o_igual_que | Children 6-59 mo received vit A by event in sem 2 | Children 6-59 mo attending vit A event in sem 2 | +| CH - Children 6-59 mo received vit A in routine sem 1 Vs Children 6-59 mo with at least 1 contact in sem 1 | Children 6-59 mo received vit A in routine sem 1 should be less than or equal to Children 6-59 mo with at least 1 contact in sem 1 | menor_que_o_igual_que | Children 6-59 mo received vit A in routine sem 1 | Children 6-59 mo with at least 1 contact in sem 1 | +| CH - Children 6-59 mo received vit A in routine sem 2 Vs Children 6-59 mo with at least 1 contact in sem 2 | Children 6-59 mo received vit A in routine sem 2 should be less than or equal to Children 6-59 mo with at least 1 contact in sem 2 | menor_que_o_igual_que | Children 6-59 mo received vit A in routine sem 2 | Children 6-59 mo with at least 1 contact in sem 2 | +| CH - Children aged 6-59 months assessed for wasting Vs Children aged 6-59 months in the community | Children aged 6-59 months assessed for wasting should be less than or equal to Children aged 6-59 months in the community | menor_que_o_igual_que | Children aged 6-59 months assessed for wasting | Children aged 6-59 months in the community | +| CH - Children and adolescents 5-19 years overweight Vs Children and adolescents 5-19 years measured | Children and adolescents 5-19 years overweight should be less than or equal to Children and adolescents 5-19 years measured | menor_que_o_igual_que | Children and adolescents 5-19 years overweight | Children and adolescents 5-19 years measured | +| CH - Consultation for children 0-5 m & infant feeding Vs Consultations with a CHW for an infant 0-5 months | Consultation for children 0-5 m & infant feeding should be less than or equal to Consultations with a CHW for an infant 0-5 months | menor_que_o_igual_que | Consultation for children 0-5 m & infant feeding | Consultations with a CHW for an infant 0-5 months | +| CH - Consultation for children 6-23 m & comp feeding Vs Consultations with a CHW for children 6-23 months | Consultation for children 6-23 m & comp feeding should be less than or equal to Consultations with a CHW for children 6-23 months | menor_que_o_igual_que | Consultation for children 6-23 m & comp feeding | Consultations with a CHW for children 6-23 months | +| CH - Non-pregnant AGW with low BMI Vs Consultations non-pregnant AGW | Non-pregnant AGW with low BMI should be less than or equal to Consultations non-pregnant AGW | menor_que_o_igual_que | Non-pregnant AGW with low BMI | Consultations non-pregnant AGW | +| CH - Receiving a dose of PC for deworming by drug Vs Receiving a dose of PC for deworming | Receiving a dose of PC for deworming by drug should be less than or equal to Receiving a dose of PC for deworming | menor_que_o_igual_que | Receiving a dose of PC for deworming by drug | Receiving a dose of PC for deworming | +| CH - Receiving a dose of PC for deworming Vs People targeted for PC for deworming | Receiving a dose of PC for deworming should be less than or equal to People targeted for PC for deworming | menor_que_o_igual_que | Receiving a dose of PC for deworming | People targeted for PC for deworming | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the NUT indicator group. + +| name | Descripción | numerator Description | denominator Description | Indicator groups | +|---------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| CH002a - Live birth delivered in the community | Live birth delivered in the community | Livebirth | 1 | CH - Newborn Health; CH - Nutrition | +| CH036 - ANC visits with breastfeeding counselling (%) | Proportion of antenatal care contacts during which women received breastfeeding counselling | ANC contacts received breastfeeding counselling | Community ANC contacts | CH - Nutrition; CH - Maternal Health | +| CH037 - Women given/prescribed iron supplements during ANC (%) | Proportion of community antenatal care contacts given/prescribed iron-containing supplements | ANC contacts given/prescribed iron supplements | Community ANC contacts | CH - Nutrition; CH - Maternal Health | +| CH047 - Newborns breastfed within the 1st hour (%) | Proportion of newborns delivered in the community who were put to breast within the first hour of birth | Newborns delivered in the community put to breast within one hour of birth | Livebirth | CH - Newborn Health; CH - Nutrition | +| CH048 - Newborns with documented birth weight (%) | Proportion of newborns delivered in the community with documented birth weight | Newborns with documented birthweight | Livebirth | CH - Newborn Health; CH - Nutrition | +| CH049 - Low birth weight among newborns delivered in the community (%) | Prevalence of low birthweight among newborns delivered in the community | Newborns with low birthweight | Newborns with documented birthweight | CH - Newborn Health; CH - Nutrition | +| CH058 - Consultations for children (0-5 m) with feeding counselling (%) | Proportion of consultations for infants under 6 months providing counselling on appropriate infant and young child feeding | Consultation for children 0-5 m & infant feeding | Consultations with a CHW for an infant 0-5 months | CH - Nutrition; CH - Child Health | +| CH059 - Consultations for children (6-23 m) with feeding counselling (%) | Proportion of consultations for children 6-23 months providing counselling on appropriate complementary feeding | Consultation for children 6-23 mos & comp feeding | Consultations with a CHW for children 6-23 months | CH - Nutrition; CH - Child Health | +| CH060 - People receiving deworming preventive chemotherapy (%) | Proportion of people receiving preventive chemotherapy for deworming | Receiving a dose of PC for deworming | People targeted for PC for deworming | CH - Nutrition; CH - Child Health; CH - Adolescent Health | +| CH061b - Children (6-59m) given Vit A each semester event(%) | Proportion of children 6-59 months given a dose of vitamin A through event CHW contacts in each semester | Children 6-59 months given vitamin A event | Contacts with children 6-59 months through event CHW contacts for Vitamin A | CH - Nutrition; CH - Child Health | +| CH062 - Children (6-59 m) assessed for wasting (%) | Proportion of children aged 6-59 months assessed for wasting | Children aged 6-59 months assessed for wasting | Children aged 6-59 months in the community | CH - Nutrition; CH - Child Health | +| CH063 - Children (6-59 m) assessed for SAM (%) | Proportion of children 6-59 months with severe acute malnutrition (SAM) | Children 6-59 months with SAM | Children 6-59 months screened for SAM | CH - Nutrition; CH - Child Health; CH - ICCM | +| CH064 - Children (6-59 m) weighted | Number of children under 5 years (6-59 months) who had their weight assessed | Children 6-59 months with weight assessed | 1 | CH - Nutrition; CH - Child Health | +| CH065 - Children (0-4 y) underweight (%) | Proportion of children under 5 years who are underweight | Children aged 0-4 years visited by a CHW and underweight | Children weighed | CH - Nutrition; CH - Child Health | +| CH066 - Children (6-59m) wasting (%) | Proportion of children (6-59m) wasting | Children 6-59 months wasting | Children (6-59m) assessed using MUAC or WHZ or bilateral pitting oedema | CH - Nutrition; CH - Child Health | +| CH067 - Children (0-4 y) with measured height (%) | Proportion of children under 5 years who had their height/length measured | Children 0-4 years whose height was measured | Children aged 0-4 years consulted by a CHW | CH - Nutrition; CH - Child Health | +| CH068 - Overweight children (0-4 y) (%) | Proportion of overweight among children under 5 years of age | Children 0-4 years visited by CHW and overweight | Children aged 0-4 years that were measured | CH - Nutrition; CH - Child Health; CH - Noncommunicable diseases | +| CH069 - Overweight and obese children (5-19 y) (%) | Proportion of overweight and obesity in school-age children and adolescents 5-19 years | Children and adolescents 5-19 years overweight | Children and adolescents 5-19 years measured | CH - Nutrition; CH - Child Health; CH - Adolescent Health; CH - Noncommunicable diseases | +| CH070b - Children (0-9 y) assessed for diarrhoea | Children (0-9 y) assessed for diarrhoea | Children (0-9 y) assessed for diarrhoea | 1 | CH - Nutrition; CH - Child Health; CH - ICCM | +| CH070 - Children (0-9 y) treated for diarrhoea (%) | Proportion of children (0-9 years)who received treatment for diarrhoea | Children 0-9 years with diarrhoea who received tx | Children 0-9 yrs presenting diarrhoea assessed | CH - Nutrition; CH - Child Health; CH - ICCM | +| CH084b - Consultations with women | Consultations with women | Women consultations | 1 | CH - Nutrition | +| CH084 - Women receiving anaemia-preventing iron supplements (%) | Proportion of adolescent girls and women of reproductive age given iron-containing supplements for anaemia prevention | AG and menstruating women who received | Consultations with AG and menstruating women | CH - Nutrition; CH - Adolescent Health | +| CH085 - Underweight women (%) | Proportion of Women and adolescent girls who are underweight | Non-pregnant AGW with low BMI | Consultations non-pregnant AGW | CH - Nutrition; CH - Adolescent Health | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Nutrition”. +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-nut-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-nut-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__people-centered-services-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__people-centered-services-md new file mode 100644 index 000000000..471f19e4d --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__people-centered-services-md @@ -0,0 +1,114 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_pcs-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - People-Centered Services { #chis-agg-pcs-design } + +## 1.Datasets { #1datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - People-centered services (PCS) module includes: + +1. A **monthly dataset** with key data elements for PCS +2. A **yearly dataset** for the follow up of key annual information on PCS +3. **Core indicators** for both datasets +4. A predefined **“CH - People-centered services” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the PCS module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the PCS module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------| +| CH109a - People eligible referred for economic support | Eligible people referred for economic (livelihood) support by a CHW | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH109b - People eligible for economic support in catchment area | People eligible in the catchment area for economic (livelihood) support | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH109c - People eligible for economic support referred | Eligible people referred for economic (livelihood) support by a CHW by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH109d - People eligible for economic support by condition | Eligible people in the catchment area for economic (livelihood) support by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111a - People eligible referred for legal services | People eligible referred for legal services | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111b - People eligible for legal services in the catchment area | People eligible for legal services in the catchment area | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111c - People eligible referred for legal services | People eligible referred for legal services by a CHW by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111d - People eligible for legal services by condition | People eligible in the catchment area for legal services by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH110a - People eligible that receive(d) any form of economic support | People eligible that receive(d) any form of economic support | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH110b - People eligible that receive(d) any form of economic support | People eligible that receive(d) any form of economic support | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH112a - People eligible that receive(d) any form of legal services | People eligible that receive(d) any form of legal services | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH112b - People eligible that receive(d) any form of legal services by condition | People eligible that receive(d) any form of legal services by condition | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH172a - People who refuse health care | People who refuse health care | CH - People-centred services (Monthly) | CH - People-centred services | +| CH172b - People targeted by CHW for health care | People targeted by CHW for health care | CH - People-centred services (Monthly) | CH - People-centred services | +| CH171 - People with unmet health needs | People who needed health care and did not get it in the last month | CH - People-centred services (Yearly) | CH - People-centred services | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly PCS Dataset { #21-monthly-pcs-dataset } + +#### 2.1.1. Economic and Legal Support { #211-economic-and-legal-support } + +The section provides information about the eligible people receiving services and support for economic and legal reasons. The data is disaggregated by age (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and sex (male, female, other, unknown). The same info is disaggregableable by condition (HIV, TB, NTDs, Other) - the options should be adapted to better mirror the local context. + +![Economic and Legal Support](resources/images/chis-pcs-m-001.png) + +#### 2.1.2. Refusal of Health Care { #212-refusal-of-health-care } + +The section collects the data on people who decided to refuse health care. The disaggregation is by age (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and sex (male, female, other, unknown). + +![Refusal of Health Care](resources/images/chis-pcs-m-002.png) + +### 2.2. Yearly PCS Dataset { #22-yearly-pcs-dataset } + +#### 2.2.1. Economic and Legal Support { #221-economic-and-legal-support } + +The section provides the information on people who received economic or legal support and on those who have not received health care according to their health needs. + +The disaggregation of data is set by age (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34, 35-39y, 40-44y, 45-49y, 50+y) and sex (male, female, other, unknown). The eligible population can be disaggregated also by condition - currently the options are set as HIV, TB, NTDs and Other, but they should be adapted locally according to the context and the activities carried out in the community. + +![Economic and Legal Support](resources/images/chis-pcs-y-001.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Adolescent health datasets: +| Name | Instruction | Operator | Left side | Right side | +|:----------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:--------------------------------------------------:|:-------------------------------------------------:| +| CH - Eligible for economic support by condition Vs Eligible people for economic (livelihood) support | Eligible for economic support by condition should be less than or equal to Eligible people for economic (livelihood) support | less_than_or_equal_to | Eligible for economic support by condition | Eligible people for economic (livelihood) support | +| CH - Eligible people for legal services by condition Vs Eligible people for legal services | Eligible people for legal services by condition should be less than or equal to Eligible people for legal services | less_than_or_equal_to | Eligible people for legal services by condition | Eligible people for legal services | +| CH - Eligible referred for legal services by a CHW Vs Eligible people for legal services | Eligible referred for legal services by a CHW should be less than or equal to Eligible people for legal services | less_than_or_equal_to | Eligible referred for legal services by a CHW | Eligible people for legal services | +| CH - Receive(d) any form of econ support by condition Vs Receive(d) any form of economic support | Receive(d) any form of econ support by condition should be less than or equal to Receive(d) any form of economic support | less_than_or_equal_to | Receive(d) any form of econ support by condition | Receive(d) any form of economic support | +| CH - Receive(d) any form of legal services by condition Vs Receive(d) any form of legal services | Receive(d) any form of legal services by condition should be less than or equal to Receive(d) any form of legal services | less_than_or_equal_to | Receive(d) any form of legal services by condition | Receive(d) any form of legal services | +| CH - Referred for economic support Vs Eligible people for economic (livelihood) support | Referred for economic support should be less than or equal to Eligible people for economic (livelihood) support | less_than_or_equal_to | Referred for economic support | Eligible people for economic (livelihood) support | +| CH - Referred for econonic support by condition Vs Referred for economic support | Referred for econonic support by condition should be less than or equal to Referred for economic support | less_than_or_equal_to | Referred for econonic support by condition | Referred for economic support | +| CH - Referred for legal services by condition Vs Eligible referred for legal services by a CHW | Referred for legal services by condition should be less than or equal to Eligible referred for legal services by a CHW | less_than_or_equal_to | Referred for legal services by condition | Eligible referred for legal services by a CHW | +| CH - People who refuse health care Vs People targeted by CHW | People who refuse health care should be less than or equal to People targeted by CHW | less_than_or_equal_to | People who refuse health care | People targeted by CHW | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the PCS indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------------------------------------|---------------------------------------------------|-----------------------------------------------------------| +| CH109 - People eligible referred for economic support (%) | Proportion of people eligible for any form of economic support referred by a CHW | Referred for economic support | Eligible people for economic (livelihood) support | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH110 - People eligible received economic support (%) | Proportion of people eligible for any form of economic support who receive(d) it | Receive(d) any form of economic support | Eligible people for economic (livelihood) support | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH111 - People eligible referred for legal services (%) | Proportion of eligible people for legal services referred by a CHW | Eligible referred for legal services by a CHW | Eligible people for legal services | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH112 - People eligible having received legal services (%) | Proportion of eligible people that receive(d) any kind of legal services | Receive(d) any form of legal services | Eligible people for legal services | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH171 - People with unmet health needs | Number of people who needed care and did not get it in the last month | Needed health care and did not get last month | 1 | CH - People-centred services | +| CH172 - People refusing health care (%) | Proportion of people who refused care among those targeted by CHW | People who refuse health care | People targeted by CHW | CH - People-centred services | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - People-centered services”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-pcs-db-001.png) + +The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-pcs-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__population-composition-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__population-composition-md new file mode 100644 index 000000000..8bc9ddd76 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__population-composition-md @@ -0,0 +1,114 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_pop-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Population Composition { #chis-agg-pop-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Population composition (POP) module includes: + +1. A **yearly dataset** for the follow up of key POP data elements +2. **Core POP indicators** +3. A predefined **“CH - Population composition”** dashboard + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the AH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. As the population DEs are very much linked to the activities that are carried out, the DEs should be modified, or new ones should be added, to better mirror the activities. Please note that some population denominators are also found in other modules (e.g. Women and girls surveyed in the households visits, Screened children <5y, People (>18m) in the catchment area) and it is up to the user to decide whether they want to keep them in the current module or if they prefer moving them to the POP module. + +All the DEs in the POP module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|-------------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CH002a - Live births delivered in the community | Live births delivered in the community | CH - Civil registration and vital statistics (Yearly), CH - Population composition (Yearly) | CH - Population composition, CH - Newborn Health, CH - Civil registration and vital statistics | +| CH002b - Live births delivered in the community (by mother's age) | Live births delivered in the community by age of mother | CH - Civil registration and vital statistics (Yearly), CH - Population composition (Yearly) | CH - Civil registration and vital statistics, CH - Population composition | +| CH001a - Households in the catchment area | Households in the catchment area | CH - Population composition (Yearly) | CH - Population composition, CH - Clean energy, CH - Child protection & interpersonal violence, CH - Water, sanitation and hygiene (WASH), CH - Noncommunicable diseases | +| CH001b - Households with children (0-4 y) | Households in the catchment area with children aged 0-4 years | CH - Population composition (Yearly) | CH - Population composition | +| CH003 - Infants (0-11 m) in catchment area | Infants aged 0-11 months | CH - Population composition (Yearly) | CH - Population composition, CH - Immunization, CH - Noncommunicable diseases, CH - Child Health, CH - Mental health | +| CH004 - Children (1-4 y) in catchment area | Children aged 1-4 years in the catchment area | CH - Population composition (Yearly) | CH - Population composition, CH - Immunization, CH - Noncommunicable diseases, CH - Child Health, CH - Mental health | +| CH005 - Children (5-9 y) in catchment area | Children aged 5-9 years in the catchment area | CH - Population composition (Yearly) | CH - Population composition, CH - Noncommunicable diseases, CH - Child Health | +| CH006 - Young adolescents (10-14 y) in catchment area | Young adolescents aged 10-14 years in the catchment area | CH - Population composition (Yearly) | CH - Population composition, CH - Adolescent Health, CH - Noncommunicable diseases | +| CH007 - Older adolescents (15-19 y) in catchment area | Older adolescents aged 15-19 years in the catchment area | CH - Population composition (Yearly) | CH - Population composition, CH - Noncommunicable diseases, CH - Mental health | +| CH008 - Pregnant women in the catchment area | Pregnant women in the catchment area | CH - Population composition (Yearly) | CH - Population composition | +| CH009 - Adults 20+ years in the catchment area | Adults aged 20+ years in the catchment area | CH - Population composition (Yearly) | CH - Population composition, CH - Noncommunicable diseases, CH - Mental health | + +In the table below there are some examples of DEs that are not in the POP module but that nonetheless could be considered as population denominators. As aforementioned, it is up to the user to modify the modules in order to better represent the local context/activities, and to facilitate the collection of population data. + +| Nombre | Descripción | Data element groups | Datasets | | +|:------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------:|:---------------------------------------------------------:|:---------------------------------------------------------------------------------------:|---| +| CH101b - Pregnant women LWHA giving birth | Pregnant women living with HIV giving birth in the past 12 months in the catchment area | CH - HIV | CH - HIV (Monthly) | | +| CH106b - People with Known HIV status in catchment area | PLWHA who know their HIV status in the catchment area | CH - HIV | CH - HIV (Monthly) | | +| CH106d - Key population with known HIV status in catchment area | PLWHA who know their HIV status in the catchment area who are key population | CH - HIV | CH - HIV (Monthly) | | +| CH109b - Eligible people for economic support in catchment area | Eligible people in the catchment area for economic (livelihood) support | CH - People-centred services, CH - HIV, TB - Tuberculosis | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | | +| CH109d - Eligible people for economic support in catchment area | Eligible people in the catchment area for economic (livelihood) support by condition | CH - People-centred services, CH - HIV, TB - Tuberculosis | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | | +| CH111d - Eligible people for legal services in the catchment area | Eligible people in the catchment area for legal services by condition | CH - People-centred services, CH - HIV, TB - Tuberculosis | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | | +| CH146 - People screened for VL and/or PKDL | People screened for signs and symptoms of VL and/or PKDL in the catchment area | CH - Neglected tropical diseases | CH - Neglected tropical diseases (Yearly) | | +| CH168c - Asymptomatic diabetic adults (40+ y) with BMI >= 25 in catchment area | Asymptomatic adults aged 40+ years with a BMI ≥ 25 in the catchment area | CH - Noncommunicable diseases | CH - Noncommunicable diseases (Yearly) | | +| CH060b -People targeted for deworming preventive chemotherapy | People targeted for preventive chemotherapy for deworming | CH - Nutrition, CH - Adolescent Health, CH - Child Health | CH - Adolescent Health (Monthly), CH - Child Health (Monthly), CH - Nutrition (Monthly) | | +| CH141e - Households targeted for messages on NTDs - case management | Households targeted for social mobilization campaigns on NTDs - case management | CH - Neglected tropical diseases | CH - Neglected tropical diseases (Yearly) | | +| CH141f - Households targeted for messages on NTDs - OneHealth | Households targeted for social mobilization campaigns on NTDs - one health approach | CH - Neglected tropical diseases | CH - Neglected tropical diseases (Yearly) | | +| CH141g - Househoulds targeted for messages on NTDs - PC | Households targeted for social mobilization campaigns on NTDs - PC | CH - Neglected tropical diseases | CH - Neglected tropical diseases (Yearly) | | +| CH141h - Households targeted for messages on NTDs - VC | Households targeted for social mobilization campaigns on NTDs - vector control | CH - Neglected tropical diseases | CH - Neglected tropical diseases (Yearly) | | +| CH150b - Houses targeted for vector reduction measure | Houses targeted for domiciliary vector reduction measures | CH - Neglected tropical diseases | CH - Neglected tropical diseases (Yearly) | | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1.Yearly POP Dataset { #21yearly-pop-dataset } + +#### 2.1.1. Households { #211-households } + +The section reports information on the households in the catchment area of a specific community. + +![Households](resources/images/chis-pop-001.png) + +#### 2.1.2. Live Births { #212-live-births } + +The section reports the live births registered in the community by sex of the newborn (male, female, otehr, unknown sex) and by the age of the mother (10-14y, 15-19y, 20+y, unknown age). + +![Live Births](resources/images/chis-pop-002.png) + +#### 2.1.3. People in Catchment Area { #213-people-in-catchment-area } + +The section reports on pregnant women by age (10-14y, 15-19y, 20+y, unknown age), on the number of adults above the age of 20 years by age groups (20-29y, 30-39y, 40-49y, 50-59y, 60-69y, 70-79y, 80+y, unknown age) and by sex (male, female, other, unknown sex). Finally the section also reports data on children and adolescents in the area by sex (male, female, other, unknown sex). + +![People in Catchment Area](resources/images/chis-pop-003.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the POP dataset: + +| Nombre | Instrucción | Operador | Left side | Right side | +|:-------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------------:|:---------------------:|:--------------------------------------:|:--------------------------------------:| +| CH - Live births delivered by age of mother Vs Live births delivered in the community | Live births delivered by age of mother should be less than or equal to Live births delivered in the community | menor_que_o_igual_que | Live births delivered by age of mother | Live births delivered in the community | +| CH - HHs with chldren aged <5 years Vs Households in the catchment area | HHs with chldren aged <5 years should be less than or equal to Households in the catchment area | menor_que_o_igual_que | HHs with chldren aged <5 years | Households in the catchment area | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the POP indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|------------------------------------------------------------------|------------------------------------------------------------------------|------------------------------------------------|-------------|---------------------------------------------------------------------------| +| CH001 - Households in the catchment area | Number of households in the catchment area | Households in the catchment area | 1 | CH - Population composition | +| CH002 - Live births delivered in the community | Number of live births | Live births delivered in the community | 1 | CH - Population composition, CH - Civil registration and vital statistics | +| CH003 - Infants aged 0-11 months in the catchment area | Number of infants in the catchment area (0 to less than 1 year old) | Infants aged 0-11 months in the catchment area | 1 | CH - Immunization, CH - Population composition | +| CH004 - Children aged 1-4 years in the catchment area | Number of children in the catchment area (1 to less than 5 years old) | Children aged 1-4 years in the catchment area | 1 | CH - Immunization, CH - Population composition | +| CH005 - Children aged 5-9 years in the catchment area | Number of children in the catchment area (5 to less than 10 years old) | Children aged 5-9 years in the catchment area | 1 | CH - Population composition | +| CH006 - Young adolescents aged 10-14 years in the catchment area | Number of young adolescents in the catchment area (10-14 years old) | Young adolescents aged 10-14 years | 1 | CH - Population composition | +| CH007 - Older adolescents aged 15-19 years in the catchment area | Number of older adolescents in the catchment area (15-19 years old) | Older adolescents aged 15-19 years | 1 | CH - Population composition | +| CH008 - Pregnant women in the catchment area | Number of pregnant women in the catchment area | Pregnant women in the catchment area | 1 | CH - Population composition | +| CH009 - Adults aged 20+ years in the catchment area | Number of adults in the catchment area | Adults aged 20+ years in the catchment area | 1 | CH - Population composition | +| CH009b - Total population in the catchment area | Total population in the catchment area | Adults aged 20+ years in the catchment area | 1 | CH - Population composition | + +## 5. Dashboard { #5-dashboard } + +The module includes a predefined dashboard called “CH - Population composition”.The first part The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-pop-db-001.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__sexual-and-reproductive-health-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__sexual-and-reproductive-health-md new file mode 100644 index 000000000..9666c2ef8 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__sexual-and-reproductive-health-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_srh-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Sexual and Reproductive Health { #chis-agg-srh-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Sexual and reproductive health (SRH) module includes: + +1. A **monthly dataset** with key data elements +2. A y**early dataset** for the follow up of key annual information +3. **Core indicators** for both datasets +4. A predefined **“CH - Sexual and reproductive health” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the SRH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the SRH module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| CH027a - Adolescents seeking FP services | Adolescents and young people seeking family planning services from CHW | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH027b - Adolescents seeking FP methods tested for HIV | Adolescents and young people seeking family planning services who were tested for HIV by CHW | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH028a - HIV positive tests returned | HIV tests conducted in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028b - HIV tests returned | HIV tests returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028c - HIV positive tests returned to key population | HIV tests conducted amongst key population in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028d - HIV tests returned to key population | HIV tests performed amongst key population where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028e - HIV positive tests returned to TB patients | HIV tests conducted amongst TB in which a new HIV-positive result or diagnosis was returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH028f - HIV tests returned to TB patients | HIV tests performed amongst TB where results were returned | CH - Adolescent Health (Yearly), CH - Child Health (Yearly), CH - HIV (Yearly), CH - ICCM (Monthly), CH - Maternal Health (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Maternal Health, CH - ICCM, CH - Adolescent Health, CH - Sexual and Reproductive Health, CH - Child Health | +| CH034a - Women (15-49 years) with FGM | Women aged 15-49 years who have undergone FGM | CH - Child protection & interpersonal violence (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - Sexual and Reproductive Health, CH - Child protection & interpersonal violence | +| CH034b - Women (15-49 years) in the catchment area | Women (15-49 years) in the catchment area | CH - Child protection & interpersonal violence (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - Sexual and Reproductive Health, CH - Child protection & interpersonal violence | +| CH030a - Women tested for syphilis - 1st ANC | Women attending 1st ANC visit provided by CHW who were tested for syphilis | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH030b - Women tested for syphilis by CHW - 1st ANC | Women tested for syphilis by CHW - 1st ANC | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH030c - Women tested for syphilis - 2nd+ ANC | Women attending other ANC visits provided by CHW who were tested for syphilis | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH030d - Women tested for syphilis by CHW - 2nd+ ANC | Women attending other ANC visits provided by CHW | CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Sexual and Reproductive Health (Monthly) | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH024 - Condoms distributed | Condones distribuidos | CH - HIV (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - Sexual and Reproductive Health, CH - HIV | +| CH031a - Women screened for cervical cancer | Women screened for cervical cancer | CH - HIV (Yearly), CH - Noncommunicable diseases (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Noncommunicable diseases, CH - Sexual and Reproductive Health | +| CH031b - Women who should have had a screening test for cervical cancer | Women who should have had a screening test for cervical cancer | CH - HIV (Yearly), CH - Noncommunicable diseases (Yearly), CH - Sexual and Reproductive Health (Yearly) | CH - HIV, CH - Noncommunicable diseases, CH - Sexual and Reproductive Health | +| CH025 - Women and adolescent girls initiating modern FP methods | Women and adolescent girls initiating modern FP methods | CH - Sexual and Reproductive Health (Monthly) | CH - Sexual and Reproductive Health | +| CH029a - Men and adolescent boys with urethral discharge | Men and adolescent boys with urethral discharge | CH - Sexual and Reproductive Health (Monthly) | CH - Sexual and Reproductive Health | +| CH029b - Men and adolescent boys with urethral discharge referred | Men and adolescent boys with urethral discharge referred | CH - Sexual and Reproductive Health (Monthly) | CH - Sexual and Reproductive Health | +| CH029c - Men and adolescent boys in the community | Referred men and adolescent boys with urethral discharge | CH - Sexual and Reproductive Health (Monthly) | CH - Sexual and Reproductive Health | +| CH032 - Women referred for any post-abortion complication | Women referred for any post-abortion complication | CH - Sexual and Reproductive Health (Monthly) | CH - Sexual and Reproductive Health | +| CH033 - Women referred for safe abortion | Women referred for safe abortion | CH - Sexual and Reproductive Health (Monthly) | CH - Sexual and Reproductive Health | +| CH026 - Women and adolescent girls on modern FP methods | Women and adolescent girls on modern FP methods | CH - Sexual and Reproductive Health (Yearly) | CH - Sexual and Reproductive Health | + +## 2. Dataset Details { #2-dataset-details } + +In both the monthly and the yearly datasets the category combinations for the age groups have age groups that go beyond the [WHO definition of adolescents](https://www.who.int/southeastasia/health-topics/adolescent-health) “WHO defines '**Adolescents**' as individuals **in the 10-19 years age group** and '**Youth**' as **the 15-24 year age group**. While 'Young People' covers the age range 10-24 years” . This has been done to avoid creating *ad hoc* age groups for each and every dataset. The age groups above the definition of Adolescent/Youth have been greyed-out and therefore blocked for data entry. Countries should nonetheless edit and apply the age categories that better reflect the local context and guidelines. + +### 2.1. Monthly SRH Dataset { #21-monthly-srh-dataset } + +#### 2.1.1. Family Planning { #211-family-planning } + +The section summarizes the uptake of modern family planning methods. The data is disaggregated by age (10-14y, 15-19y, 20+y, unknown age) and methods (Pill, Condom, Injectable, Emergency contraception, vaginal barrier, LAM, Other FP method). The methods should be adapted to the local context. + +![Family Planning](resources/images/chis-srh-m-001.png) + +#### 2.1.2. Family Planning and HIV { #212-family-planning-and-hiv } + +The section collects data on adolescent routine HIV testing and on the uptake of modern FP methods. The former is disaggregated by age group (10-14y and 15-19y as per definition of adolescent) and by result of the test (positive, negative, indeterminate); while the latter is by age groups (10-14y and 15-19y as per definition of adolescent). + +![Family planning & HIV](resources/images/chis-srh-m-002.png) + +#### 2.1.3. Urethral Discharge { #213-urethral-discharge } + +The section collects data on men presenting with urethral discharge and on the number of referrals. The data is disaggregated by age groups (10-14y, 15-19y, 20+y, unknown age). + +![Urethral Discharge](resources/images/chis-srh-m-003.png) + +#### 2.1.4. Syphilis Screening { #214-syphilis-screening } + +The section monitors women through their ANC appointments. The data is disaggregated by age groups (10-14y, 15-19y, 20+y, unknown age). + +![Syphilis Screening](resources/images/chis-srh-m-004.png) + +#### 2.1.5. Abortion Care and Services { #215-abortion-care-and-services } + +The section captures the accessibility and the use of safe abortion care. The data is disaggregated by age groups (10-14y, 15-19y, 20+y, unknown age). + +![Abortion Care and Services](resources/images/chis-srh-m-005.png) + +### 2.2. Yearly SRH Dataset { #22-yearly-srh-dataset } + +#### 2.2.1 Condom Distribution { #221-condom-distribution } + +A quick overview of the number of distributed condoms by type of condom (female or male). +The data is disaggregated by age groups (10-14y, 15-19y, 20+y, unknown age). + +![Condom Distribution](resources/images/chis-srh-y-001.png) + +#### 2.2.2. HIV Tests - All { #222-hiv-tests-all } + +The section collects the info on returned and positive HIV tests among the general population benefiting from the Maternal health services. The data are collected by age (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and sex (female, other). + +![HIV Tests - All](resources/images/chis-srh-y-002.png) + +#### 2.2.3. HIV Tests - TB Case { #223-hiv-tests-tb-case } + +THe section collects the same information as the previous section, though among presumptive and confirmed TB cases. + +![HIV Tests - TB Case](resources/images/chis-srh-y-002b.png) + +#### 2.2.4. HIV Tests - Key Population { #224-hiv-tests-key-population } + +The section provides the information on the key population by type of key population groups (SW, Prisoners, IDU, TG, Other - these can be adapted to better mirror the local context). + +![HIV Tests - Key Population](resources/images/chis-srh-y-002c.png) + +#### 2.2.5. Cervical Cancer Screening { #225-cervical-cancer-screening } + +The section collects data on the number of women who had or should have had a screening contact. The data is disaggregated by age (10+-14y, 15-19y, 20-24y, 25-29y, 30-49y, 50+y, unknown age). + +![Cervical Cancer Screening](resources/images/chis-srh-y-003.png) + +#### 2.2.6. FGM { #226-fgm } + +The section briefly records data on FGM practices in the community reportinng the number of female who had undergone FGM among all the females present in the community. The data is disaggregated by age (15-19y, 20-40y, unknown age). + +![FGM](resources/images/chis-srh-y-004.png) + +#### 2.2.7. Family Planning { #227-family-planning } + +The section summarizes the uptake of modern family planning methods. The data is disaggregated by age (10-14y, 15-19y, 20+y, unknown age) and methods (Pill, Condom, Injectable, Emergency contraception, vaginal barrier, LAM, Other FP method). The methods should be adapted to the local context. + +![Family Planning](resources/images/chis-srh-y-005.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the SRH datasets: + +| Nombre | Instrucción | Operador | Left side | Right side | +|:-------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:--------------------------------------------------:|:--------------------------------------------------:| +| CH - HIV tests performed amongst KP & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst KP & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst KP & results returned | HIV tests performed where results were returned | +| CH - HIV tests performed amongst TB & results returned Vs HIV tests performed where results were returned | HIV tests performed amongst TB & results returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | HIV tests performed amongst TB & results returned | HIV tests performed where results were returned | +| CH - New HIV-positive result or diagnosis was returned Vs HIV tests performed where results were returned | New HIV-positive result or diagnosis was returned should be less than or equal to HIV tests performed where results were returned | menor_que_o_igual_que | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | +| CH - New HIV-positive result returned for KP Vs HIV tests performed amongst KP & results returned | New HIV-positive result returned for KP should be less than or equal to HIV tests performed amongst KP & results returned | menor_que_o_igual_que | New HIV-positive result returned for KP | HIV tests performed amongst KP & results returned | +| CH - New HIV-positive result returned for KP Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for KP should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for KP | New HIV-positive result or diagnosis was returned | +| CH - New HIV-positive result returned for TB Vs HIV tests performed amongst TB & results returned | New HIV-positive result returned for TB should be less than or equal to HIV tests performed amongst TB & results returned | menor_que_o_igual_que | New HIV-positive result returned for TB | HIV tests performed amongst TB & results returned | +| CH - New HIV-positive result returned for TB Vs New HIV-positive result or diagnosis was returned | New HIV-positive result returned for TB should be less than or equal to New HIV-positive result or diagnosis was returned | menor_que_o_igual_que | New HIV-positive result returned for TB | New HIV-positive result or diagnosis was returned | +| CH - AYP seeking FP services tested for HIV by CHW Vs AYP seeking family planning services from CHW | AYP seeking FP services tested for HIV by CHW should be less than or equal to AYP seeking family planning services from CHW | menor_que_o_igual_que | AYP seeking FP services tested for HIV by CHW | AYP seeking family planning services from CHW | +| CH - Women attending 1st ANC visit provided by CHW Vs Attending 1st ANC visit & tested for syphilis | Women attending 1st ANC visit provided by CHW should be less than or equal to Attending 1st ANC visit & tested for syphilis | menor_que_o_igual_que | Women attending 1st ANC visit provided by CHW | Attending 1st ANC visit & tested for syphilis | +| CH - Women attending other ANC visits provided by CHW Vs Other ANC visits tested for syphilis | Women attending other ANC visits provided by CHW should be less than or equal to Other ANC visits tested for syphilis | menor_que_o_igual_que | Women attending other ANC visits provided by CHW | Other ANC visits tested for syphilis | +| CH - Women who had a screening test for cervical cancer Vs Women who should have screened for cervical cancer | Women who had a screening test for cervical cancer should be less than or equal to Women who should have screened for cervical cancer | menor_que_o_igual_que | Women who had a screening test for cervical cancer | Women who should have screened for cervical cancer | +| CH - Women aged 15-49 years who have undergone FGM Vs Women aged 15-49 years in the catchment area | Women aged 15-49 years who have undergone FGM should be less than or equal to Women aged 15-49 years in the catchment area | menor_que_o_igual_que | Women aged 15-49 years who have undergone FGM | Women aged 15-49 years in the catchment area | +| CH - Men and adolescent boys with urethral discharge Vs Men and adolescent boys in the community | Men and adolescent boys with urethral discharge should be less than or equal to Men and adolescent boys in the community | menor_que_o_igual_que | Men and adolescent boys with urethral discharge | Men and adolescent boys in the community | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the SRH indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| CH024 - Condoms distributed | Number of condoms distributed | Condones distribuidos | 1 | CH - HIV, CH - Sexual and Reproductive Health | +| CH025 - Women and adolescent girls initiating modern FP methods | Number of women and adolescent girls (WAG) who initiate modern methods for family planning in the community | AGW initiating a modern contraceptive | 1 | CH - Sexual and Reproductive Health | +| CH026 - Women and adolescent girls on modern FP methods | Number of women and adolescent girls (WAGs) who use modern methods for family planning | Women and adolescent girls who use modern methods | 1 | CH - Sexual and Reproductive Health | +| CH027 - Adolescents seeking FP methods | Number of adolescents and young people seeking contraception/family planning who received an HIV test | AYP seeking FP services | 1 | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH027 - Adolescents seeking FP methods tested for HIV (%) | Proportion of adolescents and young people seeking contraception/family planning who received an HIV test | AYP seeking FP services tested for HIV by CHW | AYP seeking family planning services from CHW | CH - HIV, CH - Adolescent Health, CH - Sexual and Reproductive Health | +| CH028a - HIV tests with returned results | Number of HIV tests conducted and results returned | HIV tests performed where results were returned | 1 | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH028b - HIV +ve tests returned to people (%) | Proportion of HIV tests performed that were positive and results returned to people | New HIV-positive result or diagnosis was returned | HIV tests performed where results were returned | CH - HIV, CH - Child Health, CH - Maternal Health, CH - Adolescent Health, CH - ICCM, CH - Sexual and Reproductive Health | +| CH029 - Men and adolescent boys with urethral discharge (%) | Proportion of men and adolescent boys with urethral discharge | Men and adolescent boys with urethral discharge | Men and adolescent boys in the community | CH - Sexual and Reproductive Health | +| CH030 - Antenatal care attendees tested for syphilis (%) | Proportion of antenatal care attendees tested for syphilis | Women attending ANC & tested for syphilis | Women attending ANC provided by CHW | CH - HIV, CH - Maternal Health, CH - Sexual and Reproductive Health | +| CH031 - Women screened for cervical cancer (%) | Proportion of women who have been screened for cervical cancer | Women who had a screening test for cervical cancer | Women who should have screened for cervical cancer | CH - HIV, CH - Noncommunicable diseases, CH - Sexual and Reproductive Health | +| CH032 - Women referred for post-abortion complications | Number of women referred for any post-abortion complication | Women referred for any post-abortion complication | 1 | CH - Sexual and Reproductive Health | +| CH033 - Women referred for safe abortion | Number of women referred for safe abortion | Women referred for safe abortion | 1 | CH - Sexual and Reproductive Health | +| CH034b - Women (15-49 years) with FGM | Number of women aged 15-49 years old who have undergone female genital mutilation | Women aged 15-49 years who have undergone FGM | 1 | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | +| CH034 - Women (15-49 years) with FGM (%) | Proportion of women aged 15-49 years old who have undergone female genital mutilation | Women aged 15-49 years who have undergone FGM | Women aged 15-49 years in the catchment area | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | +| CH155 - Girls (0-14 y) who have undergone FGM (%) | Proportion of girls (0-14 y)who have undergone female genital mutilation (FGM) or are at risk of FGM | Girls (0-14 y) who have undergone FGM | Girls (0-14 y) | CH - Child protection & interpersonal violence, CH - Sexual and Reproductive Health | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Sexual and Reproductive Health”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +[https://drive.google.com/drive/u/0/folders/14tjbmJTetoNrUF8dPscCCBSemnjxO43i](https://drive.google.com/drive/u/0/folders/14tjbmJTetoNrUF8dPscCCBSemnjxO43i) SRH_DB_001 + +![Dashboard](resources/images/chis-srh-db-001.png) + + The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-srh-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__tuberculosis-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__tuberculosis-md new file mode 100644 index 000000000..74f7b6af1 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__tuberculosis-md @@ -0,0 +1,234 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_tb-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Tuberculosis { #chis-agg-tb-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Tuberculosis (TB) module includes: + +1. A **monthly dataset** with key data elements +2. A **yearly dataset** for the follow up of key annual information +3. **Core indicators** for both datasets +4. A predefined **“CH - Tuberculosis” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the TB module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. + +All the DEs in the TB module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH041a - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/ MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041b - People with possible MNS symptoms | People with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041c - People assessed for MNS disorders/ MH conditions | People assessed for MNS disorders/mental health conditions by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041d - People with possible MNS symptoms | People with possible symptoms of MNS conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041e - Women assessed for MNS disorders/ MH conditions | Women and adolescent girls assessed for MNS disorders / MH conditions | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH041f - Women with possible MNS symptoms | Women and adolescent girls with possible MNS symptoms | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042a - People with MNS disorders referred | People with MNS disorders referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042b - People with MNS disorders referred by type | People with MNS disorders referred by type | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH042c - Women with MNS disorders referred | Women and adolescent girls with MNS disorders/mental health conditions referred | CH - Adolescent Health (Monthly), CH - HIV (Monthly), CH - Maternal Health (Monthly), CH - Mental health (Monthly), CH - Neglected tropical diseases (Monthly), CH - Tuberculosis (Monthly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043a - People with MNS disorders receiving services | People with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043b - People assessed for MNS disorders | People assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043c - People with MNS disorders receiving services - MH awareness | People with MNS disorders/mental health conditions receiving services - mental health awareness | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043d - People with MNS disorders receiving services - MH HP | People with MNS disorders/mental health conditions receiving services - mental health promotion and prevention | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043e - People with MNS disorders receiving services - MH support | People with MNS disorders/mental health conditions receiving services - support for people with mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043f - People with MNS disorders receiving services - recovery/rehab | People with MNS disorders/mental health conditions receiving services - recovery and rehabilitation | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043g - Women with MNS disorders receiving services | Women and adolescent girls with MNS disorders/mental health conditions receiving services | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH043h - Women assessed for MNS disorders | Women and adolescent girls assessed for MNS disorders/mental health conditions | CH - Adolescent Health (Yearly), CH - HIV (Yearly), CH - Maternal Health (Yearly), CH - Mental health (Yearly), CH - Neglected tropical diseases (Yearly), CH - Tuberculosis (Yearly) | CH - Neglected tropical diseases, CH - HIV, CH - Maternal Health, CH - Adolescent Health, CH - Mental health, TB - Tuberculosis | +| CH109a - People eligible referred for economic support | Eligible people referred for economic (livelihood) support by a CHW | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH109b - People eligible for economic support in catchment area | People eligible in the catchment area for economic (livelihood) support | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH109c - People eligible for economic support referred | Eligible people referred for economic (livelihood) support by a CHW by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH109d - People eligible for economic support by condition | Eligible people in the catchment area for economic (livelihood) support by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111a - People eligible referred for legal services | People eligible referred for legal services | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111b - People eligible for legal services in the catchment area | People eligible for legal services in the catchment area | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111c - People eligible referred for legal services | People eligible referred for legal services by a CHW by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH111d - People eligible for legal services by condition | People eligible in the catchment area for legal services by condition | CH - HIV (Monthly), CH - People-centred services (Monthly), CH - Tuberculosis (Monthly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH110a - People eligible that receive(d) any form of economic support | People eligible that receive(d) any form of economic support | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH110b - People eligible that receive(d) any form of economic support | People eligible that receive(d) any form of economic support | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH112a - People eligible that receive(d) any form of legal services | People eligible that receive(d) any form of legal services | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH112b - People eligible that receive(d) any form of legal services by condition | People eligible that receive(d) any form of legal services by condition | CH - HIV (Yearly), CH - People-centred services (Yearly), CH - Tuberculosis (Yearly) | CH - HIV, CH - People-centred services, TB - Tuberculosis | +| CH127a - Confirmed TB cases referred by CHW | People who were confirmed with TB through referral by CHW | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH127b - People referred for TB confirmation | People who were referred by CHW for TB diagnosis | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH128a - Notified TB confirmed cases via CHW | People who were confirmed to have TB notified with TB through CHW referral | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH128b - Notified TB cases in the catchment area | Notified TB cases in the catchment area | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH129a - People followed-up for TPT by CHW | People to whom TPT continuation support/follow-up was provided by CHW | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH129b - People eligible to start TPT in catchment area | People who were eligible started on TPT in the catchment area of CHW | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH129c - People followed-up for TPT by CHW by HIV status and type | People followed-up for TPT by CHW by HIV status and type | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH129d - People eligible to start TPT ini catchment area by HIV status and type | People eligible to start TPT ini catchment area by HIV status and type | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH130a - People followed-up for adherence TPT by CHW | People receiving TB treatment to whom treatment adherence support was provided by CHW | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH130b - People receiving TB treatment in the catchment area | People receiving TB treatment in the catchment area | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH131a - Contacts of BCTB patients referred | Contacts of bacteriologically confirmed TB patients who were referred for diagnosis of TB disease | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH131b - Contacts of BCTB patients in catchment area | Contacts of bacteriologically confirmed TB patients in the catchment area of the CHW | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH131c - Contacts of BCTB patients by TB and HIV status referred | Contacts of bacteriologically confirmed TB patients who were referred for diagnosis of TB disease by HIV status | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH131d - Contacts of BCTB patients in catchment areaby TB and HIV status | Contacts of BCTB patients in catchment areaby TB and HIV status | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH132a - Treated TB cases with CB support | TB cases who were successfully treated and who benefited from any form of community-based treatment support | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH132b - Treated TB cases with CB adherence support | People to whom TB disease treatment adherence support was provided at community level | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH133a - People completing the TBT received via CHW | People who received TPT through CHW who completed the course | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH133b - People started on TPT in the catchment area | People started on TPT in the catchment area of designated health-care facility | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH133c - People completing the TBT received via CHW by indication | People completing the TBT received via CHW by indication | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH133d - People started on TPT in the catchment area by indication | People started on TPT in the catchment area of designated health-care facility by indication | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH134a - People with TBT side effects referred by CHW | People with TB with drug side effects referred to a health facility by a CHW to manage drug side effects | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH134b - People with TBT side effects referred by CHW for CM | People with TB with drug side effects referred to a health facility by a CHW to manage drug side effects | CH - Tuberculosis (Monthly) | TB - Tuberculosis | +| CH134c - People treated for TB in the catchment area | People treated for TB in the catchment area | CH - Tuberculosis (Monthly) | TB - Tuberculosis | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Monthly TB Dataset { #21-monthly-tb-dataset } + +#### 2.1.1. Mental Health Disorders and Conditions - All { #211-mental-health-disorders-and-conditions-all } + +The section focuses on all the people benefiting from MH assessments and referrals. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Mental Health Disorders and Conditions](resources/images/chis-tb-m-001.png) + +#### 2.1.2. Mental Health Disorders and Conditions - by Type { #212-mental-health-disorders-and-conditions-by-type } + +The information collected on the general population (section 2.1.1.) can also be disaggregated by type of condition (depression, psychoses, behavioural conditions, dementia, substance use, suicide/self harm) - the conditions should be edited and adapted to the local context. + +![Mental Health Disorders and Conditions - by Type](resources/images/chis-tb-m-001b.png) + +#### 2.1.3. Mental Health Disorders and Conditions - Pregnant and Postpartum { #213-mental-health-disorders-and-conditions-pregnant-and-postpartum } + +This section collects the same variables as the other two sections on MH, but it focuses specifically on pregnant and postpartum women benefiting from MH community activities. + +![Mental Health Disorders and Conditions - Pregnant and Postpartum](resources/images/chis-tb-m-001c.png) + +### 2.1.2. Legal and Economic Support { #212-legal-and-economic-support } + +The section gathers information on the eligible people who can benefit from legal and economic support. The same information can be collected by age group (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and by sex (male, female, other, unknown sex), or by type of condition (HIV, TB, NTDs, other - the options should be adapted locally to better mirrorx the context). + +![Legal and Economic Support](resources/images/chis-tb-m-002.png) + +#### 2.1.3. TB TPT { #213-tb-tpt } + +The section collects a wide range of data about TB preventive treatment. The first table targets people who completed the TPT by target category (PLHIV and contact - the options should be adapted locally to better mirror the context). The second bigger table summarises the info on people receiving TPT and their contacts. The information is disaggregated by age group (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and by sex (male, female, other, unknown sex). + +![TB TPT](resources/images/chis-tb-m-003.png) + +The third table gives more information on the HIV status of the people benefitting from the TPT. The information can be disaggregated by status (Positive or negative) and/or by TPT treatment regimen (GH, 4R, 3HP, 3HR, 1HP) and by HIV status (positive or negative). + +![TB TPT HIV](resources/images/chis-tb-m-003b.png) + +#### 2.1.4. Drug Side Effects { #214-drug-side-effects } + +The final section of the monthly dataset collects information on the side effects among people receiving the treatment and their referral for care. The data are disaggregated by age group (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and by sex (male, female, other, unknown sex). + +![Drug Side Effects](resources/images/chis-tb-m-004.png) + +### 2.2. Yearly TB Dataset { #22-yearly-tb-dataset } + +#### 2.2.1. Mental Health Conditions and Disorders - All { #221-mental-health-conditions-and-disorders-all } + +The section focuses on all the people benefiting from MH assessments and referrals among the TB patients. The data are disaggregated by age (10-14y, 15-19y, 20-39y, 40-49y, 50-59y, 60-69y, 70+, unknown age) and sex (male, female, other, unknown). + +![Mental Health Conditions and Disorders - All](resources/images/chis-tb-y-001.png) + +#### 2.2.2. Mental Health Conditions and Disorders - Awareness and Support { #222-mental-health-conditions-and-disorders-awareness-and-support } + +The section collects the number of people accessing MH-related services and support activities offered to TB patients in the community. + +![Mental Health Conditions and Disorders - Awareness and Support](resources/images/chis-tb-y-001b.png) + +#### 2.2.3. Mental Health Conditions and Disorders - Pregnant and Postpartum { #223-mental-health-conditions-and-disorders-pregnant-and-postpartum } + +This section collects the same variables as the other section on MH, but it focuses specifically on pregnant and postpartum TB(+) women. + +![Mental Health Conditions and Disorders - Pregnant and Postpartum](resources/images/chis-tb-y-001c.png) + +#### 2.2.4. Legal and Economic Support { #224-legal-and-economic-support } + +The section gathers information on the eligible people who can benefit from legal and economic support. The same information can be collected by age group (0-4y, 5-9y, 10-14y, 15-19y, 20-24y, 25-29y, 30-34y, 35-39y, 40-44y, 45-49y, 50+y, unknown age) and by sex (male, female, other, unknown sex), or by type of condition (HIV, TB, NTDs, other - the options should be adapted locally to better mirrorx the context). + +![Legal and Economic Support](resources/images/chis-tb-y-002.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the Adolescent health datasets: + +| Nombre | Instrucción | Operador | Left side | Right side | +|:---------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:--------------------------------------------------:|:-------------------------------------------------:| +| CH - AGW assessed for MNS disorders Vs AGW with a possible MNS symptoms | AGW assessed for MNS disorders should be less than or equal to AGW with a possible MNS symptoms | menor_que_o_igual_que | AGW assessed for MNS disorders | AGW with a possible MNS symptoms | +| CH - AGW with MNS disorders/receiving Vs AGW assessed for MNS MH disorders | AGW with MNS disorders/receiving should be less than or equal to AGW assessed for MNS MH disorders | menor_que_o_igual_que | AGW with MNS disorders/receiving | AGW assessed for MNS MH disorders | +| CH - AGW with MNS disorders/receiving Vs People with MNS disorders/receiving | AGW with MNS disorders/receiving should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | AGW with MNS disorders/receiving | People with MNS disorders/receiving | +| CH - Assessed for MNS disorders conditions by type Vs People with a possible MNS symptoms by type | Assessed for MNS disorders conditions by type should be less than or equal to People with a possible MNS symptoms by type | menor_que_o_igual_que | Assessed for MNS disorders conditions by type | People with a possible MNS symptoms by type | +| CH - MNS disorders receiving - recovery & rehab Vs People with MNS disorders/receiving | MNS disorders receiving - recovery & rehab should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - recovery & rehab | People with MNS disorders/receiving | +| CH - MNS disorders receiving - support for MH Vs People with MNS disorders/receiving | MNS disorders receiving - support for MH should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | MNS disorders receiving - support for MH | People with MNS disorders/receiving | +| CH - People assessed for MNS disorders conditions Vs Assessed for MNS disorders conditions by type | People assessed for MNS disorders conditions should be less than or equal to Assessed for MNS disorders conditions by type | menor_que_o_igual_que | People assessed for MNS disorders conditions | Assessed for MNS disorders conditions by type | +| CH - People assessed for MNS disorders conditions Vs People with a possible MNS symptoms | People assessed for MNS disorders conditions should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People assessed for MNS disorders conditions | People with a possible MNS symptoms | +| CH - People with a possible MNS symptoms by type Vs People with a possible MNS symptoms | People with a possible MNS symptoms by type should be less than or equal to People with a possible MNS symptoms | menor_que_o_igual_que | People with a possible MNS symptoms by type | People with a possible MNS symptoms | +| CH - People with MNS disorders - MH promotion and prev Vs People with MNS disorders/receiving | People with MNS disorders - MH promotion and prev should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders - MH promotion and prev | People with MNS disorders/receiving | +| CH - People with MNS disorders receiving - MH awareness Vs People with MNS disorders/receiving | People with MNS disorders receiving - MH awareness should be less than or equal to People with MNS disorders/receiving | menor_que_o_igual_que | People with MNS disorders receiving - MH awareness | People with MNS disorders/receiving | +| CH - People with MNS disorders/receiving Vs People assessed for MNS disorders | People with MNS disorders/receiving should be less than or equal to People assessed for MNS disorders | menor_que_o_igual_que | People with MNS disorders/receiving | People assessed for MNS disorders | +| CH - People with MNS disorders referred Vs People assessed for MNS disorders conditions | People with MNS disorders referred should be less than or equal to People assessed for MNS disorders conditions | menor_que_o_igual_que | People with MNS disorders referred | People assessed for MNS disorders conditions | +| CH - Eligible for economic support by condition Vs Eligible people for economic (livelihood) support | Eligible for economic support by condition should be less than or equal to Eligible people for economic (livelihood) support | menor_que_o_igual_que | Eligible for economic support by condition | Eligible people for economic (livelihood) support | +| CH - Eligible people for legal services by condition Vs Eligible people for legal services | Eligible people for legal services by condition should be less than or equal to Eligible people for legal services | menor_que_o_igual_que | Eligible people for legal services by condition | Eligible people for legal services | +| CH - Eligible referred for legal services by a CHW Vs Eligible people for legal services | Eligible referred for legal services by a CHW should be less than or equal to Eligible people for legal services | menor_que_o_igual_que | Eligible referred for legal services by a CHW | Eligible people for legal services | +| CH - Receive(d) any form of econ support by condition Vs Receive(d) any form of economic support | Receive(d) any form of econ support by condition should be less than or equal to Receive(d) any form of economic support | menor_que_o_igual_que | Receive(d) any form of econ support by condition | Receive(d) any form of economic support | +| CH - Receive(d) any form of legal services by condition Vs Receive(d) any form of legal services | Receive(d) any form of legal services by condition should be less than or equal to Receive(d) any form of legal services | menor_que_o_igual_que | Receive(d) any form of legal services by condition | Receive(d) any form of legal services | +| CH - Referred for economic support Vs Eligible people for economic (livelihood) support | Referred for economic support should be less than or equal to Eligible people for economic (livelihood) support | menor_que_o_igual_que | Referred for economic support | Eligible people for economic (livelihood) support | +| CH - Referred for econonic support by condition Vs Referred for economic support | Referred for econonic support by condition should be less than or equal to Referred for economic support | menor_que_o_igual_que | Referred for econonic support by condition | Referred for economic support | +| CH - Referred for legal services by condition Vs Eligible referred for legal services by a CHW | Referred for legal services by condition should be less than or equal to Eligible referred for legal services by a CHW | menor_que_o_igual_que | Referred for legal services by condition | Eligible referred for legal services by a CHW | +| CH - Confirmed TB notified with TB thru CHW referral Vs People who were notified with TB | Confirmed TB notified with TB thru CHW referral should be less than or equal to People who were notified with TB | menor_que_o_igual_que | Confirmed TB notified with TB thru CHW referral | People who were notified with TB | +| CH - Confirmed with TB through referral by CHW Vs People who were referred by CHW for TB diagnosis | Confirmed with TB through referral by CHW should be less than or equal to People who were referred by CHW for TB diagnosis | menor_que_o_igual_que | Confirmed with TB through referral by CHW | People who were referred by CHW for TB diagnosis | +| CH - Contacts of BC TB referred by HIV status Vs Contacts of BC TB cases by HIV status | Contacts of BC TB referred by HIV status should be less than or equal to Contacts of BC TB cases by HIV status | menor_que_o_igual_que | Contacts of BC TB referred by HIV status | Contacts of BC TB cases by HIV status | +| CH - Contacts of BC TB referred for diagnosis Vs Contacts of BC TB patients of the CHW | Contacts of BC TB referred for diagnosis should be less than or equal to Contacts of BC TB patients of the CHW | menor_que_o_igual_que | Contacts of BC TB referred for diagnosis | Contacts of BC TB patients of the CHW | +| CH - People started on TPT of designated HF indication Vs People started on TPT of designated HF | People started on TPT of designated HF indication should be less than or equal to People started on TPT of designated HF | menor_que_o_igual_que | People started on TPT of designated HF indication | People started on TPT of designated HF | +| CH - Received and completed TPT course by indication Vs Received TPT through CHW who completed the course | Received and completed TPT course by indication should be less than or equal to Received TPT through CHW who completed the course | menor_que_o_igual_que | Received and completed TPT course by indication | Received TPT through CHW who completed the course | +| CH - Receiving TB Tx with adherence support by CHW Vs People receiving TB Tx in the catchment area | Receiving TB Tx with adherence support by CHW should be less than or equal to People receiving TB Tx in the catchment area | menor_que_o_igual_que | Receiving TB Tx with adherence support by CHW | People receiving TB Tx in the catchment area | +| CH - TPT continuation support and follow-up by CHW Vs People who were eligible started on TPT of CHW | TPT continuation support and follow-up by CHW should be less than or equal to People who were eligible started on TPT of CHW | menor_que_o_igual_que | TPT continuation support and follow-up by CHW | People who were eligible started on TPT of CHW | +| CH - TPT follow-up by CHW by HIV status and type Vs Started on TPT by HIV status and type | TPT follow-up by CHW by HIV status and type should be less than or equal to Started on TPT by HIV status and type | menor_que_o_igual_que | TPT follow-up by CHW by HIV status and type | Started on TPT by HIV status and type | +| CH - Treated for TB & received community tx support Vs TB cases provided Tx support at community level | Treated for TB & received community tx support should be less than or equal to TB cases provided Tx support at community level | menor_que_o_igual_que | Treated for TB & received community tx support | TB cases provided Tx support at community level | +| CH - With TB drug side effects referred for mgt Vs People treated for TB in the catchment area | With TB drug side effects referred for mgt should be less than or equal to People treated for TB in the catchment area | menor_que_o_igual_que | With TB drug side effects referred for mgt | People treated for TB in the catchment area | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the TB indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| CH041m - Women assessed for MNS disorders | Number of Women assessed for mental, neurological and substance use (MNS) disorders | Women assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH041 - People assessed for MNS disorders | Number of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | 1 | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health | +| CH041 - People assessed for MNS disorders (%) | Proportion of people assessed for mental, neurological and substance use (MNS) disorders | People assessed for MNS disorders conditions | People with a possible MNS symptoms | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042b - Women referred for MNS disorders (%) | Proportion of Women with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | Women assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH042 - People referred for MNS disorders (%) | Proportion of people with mental, neurologic and substance use (MNS) referred | People with MNS disorders referred | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH043 - People with MNS disorders receiving services (%) | Proportion of people with mental, neurologic and substance use (MNS) disorders receiving services | People with MNS disorders/receiving | People assessed for MNS disorders conditions | CH - HIV, CH - Tuberculosis, CH - Neglected tropical diseases, CH - Maternal Health, CH - Adolescent Health, CH - Mental health | +| CH109 - People eligible referred for economic support (%) | Proportion of people eligible for any form of economic support referred by a CHW | Referred for economic support | Eligible people for economic (livelihood) support | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH110 - People eligible received economic support (%) | Proportion of people eligible for any form of economic support who receive(d) it | Receive(d) any form of economic support | Eligible people for economic (livelihood) support | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH111 - People eligible referred for legal services (%) | Proportion of eligible people for legal services referred by a CHW | Eligible referred for legal services by a CHW | Eligible people for legal services | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH112 - People eligible having received legal services (%) | Proportion of eligible people that receive(d) any kind of legal services | Receive(d) any form of legal services | Eligible people for legal services | CH - HIV, CH - Tuberculosis, CH - People-centred services | +| CH127 - People confirmed with TB via CHW referral (%) | Proportion of people confirmed with TB out of all people who were referred for diagnosis by CHW | Confirmed with TB through referral by CHW | People who were referred by CHW for TB diagnosis | CH - Tuberculosis | +| CH128b - Notified TB cases | Number of people notified with TB through CHW | People notified with TB through CHW | 1 | CH - Tuberculosis | +| CH128 - Notified TB-confirmed cases (%) | Proportion of people notified with TB through CHW referrals out of all people notified with TB | Confirmed TB notified with TB thru CHW referral | People who were notified with TB | CH - Tuberculosis | +| CH129 - People followed-up for TPT by CHW (%) | Proportion of people whose TB preventive treatment (TPT) support/follow-up was provided by CHW | TPT continuation support and follow-up by CHW | People who were eligible started on TPT of CHW | CH - Tuberculosis | +| CH130 - People followed-up for adherence TPT by CHW (%) | Proportion of People receiving TB treatment to whom treatment adherence support was provided by CHW | Receiving TB Tx with adherence support by CHW | People receiving TB Tx in the catchment area | CH - Tuberculosis | +| CH131 - Contacts of BCTB patients referred (%) | Proportion of contacts of BCTB patients referred | Contacts of BC TB referred for diagnosis | Contacts of BC TB patients of the CHW | CH - Tuberculosis | +| CH132b - TB cases eligible for TPT | TB cases eligible for TPT | People eligible to start TPT | 1 | CH - Tuberculosis | +| CH132c - HIV +ve TPT eligible people (%) | Proportion of people eligible to get started on TOT who are HIV positive | ppl eligible to start TPT who are HIV+ | People eligible to start TPT | CH - Tuberculosis | +| CH132 - Treated TB cases with CB support (%) | Proportion of people who were successfully treated and who benefited from community-based TB treatment adherence support | Treated for TB & received community tx support | TB cases provided Tx support at community level | CH - Tuberculosis | +| CH133 - People completing the TBT received via CHW (%) | Proportion of People who received TPT through CHW who completed the course | Received TPT through CHW who completed the course | People started on TPT of designated HF | CH - Tuberculosis | +| CH134 - People with TBT side effects referred by CHW (%) | Proportion of People with TB with drug side effects referred to a health facility by a CHW to manage drug side effects | With TB drug side effects referred for mgt | People treated for TB in the catchment area | CH - Tuberculosis | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - Tuberculosis”. + +The dashboard is divided in two based on the periodicity of the datasets. + +The first part is for monthly indicators. The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![Dashboard](resources/images/chis-tb-db-001.png) + + The second part of the dashboard is dedicated to the annual dataset (Annual Household Assessment Indicators). The predefined analyse and visualize the main areas of the dataset, though the dashboard should be modified to better mirror the local activities. + +![Dashboard](resources/images/chis-tb-db-002.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__water-sanitation-and-hygiene-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__water-sanitation-and-hygiene-md new file mode 100644 index 000000000..ac61ce13a --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__DESIGN__water-sanitation-and-hygiene-md @@ -0,0 +1,125 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/chis_agg_wash-design.md" +revision_date: '2022-11-02' +tags: +- Implementar +--- + +# CHIS - Water, Sanitation and Hygiene { #chis-agg-wash-design } + +## 1. Datasets { #1-datasets } + +### 1.1. Configuration Summary { #11-configuration-summary } + +The aggregate CH - Water, Sanitation and Hygiene (WASH) module includes: + +1. A **yearly dataset** for the follow up of key annual information +2. **Core indicators** for the dataset +3. A predefined **“CH - WASH” dashboard** + +It is recommended that the datasets get assigned to Organisation Units **at the lowest level** of the health system feasible for reporting data, such as Villages or any appropriate community demarcation according to the local context. + +### 1.2. Data Elements { #12-data-elements } + +The table below summarizes the data elements present in the WASH module. The “Data elements groups” and “Datasets” columns will provide extra information on where the same DEs can be found in the other CHIS modules. This should facilitate the mapping of the package among all its modules and navigate the datasets while avoiding the collection and data entry of the same DEs in multiple locations. In this case the DEs in the WASH module are not shared among any other module. + +All the DEs in the WASH module are used in the build up of indicators. + +| Nombre | Descripción | Datasets | DE groups | +|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CH001a - Households in the catchment area | Households in the catchment area | CH - Population composition (Yearly) | CH - Population composition, CH - Clean energy, CH - Child protection & interpersonal violence, CH - Water, sanitation and hygiene (WASH), CH - Noncommunicable diseases | +| CH010 - Households with access to an improved source of water | Households with access to an improved source of water | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH011 - Households accessing drinking water under 30 mins | Households needing not more than 30 minutes to access drinking-water | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH012 - Households with drinking water on premises | Households with drinking water on premises | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH013a - Water tests conducted - test results | Water tests conducted in the catchment area by test results | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH013b - Water tests conducted - type source | Water tests conducted in the catchment area by type of source | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH014 - Households with insufficient drinking water | Households that did not have sufficient quantities of drinking-water when needed | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH015a - Households with fixed hand-washing facilities on premises | Households with access to handwashing facilities with water and soap available on premises - fixed | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH015b - Households with mobile hand-washing facilities on premises | Households with access to handwashing facilities with water and soap available on premises - mobile | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH016 - Households with access to improved sanitation facilities | Households with access to improved sanitation facilities | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH017 - Households sharing sanitation facilities in use | Households sharing the sanitation facilities they use | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH018a - Households with onsite sanitation facilities never emptied | Households using on-site sanitation facilities that have ever been emptied | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH018b - Households with onsite sanitation facilities and storage | Households using on-site sanitation facilities with on-site storage | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH018c - Households with onsite sanitation facilities never emptied by emptying mode | Households using on-site sanitation facilities that have ever been emptied by emptying mode | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH018d - Households with onsite sanitation facilities and storage by emptying mode | Households with onsite sanitation facilities with storage by emptying mode | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH019a - Women with a private wash and change space during menses | Women and girls who have a private place to wash and change during menstruation | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH019b - Women and girls surveyed during household visits | Women and girls surveyed during household visits | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | +| CH020 - Women using hygiene products during menses | Women and girls using hygiene materials during menstruation | CH - Water, sanitation and hygiene (Yearly) | CH - Water, sanitation and hygiene (WASH) | + +## 2. Dataset Details { #2-dataset-details } + +### 2.1. Yearly WASH Dataset { #21-yearly-wash-dataset } + +#### 2.1.1. Drinking Water { #211-drinking-water } + +The section reports data on access to drinking water among the assessed households. The disaggregation of the data is by type of source of water (piped water, boreholes or tube wells, protected dug wells, protected springs, rainwater, packaged or delivered water - the categories should be adapted to better mirror the local context). + +![Drinking Water](resources/images/chis-wash-y-001.png) + +#### 2.1.2. Water Quality { #212-water-quality } + +The section focuses on the tests conducted on the water. The tests are disaggregated by results (positive and negative) and/or by source of the water (piped water, boreholes or tube wells, protected dug wells, protected springs, rainwater, packaged or delivered water - the categories should be adapted to better mirror the local context). + +![Water Quality](resources/images/chis-wash-y-002.png) + +#### 2.1.3. Hand-Washing Facilities { #213-hand-washing-facilities } + +The section reports the presence of fixed or mobile hand-washing facilities among the households. The disaggregation of the facilities is by location (dwelling, plot/yard, elsewhere). The categories can be edited according to the local context. + +![Hand-Washing Facilities](resources/images/chis-wash-y-003.png) + +#### 2.1.4.Improved/Shared Sanitation { #214improvedshared-sanitation } + +The section provides information on households sharing facilities (disaggregated by type of facility) and those having access to improved facilities (disaggregated by type of improved facility). + +![Improved/Shared Sanitation](resources/images/chis-wash-y-004.png) + +#### 2.1.5. Emptying of On-Site Sanitation Facilities { #215-emptying-of-on-site-sanitation-facilities } + +The section reports data on sanitation that are located on site and how they are emptied, if ever. The information is disaggregated by emptying method (service provider, buried, uncovered pit, open ground, water body, elsewhere - the options should be adapted to better mirror the local context) and by type of toilet/storage (latrines, septic tanks, composting toilet, twin pits). + +![Emptying of On-Site Sanitation Facilities](resources/images/chis-wash-y-005.png) + +#### 2.1.6. Hygiene Facilities { #216-hygiene-facilities } + +The section collects information on women and their accessibility to hygenic spaces and materials during their menses. The data on hygiene product is disaggregated by product type (Sanitary pads - disposable, sanitary pads - reusable, cloths - disposable, cloths - reusable, tampons - disposable, menstrual cups - reusable, other - disposable, other - reusable, none). + +![Hygiene Facilities](resources/images/chis-wash-y-006.png) + +## 3. Validation Rules { #3-validation-rules } + +The following validation rules have been set up for the WASH dataset: + +| name | instruction | operator | leftSide description | rightSide description | +|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------|---------------------------------------------------| +| CH - HHs on-site sanitation facilities never emptied Vs HHs on-site sanitation facilities on-site storage | HHs on-site sanitation facilities never emptied should be less than or equal to HHs on-site sanitation facilities on-site storage | menor_que_o_igual_que | HHs on-site sanitation facilities never emptied | HHs on-site sanitation facilities on-site storage | +| CH - Water tests conducted by type of source Vs Water tests conducted by test results | Water tests conducted by type of source should be less than or equal to Water tests conducted by test results | menor_que_o_igual_que | Water tests conducted by type of source | Water tests conducted by test results | +| CH - WYG have a private place to change during menses Vs Women and girls surveyed during household visits | WYG have a private place to change during menses should be less than or equal to Women and girls surveyed during household visits | menor_que_o_igual_que | WYG have a private place to change during menses | Women and girls surveyed during household visits | +| CH - WYG using hygiene materials during menses Vs Women and girls surveyed during household visits | WYG using hygiene materials during menses should be less than or equal to Women and girls surveyed during household visits | menor_que_o_igual_que | WYG using hygiene materials during menses | Women and girls surveyed during household visits | + +## 4. Analytics and Indicators { #4-analytics-and-indicators } + +Just as for the DEs, in the table below the column “Indicator Groups” provides information about whether the indicator is found in groups other than the WASH indicator group. + +| Nombre | Descripción | Numerador | Denominador | Indicator Groups | +|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|-------------------------------------------| +| CH010 - Households with access to an improved source of water (%) | Proportion of HH with access to an improved source of water | HHs with access to an improved source of water | Households in the catchment area | CH - Water, sanitation and hygiene (WASH) | +| CH011 - Households accessing drinking water under 30 mins (%) | Proportion of HH with time to collect drinking-water =< 30 minutes | HHs needing < 30 minutes to access drinking-water | Households in the catchment area | CH - Water, sanitation and hygiene (WASH) | +| CH012 - Households with drinking water on premises (%) | Proportion of HH with drinking water on premises | Households that have water on premises | Households in the catchment area | CH - Water, sanitation and hygiene (WASH) | +| CH013 - Water tests in catchment area -ve for E. coli (%) | Proportion of drinking-water quality at the sources negative for E. coli | Negative water tests conducted | Water tests conducted | CH - Water, sanitation and hygiene (WASH) | +| CH014 - Households with insufficient drinking water (%) | Proportion of HH with insufficient drinking-water when needed | HHs that lack sufficient amount of drinking-water | Households in the catchment area | CH - Water, sanitation and hygiene (WASH) | +| CH015 - Households with hand-washing facilities on premises (%) | Proportion of HH with access to handwashing facilities with water and soap available on premises | HHs handwashing facilities on premises - fixed | Households in the catchment area | CH - Water, sanitation and hygiene (WASH) | +| CH016 - Households with access to improved sanitation facilities (%) | Proportion of HH using improved sanitation facilities | HHs with access to improved sanitation facilities | Households in the catchment area | CH - Water, sanitation and hygiene (WASH) | +| CH017 - Households sharing sanitation facilities in use (%) | Proportion of HH sharing of sanitation facilities | HHs sharing the sanitation facilities they use | Households in the catchment area | CH - Water, sanitation and hygiene (WASH) | +| CH018 - Households with unemptied sanitation facilities on premises (%) | Proportion of HH with emptying of on-site sanitation facilities (septic tanks and pit latrines) | HHs on-site sanitation facilities never emptied | HHs on-site sanitation facilities on-site storage | CH - Water, sanitation and hygiene (WASH) | +| CH019 - Women with a private wash and change space during menses (%) | Proportion of women with private place to wash and change during menstruation | WYG have a private place to change during menses | Women and girls surveyed during household visits | CH - Water, sanitation and hygiene (WASH) | +| CH020 - Women using hygiene products during menses (%) | Proportion of women using of hygiene materials during menstruation | WYG using hygiene materials during menses | Women and girls surveyed during household visits | CH - Water, sanitation and hygiene (WASH) | + +## 5. Dashboards { #5-dashboards } + +The module includes a predefined dashboard called “CH - WASH”. + +The predefined items on the dashboard include data as per the sections present in the dataset, but the content should be adapted based on the local activities. + +![WASH Dashboard](resources/images/chis-wash-db.png) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__IMPLEMENTATION__sustainability-and-governance-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__IMPLEMENTATION__sustainability-and-governance-md new file mode 100644 index 000000000..d345aa95e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__IMPLEMENTATION__sustainability-and-governance-md @@ -0,0 +1,574 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/chis_implementation/08_governance_sustainability.md" +revision_date: '2022-04-20' +tags: +- Implementar +--- + +# Sustainability and Governance { #sustainability-and-governance } + +## Introducción { #introduction } + +Ensuring sustainability, broadly concerning how the CHIS endures over time and space is one of the most difficult challenge that policy makers and implementers have to deal with. + +The key to long term sustainability rests with governance of data management, which is a cross-cutting issue that involves formal management structures, policies and procedures, staffing, and workforce development, monitoring and evaluation of the CHIS program. By the end of this chapter, readers should be able to: + +## What Do We Mean by Sustainability? { #what-do-we-mean-by-sustainability } + +Sustainability of HIS in general, and CHIS in particular, is one of the most significant challenges facing designers, implementers, and policy makers of CHIS. Sustainability is a "wicked" problem, implying that if you try to address one of its facets, other problems will arise elsewhere. For example, to address the problem of CHIS continuity, a donor may be approached for funding. However, this may lead to other dependencies that can further put pressure on sustainability. + +Some relevant characteristics of a sustainable CHIS include: + +1. The CHIS must be well integrated into existing organizational routines of work practices, budgeting, training, reporting, and infrastructure provision. +2. On one hand the CHIS has to be well institutionalized, on the other hand, it must remain flexible, so that it can continue to evolve with the changing informational needs of the health system. This often leads to a dilemma of ensuring both stability and change, which designers and implementers have to constantly engage with. +3. The CHIS must be integrated with other systems like the routine facility HIS to ensure it does not remain standalone and lead to double work for the CHWs. A standalone CHIS is a sure recipe for unsustainability. +4. The outputs of the CHIS must provide real value to the key stakeholders, particularly the CHWs and their supervisors, but also mid-level and senior system managers. + +## Ensuring CHIS Sustainability { #ensuring-chis-sustainability } + +To address sustainability the primary focus of CHIS design should be on strengthening the "demand side" conditions such as how the CHIS adds value to the CHW, how it is integrated with their everyday work practices, and their needs for ongoing technical and public health support, rather than the dominant "supply side" approach of merely providing computers, internet and training. + +To make a CHIS sustainable, planners need to address key technical, organizational and behavioral factors. These are explained in detail in the Performance of Routine Information Systems (PRISM) framework^[MEASURE Evaluation, “PRISM: Performance of Routine Information System Management Framework,” [https://www.measureevaluation.org/resources/prism.html](https://www.measureevaluation.org/resources/prism.html)] and shown schematically in Figure 6.1 below. + +![](resources/images/chis_figure39.png) + +*Figure 6.1:* The PRISM framework + +In this approach, CHIS inputs such as assessments, interventions and strategies need to be addressed by technical, organizational, and behavioral determinants in order to achieve the desired outputs of a sustainable system that produces good quality information used to improve overall health system performance. A few aspects focused specifically on CHIS sustainability are detailed below. + +1. **Technical Design** + + a. **Integrated CHIS**: There are a number of examples of CHIS developed as an integrated part of the overall HMIS, linked directly to other systems in the community, particularly the routine facility information systems. Using an architectural approach, the CHIS becomes part of the system, reducing CHW workload and adding value. + b. **Increasing ICT infrastructure**: MHealth projects are increasingly based on internet connectivity, which is increasing exponentially allowing the use of android devices and mobile phones. However, This infrastructure must be carefully assessed, ensuring that the CHIS projects use available connectivity to its maximum while becoming fully operational. + c. **Free open Source software (FOSS) systems**: Successful CHIS projects are developed based on free open source software such as DHIS2, ensuring interoperability with other systems. FOSS flexibility and iterative design processes allow ongoing changes required for the application. As a result, the CHIS can evolve with changing needs, constantly adapted to the needs of the end users. +2. **Human Behavior** + Human behavior is the most difficult aspect of implementing a sustainable CHIS, and this aspect needs consistent attention. This phenomenon is increasingly being addressed by dealing with common issues with CHIS such as: + + a. **Changing Facility Staff attitude to CHWs.** Many health workers do not understand the role of CHWs and look down on their work as being second class. Major effort needs to be put into encouraging facility level workers to support the community health services, the CHIS and providing CHWs with necessary feedback, support and supervision. Facility staff also need to be involved in addressing sustainable remuneration of CHWs, building this into the budgets, to increase motivation, reduce dropout, and minimize attrition. + b. **Providing targeted feedback.** CHIS stakeholders need to see the practical value of data and increase data use through regular, targeted feedback that demonstrates data driven actions based on data. This further increases local demand for and use of data, stimulates ownership and promotes a culture of information use, creating the virtuous data cycle. (see figure 3.1) + c. **CHIS provides added value to end users.** For the CHIS to add value to the CHWs, the system design must be integrated with their work practices, reduce their work burden and add value for them to perform their work. A CHIS that is designed for local use and program monitoring rather the surveillance needs of administrators, means that CHWs and stakeholders are motivated to use the system. + d. **Ongoing CHIS support and capacity strengthening**. CHIS should focus on ongoing training, and provide support to CHWs in the many challenges they face when they use the system, providing feedback and support rather than criticism. CHIS supervision needs to encourage CHWs to use the system and make it sustainable. +3. **Organization** + + a. **Strong Data governance:** Governance is key to sustainability of any CHIS. All community level stakeholders must agree to common data standards and high-level coordination based on accountability, transparency and local participation. Key to these standards, are common data collection formats that reduce the data burden of the CHW and minimise the fragmentation of the CHIS. These in the long run contribute to systems becoming sustainable and enduring. + b. **Plan for scaling up:** Many CHIS projects are initiated as pilots with a limited timeframe and funding, known as "pilotitis". This needs to be avoided and scaling up planned for from the beginning with adequate resources and support. CHIS is about bringing about long term institutional and human behavior change, and systems take a long time to mature, usually beyond the short term "project" timeframe. + +In summary, various reasons, technical, institutional, and human related, contribute to the CHIS becoming sustainable. Many of the reasons are inter-connected, requiring a holistic design and a health systems based approach to address sustainability. + +Unsustainable systems do not scale, do not add value to the administrators who want data on the entire catchment population and not just from pilot areas. This challenge has been called the "all or nothing" consideration in HIS. Because the CHIS are not able to surmount these challenges, they don't add value, and thus do not attract the required support from the administrators. This vicious cycle of unsustainable systems that do not scale and thus add limited or no value to users, leads to poor support and further adds to the unsustainability of the CHIS. + +## CHIS Governance { #chis-governance } + +Information systems are not what they used to be and are becoming more important as interdependence among systems increases and demands for social accountability increase. Health information systems are becoming more important as information and communication technology spreads and have a greater impact on health workers lives, with pressures growing for more and better quality data. This trend is occurring at the same time as other significant changes are taking place with demands for greater transparency, participation and accountability and a reduction in the "digital divide" between countries. The challenge to CHIS designers and implementers is to build relationships of trust between stakeholders and to deliver effective social accountability. + +The growing expectation that it is right to be involved in decisions that affect one's future and the increasing knowledge about what is going on in the health system are a powerful combination to pressure health managers to improve trust between different levels of the system. Civil society, health workers and other stakeholders are increasingly demanding participation in decisions that are made about them, insisting on transparency about allocation of resources and using the internet and social media to voice these demands. At the same time international organisations are insisting on accountability, demanding value for money for aid projects. + +These three concepts - participation, accountability and transparency - are the core principles of good governance and need to be applied to any development of a CHIS. + +***Participation*** in CHIS governance emphasizes the broad participation of stakeholders in the direction and operation of information systems to develop a degree of consensus around decision making rules and capacity development processes. Participation implies increased citizen participation and greater community representation than traditional systems, creating opportunities for stakeholders to make meaningful contributions to decision-making, and seeks to broaden the range of people who have access to such opportunities. Technology may provide important forces leading to empowerment in participatory models, though face to face meetings remain important + +***Transparency*** refers to the availability of information to the general public and clarity about government rules, regulations, and decisions. Transparent procedures include open meetings, financial disclosure statements, freedom of information legislation, budgetary review, and audits. Transparent CHIS governance, therefore, means not hiding things from community stakeholders, not engaging in shady deals and not making discretionary decisions. There should be clear guidelines to adhere upon, based on openness. + +**Accountability** in governance refers to the collective responsibility of officials to preserve the public's trust in government by delivering on policy outcomes and safeguarding public funds. Accountable governance of a CHIS involves systems and coordinated actions through which the MoH (with donors) ensures the effectiveness, efficiency and economy of expenditure. It relies on tools that promote value-for-money, integrity and transparency in government, such as external control, internal control, sanctions, and enforcement. These tools create an enabling environment for greater accountability and improved governance. + +### Governance implications for donors and government { #governance-implications-for-donors-and-government } + +While governance is ultimately the role of government, accountable governance is not the responsibility of one institution, but many entities and individuals across all levels, particularly local government for the CHIS. + +The donor community (development partners) has a distinct role in supporting government to develop and implement CHIS governance guidelines around transparency, accountability and accountability. The donors wield considerable influence over the availability of resources and need to support the design principles, harmonize CHIS and end pilotitis. + +### Governance of Data Management { #governance-of-data-management } + +Effective data governance is the key to sustainability and is essential to all forms of routine HIS, including CHIS. + +Data management governance is at the core of all information systems and is crucial for the sustainable functioning of a CHIS. This section is adapted from "Guidelines for Data Management Standards in Routine Health Information Systems"^[Heywood & Boone Guidelines for Data Management Standards in Routine Health Information Systems Measure evaluation 2013] and readers are encouraged to refer to that for further details. + +This section defines CHIS governance, provides an overview of governance of CHIS, and proposes standards for data management governance which, when applied, can strengthen CHIS performance. + +> *Governance in data management can be defined as:* The development and implementation of administrative policies, procedures, and processes that define workflow, program inputs and outputs, management structure and oversight functions, and the methods and frequency of performance evaluation. + +Data management governance dictates how the different components of the CHIS, at the same or different levels of the health system, work together to achieve a common goal - quality health data for decision making. For the purposes of this guideline, governance is applied largely to CHIS and is seen as a core function of high level management at all levels -that is, to monitor, assess, and strengthen these systems to facilitate improvements in service delivery + +Data management governance ensures that data is of high quality - current, correct, consistent, and complete - as well as readily available to stakeholders (i.e., ensuring access to consumers, or those who require health information to inform decision making). In practical terms, that means putting personnel, policies, procedures, and organizational structures in place to ensure that data is accurate, consistent, secure, and available. + +The process of data management governance for a CHIS should foster cross-organizational collaboration, facilitate structured policy making and balance ad hoc or narrow information needs with the interest of the Community health system. Interventions to improve governance should address the institutional, behavioral, and technical determinants of CHIS performance described above and focus on improving the desired CHIS output of good-quality data that is regularly used to improve service delivery. + +Good governance requires commitment at all levels. It is not enough to have good structures, policies and procedures at the top. They need to be implemented by a dedicated team of well-trained stakeholders at the lower levels who have the motivation and skills to monitor and evaluate the CHIS based on the principles of participation, accountability and transparency. + +![](resources/images/chis_figure40.png) + +*Figure 6.2* Governance of Data management + +This model brings together in one place a number of concepts dealt with in other places in this guideline including: + +- Formal governance structures such as SOPs and strategic planning and financial systems, as well as oversight mechanisms such as technical working groups (TWG). +- Workforce development, training, and supervision to identify best practices pertaining to CHIS staffing. (Chapter 5) +- Policies and procedures for data management, with particular regard to standard operating procedures, data and metadata stewardship. (Chapter 4) +- CHIS assessment, starting with general assessment questions and then exploring the Performance of Routine Information Systems (PRISM) model to see how CHIS converts inputs into appropriate outputs by influencing determinants of health outputs (organizational, behavioral, and technical) and their influence on overall health system performance.(Chapter 2) +- Ways to promote a culture of information use is the core theme of this manual. + +## Formal Governance Structures { #formal-governance-structures } + +CHIS governance is the oversight and monitoring function necessary to ensure that the CHIS functions as designed. Adequate governance allows the system to identify threats to performance and make necessary corrections, as well as to find opportunities to improve the CHIS and advance the aims of the system. + +Governance structures are the formal mechanisms through which this oversight and local management takes place, including organizational frameworks, TWG (Technical Working Groups), and boards of directors. Governance structures oversee the management functions and inputs to ensure optimal system functioning + +### Mission Statement { #mission-statement } + +A mission statement is a formal expression of the purpose of the CHIS and its reason for being. A good mission statement states the reason for the organization's existence and includes goals, names primary stakeholders, and articulates how the organization provides value to stakeholders. + +### Organizational Chart { #organizational-chart } + +An organizational chart is a diagram used to depict the CHIS structure and personnel. It helps organize personnel by identifying management control within the organization. + +An organizational chart is useful for planning, resolving disputes, and managing change. It can be used as a baseline for planning, budgeting, and workforce modeling as it gives a succinct overview of the organization. + +### Effective participation structures { #effective-participation-structures } + +CHIS oversight committees should be formed at each level of the system---that is, in each district and facility, to monitor CHIS system performance. The committee should be made up of CHIS stakeholders from health care institutions, implementing partners, local governments, and, where possible, civil society. These committees should facilitate the CHIS mission in their area of influence by monitoring performance, alerting CHIS management to strengths and weaknesses, and facilitating capacity building. + +Village Health Committees are crucial to spread participatory processes to the lowest levels and these need capacity development, funding and regular feedback to become effective + +The CHIS regulatory authority and data governance council (see policies and participation section) also need to have effective representation of community stakeholders + +### Reporting Structures { #reporting-structures } + +In a CHIS, data and information begin at the service delivery point in the community and then flow toward the center to be shared with stakeholders to ensure that relevant information, based on quality data is available to those who need it in timely fashion. + +Reporting structures include directives (SOPs) from CHIS management, which state who reports what and to whom, when reports are due, in what format and by which mechanisms. + +In the context of CHIS, reporting structures clearly define: + +- The source document for reporting---that is, the individual client record +- The standardized, aggregate, periodic report for reporting to the next level +- Reporting deadlines---the date reports of various types are due to the next level. +- Indicator calculation guidelines and compilation, and completing the forms +- Reporting Procedures for sending the data to the next level. +- Data quality review procedures +- Sanctions (if any) for failure to meet reporting obligations. +- Responsibilities of staff members to monitor reporting of performance and compliance, and enforcement of these standards? + +### Master Facilities List { #master-facilities-list } + +A master facilities list, in DHIS2, is a complete listing of all health service delivery sites in a country, including CHIS reporting units, with information about capacity and services available. It is dynamic and should be kept up to date as reporting units (CHWs) are added to or subtracted from the system. + +A master facilities list improves record keeping by improving transparency and reporting efficiency. It minimizes duplicate reporting and promotes analysis and synthesis of data to improve decision making and health system functioning. + +### Planning Structures { #planning-structures } + +Planning is critical to ensure that CHIS resources are targeted efficiently and according to need, so that maximal benefit is achieved from CHIS investments. Planning *structures* refers to mechanisms for planning, such as periodic program reviews and needs assessments, combined with financial reviews and budgeting. Setting targets and situational analyses are also aspects of regular planning. + +## Policies and Procedures for Data Management Governance { #policies-and-procedures-for-data-management-governance } + +The management of CHIS data should be standardized such that the steps performed in turning data into information are the same throughout the system---from one district or CHW to another. + +These policies and procedures are an integral part of governance and should be well defined, detailed, written down, and made accessible to all staff and other stakeholders in the data management process. Processes should be supported by policies that are well known and enforced, so that standards are applied uniformly across the system. The following are standards and best practices for data management policies and procedures. + +### CHIS Regulatory Authority { #chis-regulatory-authority } + +For a CHIS to function effectively, all community role-players should routinely report, using standard mechanisms, to the CHIS. Regulatory authority often takes the form of public institutions empowered to regulate public health practice according to government imposed standards. This is necessary to ensure complete reporting from all sources of health service delivery including CHWs. However, the MOH often has no formal influence over CHWs to ensure reporting, other than the regulatory authority provided through government. + +To efficiently target resources for disease control and prevention, CHIS managers need to understand where disease is occurring in the population and where services are being utilized. Without accurate targeting based on complete, reliable data, resources can be wasted by sending too much to areas that do not need it or too little to areas that do. + +### E- Health and Information and Communication Technology Policies { #e-health-and-information-and-communication-technology-policies } + +ICT governance is essential to ensure that there are rules and regulations guiding use of electronic tools for managing and transmitting data and information, such as computers (hardware and software), networks, tablets, personal data assistants (PDAs), flash media, and communication tools, such as cell phones, modems, e-mail, instant messaging, and social networking. + +A policy framework should be developed by the MOH to manage ICT resources in the system. What resources to acquire, how they should be used and by whom, when they should be upgraded or replaced, and how they are maintained should all be codified into the framework to ensure efficient stewardship of CHIS resources. + +Because CHIS personnel should not be expected to have knowledge of maintenance and repair of ICT hardware and software, outside resources can be utilized. Reputable, licensed computer hardware and software vendors and repair firms can be contracted to maintain the ICT resources in the CHIS, reducing the burden on HMIS personnel and allowing them to focus on data collection, analysis, and use for planning and management. + +### CHIS Data Governance Plan Based on Best International Practices { #chis-data-governance-plan-based-on-best-international-practices } + +A CHIS governance plan refers to roles and processes that serve as a guideline for fulfilling, sustaining, and extending CHIS planning. A governance plan crosses all organizational layers, including stakeholders, administration, maintenance, strategy, policy, and support.^[*Technopedia:* [Governance Plan](http://www.techopedia.com/definition/2910/governance-plan)] + +A CHIS governance plan should clearly state who does what, when, and how with regard to CHIS management, to management of data and information, and to decision making. A governance plan is useful in times of transition or change in the CHIS, since it provides a reference tool to clarify roles and settle disputes. + +### Data Standardization Policies, Framework, and Procedures { #data-standardization-policies-framework-and-procedures } + +Most countries still lack policies that bring together the various components of CHIS under a single unifying framework and provide clear lines of responsibility and functionality. CHIS management structures should be strengthened centrally and resources and authority decentralized to serve the specific needs of the people involved in implementing CHIS, particularly at the periphery. + +The CHIS framework in both national health policies and strategic plans should encapsulate an integrated CHIS as part of overall health systems strengthening and governance reform, with buy-in to the plan from local government, political authorities, the MOH, and donors. The framework should recommend the pooling of CHIS expertise and resources into "one plan, one framework and one funding mechanism."^[Paris Declaration on Aid effectiveness 2005] + +Countries also need a practical CHIS operational plan wherein all CHIS activities within the MOH are centrally guided, with clear lines of decentralized responsibilities in the spirit of administrative, financial, and operational decentralization toward districts. + +As defined in the CHIS framework, institutionalized mechanisms should be developed for integrated CHIS data quality assurance (as measured by its completeness, accuracy, timeliness, and consistency), with validation rules for electronic systems and a team approach to data quality. In addition, these policies should: + +1. Specify interoperability of CHIS subsystems. +2. Define human resource needs and capacity strengthening requirements. +3. Define responsibilities for data collection, information flow, and use. + +National policies should provide for a balanced, limited set of national CHIS indicators, which are regularly reviewed in a participative manner, with clearly defined numerators and denominators, data sources, baselines, and national targets. There should be a regular indicator review process in which program and subnational managers participate to ensure that the existing indicator set fulfills their needs. + +Most countries have policies, laws, and regulations governing health services that, if applied, would greatly improve health system functioning. Too often inadequate resources or a lack of incentives mean that these policies are not enforced. Their implementation could be strengthened by the application of SOPs. + +### Metadata stewardship { #metadata-stewardship } + +In CHIS, stewardship of metadata, or responsible planning and management of data about data, is needed to foster consistent use of data management resources and facilitate data mapping among computer systems. A data steward holds responsibility for maintaining a data element in a metadata registry. Data stewardship roles are common when organizations need to exchange data precisely and consistently among computer systems and to reuse data-related resources. + +A data steward ensures that each assigned data element: + +1. Has a clear and unambiguous definition. +2. Does not conflict with other data elements in the metadata registry. +3. Is being used and is being used consistently in all interlinked computer systems; unused data elements are removed. +4. Has adequate documentation on appropriate usage and notes. +5. Is documented with regard to its origin and sources of authority. + +Assignment of data elements to an individual promotes trust in systems where users can contact a specific staff member with questions on specific data elements. + +### Data Quality Assessment and Auditing { #data-quality-assessment-and-auditing } + +CHIS data quality should be assessed periodically to enhance confidence in data and promote use of the data for decision making. Data quality should be assessed routinely for high-priority indicators as a part of regular supervision, and less often for other indicators. A periodic assessment of CHIS performance should include a data quality assessment. + +### Data Standards { #data-standards } + +Governance refers to a process which outlines the process and mechanisms of how decisions are taken. In the CHIS case, the governance decisions concern how and why new systems are introduced, and their implications. As emphasized throughout this document, the CHIS is not a standalone system, but is linked by standards with other data collection processes and systems based on the six WHO building blocks. + +Data standards are multifaceted in nature, involving both technical and semantic standards: + +1. Technical (syntactic) standards such as data transfer protocols. +2. Semantic (nomenclature) aspects. Important semantic standards in the context of CHIS include metadata stewardship issues such as : + a. Meta data naming conventions for data elements, indicators, organizational units, shape files and others. + b. Reporting periods for different elements and the formats in which they are reported, that enable ease of compilation of data for the CHW. + +A universal governance problem is that donors and NGOs want to introduce their own parallel community systems and data collection formats without being accountable to other standards and systems in the community setting. This lack of governance adds to the workload of the CHWs since all data collection work converges on them, and magnifies the fragmentation. + +This situation is primarily due to the absence of a higher level mechanism for governance of data and standards. A typical governance mechanism is the establishment of a steering committee at the MoH level, and all proposals for the introduction of new systems should be approved by them. For example, they should need ensure that the new system being proposed is feasible, how it overlaps with other systems, what duplications are involved, the implications on data collection burden, compliance with laid out standards, and whether the required outputs can be met through existing systems. Such a systematic and thorough process of governance goes a long way to control duplications and redundancies and reducing the work burden of the CHW. However this governance needs to be enforced at lower levels, with responsibility and authority being given to districts and facilities to prevent parallel systems proliferating. + +These guiding principles generated a community driven framework of standards, as contrasted with those which are typically imposed from the top with most often sub-optimal results. A framework of standards which represent everyday work, and are bottom up driven are more likely to add value and be accepted by the CHWs. + +### Standard Operating Procedures (SOPs) { #standard-operating-procedures-sops } + +SOPs are the translation of policies and procedures into day to day life of the CHIS stakeholders. All stakeholders need their roles and responsibilities clearly defined in a set of SOPs that form part of the organizational culture of the CHIS. SOPs should describe clearly who should do what, when, and with what resources, to manage and maintain the CHIS. + +There are many ways to define SOPs, and the actual SOPs vary tremendously from country to country and project to project. The SOPs outlined below represent some very basic, practical SOPs that could serve as the foundation for country or program specific SOPs. + +#### Visión general { #overview } + +There are three, basic SOPs outlined in this manual: + +1. Reporting Guidelines in Chapter 4 +2. Training protocol in the Chapter 5 +3. Supervision protocol in Chapter 5 + +![](resources/images/chis_figure41.png) + + +*Figure 6.3:* Standard operating procedures outlined in this manual. + +#### SOP Best Practices { #sop-best-practices } + +1. **Harmonize multiple programs into a single protocol.** This is especially true for the data capture protocol described in this chapter and the training and supervision protocols in the training chapter. +2. **Develop SOPs for each individual community project** especially if multiple data flows exist from. +3. **Turn the SOP into illustrated posters** and have the facility staff post them on their walls for public viewing. +4. **Print SOPs and make sure all CHWs, facility staff, and district staff have copies** +5. **Stakeholders to sign the SOPs** at the completion of training. +6. **Stakeholder participation in the creation and approval of SOPs.** The SOPs must institutionalize the best practices and workflow of the actors in the CHIS. Include representation from all relevant stakeholders in the process of developing SOPs. +7. **Ensure all data elements and indicators are captured.** The project should have an M&E framework (see Chapter 3) that should clearly define all data elements and indicators. The CHWs should clearly understand the meaning, and measurement of each data element and indicator to remove ambiguity +8. **Use data capture guidelines at trainings.** To build accountability, CHWs and facility staff need to know they are part of a larger system. They need to know how their data is used for planning at higher levels and specific actions at lower levels. +9. **Have the CHWs explain the data capture guidelines.** This teach-back method is an effective adult learning practice. By explaining the data capture guidelines, this elevates the CHW's credibility with the health committee. +10. **Produce, simple-to-use, local language guidelines.** CHWs and facility staff need guides and instructions on what to do. Consider making posters or small laminated portable data capture guidelines for CHWs and facilities to put on the wall or carry with them that outline their role and responsibilities based upon the data capture guidelines. +11. **Have CHWs, facility, district staff and national staff sign guidelines.** This is a symbolic "commitment" measure. The aim is that they have read it, understand their reporting responsibilities as defined in the data capture guidelines, and will carry out these responsibilities. +12. **Produce simple videos or audio and upload them to phones.** Responsibilities and actions for every event are made easier with a simple, local-language videos or audio guides that facility staff and CHWs can refer to. + +## CHIS Staffing and Workforce Planning and Development { #chis-staffing-and-workforce-planning-and-development } + +People are the lifeblood of CHIS, and even the best system would generate no information products without the combined efforts of all CHIS staff. An entire chapter of these guidelines are dedicated to capacity development, but the topic outline is repeated here to reinforce its importance in CHIS governance. + +- Training needs to be carefully planned and costed, with the appropriate infrastructure, equipment and curriculum, trained teachers +- CHIS staff must have the training they need to perform the tasks expected and to produce the data and information necessary to monitor the community health system. +- Adequate numbers of staff is also necessary. A staff that is too small risks underperformance, while a staff that is too large wastes precious CHIS resources. +- The staff and its training should be organized, efficient and of high quality. +- Certain standard elements of CHIS staffing and training help ensure high quality output from the workforce while avoiding redundancy or wastage. + +Components of CHIS planning and development that should be covered by this planning and development process include + +**Training Infrastructure and staff:** + +- Costed training plan| +- Standardized training curriculum/materials| +- Equipped training institutions| +- Adequate numbers of competent, trained trainers | + +**Supportive Supervision and Mentoring:** + +- Guidelines for standardized, effective supervision +- Standardized supervisory checklists +- Targeted feedback mechanisms| +- Standardized supervision reports---tracking results and monitoring trends | + - Schedule of supervisory visits| +- Data quality checks + +## Monitoring and Evaluation { #monitoring-and-evaluation } + +Monitoring and evaluation (M&E) is the final, but crucial component of Data Governance and concerns maintaining data quality and ensuring quality of the overall CHIS as well as regular assessments of CHIS functionality. This is in addition to the standard programmatic M&E, which is not covered here. + +### Maintaining CHIS Quality { #maintaining-chis-quality } + +CHIS quality is essential and the determinants are similar to those already described for sustainability -technical, organizational, and behavioral factors that convert CHIS functions into the key outputs in the form of quality data that is regularly used so as to improve health system performance. (PRISM framework^[MEASURE Evaluation, “PRISM: Performance of Routine Information System Management Framework,” [https://www.measureevaluation.org/resources/prism.html](https://www.measureevaluation.org/resources/prism.html)]) + +#### Technical Determinants { #technical-determinants } + +These are the specialized know-how and technology to develop, manage, and improve CHIS processes and performance. Affecting CHIS performance both directly and via behavioral factors, they include: CHIS design, computer software, as well as the complexity of information technology, reporting forms and procedures. + +#### Organizational Determinants { #organizational-determinants } + +These relate to organizational structure, resources, procedures, support services, and work environment that promote a "culture of information"---the capacity and control to promote values and beliefs within the organization by collecting, analyzing, and using information to achieve the organization's goal and mission. Organizational factors include: governance, planning, resource availability, training and capacity development, supervision, finances, information distribution, and the culture of information. + +#### Behavioral Determinants { #behavioral-determinants } + +These include: the CHIS users' demand for data, data quality checking skills, competence and problem-solving skills for CHIS tasks, confidence levels in their ability to perform CHIS tasks, and motivation to perform at peak ability. These behavioral factors are influenced by both technical and organizational determinants (above). + +### Assessing CHIS Functionality { #assessing-chis-functionality } + +Assessment has been dealt extensively in Chapter 2 and is summarised here. + +A major test of the effectiveness of CHIS governance is regular participatory assessment to see whether CHIS is improving health program outputs and health impacts. Yet, surprisingly, this aspect of performance is rarely formally evaluated. + +CHIS impacts on health programs can be measured by four simple questions: + +- Is the information relevant? +- Is the information of good quality? (Is it timely, consistent, complete, and accurate?) +- Is the information presented in a user-friendly way? (Is it easy to access and easy to interpret?) +- Is there capacity to act on the information provided? +The answers to these questions need to be approached in a way that addresses the health systems framework and should be further elaborated by asking: +- Has the CHIS been decentralized, and have lower-level program managers contributed to decision making? +- Have the systems been integrated and contributed to broader program integration? +- Has CHIS contributed to evidence-based decision making and more effective health outcomes? + +### Assessment methods { #assessment-methods } + +Here we provide an overview of some of the popular methodologies to assess CHIS functionality, including: + +#### Decentralised Self-Assessment { #decentralised-self-assessment } + +To strengthen data management, countries should institutionalize regular self-assessment data use meetings, particularly at facility and district levels. Self-assessment should use local data to calculate indicators in order to review performance against targets for client, facility, and system indicators and to compare the results to those of similar institutions, other geographic areas, and national norms. Self-assessment meetings should be conducted at least quarterly and should be made part of routine SOPs for work and management procedures. + +#### Health Metrics Network Assessment Framework { #health-metrics-network-assessment-framework } + +This comprehensive assessment framework, considered the gold standard for HIS assessment, is the basis for the Macro-assessment described in chapter 2. The HMN framework deals with the holistic HIS (the CHIS being just one aspect) and is not discussed further here, but constitutes a valuable tool for evaluating overall HIS functionality, in which CHIS plays a significant role. + +The full HMN assessment asks stakeholders approximately 200 questions regarding all six HIS components---HIS resources, indicators, data sources, data management, information products, and data dissemination and use ---and scores the answers electronically, producing a series of graphs for each component. + +#### The PRISM Framework { #the-prism-framework } + +The PRISM framework and toolkit takes a holistic approach to CHIS monitoring and evaluation, seeking to assess system performance by investigating CHIS performance determinants (the technical, organizational, and behavioral factors described above). Performance, as assessed by the PRISM methodology, is measured by the level of data quality, the extent of data use for decision making, and the management capacity. + +PRISM assessments can be used to establish a baseline measurement of performance and can then be repeated after interventions to gauge their effectiveness. PRISM tools can also be used for routine monitoring of CHIS performance (such as conducting data quality checks as part of routine supervision). + +## Conclusión { #conclusion } + +Many of the governance issues dealt with above are illustrated in a case study from Zambia in which an NGO- initiated project transitioned to government ownership while achieving remarkable results for community sanitation. + +## Case Study: Community Led Total Sanitation from Zambia { #case-study-community-led-total-sanitation-from-zambia } + +This case study describes the development of an information system for Water and sanitation for Health (WASH) based on the DHIS2 platform. This system was built by Akros, an NGO, and were engaged with the challenge of sustainability after successful implementation of the system. The case illustrates the approach they adopted in transition the system from the NGO to the government in their bid to establish sustainability. This case is thus unique in illustrating the challenges of transitioning systems to establish robust government ownership. + +In 2013, DFID funded a Water and Sanitation for Health (WASH) program in Zambia. Community led total sanitation (CLTS) conducted by the Zambian Ministry of Local Government and Housing (MLGH), UNICEF, and an implementing partner. In response to concerns of poor data reporting and targets which were not being achieved, the team layered a unique mobile-to-web application (M2W) using DHIS2, over traditional paper based CLTS data collection methods, resulting in an innovative service delivery and monitoring system dubbed "CLTS M2W". CLTS M2W uses mobile feature phones, automated data feedback loops, and engagement of traditional leaders to provide communities with the ability to clearly see their progress towards sanitation goals. + +These tools require data collection at the community level by Sanitation Action Groups in each village, data entry onto phone by community champions, and the management of this process by local chiefs and at district level. CLTS M2W paved the way for unprecedented CLTS uptake in Zambia, facilitating the creation of over 1,500,000 new users of sanitation over 18 months. + +#### Government involvement and Ownership { #government-involvement-and-ownership } + +The leadership of the Ministry of Local Government and Housing was critical from the beginning of the project, but most important was the leadership of the local government in the districts and the traditional leadership of chiefs in the villages, where the intervention was ongoing. When a CLTS program is first introduced in a district, the intervention, technology, and supervision is initially led by the implementing partners with the goal of ultimately transitioning ownership of the program fully to the government. Though the initiation visits were led by the governments' partners, the following visits and all supervision visits were led by the district government officials with each subsequent visit involving less outside partner involvement than the prior. + +Focal Point Persons (FPP) are the local or national government employees who coordinate these activities and channel knowledge and communication for programs in the field and at the district level. To promote their ownership and engagement of the data, FPPs receive DHIS2 data analysis training during supervision visits. Long term sustainability requires fully trained ministry staff and community champions, who understand and can troubleshoot the system. + +#### Capacity Development { #capacity-development } + +Trainings were conducted by partner staff to district staff, who then trained community champions (CCs) and Sanitation action groups (SAGs) in a training of trainers approach. There were different trainings at every level of data collection and regular feedback to ensure that data collection tools were properly used and understood. + +- The Sanitation Action Groups required an understanding of the paper-based data collection tools, what was being monitored and why; +- Community Champions needed to operate feature phones for data reporting, understand the data being collected and the feedback loops they were receiving; +- Environmental Health Technicians (EHTs) required training to understand the mobile platform and how to troubleshoot minor problems. EHTs and other government officials also benefited from data use trainings. + +District Water Sanitation and Hygiene Education (DWASHE) committees were created in districts with staff from all government ministries to review sanitation progress at quarterly meetings. They are trained in the use of DHIS2, using specially developed dashboards and other visualization tools to enable them to inspect the sanitation state of the districts and make district WASH plans based on these data. + +#### Feedback to Stakeholders { #feedback-to-stakeholders } + +Custom-developed reports with DHIS2 data are sent to partners monthly, giving an overview of "open defecation free" (ODF) status, and reporting rates. There are several iterations of these html based reports, designed to communicate the necessary information to the receivers. + +- EHTs receive information on total reports received out of the total expected within their assigned catchment area. +- UNICEF and MLGH receive reports on sanitation progress of each data element per district. + +These reports were designed to help EHTs target their activities based on which CCs need help reporting, and respectively can help UNICEF and MLGH in resource allocation. + +#### Involvement of chiefs { #involvement-of-chiefs } + +After a few months of monitoring data and not seeing a dramatic effect on latrine construction, a program manager proposed incorporating the power of traditional leadership into the protocol design of CLTS. A tablet-based chiefdom widget was designed to enable chiefs to view relevant information without logging in to DHIS2 and requiring minimal mobile data to support. This information is presented in charts, tables, and graphics, that exist on the home screen of the tablets. + +![](resources/images/chis_figure42.png) + +*Figure 6.5:* Snapshot of the Chief's Visualization App active on a tablet home screen. + +![](resources/images/chis_figure43.png) + +*Figure 6.6:* Enlarged list of sanitation performance of individual villages of the chiefdom. + +Armed with this information, chiefs could compare the performance of their villages to their neighboring chiefdoms villages' performance, combining the power of community behavior changes, with the traditional authority chiefs must instigate that change. Following tablet distribution came positive change in open defecation free status, as chiefs used their influence to encourage their headman and villages to build more latrines (see figures 6.7 & 6.8). + +![](resources/images/chis_figure44.png) + +*Figure 6.7:* Figure illustrating the influence and process of chiefdom orientation + +![](resources/images/chis_figure45.png) + +*Figure 6.8:* Sanitation Uptake over Time. Ministry of Local Government Republic of Zambia + +#### CHIS Development { #chis-development } + +The development process benefited from a "boots-on-the-ground" approach at district level and below in Zambia. This local understanding combined with DHIS2 skills enabled an agile development approach that allowed for flexible platform creation and modification as needs and priorities shifted. This flexibility allowed the data collection process to mature as needs developed. As the program grew and donor interest expanded, data collection was able to expand to include monitoring of water access, face washing and environmental cleanliness. + +The paper tools themselves also changed: originally, paper sheets were printed on single-sided documents and distributed to SAGs, but as the program grew, notebooks were printed for SAGs to collect their monthly reports and share with the CC. The notebooks included helpful tools and guides for implementing CLTS in their communities on the front and back cover and prevented the loss of paper records. + +One key example of agility that the development approach facilitated was the selection of the most appropriate hardware for data collection. Smart phones were piloted in the first year, but were not working well due to the low literacy level of the CCs and the added costs associated with more expensive and fragile phones. The pilot approach allowed procurement and training strategies to shift to use simpler feature phones, a more fitting option for the data collection tool. + +The CHIS development strategy also relied heavily on the CHIS pillar that stressed balancing the reporting burden. Pushing against the tendency to collect more, do more, and learn more is tough work. As stakeholders learn of a successful program, they want to be involved. Keeping the reporting burden of village SAGs and CCs light enables reporting incentives to remain low, reporting rates high and training costs low. Nowhere was this more evident than in the roll out of water access monitoring. Initial requests had CCs collecting an additional 12 new data elements. It took months of negotiation, a pilot, and subsequent data collection revisions to keep the list of new data elements reasonable. + +Historically, a paper to Excel system was used for CLTS, requiring community facilitators to collect and aggregate hand-written reports for each village Sanitation Action Group (SAG). Environmental Health Technicians (EHTs) collected aggregated paper records from community facilitators and reported to the district to enter Microsoft Excel. These Excel records were submitted to the central level for manual aggregation into one master Excel file for data analysis. This process was error prone, extremely slow, and only offered basic analytical functions. + +![](resources/images/chis_figure46.png) + +*Figure 6.9:* Data flow of CLTS reports. Sanitation action groups (SAGs) in each village report data to community champions (CCs). CCs submit data to the DHIS2 via mobile phones. EHTs oversee CC cadres. + +The new system depicted above in Figure 3 was designed to maintain the paper-based village SAG forms containing 14 data elements on latrine construction. Data burden was reduced by reporting only data for a set of indicators developed with MLGH for performance of village-level sanitation. CC's were given mobile feature phones with a java app to report SAG data directly onto the DHIS2 database, minimizing reporting duplication. + +#### SOP Development { #sop-development } + +Strong protocol development and implementation also helped move the program towards sustainable success. These protocols (e.g. Supervision Visit Protocol, Surveillance Protocol, Event Protocol, Exit Protocol, and Final SV Checklist) were developed together with MLGH, based on improving existing practices and are the basis for activities that Surveillance Officers, Environmental Health Technicians, and traditional leaders undergo for successful implementation. + +A key protocol that ensured government engagement throughout all parts of the reporting process was the Event Protocol. This protocol provides a foundation for government transition support as well as structured approach to each necessary task that delineates for each event: who is responsible, when it should occur, why it should occur, and what the goal of that event is. Within the WASH program, these events are Community Mobilization, Mobile Surveillance Training, SAG Data Collection, CC Data Collection, EHT Feedback, District Monitoring, ODF Verification, Quarterly Ward Meetings, and Quarterly DWASHE Meetings. + +Two examples are given in Figures 6.10 and 6.11: + +> | Community Mobilization | | +> |:-|:-| +> | Responsible Person | Chief and/or Senior Headmen | +> | Periodicity | Ongoing| +> | Purpose | To continue building village-level awareness of and support for community-led total sanitation | +> | Outcome | Continued propagation of improved latrines | +> +> CLTS community mobilization includes any event that involves a SAG, CC, EHT, Headman and/or Chief pushing the CLTS agenda at the village-level. On a monthly basis, the SAG mobilizes each household in the village, fills out the CLTS Data Collection Sheet while monitoring latrine propagation and conducting sensitization. + +*Figure 6.10:* Table illustrating community mobilization. + +> | **ODF Verification**| | +> | :- | :- | +> | Responsible Person| District CLTS Focal Point Person| +> | Periodicity | When a village claims ODF status| +> | Purpose | To verify if villages are open defecation free| +> | Outcome | Villages that claim ODF are verified to be ODF or not | +> +> This process helps maintain data quality. When the District CLTS FPP logs into DHIS, he/she will see a notification on the Dashboard for any villages that claim ODF status. The notification will indicate the name of the village and prompt the District CLTS FPP to mobilize the verification team to conduct a field visit to the village. +> +> It is the EHT's responsibility to coordinate a verification team, acquire funds from the District Office and verify the village. After the verification visit, the EHT reports their findings through the DHIS2 mobile application's ODF Verification Form. +> +> Once a village has been verified for 3 months, a team of District Officers then visits the village to conduct a spot-check certification. Districts are able to monitor ODF progression through DHIS2 visualization tools. + +*Figure 6.11:* Table illustrating ODF verification. + +These protocols strengthen operations, and streamline reporting by standardizing expectations for all roles, and providing people with needed tools to meet these expectations. + +#### Lessons learned { #lessons-learned } + +1. Government sustainability was fostered from the very inception of the program as program implementers worked hand-in-hand with MLGH at all levels of the hierarchy. Surveillance visits always incorporated local government staff. +2. Visualization of data by key 'change agents', in this case local chiefs and traditional leaders creates ownership and motivation. These change agents were provided a means to understand the performance of their villages in relation to sanitation practices and not only had the data, but the leadership authority to encourage village level improvement. +3. Clear documentation through SOPs is essential for clear system functioning and management of all parties. +4. Multi-ministerial collaboration is important. In this case, Ministry of Chiefs and Traditional Affairs (MOCTA) and MLGH collaborated to ensure chiefs and traditional leaders were engaged in sanitation at local level. This was a success. + +A future goal is to better link data from MLGH with data from the Ministry of Health. Specifically, MLGH data (CLTS intervention data) is currently captured within an instance of DHIS2, with health-outcome data (e.g. diarrheal disease incidence) captured in a separate instance of DHIS2 (Ministry of Health). By linking the two systems, it will be easier to understand the impact of the CLTS program on health outcomes. + +## Case Study Liberia Community Based Information System (CBIS) { #case-study-liberia-community-based-information-system-cbis } + +### The National Community Health policy and programs { #the-national-community-health-policy-and-programs } + +In 2015, the national policy on Community Health Services was revised to fully reflect the community health components of the National Health Plan. The Revised National Community Health Services Policy aims to strengthen Liberia's health system and health services that were lost due to the Ebola Virus Disease (EVD) crisis, to provide health security by reducing risks due to epidemics and other health threats' to accelerate progress towards universal health coverage by improving access to safe and quality health services and to narrow the equity gap for Liberia's most vulnerable populations that live in the last mile. + +Community-based services are vital to the health and wellbeing of these communities. Additionally, the recent Ebola epidemic in Liberia and across West Africa highlighted the critical role that communities play in addressing their own health needs and changing their own health behaviors. + +A key feature of this revised policy is the institution of a new cadre of Community Health Assistants (CHAs), who are selected from and serve communities located more than a one-hour walk (more than 5km) from the nearest health facility. Through established criteria, CHAs are selected by their respective communities to undergo an integrated and standardized CHA training. Upon successful completion of the training, these individuals will be certified as CHAs. Throughout training and continuing after certification, CHAs will be supervised to deliver an integrated and standardized service delivery package---which includes curative, preventive, promotive, rehabilitative and palliative services as well as epidemic surveillance services---to households in their communities. + +#### Community Health Services Vision { #community-health-services-vision } + +*A coordinated national community health care system in which households have access to life-saving services and are empowered to mitigate potential health risks.* + +![](resources/images/chis_figure47.png) + +### Key figures in Liberia's CHA program structure { #key-figures-in-liberias-cha-program-structure } + +#### Community { #community } + +The Community Health Committee (CHC) is elected by the community with guidance from the catchment Health Facility. The CHC is to oversee and assist in the selection of CHAs and provide administrative support for health activities in the community. The committee shall comprise of a total number of 5 - 9 elected members depending on the size of the community. Every attempt should be made that at least 30 % of the members are women + +The Health Facility Development Committee's (HFDC) primary responsibility is to act as a governing body for all CHCs in the facility catchment area. The CHSS, in consultation with the OIC, shall serve as secretary to the HFDC. The HFDC is to meet monthly, providing a direct connection between community members and the District Health Team (DHT)/County Health Team (CHT), as well as local representatives and coordinating bodies of the Ministry of Internal Affairs + +#### Community Health Assistant (CHA) { #community-health-assistant-cha } + +CHAs is recruited by the community, trained and supervised the formal health system (Facility) to deliver an integrated and standardized service delivery package, which includes preventive, curative, promotive, rehabilitative and palliative services and epidemic surveillance to households located more than a one-hour walk (>5km) from the nearest health facility. CHAs will be responsible for recording information on individuals in each household during visits when conducted and services are provided. These data are reported into an aggregated monthly service report and sent to the facility at the end of each month. + +**Profile of CHAs** + +- Permanent resident in the community which s/he serves, between 18 and 50 years of age +- Involved in community project/s in the past, trustworthy and respected +- Able to read and write and to add, subtract and multiply +- A good mobilizer and communicator fluent in the village dialect + +#### Community Health Services Supervisor (CHSS) { #community-health-services-supervisor-chss } + +Community Health Services Supervisor (CHSS) is a clinically trained professional assigned to the health facility to supervise the CHAs. The CHSS shall provide field-based supervision to CHAs working in remote catchment communities of the health facility. One CHSS shall supervise up to 10 CHAs and is responsible to manage the CBIS system and serve as first point of contact for CHAs at facility level, provide leadership and clinical supervisions to CHAs, ensure logistics (forms, commodities, etc.) and to aggregate data from the CHAs and submit to the relevant facility. + +#### Officer in Charge (OIC) of the Facility { #officer-in-charge-oic-of-the-facility } + +The OIC is responsible for coordinating all health-related activities in all catchment communities for each health facility. He/she is responsible to supervise the CHSS and provide feedbacks to health facility development committee (HFDC) on which he/she serve as secretary. + +#### Community Health Services Focal Point (CHFP) { #community-health-services-focal-point-chfp } + +The Community Health Department of each CHT shall be responsible for integrating all community health activities into their county operational plan. The Community Health Focal Person (CHFP), assigned by the CHT, work under the supervision of the Community Health Department Director (CHDD) to coordinate all community health activities in the county. He/she work with the District Health Teams and facilities in the implementation of the community health programs. + +### The CBIS { #the-cbis } + +During the Ebola epidemic it became clear that the fragmentation of the current health information system made it impossible to have the "right information at the right time and in the right place". Many HIS subsystems were not interconnected, and stakeholders did not coordinate, contributing even further to the fragmentation by setting up separate reporting systems. After the Ebola crisis, strengthening the National Health Information System (HIS), and the Monitoring and Evaluation (M&E) system was recognized by the Ministry of Health of Liberia as one of the key interventions of the Investment Plan. + +In 2016 as the National Community Health Assistant (CHA) Program was created, the need for a CHIS became apparent. With the support of development partners, the MoH developed a comprehensive community-based information system (CBIS) as a subsystem within the HIS. These partners formed an M&E sub-group, which informed the system and development of tools to capture information from the CHA Program. + +The CBIS connects community-level health services with national health system, the lowest tier where service is provided. MOH attaches great importance to the preventive, curative, awareness, etc services provided by CHAs + +Data collection and reporting forms and ledgers were develop and built in the DHIS2 system. Future efforts include integrating CBHIS, LMIS and HRIS to improve management of community-based health services, produce supply chain efficiency gains and reduce stock-outs. + +#### Service Delivery Package and Data Sources { #service-delivery-package-and-data-sources } + +The ministry, with support from development partners, developed an integrated service delivery package for the Community Health Assistant (CHA) program, using modular packages. The CHA service package focuses on disease prevention, surveillance, reproductive, maternal, neonatal and child health, including integrated Community Case Management and its main approach is community mobilization, health education and health promotion. The goal is help residents realize that they are responsible to manage their own health matters; communities are empowered to create structures and identify and put together resources for health. + +#### Liberia Data Flow { #liberia-data-flow } + +Data collection tools from each of these module-based service delivery area were developed. Each of these service specific tools will be aggregated into the monthly service report each month at the level of the community health assistant (CHA) and at the level of the community health services supervisor (CHSS). The graphics illustrate this process. + +#### Reporting Timeline { #reporting-timeline } + +![](resources/images/chis_figure48.png) + +### Data Use { #data-use } + +CBIS was designed as a streamlined flexible system to allow for decentralized data entry and local use. + +#### Data Use at the CHA level { #data-use-at-the-cha-level } + +Data forms (ledgers) are kept in the community once completed, to keep an accurate record in the community of the work of the CHA. The CHA aggregates the ledgers into the CHA Monthly Service Report. This report is per community catchment area and can be entered into DHIS-2 to show indicators at the community level. For example, The CHA Monthly Service Report can be used in DHIS-2 to show a spike in the incidents of malaria in children under five in a given catchment area. + +#### Data Use at the CHSS (facility) level { #data-use-at-the-chss-facility-level } + +Each CHSS is responsible for analyzing CHA Forms to make informed decisions and targeted remedial supervision based on findings. For example: if the number of patients treated for malaria is much lower than the number of patients treated for malaria, the CHSS can coach the CHA on the value of routine visits and community education on malaria. Or if the number of home births is high compared to number of facility births the CHSS can coach the CHA to encourage facility delivery. + +The CHSS Monthly Service Report shows the aggregated indicators across all the CHAs, aggregated at the Health Facility level. They use this data to see the status of the communities around health facilities. For example, any maternal death in a CHSS catchment area is investigated. + +#### Data Use at County level { #data-use-at-county-level } + +The M&E Officer is responsible for providing information to various line managers, program supervisors and other stakeholders in the county. CBIS data should be analyzed and used in coordination and other management meetings. For example, the M&E Officer can provide data or help the stakeholders understand the data for the CHA program such as high numbers of diarrhea in certain facilities. + +#### Data Use at Central level { #data-use-at-central-level } + +The Central Level CBIS builds the capacity of the County Teams, training county level M&E staff how to create and run reports. He / She analyzes the data to troubleshoot and strategize for the programs. The data and reports should be accessible to the Ministry of Health and partners to use for decision making at all levels of the health system. + + +\[2\] "Paris Declaration on Aid Effectiveness: Ownership Harmonization, Alignment, Results and Mutual Accountability," in *The Paris Declaration on Aid Effectiveness and the Accra Agenda for Action* (Paris: Organization for Economic Co-operation and Development, n.d.), 4--13, [[http://www.oecd.org/dac/effectiveness/34428351.pdf]{.ul}](http://www.oecd.org/dac/effectiveness/34428351.pdf). + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md index 76be0232e..3a9eb38bd 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md @@ -7,7 +7,7 @@ tags: # CHIS Installation Guide { #chis-agg-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing configuration packages for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -40,7 +40,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -59,34 +59,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -99,30 +99,30 @@ The .json metadata file is imported through the [Import/Export](#import_export) If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -140,7 +140,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -157,7 +157,7 @@ The user groups that usually come with the package include: We recommend to provide the following access to these groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_{Package Name} access_|_{Package Name} admin_|_{Package Name} data capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -165,7 +165,7 @@ We recommend to provide the following access to these groups |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__release-note-md new file mode 100644 index 000000000..610a17b07 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__release-note-md @@ -0,0 +1,37 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CHIS_AGG/blob/master/docs/release_note.md" +revision_date: '2023-12-19' +tags: +- Implementar +--- + +# Release Note { #chis-release-note } + +## 1.1.0 { #110 } + +Version 1.1.0 is a compatibility release with minor fixes to metadata and new guidance for implementation and use of the CHIS toolkit in DHIS2. + +**New Content** +This release is linked to an updated set of CHIS System Design & Implementation guidance (1.1.0), now available in the Resources section with new sections on: +- Guidance for localization and adaptation to country CHIS structures & reporting/administrative hierarchies, considerations ofr Org Unit hierarchy +- Design considerations for integrating CHW data with facility data within national HMIS +- Guidance on configuring composite indicators to combine facility and community service delivery data in DHIS2 dashbaords and analytics tools +- Updated Implementation Planning guide + +**Fixes & Improvements** +Minor fixes to metadata have been made such as: +- Naming of metadata according to naming conventions +- Updated sharing settings for metadata using CHIS user groups + +## 1.0.1 { #101 } + +Version 1.0.1 comes with minor changes to the dashboard layout design and metadata sharing. + +- Dashboard items have been re-arranged and some have been stretched to fully fit the dashboard layout space. +- The text in some textbox items has been edited and made bold for better visibility. +- Metadata sharing for data sets and dashboards has been reviewed and aligned across all modules. + +## 1.0.0 { #100 } + +Initial release of CHIS + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md index 8cd2229df..783c93ef4 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -53,7 +53,7 @@ It is recommended that the weekly dataset is assigned to Organisation Units at t Digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [GooglePlay store](https://play.google.com/store/apps/details?id=com.dhis2&hl=en). -### Usuarios previstos { #intended-users } +### Usuarios objetivo { #intended-users } - Health facility users: capture and report key data on COVID-19 cases and deaths presenting at the health facility - Surveillance officers: surveillance officers at national and sub-national level may be responsible for supporting data entry and analysis. @@ -118,7 +118,7 @@ This section summarizes the major form of transmission classification experience ![Picture7](resources/images/AGG_Picture6.png) -### Customizing Data Entry Forms { #customizing-data-entry-forms } +### Personalización de formularios de entrada de datos { #customizing-data-entry-forms } The dataset in this package does not contain a custom form. To improve the usability of the form for data entry, implementers may design a custom form to meet their needs by following the DHIS2 User manual: [https://docs.dhis2.org/2.33/en/user/html/dhis2\_user\_manual\_en\_full.html#manage\_customform](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/metadata.html#manage_customform) @@ -136,7 +136,7 @@ The following data validation rules have been configured. These validation rules | COVID19 - New cases among HW (confirmed + probable) \<= All new cases | less\_than\_or\_equal\_to | New cases among HW (confirmed + probable) should be less than or equal to All new cases | New cases among HW (confirmed + probable) | All new cases | | COVID19 - New deaths among HW (confirmed + probable) \<= new cases among HW (confirmed + probable) | less\_than\_or\_equal\_to | New deaths among HW (confirmed + probable) should be less than or equal to new cases among HW (confirmed + probable) | New deaths among HW (confirmed + probable) | New cases among HW (confirmed + probable) | -## User Groups { #user-groups } +## Grupos de Usuarios { #user-groups } The following user groups are included in the metadata package: diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md index 0cac7eb8d..2954517e1 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -7,7 +7,7 @@ tags: # Aggregate Package Installation Guide { #c19-agg-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing the COVID-19 standard configuration package for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -39,7 +39,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -58,34 +58,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -98,30 +98,30 @@ The .json metadata file is imported through the [Import/Export](https://docs.dhi If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -139,7 +139,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -156,7 +156,7 @@ There are three user groups that come with the package: We recommend the following access -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -164,7 +164,7 @@ We recommend the following access |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md index fb9e3c298..d44be85d8 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -73,7 +73,7 @@ The design of the case tracker program assumes that [WHO case definitions][1] ar > >\*\*\* Confirmed case: A person with laboratory confirmation of COVID-19 infection, irrespective of clinical signs and symptoms. -### Intended Users { #intended-users } +### Usuarios objetivo { #intended-users } * Health facility users: capture and record details about a suspected case, including clinical symptoms & exposures; track lab results; record case outcome * Laboratory users: receive lab requests and record laboratory results for a particular suspected case diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md index 2e84501eb..aea24cf92 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -7,7 +7,7 @@ tags: # COVID-19 Surveillance - Installation Guide { #c19-cs-installation } -## Overview { #overview } +## Visión general { #overview } The COVID-19 tracker package was developed using DHIS2.33.2. This was done in order to support some of the latest features in DHIS2. In order to use the package, it is recommended that you install it into a DHIS2 instance using DHIS2 2.33.2 or above. If you will be setting this up on a new instance, please refer to the [DHIS2 installation guide](https://docs.dhis2.org/en/manage/performing-system-administration/dhis-core-version-master/installation.html). This document covers the installation of the following packages: @@ -18,7 +18,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -27,89 +27,89 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. ***Note that this search and replace operation must be done with a plain text editor***, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| -#### Tipo de entidad Tracked { #tracked-entity-type } +#### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| +|Persona|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } ***NOTE***: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -122,7 +122,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| |_*Tracked entity type*_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and view| @@ -132,24 +132,24 @@ By default the following is assigned to these user groups You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -157,10 +157,10 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 000000000..57a3fb4ea --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md @@ -0,0 +1,56 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implementar +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Visión general { #overview } + +We have made several updates to the existing package to align with new COVID-19 [surveillance guidelines released by the WHO on March 20, 2020](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and introduced new components to the overall package of support. Please review the notes here and contact us on the COVID-19 discussion board in the [community of practice](https://community.dhis2.org/c/implementation/covid-19/) with any questions. + +**All metadata packages and documentation can be downloaded from [dhis2.org.covid-19](https://www.dhis2.org/covid-19).** + +Packages are currently translated into French, Spanish, Portuguese and Russian, with additional languages in the pipeline (Arabic, Lao, Burmese). We can support metadata package translations in our global translation platform and invite the community to contribute if your country is interested in translating the package for a new language. [Check out our Community of Practice announcement](https://community.dhis2.org/t/the-new-dhis2-translation-platform-is-now-available/37755)and get started as a contributing translator here [by joining the DHIS2 translation platform](https://docs.dhis2.org/en/implement/understanding-dhis2-implementation/localization-of-dhis2.html). Please contact us at translate@dhis2.org. + +The new release includes: + +1. COVID-19 Case-based Surveillance Tracker program +2. COVID-19 Contact Registration & Follow-Up program +3. COVID-19 Aggregate Surveillance Reporting +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Metadata codes updated to align with the [WHO case-based reporting data dictionary](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Program indicators updated to reflect new WHO case definitions for probable cases (reference the updated case definitions in the interim surveillance guidelines updated March 20, 2020 [WHO interim surveillance guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Age legends have been updated to meet new WHO guidance for weekly reporting +4. relationshipType added to metadata package +5. Minor fixes to the metadata to enable easier installation of the package (i.e. indicatorType UID matches indicator type included in aggregate package) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. A new program stage has been added to enable repeatable ‘follow-up’ of a case contact. This was added to reflect workflows implemented in Uganda and Togo where contacts may be monitored repeatedly over the course of 14 days to determine if there are symptoms. The ***program*** is based on WHO guidelines which can be found [here](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), as well as information obtained via the [OpenWHO](https://openwho.org/courses/introduction-to-ncov) website. +2. Age legends have been updated to meet new WHO guidance for weekly reporting +3. relationshipType added to metadata package +4. Minor fixes to the metadata to enable easier installation of the package + +### COVID-19 Aggregate Surveillance Reporting { #covid-19-aggregate-surveillance-reporting } + +The following updates were made to reflect new guidance in [WHO guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), including updated global aggregate reporting to WHO (weekly & daily) + +1. Age categories updated according to new age groups +2. New indicators added for proportion of males among confirmed cases and proportion of males among confirmed deaths +3. New weekly dataset to capture classification of transmission at sub-national level one (i.e. provincial -- can be assigned to any sub-national level as appropriate in country) per updated WHO weekly reporting guidelines +4. Minor fixes to the metadata to enable easier installation of the package + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +The Points of Entry tracker program use case was designed to support the registration of travellers entering a country with a history of travel to, or residence in, a country/area/territory reporting local transmission of COVID-19 who may need to be followed up to ensure no symptoms develop. It is based on the design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health with minor changes to make the program more generic to global use and to align with the other tracker programs in the COVID-19 package. The package supports interventions at Points of Entry detailed in the WHO [technical guidance for the management of ill persons at points of entry](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings). + +Please read more about the POE program in the [system design document](https://docs.dhis2.org/en/topics/metadata/covid-19-surveillance/covid-19-poe-tracker-design.html). + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md index a61cecc37..f03eeee8d 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -29,7 +29,7 @@ In the development of this configuration package, an effort has been made to fol DHIS2 digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [Google Play store](https://play.google.com/store/apps/details?id=com.dhis2&hl=en). -### Usuarios previstos { #intended-users } +### Usuarios objetivo { #intended-users } * POE users: personnel responsible for screening travelers at points of entry such as airports, seaports and land crossings who may conduct initial screening at POE, make a determination about the traveler’s clearance and register the traveler into the Tracker program. * Public health workers: personnel responsible for following up with travelers for 14 days to inquire about onset of symptoms and refer the person for testing if required. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md index 961d89ecf..f3fbe84e7 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -52,7 +52,7 @@ As cases increase rapidly, some countries may struggle with case-based reporting The design of the event-based line-listing program assumes that [WHO case definitions](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) are followed in the use case; countries should follow national case definitions for classifying cases as suspected, probably or confirmed. -#### Usuarios previstos { #intended-users } +#### Usuarios objetivo { #intended-users } * Health facility users: capture and report key data on COVID-19 cases and deaths presenting at the health facility * National and local health authorities: monitor and analyse disease surveillance data through dashboards and analytics tools to conduct risk assessments and plan response measures; generate reports for regional and global reporting @@ -83,7 +83,7 @@ The program is called ‘COVID-19 Cases (events)’ |**Status**|**This is a generic field included in all Event Program**
**Complete event**
Option: Yes
The event should only be marked as ‘complete’ if all data entry has been completed. If the user is waiting to complete certain fields (such as case outcome), the event should be left not complete.
Events that are not marked as ‘Complete’ are maintained as active and can be more easily searched by the user in a working list| |Section 9
**Comments**|- **Comments**
Optional comments and remarks. Note that these comments will not display in the analytics and can only be accessed through the Capture app used to enter line-listed data.| -### User Groups { #user-groups } +### Grupos de Usuarios { #user-groups } The following user groups are included in the metadata package: diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 000000000..57a3fb4ea --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-SURVEILLANCE__release-note-md @@ -0,0 +1,56 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implementar +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Visión general { #overview } + +We have made several updates to the existing package to align with new COVID-19 [surveillance guidelines released by the WHO on March 20, 2020](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and introduced new components to the overall package of support. Please review the notes here and contact us on the COVID-19 discussion board in the [community of practice](https://community.dhis2.org/c/implementation/covid-19/) with any questions. + +**All metadata packages and documentation can be downloaded from [dhis2.org.covid-19](https://www.dhis2.org/covid-19).** + +Packages are currently translated into French, Spanish, Portuguese and Russian, with additional languages in the pipeline (Arabic, Lao, Burmese). We can support metadata package translations in our global translation platform and invite the community to contribute if your country is interested in translating the package for a new language. [Check out our Community of Practice announcement](https://community.dhis2.org/t/the-new-dhis2-translation-platform-is-now-available/37755)and get started as a contributing translator here [by joining the DHIS2 translation platform](https://docs.dhis2.org/en/implement/understanding-dhis2-implementation/localization-of-dhis2.html). Please contact us at translate@dhis2.org. + +The new release includes: + +1. COVID-19 Case-based Surveillance Tracker program +2. COVID-19 Contact Registration & Follow-Up program +3. COVID-19 Aggregate Surveillance Reporting +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Metadata codes updated to align with the [WHO case-based reporting data dictionary](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Program indicators updated to reflect new WHO case definitions for probable cases (reference the updated case definitions in the interim surveillance guidelines updated March 20, 2020 [WHO interim surveillance guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Age legends have been updated to meet new WHO guidance for weekly reporting +4. relationshipType added to metadata package +5. Minor fixes to the metadata to enable easier installation of the package (i.e. indicatorType UID matches indicator type included in aggregate package) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. A new program stage has been added to enable repeatable ‘follow-up’ of a case contact. This was added to reflect workflows implemented in Uganda and Togo where contacts may be monitored repeatedly over the course of 14 days to determine if there are symptoms. The ***program*** is based on WHO guidelines which can be found [here](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), as well as information obtained via the [OpenWHO](https://openwho.org/courses/introduction-to-ncov) website. +2. Age legends have been updated to meet new WHO guidance for weekly reporting +3. relationshipType added to metadata package +4. Minor fixes to the metadata to enable easier installation of the package + +### COVID-19 Aggregate Surveillance Reporting { #covid-19-aggregate-surveillance-reporting } + +The following updates were made to reflect new guidance in [WHO guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), including updated global aggregate reporting to WHO (weekly & daily) + +1. Age categories updated according to new age groups +2. New indicators added for proportion of males among confirmed cases and proportion of males among confirmed deaths +3. New weekly dataset to capture classification of transmission at sub-national level one (i.e. provincial -- can be assigned to any sub-national level as appropriate in country) per updated WHO weekly reporting guidelines +4. Minor fixes to the metadata to enable easier installation of the package + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +The Points of Entry tracker program use case was designed to support the registration of travellers entering a country with a history of travel to, or residence in, a country/area/territory reporting local transmission of COVID-19 who may need to be followed up to ensure no symptoms develop. It is based on the design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health with minor changes to make the program more generic to global use and to align with the other tracker programs in the COVID-19 package. The package supports interventions at Points of Entry detailed in the WHO [technical guidance for the management of ill persons at points of entry](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings). + +Please read more about the POE program in the [system design document](https://docs.dhis2.org/en/topics/metadata/covid-19-surveillance/covid-19-poe-tracker-design.html). + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md index 7ec27b44a..a6b9bd522 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md @@ -7,7 +7,7 @@ tags: # Aggregate Package Installation Guide { #cvc-agg-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing the COVID-19 vaccination standard configuration package for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -39,7 +39,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -58,34 +58,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -98,30 +98,30 @@ The .json metadata file is imported through the [Import/Export](https://docs.dhi If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -139,7 +139,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -156,7 +156,7 @@ There are three user groups that come with the package: We recommend the following access -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_COVAC access_|_COVAC admin_|_COVAX capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -164,7 +164,7 @@ We recommend the following access |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__release-note-md new file mode 100644 index 000000000..a16311efc --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__release-note-md @@ -0,0 +1,17 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CVC_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-22' +tags: +- Implementar +--- + +# Release Note { #cvc-agg-release-note } + +## 1.1.0 { #110 } + +Configuration updates, metadata for new vaccines added. + +## 1.0.0 { #100 } + +Initial release + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__design-md index ec4044b52..28b0cee0b 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__design-md @@ -37,7 +37,7 @@ The package includes: * A set of indicators based on the aggregate data set * A daily monitoring dashboard based on the aggregate data set -### Intended Users { #intended-users } +### Usuarios objetivo { #intended-users } The programme is designed to support clinical/facility-level users, empowering staff with better decision-making tools and placing the client at the center of the information system, while also eliminating their reporting redundancies. However, depending on the infrastructure and resource availability in-country, data entry can be completed at the district level based on paper registers. @@ -290,7 +290,7 @@ Once a client has received the first dose, the option for the first dose is hidd The stage is configured to ‘Ask the user to create a new event when a stage is completed’, which triggers a pop-up for scheduling the follow-up appointment. ‘Standard interval days’ are currently set to 10 so that the next appointment (event) date is scheduled 10 days from the current event date by default, but can be modified depending on the product used. -### User Groups { #user-groups } +### Grupos de Usuarios { #user-groups } The programme is packaged together with four user groups: diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md index ebcb5a4d8..9e1be71c3 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md @@ -9,35 +9,35 @@ tags: This document includes an installation guide for the updated COVAC Electronic Immunization Registry tracker package and a supplementary aggregate module for daily reporting based on tracker data. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Covid-19 Electronic Immunization Registry tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -52,7 +52,7 @@ The Covid-19 Electronic Immunization Registry tracker package includes three met > The package is not an out-of-the-box tool for tracker-to-aggregate data transfer. > The structure of the metadata package and the suggested mapping of metadata allow the implementer to set up the transfer of data based on existing tools and guidance. More information is available in the [Tracker to aggregate data Transfer Document](https://docs.dhis2.org/en/implement/maintenance-and-use/tracker-and-aggregate-data-integration.html#how-to-saving-aggregated-tracker-data-as-aggregate-data-values). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } ### Mapping guide for data transfer { #mapping-guide-for-data-transfer } @@ -100,44 +100,44 @@ These program indicators are part of the original package but need to be updated > If the original program indicators in your system were modified as part of local adaptation process, be aware that all changes will be overwritten once you import the updated set of program indicators. > If any of your modified program indicators have the same UID as the program indicators listed in the table above, make sure to duplicate the modified program indicators before import. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|----------------------------------------| -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -219,53 +219,53 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros -* Visualizations, maps, event reports and report tables -* Data sets -* Category options +* Visualizaciones, mapas, informes de eventos y tablas de informes +* Sets de datos +* Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. Four core user groups are included in the package: @@ -276,53 +276,53 @@ Four core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | | +|Objeto |User Group | | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------------------------------| | | _COVAC - COVID-19 Immunization Data Analysis_ | _COVAC - COVID-19 Immunization Data Admin_ | _COVAC - COVID-19 Immunization Data Entry_ | _COVAC - COVID-19 Immunization Metadata Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | | _*Program Stages*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | -| _*Dashboards*_ | Metadata : can view | Metadata : can view | No Access | Metadata : can edit and view | -| _*Data Sets*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | No Access | Metadata : can edit and view
Data: No access | +| _*Dashboards*_ | Metadata : can view | Metadata : can view | Sin acceso | Metadata : can edit and view | +| _*Data Sets*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Sin acceso | Metadata : can edit and view
Data: No access | The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md new file mode 100644 index 000000000..5e78dcf61 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/crvs_cod-installation.md" +revision_date: '2022-09-19' +tags: +- Implementar +--- + +# WHO Cause of Death - Tracker Installation Guide { #crvs-cod-installation } + +## Introducción { #introduction } + +This document is intended to guide administrators though the process of installing the Cause of Death module in a DHIS 2 database. Good understanding of DHIS 2, including the Tracker (case-based) functionality is required. + +The Cause of Death module consists of a file with DHIS 2 metadata. More specifically, it includes: + +For Tracker program: + +- A tracker program with data elements, option sets, custom data entry form, program rules, program indicators etc. +- A standard report for validation of data. +- A dashboard with charts and tables for key data. +- This document describes how to install this module, and perform routine maintenance. This includes the critical task of adapting and improving the dictionary of diagnosis/medical terms, which is essential for the functioning of the module. + +In addition, a [node.js](https://nodejs.org/en/) script for linking the Cause of Death module in DHIS 2 with the [IRIS software](https://www.dimdi.de/dynamic/en/classifications/iris-institute/index.html) for semi-automatic coding of causes of death to full ICD-10 and sending the result back to the DHIS 2 database. Outputs are provided to export this again data to the ANACOD data analysis tool. This functionality is described in a separate document. + +## Description of the module { #description-of-the-module } + +This section gives an overview of the design and structure of the module. + +### The data collection form { #the-data-collection-form } + +The data collection form is created based on the International Medical Certificate of Causes of Death. As such, it uses a custom form that mimics the layout of this certificate. However, the logic built into the form for coding and validation also works without the custom form, allowing the module to be used on e.g. mobile devices with the DHIS 2 android applications. + +### Dealing with "Age" { #dealing-with-age } + +For collecting data on the age of the deceased, the data collection form supports use of both date of birth and an estimated age. To facilitate analysis of the data, an additional data element for Age in years has been added to the form, but as a disabled/read-only field. Based on what is entered either as date of birth or estimated age, program rules calculate the age in years and assigns that value to the Age in years data element. + +### Dictionary { #dictionary } + +A critical component of the module is a dictionary (ICD-SMoL - local dictionary). The dictionary functions as a link between the medical terms used in data entry, and the ICD-SMoL code used for reporting and analysis of causes of death. In DHIS 2, the dictionary is implemented as an option set. The medical term is the option name, and the option code is made up of three components: the ICD-SMoL code, the ICD-10 code, and an ID. The ID is necessary because several terms could refer to the same ICD-SMoL and ICD-10 codes, and codes need to be unique. The ID itself consists of two parts: a country code (or INT for the ones provided with the module) and a counter. Keeping track of the international and country-specific terms will make it easier in the future to e.g. identify terms used in different countries which could be proposed for the international dictionary. + +Fully localised French "Cause of Death" module uses a local dictionary that is different from the English ICD-SMoL - local dictionary. This dictionary is maintained in a different option set that is only included in the French package file. + +The dictionary is sorted by length of the term, with the shortest terms appearing first. This ensures that as users search the dictionary, the terms where the largest proportion of the medical term matches with the search term is displayed first. + +### Selecting underlying cause of death { #selecting-underlying-cause-of-death } + +Selecting the underlying cause of death is a key component of the module. This is done through four checkboxes, which indicate which of the (up to) four causes is the underlying cause. Program rules are used to ensure that only one of the checkboxes can be selected, and that each checkbox can only be used if a diagnosis has been selected for that line/cause. + +Once a cause has been selected as underlying, two read-only fields are assigned with the ICD-SMoL name and code for the selected cause. + +## Instalación { #installation } + +### Requirements and preparation { #requirements-and-preparation } + +In order to install the module, an administrator user account on DHIS 2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS 2. + +Great care should be taken to ensure that the server itself and the DHIS application is well secured, to restrict access to the data being collected. Even if using this module without any direct patient identifiers like ID or names, the age, sex and health facility could be sufficient to identify an individual. Details on securing a DHIS 2 system is outside the scope of this document, and we refer to the DHIS 2 documentation. + +### Choosing a version of the module { #choosing-a-version-of-the-module } + +### Importar metadatos { #importing-metadata } + +The module is imported through a `.json` file with DHIS 2 metadata, using the Metadata import feature of the DHIS 2 Import/Export app. When importing the metadata in a DHIS 2 database with existing metadata, you might see errors if you look at the detailed import summary. These could require action, for example if a data element with the same name or code already exists in the database your are importing the module into. In this case, you will either have to change the identifier (name, code) in the database, or modify the name/code in the import file. Any such modifications should be done first in a test or staging environment, to make sure the changes do not affect other parts of the system. + +### Additional configuration { #additional-configuration } + +Once all metadata has been successfully imported, there are a few steps that needs to be taken before the module is functional. + +1. The programme must be assigned to a new or existing user role before users can start entering data. In addition, users need to have the necessary authorities in order to enter and/or see tracker data. Refer to the DHIS 2 Documentation for more information on configuring user roles. + +2. The programme must be assigned to the organisation units for which data will be entered. + +3. Optionally, you might also want to use the Sharing functionality of DHIS 2 to configure which users (user groups) should see the metadata and data associated with the programme. Sharing can be configured for the program itself, data elements, program indicators, aggregate indicators, option sets, and the analytical outputs. + +### Adapting the tracker program { #adapting-the-tracker-program } + +Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that could be made include: + +- Añadir variables adicionales al formulario. +- For the tracker programme, linking the programme to an existing tracked entity type and/or modifying the tracked entity attributes. A placeholder tracked entity is included in the module. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- However, it is strongly recommended not to change or remove any of the included form/metadata. This is both because the included variables are the standard recommended variables from the international death notification form, and because there is a danger that modifications could break functionality, for example program rules and program indicators. For example almost all variables in the form are linked to one or more program rules, which would cease to function if the variable is removed or replaced. Changing the default variables could also complicate updates to the module in the future. + +### Maintenance { #maintenance } + +Maintenance of the module has two main aspects: maintenance of the dictionary of medical terms, and maintenance related to new versions of DHIS 2. Each of these aspectes will be described here. + +#### Dictionary maintenance { #dictionary-maintenance } + +The dictionary of medical terms is a key component of the module, and is critical in order to produce meaningful data. This section describes how to check the integrity of the dictionary (e.g. that the codes used are valid), list terms that have been collected which are not in the dictionary and should thus be considered for inclusion, and how to add new terms to the dictionary. Several SQL-views are included in the module to facilitate these tasks. + +#### Checking integrity of dictionary { #checking-integrity-of-dictionary } + +As described above, the dictionary is implemented as an option set in DHIS 2, with the medical term as the option name and a special format for the option code that consists of the ICD-SMoL code, ICD-10 code and an ID separated by the | (pipe) symbol. SQL-views are included to verify that all entries in the dictionary follow this format: + +- Dictionary entries with invalid code format - list entries where the code does not follow the format of `[content]|[content]|[content]`. +- Dictionary entries with invalid ICD-SMoL reference - list entries where the ICD-SMoL-part of the code is not in the ICD-SMoL list, which is provided as a separate option set. +- Dictionary entries mixing main- and sub-categories - list entries where, for the same ICD-SMoL code, some entries link to the main ICD-SMoL code and some to the specific code (e.g. some to 5-4 and 5-4.1). This can create misleading outputs when analysing data within DHIS 2 as deaths might be double counted. + +#### Adding terms to the dictionary { #adding-terms-to-the-dictionary } + +An SQL view "Terms not found in dictionary" is included that will list all medical terms that have been entered as free text, i.e. which were not found in the dictionary during data entry, and the number of times they have been entered. These are terms that should be considered for inclusion in the dictionary if they occur frequently and are meaningful. + +Before a term can be added to the dictionary, the correct ICD-SMoL and ICD-10 code must be identified. Together with the ID, these make up the code to be used in the dictionary. To find the ID, an SQL view Next dictionary index number is included that will show the next ID to use. It has two columns, termtype and nextvalue. As discussed above, it is recommended that each country uses a county code for local additions to the dictionary, in which case that code will be listed under termtype and the next number to use in the nextvalue column. If no local terms have yet been added, use [country code]00001 as the first ID, e.g. GH00001 if using GH as country code. Once the first local term has been added, the SQL view will show the next ID to use at any time. + +To ensure that the right terms are displayed first in the dictionary, it must be sorted by the length of the term. After adding new terms to the dictionary, it must be re-sorted so that the new terms are not always last in the list. This can be done with the follwing SQL query (for PostgreSQL databases): + +```sql + with ordered as ( + select + uid, + name, + code, + row_number() OVER (ORDER BY length(name),name) AS sort_order + from optionvalue + where + optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY') + ) + update optionvalue ov + set sort_order = ord.sort_order + from ordered ord + where + ov.uid = ord.uid and + ov.optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY'); +``` + +**Note** that this is an UPDATE query that must be executed directly in the database, not through the DHIS2 user interface. + +Upgrading DHIS + +When new versions of DHIS2 are released, it is important to test all functionality of the module on a staging/test server before upgrading any production instances of system. + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md index dc58c8426..8a5b78380 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md @@ -42,7 +42,7 @@ The **Cause of Death event program** is no longer included in the WHO Cause of D - ID replacement -| Object | Property | Old value | New value | Programa | +| Objeto | Property | Old value | New value | Programa | |-|-|-|-|-| | option | id | CvivP1rh4ii | x9yVKkv9koc | Event and Tracker | | option | id | PLlPgcfbL1D | R98tI2c6rF5 | Event and Tracker | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md index 9bb6f2633..1cc5d435c 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md @@ -25,7 +25,7 @@ Unlike cause-based mortality surveillance systems and death certification system For cause-based mortality surveillance, please reference the [DHIS2 Cause of Death metadata package](#cod-design) designed to support the WHO recommended medical certification of cause of death and International Classification of Disease (ICD) standards. -### Intended Users { #intended-users } +### Usuarios objetivo { #intended-users } The package is designed with the following end users in mind: @@ -65,7 +65,7 @@ Three core user groups are included in the package. By default the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|-----------------------------------------------------| | | _RMS - access_ | _RMS - admin_ | _RMS - data capture_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: no access | Metadata : can view
Data: can capture and view | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md index 01fd064de..d0fc3a56c 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -129,50 +129,50 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -182,24 +182,24 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------|---------------------------------------------------|-----------------------------------------------------| | | _RMS access_ | _RMS admin_ | _RMS data capture_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: no access | Metadata : can view
Data: can capture and view | -| _*Dashboards*_ | Metadata : can view | Metadata : can edit and view | No Access | +| _*Dashboards*_ | Metadata : can view | Metadata : can edit and view | Sin acceso | The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -210,22 +210,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__design-md index 71c347a55..b602de30e 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__design-md @@ -167,7 +167,7 @@ The data elements reported in this stage and options available in dropdown lists |:-----------------:|:-----------------:|:-----------------:|:--------------------:| | VE - Admin | Puede editar y visualizar | Puede editar y visualizar | Solo lectura | | VE - Access | Puede editar y visualizar | Solo lectura | Solo lectura | -| VE - Data capture | No Access | Solo lectura | Puede capturar y visualizar | +| VE - Data capture | Sin acceso | Solo lectura | Puede capturar y visualizar | **These should be adapted depending on the local context.** ## Realtime notifications { #realtime-notifications } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__installation-md index 61086cf76..f6685cec9 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__CRVS-MORTALITY__VITAL-EVENTS__installation-md @@ -9,13 +9,13 @@ tags: This document includes an installation guide for the updated Vital Events tracker package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese -## Overview { #overview } +## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -55,29 +55,29 @@ The package metadata json files contain a "package" component that provides tech ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Vital Events tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -85,34 +85,34 @@ The Vital Events tracker package includes three metadata files. The contents and |---------------------------------------------------------------|-------------------------|--------------------| | CRVS_VE_TKR_1.1.0_DHIS2.35.11-en | Updated tracker package | New implementation | -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|---------------------------------------------------------------------------| -| Numerator only (number)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Per 1000 | `zpa0vUC7IWd` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1000` | | Porcentaje | `hmSnCXmLYwt` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -120,13 +120,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|----------------------------------------| -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -213,53 +213,53 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros -* Visualizations, maps, event reports and report tables -* Data sets -* Category options +* Visualizaciones, mapas, informes de eventos y tablas de informes +* Sets de datos +* Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -269,53 +269,53 @@ Three core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _VE - Access_ | _VE - Data capture_ | _VE - Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | | _*Program Stages*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | -| _*Dashboards*_ | Metadata : can view | No Access | Metadata : can edit and view | -| _*Data Sets*_ | Metadata : can view
Data: can view | No Access | Metadata : can edit and view
Data: No access | +| _*Dashboards*_ | Metadata : can view | Sin acceso | Metadata : can edit and view | +| _*Data Sets*_ | Metadata : can view
Data: can view | Sin acceso | Metadata : can edit and view
Data: No access | The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DHIS2-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DHIS2-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md new file mode 100644 index 000000000..f2301c49a --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DHIS2-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md @@ -0,0 +1,93 @@ +--- +edit_url: "https://github.com/dhis2-metadata/GEN_LIB/blob/master/docs/gen_lib-installation.md" +revision_date: '2022-07-01' +tags: +- Implementar +--- + +# Common metadata library - Installation Guide { #gen-lib-installation } + +This document includes an installation guide for the common metadata library. + +Idioma predeterminado del sistema: Inglés + +Available translations: French, Spanish, Portuguese, Arabic + +## Instalación { #installation } + +The table below will help you identify which metadata file/s are relevant for your implementation: + +| Metadata file | Application area | +|------------------------------------|------------------| +| Common metadata library (complete) | DHIS2 environment containing both tracker and aggregate modules, implementation of published metadata packages, development of custom programs and modules that utilise common metadata | +| Common tracker metadata library | Tracker-based DHIS2 environment, implementation of published tracker packages, development of custom tracker programs that utilise common tracker metadata | +| Core case profile | Tracker-based DHIS2 environment, implementation of published tracker packages, development of custom tracker programs that utilise core case profile data (Person) | +| Common aggregate metadata | Implementation of published aggregate modules, development of custom aggregate modules that utilise common aggregate metadata | + +For more information, refer to the [Common metadata library design guide](#common-metadata-library) + +Carefully read through each section of the installation guide before importing the metadata files into your DHIS2 instance! + +### Importing common metadata into a blank DHIS2 instance { #importing-common-metadata-into-a-blank-dhis2-instance } + +The application area of the DHIS2 instance will help you identify, which metadata file/s to import. The metadata can be imported without any additional adjustments. + +### Importing common metadata into a working DHIS2 instance { #importing-common-metadata-into-a-working-dhis2-instance } + +Overwriting metadata in the target instance may change the configuration of the existing programs and may lead to errors. When you import the Common metadata library into a working DHIS2 environment, you need to make sure that you do not lose any existing configurations (ie. sharing settings, option sort order, etc). + +If the metadata objects in the common metadata library and in the target instance share the same UIDs but are not identical (eg. different aggregation type, different assigned option set, different number of options), consider assigning new UIDs to the metadata objects in the target instance, before importing the common metadata library. + +#### UIDs { #uids } + +Replacing UIDs for metadata elements in the target system to match the source metadata file can be a complex task, as the uid maybe referenced in other metadata objects, such as program rules, indicators, predictors, validation rules, etc. +Make sure to replace all occurances of the old uid with the new uid in the system before importing the metadata object. + +> **EXAMPLE** +> +> To update the uid of a category option use the following command: +> +> ```SQL +> UPDATE dataelementcategoryoption SET uid = '' WHERE uid = ''; +> ``` + +#### Tracked entity attributes, data elements, option sets and options { #tracked-entity-attributes-data-elements-option-sets-and-options } + +For option set based data elements and attributes, make sure that these option sets are identical in the source file and in the target instance. +Check that the matching option sets contain the same options. + +Check the aggregation and value types of the data elements and attributes in the source file and the target instance. + +#### Option codes { #option-codes } + +According to the DHIS2 naming conventions, the metadata codes use capital letters, underscores and no spaces. Some exceptions that may occur are specified in the corresponding package documentation. If data values in the target instance contain lower case codes, it is important to update those values directly in the database. + +The table below contains all option sets where codes were changed to upper case in the metadata package. Before importing metadata into the instance, check whether the option sets in the existing system match those in the package .json and use the same upper case option codes. + +> **Important** +> +> During the import, the existing option codes will be overwritten with the updated upper case codes. +> In order to update the existing data values, it is necessary to update the values stored in the database using database commands. +> Make sure to map existing old option codes and new option codes before replacing the values. Use staging instance first, before making adjustments on the production server. + +For data element values, use: + +```SQL +UPDATE programstageinstance +SET eventdatavalues = jsonb_set(eventdatavalues, '{"","value"}', '""') +WHERE eventdatavalues @> '{"":{"value": ""}}'::jsonb +AND programstageid=; +``` + +For tracked entity attribute values, use: + +```SQL +UPDATE trackedentityattributevalue +SET value = +WHERE trackedentityattributeid= AND value=; +``` + +#### Tracked entity type { #tracked-entity-type } + +If the tracked entity types in the Common metadata library and the target instance match, reviw the sharing settings, the assigned tracked entity type attributes and their settings, before importing the Common metadata library. + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md index e6cb9ddbd..2ffd8b537 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md @@ -11,7 +11,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,41 +20,41 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -62,15 +62,15 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |--------|-------------|--------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -79,39 +79,39 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -#### Sharing { #sharing } +#### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -124,12 +124,12 @@ A metadata package usually contains several user groups: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | AFI access | AFI admin | AFI data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | Please refere to the individual package installation annex for information about user groups. @@ -142,47 +142,47 @@ If your TET Person already matches the one in the package and you want to avoid * Import the package * Update sharing properties for this TET using the table above. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ### [CONFIG] metadata { #config-metadata } The following metadata needs to be configured after import. -| Metadata Type | Nombre | +| Tipo de metadatos | Nombre | |---------------------|----------------------------------------------------| -| Option Sets | [CONFIG]\_Race / Ethnicity / Nationality | -| Option Sets | [CONFIG]\_Occupation | -| Option Sets | [CONFIG]\_Diagnosis | +| Set de opciones | [CONFIG]\_Race / Ethnicity / Nationality | +| Set de opciones | [CONFIG]\_Occupation | +| Set de opciones | [CONFIG]\_Diagnosis | | Data Elements | [CONFIG]\_Month before illness, [Other exposure X] | | Data Elements | [CONFIG]\_Laboratory test X | | Data Elements | [CONFIG]\_Date of test X | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md index c42b2ad7d..192743f2e 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md @@ -9,11 +9,11 @@ tags: This document includes an installation guide for the IDS aggregate package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. @@ -24,62 +24,62 @@ The metadata package consists of the following modules: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file) 2. [Importing the metadata file into DHIS2](#importing-metadata) 3. [Configuring the imported metadata](#configuration) -4. [Adapting the program after import](#adapting-the-program) +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Preparing the Metadata File { #preparing-the-metadata-file } -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Visualizations using root organisation unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -233,50 +233,50 @@ Note that all validation rule notifications for this package are all set to be s ***NB: Note that you can also change this in maintenance for each validation rule notification at any time after they are imported as you may want to demonstrate or test both strategies to select one that is appropriate for your own setting***. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } Use the [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -286,16 +286,16 @@ Three core user groups are included in the package: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: 1. Aggregate data analysis : Can access dashboards, data visualizer, pivot tables, reports and maps. 2. Aggregate data capture : Can acccess the data entry app and add/modify data values, -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } The data sets must be assigned to organisation units within existing hierarchy in order to be accessible for data entry and data analysis personnel. @@ -341,30 +341,30 @@ By default, notifications will be sent out to via the DHIS2 messaging app. In order to send out notifications via SMS or e-mail, you will need an [SMS gateway](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/configure-sms.html#sms-configuration-gateways) and/or an [e-mail configuration](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/system-settings.html#system_email_settings) set up within your DHIS2 instance. The settings necessary for these will vary between implementations and it is best to consult the documentation links provided here for more information. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. +- Añadir variables adicionales al formulario. - Adapting data element names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales - Adding dashboards/dashboard items However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example predictors or notifications. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadata requires advanced knowledge of DHIS2 and various dependencies. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md index 23c5c3c56..35bd4f3a9 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md @@ -7,11 +7,11 @@ tags: # VPD CS Tracker Installation Annex { #vpd-cs-installation } -## Overview { #overview } +## Visión general { #overview } The VPD CS tracker package is self-contained, meaning it can be installed on its own. However, it is worth noticing that this package contains some metadata from the IDSR package. The reason for this is that there is a comparative table which makes it possible to compare the aggregated data and the tracker data. Thus, we recommend installing the aggregate disease surveillance ("IDS") package prior to this one, although it is not a mandatory requirement. -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,41 +20,41 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -62,13 +62,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |--------|-------------|--------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Generic metadata { #generic-metadata } @@ -76,7 +76,7 @@ The package contains some metadata that is typically common or shared across man Generic Data Elements used in the VPD CS package -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------------------------|-------------|--------------------------------------------------------------| | GEN - Population | DkmMEcubiPv | `../api/dataElements.json?filter=name:like:GEN - Population` | | GEN - Population < 15years | cPLAnOTldta | `../api/dataElements.json?filter=name:like:GEN - Population` | @@ -85,7 +85,7 @@ Generic Data Elements used in the VPD CS package Category options, categories, category Combos for ages -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |--------------------|-------------|------------------------------------------------------| | 0-4 years | UPvKbcqTEY3 | `../api/categoryOptions.json?filter=name:like:years` | | 5+ years | afpMrUgPzl3 | `../api/categoryOptions.json?filter=name:like:years` | @@ -98,7 +98,7 @@ There are many predictors in the package which are using a placeholder for distr The placeholder uses the label . Before attempting to import the package you need to replace this label with the UID of the equivalent OUL in your system. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -107,35 +107,35 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } There are three user groups that come with the package: @@ -145,12 +145,12 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|------------------------------------|---------------------------------------------|------------------------------------------------| | | VPD CS access | VPD CS admin | VPD CS data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](#sharing) for more information on configuring sharing. @@ -163,35 +163,35 @@ If your TET Person already matches the one in the package and you want to avoid * Import the package * Update sharing properties for this TET using the table above. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md index 8bb7010a1..0a7cfa87b 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -113,50 +113,50 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -166,7 +166,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _ENTO - Field Access_ | _ENTO - Field Data Capture_ | _ENTO - Field Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: no access | @@ -176,16 +176,16 @@ By default, the following permissions are assigned to these user groups: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -196,22 +196,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md index c1ae4e442..8c9add516 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md @@ -11,7 +11,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,49 +20,49 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -71,35 +71,35 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -#### Sharing { #sharing } +#### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: @@ -115,11 +115,11 @@ A metadata package usually contains several user groups: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | VC-IRS Access | VC-IRS Admin | VC-IRS Data Capture | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | Please refere to the individual package installation annex for information about user groups. @@ -127,36 +127,36 @@ Please refere to the individual package installation annex for information about You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](#sharing) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. 2. Tracker data capture : Can add data values, access capture to create events Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the event program](#adapting-the-event-program)." Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the event program { #adapting-the-event-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. * Adapting the Category Combo used in the Event program to use category options for the Partners involved in the campaign -* Adding translations to variables and/or the data entry form. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md index 2fdddae81..6d8055a23 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -113,49 +113,49 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -165,7 +165,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _ENTO - Field Access_ | _ENTO - Field Data Capture_ | _ENTO - Field Admin_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: no access | @@ -173,16 +173,16 @@ By default, the following permissions are assigned to these user groups: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -193,22 +193,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md index 8dc5deb04..cdc7b1739 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -113,49 +113,49 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -165,7 +165,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _ENTO - Field Access_ | _ENTO - Field Data Capture_ | _ENTO - Field Admin_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: no access | @@ -173,16 +173,16 @@ By default, the following permissions are assigned to these user groups: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -193,22 +193,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md index 3f5d6b837..cfaf63a1b 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md @@ -11,7 +11,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,41 +20,41 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -62,15 +62,15 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |---------------|-------------|-----------------------------------------------------------| | VC- Household | fT6xzEDXQAu | `../api/trackedEntityTypes.json?filter=name:eq:Household` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -79,39 +79,39 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -#### Sharing { #sharing } +#### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -124,12 +124,12 @@ A metadata package usually contains several user groups: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | VC-ITN Access | VC-ITN Admin | VC-ITN Data Capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | Please refere to the individual package installation annex for information about user groups. @@ -142,36 +142,36 @@ If your TET Household already matches the one in the package and you want to avo * Import the package * Update sharing properties for this TET using the table above. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker and event programs { #adapting-the-tracker-and-event-programs } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. * Adapting the Category Combo used in the Event program to use category options for the years you are doing the campaigns -* Adding translations to variables and/or the data entry form. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__general-design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__general-design-md index 16563d8a3..154aebf66 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__general-design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__ENTOMOLOGY-AND-VECTOR-CONTROL__general-design-md @@ -59,7 +59,7 @@ These packages are intended to be used by: | Grupo de usuarios | Tablero (Dashboard) | Program Metadata | Program data | |-------------------|-------------------|-------------------|----------------------| -| **ENTO-Admin** | Puede editar y visualizar | Puede editar y visualizar | No Access | +| **ENTO-Admin** | Puede editar y visualizar | Puede editar y visualizar | Sin acceso | | **ENTO-Access** | Puede editar y visualizar | Solo lectura | Solo lectura | | **ENTO-Data capture** | No access | Solo lectura | Puede capturar y visualizar | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__design-md index 571e36ce8..a315b0abe 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__design-md @@ -226,7 +226,7 @@ For example, to capture multiple services provided by Community Health Workers, | Grupo de usuarios | Metadatos | Datos | |-----------------------|-------------------|----------------------| -| HFP - Admin | Puede editar y visualizar | No Access | +| HFP - Admin | Puede editar y visualizar | Sin acceso | | HFP - Access | Solo lectura | Solo lectura | | HFP - Data capture | Solo lectura | Puede capturar y visualizar | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__installation-md index 0e98b7f03..d5cc8cd67 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HEALTH-FACILITY-PROFILE__installation-md @@ -9,36 +9,36 @@ tags: Package Version 1.0.0 -System default language: English +Idioma predeterminado del sistema: Inglés ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. 3. [Configuring](#configuration) the imported metadata. 4. [Adapting](#adapting-the-tracker-program) the program after being imported -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata (No other versions of HFP tracker imported previously). 3. Update existing/older version of the HFP tracker. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](http://dhis2.org/documentation). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section [Importing a metadata file into DHIS2](#importing-metadata) -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension (if applicable) { #default-data-dimension-if-applicable } @@ -46,39 +46,39 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:----------------------------|:------------|:----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into , the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. **_Note that this search and replace operation must be done with a plain text editor_**, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. The following table shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-----------|:------------|:-------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | | Rate (factor=1)| k4RGC3sMTzO | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1`| | Per 10 000 | FWTvArgP0jt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:10000`| -| Numerator only (number) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| +| Sólo numerador (número) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-------|:------------|:-------------------------------------------------------| | Health Facility | xzck98PlU28 | `../api/trackedEntityTypes.json?filter=name:eq:Health%20Facility` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. Some visualizations and maps may contain references to organisation unit levels. Maps that consist of several map views may contain various Organisation unit level references based on the configuration of the map layer. Adjust the organisation unit level references in the metadata json file to match the organisation unit structure in the target instance before importing the metadata file. @@ -92,45 +92,45 @@ The process of upgrading an existing package to a newer version in a working DHI - the new objects are created; - assignment of users to relevant user groups is reviewed. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/master/en/user/html/import_export.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } > NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to conflict with. Follow the instructions to import the metadata then please proceed to the “[Configuration](#configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -143,46 +143,46 @@ A metadata package usually contains several user groups: By default, the following is assigned to these user groups -| Object | User Groups | User Groups | User Groups | +| Objeto | Grupos de usuarios | Grupos de usuarios | Grupos de usuarios | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | HFP - Access | HFP - Admin | HFP - Data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/master/en/dhis2_user_manual_en/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. ## Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__design-md index ddeb790b8..c5d164347 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__design-md @@ -11,9 +11,9 @@ tags: El componente de vigilancia de casos del kit de herramientas para el VIH de DHIS2 se basa en las últimas directrices de la OMS [Directrices consolidadas sobre información estratégica del VIH centrada en la persona: fortalecimiento de los datos de rutina para generar impacto] (https://www.who.int/publications/i/item/9789240055315) (2022) y el Kit de adaptación digital para el VIH: requisitos operativos para implementar las recomendaciones y estándares de la OMS dentro de los sistemas digitales, segunda edición. -This toolkit includes +Este kit de herramientas incluye - Análisis de tableros e indicadores básicos recomendados por la OMS para monitorear las iniciativas de atención y tratamiento del VIH y utilizar métricas clave para ajustar la programación e impulsar el impacto. -- DHIS2 Tracker program aligned with the WHO Digital Adaptation Kit data standards for individual level data collection and operational person-centred monitoring at facility and community levels +- El programa Tracker DHIS2 está alineado con los estándares de datos del kit de adaptación digital de la OMS para la recopilación de datos a nivel individual y el monitoreo operativo centrado en la persona a nivel de establecimiento y comunidad - Set de datos agregados y elementos de datos para el modelo de datos tracker agregados para análisis anónimos y de alto rendimiento - Data exchange mapping for aggregating DHIS2 tracker data for Case Surveillance indicators and integration of key indicators with national HMIS @@ -36,7 +36,7 @@ Efforts to end the HIV epidemic by 2030 face persistent challenges, with 1.5 mil A person-centred monitoring approach offers distinct advantages for longitudinal HIV data collection that can track and record HIV care and treatment services provided to an individual over time and space (e.g. different service delivery sites and touchpoints with HIV care and treament programmes). Scaling up individual level data collection allows for flexible disaggregation and enhanced analysis by various factors such as time, location, age, gender, clinical status, coinfections, treatment and more. This depth of information enhances our understanding of HIV epidemiology and facilitates ongoing monitoring of trends. Implementation of case-based electronic data is anticipated to enhance data quality by minimising data entry steps, integrating automatic calculations and validations, swiftly correcting or completing inconsistent or incomplete individual records, and facilitating de-duplication. -Sin embargo, en la mayoría de los PIBM, la digitalización de los sistemas de datos a nivel individual administrados por los Ministerios de Salud a menudo tarda años en alcanzar a escalar y debe ir acompañada de recursos sustanciales en el país para sostener el sistema a lo largo del tiempo. Además, los datos históricos y otros datos programáticos a menudo se recopilan o representan a través del modelo de datos agregados, como denominadores basados ​​en estimaciones del espectro para personas que viven con el VIH e informes agregados basados en papel de sitios de prestación de servicios con conectividad escasa o nula, disponibilidad limitada de dispositivos y/o infraestructura deficiente. +Sin embargo, en la mayoría de los PIBM, la digitalización de los sistemas de datos a nivel individual administrados por los Ministerios de Salud a menudo tarda años en alcanzar a escalar y debe ir acompañada de recursos sustanciales en el país para sostener el sistema a lo largo del tiempo. Además, los datos históricos y otros datos programáticos a menudo se recopilan o representan a través del modelo de datos agregados, como denominadores basados ​​en estimaciones de Spectrum para personas que viven con el VIH e informes agregados basados en papel de sitios de prestación de servicios con conectividad baja o nula, disponibilidad limitada de dispositivos y/o infraestructura deficiente. Therefore, the HIV Case Surveillance toolkit leverages all DHIS2 applications and data models to support practical, implementable approaches to collecting, analysing and using HIV Case Surveillance data effectively to manage and link newly identified HIV cases into treatment programs and ensure a proper monitoring of people living with HIV. These tools can be used in a modular way to meet the needs of any country along the maturity model for digitization of health data – including hybrid implementation of paper-based and digitised systems, as well as incorporating data from other electronic tools like hospital EMRs where these may be used. @@ -55,7 +55,7 @@ El diseño del sistema de Vigilancia de Casos de VIH se centra en satisfacer las - **Directores y personal del programa de VIH (nacional y subnacional)**: usuarios de datos que son responsables del análisis rutinario de los datos, de su utilización para mejorar las operaciones y las estrategias del programa, y ​​de proporcionar al personal del programa retroalimentación basada en datos, incluidos los socios implementadores, instalaciones y otros puntos de prestación de servicios - **Administradores de datos del programa de VIH**: usuarios responsables de supervisar la recopilación, gestión, calidad de los datos, funciones de análisis y presentación de informes para el programa nacional de VIH - **Administradores de sistemas/puntos focales de HMIS**: personal del Ministerio de Salud y/o equipo central de DHIS2 responsable de mantener y mejorar los sistemas de datos para programas de salud, integrar flujos de datos en plataformas nacionales, brindar soporte técnico para el diseño del sistema, adaptación y soporte al usuario final; y mantenimiento del sistema DHIS2 a lo largo del tiempo -- **Sitios de prestación de servicios**: el personal de los sitios de prestación de servicios puede utilizar el programa Tracker DHIS2 para registrar datos para visitas de rutina, así como utilizar herramientas de DHIS2 como listas de trabajo y listas de líneas para realizar un seguimiento de los clientes y monitorear la aceptación de los servicios a nivel individual. +- **Sitios de prestación de servicios**: el personal de los sitios de prestación de servicios puede utilizar el programa Tracker DHIS2 para registrar datos de visitas de rutina, así como utilizar herramientas de DHIS2 como listas de trabajo y listados para realizar un seguimiento de los clientes y monitorear la aceptación de los servicios a nivel individual. - **Socios implementadores**: organizaciones que brindan asistencia técnica al programa nacional de VIH, recopilan y analizan datos en nombre de la estrategia general del programa nacional y pueden ser responsables de las operaciones de las redes de prestación de servicios como asesoramiento sobre VIH, difusión educativa, trabajadores de salud comunitarios. ### Estructura de diseño { #design-structure } @@ -93,17 +93,16 @@ El programa tracker de vigilancia de casos de VIH DHIS2 permite la inscripción ### Inscripción { #enrollment } -Se supone que el flujo de trabajo de vigilancia de casos de VIH comienza con la inscripción de cualquier persona con un estado positivo de VIH confirmado. +Se supone que el flujo de trabajo de vigilancia de casos de VIH comienza con la inscripción de cualquier persona con un estado VIH positivo confirmado. -Cuando una persona está inscrita en el programa de vigilancia de casos de VIH como Instancia de Entidad Tracker (TEI), los Atributos de Entidad Tracker (TEA) se registran para formar el perfil del caso. -Todos los TEA están alineados y armonizados con los incluidos en el tracker de Prevención del VIH, lo que permite la inscripción en ambos programas o la integración en un único programa tracker si se desea a nivel de implementación local. Tenga en cuenta que varios TEA se comparten entre programas Tracker DHIS2 que no son de VIH; estos están configurados con un prefijo 'GEN' (general) para indicar que se comparten entre programas de tracker. Consulte la [Biblioteca de metadatos comunes](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html) para obtener más información sobre los metadatos de tracker compartidos. +Cuando una persona está inscrita en el programa de vigilancia de casos de VIH como Instancia de Entidad Tracker (TEI), los Atributos de Entidad Tracker (TEA) se registran para formar el perfil del caso. Todos los TEA están alineados y armonizados con los incluidos en el tracker de Prevención del VIH, lo que permite la inscripción en ambos programas o la integración en un único programa tracker si se desea a nivel de implementación local. Tenga en cuenta que varios TEA se comparten entre programas Tracker DHIS2 que no son de VIH; estos están configurados con un prefijo 'GEN' (general) para indicar que se comparten entre programas de tracker. Consulte la [Biblioteca de metadatos comunes](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html) para obtener más información sobre los metadatos de tracker compartidos. El atributo **program UID** de TEA se refiere a un identificador específico del programa de VIH. Se ha mantenido intencionalmente en blanco ya que los procesos de codificación dependen del contexto local. Consulte la [Documentación del usuario DHIS2 sobre la configuración de identificadores únicos en todo el sistema como TEA DHIS2](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-238/configuring-the-system/programs.html#create_tracked_entity_attribute:~:text=Select%20Unique%20to,same%20organisation%20unit.). El uso de códigos UID anónimos permite identificar de forma única a las personas que acceden a los servicios de prevención del VIH y realizar un seguimiento longitudinal, sin recopilar otros tipos de información de identificación personal (OMS, 2022). La **fecha de nacimiento y edad** se puede asignar de dos formas diferentes: - Fecha de nacimiento conocida: seleccione la fecha de nacimiento -- Unknown date of birth: select the Date of birth - Unknown option and then enter the age either in years or months. +- Fecha de nacimiento desconocida: seleccione la opción fecha de nacimiento -Desconocida y luego ingrese la edad en años o meses. Una vez hecho esto, se asigna una edad de nacimiento "probable" a la fecha de nacimiento en función del valor ingresado en los años o el mes TEA. @@ -125,7 +124,7 @@ Concerning the key population information we recommend implementations to refer Los detalles del diagnóstico de VIH y los datos de la población clave se recopilan como una etapa del programa con el fin de proteger aún más la naturaleza sensible de estos datos. Específicamente, al incluir estos datos solo en la etapa del programa, no son accesibles para buscar una TEI, donde los usuarios pueden tener un acceso más amplio para buscar clientes. -In some implementations, instead of having the different key population groups listed as selectable categories, a set of questions has been proposed and according to the answer a key population identification is assigned to the clients. [See the section Implementation Considerations & Local Adaptation in this document](https://docs.google.com/document/d/1h7KBCLA99jVoTmDTBttIiSk4SKKD7tcIw7yq5A3yH68/edit#heading=h.7690t3h1dai8). +En algunas implementaciones, en lugar de tener los diferentes grupos de poblacion clave listados como categorías seleccionables, se ha propuesto un conjunto de preguntas y según la respuesta se asigna una identificación de población clave a los clientes. [Ver la sección consideraciones de implementación y adaptación local en este documento](https://docs.google.com/document/d/1h7KBCLA99jVoTmDTBttIiSk4SKKD7tcIw7yq5A3yH68/edit#heading=h.7690t3h1dai8). Para una persona inscrita en un programa de vigilancia de casos de VIH, es posible que su asociación con un grupo de población clave cambie con el tiempo, ya que el riesgo de una persona de contraer el VIH, su participación en conductas de alto riesgo y sus necesidades de prevención del VIH varían con el tiempo. La etapa del programa se ha diseñado intencionalmente como no repetible para permitir un análisis optimizado basado ​​en el grupo de población clave. Sin embargo, un usuario puede volver a visitar esta etapa y modificar los grupos de población clave según sea necesario. @@ -135,11 +134,11 @@ Para una persona inscrita en un programa de vigilancia de casos de VIH, es posib Esta etapa repetible del programa captura toda la información relevante para las visitas/encuentros de la persona que recibe servicios de atención y tratamiento del VIH, independientemente del tipo de servicio al que acceda. Permite capturar múltiples tipos de servicios prestados en una visita. Esto es fundamental para un sistema integral de gestión y presentación de informes centrado en la persona. -En esta etapa del programa, la 'fecha de evento' del programa DHIS2 (o 'fecha de informe' por defecto en la aplicación de Mantenimiento para la configuración del programa) ha sido renombrada para representar la 'Fecha de visita'. Esto significa que todos los análisis basados ​​en la fecha del evento se evaluarán en funció de la fecha del encuentro (visita) de la persona con el proveedor de servicios de atención y tratamiento del VIH. +En esta etapa del programa, la 'fecha de evento' del programa DHIS2 (o 'fecha de informe' por defecto en la aplicación de Mantenimiento para la configuración del programa) ha sido renombrada para representar la 'Fecha de visita'. Esto significa que todos los análisis basados ​​en la fecha del evento se evaluarán en función de la fecha del encuentro (visita) de la persona con el proveedor de servicios de atención y tratamiento del VIH. ![Fecha de evento DHIS2](resources/images/event_date_visit_date.png) -Además de la fecha de la visita, se han configurado fechas clave adicionales como elementos de datos del dominio Tracker relacionados con estas actividades (por ejemplo, inicio de TAR, fecha de test de ITS, etc.) y estas deben informarse para permitir análisis adicionales basados ​​en el tiempo. +Además de la fecha de la visita, se han configurado fechas clave adicionales como elementos de datos del dominio Tracker relacionados con estas actividades (por ejemplo, inicio de TAR, fecha de la prueba de ITS, etc.) y estas deben informarse para permitir análisis adicionales basados ​​en el tiempo. #### Detalles de la visita { #visit-details } @@ -215,7 +214,7 @@ En la segunda sección, "Visita de seguimiento", se solicita información relaci En la sección de Infecciones de Transmisión Sexual (ITS), se recoge información relacionada con el síndrome de ITS diagnosticado, la prueba de ITS realizada y el tratamiento administrado entre los clientes inscritos en el programa de vigilancia de casos de VIH. -![Recogida de datos ITS](resources/images/STI.png] +![Recopilación de datos ITS](resources/images/STI.png] #### Hepatitis viral { #viral-hepatitis } @@ -250,7 +249,7 @@ Todos los elementos de datos configurados para el dominio Tracker también se in #### Elementos de datos clonados para la selección de opciones múltiples { #cloned-data-elements-for-multiple-option-selection } -Dentro de las etapas del programa para "Informe de caso inicial" y "Visitas", hay una serie de elementos de datos que se clonan para permitir la selección de opciones múltiples para un concepto determinado, compartiendo el mismo conjunto de opciones. Este diseño se implementa de la siguiente manera: +Dentro de las etapas del programa para "Informe de caso inicial" y "Visitas", hay una serie de elementos de datos que se clonan para permitir la selección de múltiples opciones para un concepto determinado, compartiendo el mismo conjunto de opciones. Este diseño se implementa de la siguiente manera: - Clonación de elementos de datos elegibles para elección de opciones múltiples - El número de clones del elemento de datos debe ser el mismo que el número de opciones presentes en el set de opciones relacionado - Cada elemento de datos clonado tiene su propio UID, nombre y código @@ -443,7 +442,7 @@ En el numerador de este indicador debemos contar las MVVS con diagnóstico de c ### Indicadores de programa { #program-indicators } -Los **indicadores del programa** se utilizan para agregar datos a nivel individual capturados en el modelo de datos del tracker; y asignarlos al modelo de datos agregados para su presentación, consumo y uso en las aplicaciones y tableros de análisis de DHIS2. El uso de la aplicación intercambio de datos DHIS2 para transferir valores de los indicadores de programa a elementos de datos agregados se describe con más detalle en la sección sobre Mapeo de metadatos e intercambio de datos. +Los **indicadores del programa** se utilizan para agregar datos a nivel individual capturados en el modelo de datos del tracker; y asignarlos al modelo de datos agregados para su presentación, consumo y uso en las aplicaciones y tableros de análisis de DHIS2. El uso de la aplicación Data Exchange DHIS2 para transferir valores de los indicadores de programa a elementos de datos agregados se describe con más detalle en la sección sobre Mapeo de metadatos e intercambio de datos. Los indicadores de programa se organizan en dos grupos de indicadores de programa: - *Vigilancia de casos de VIH - Intercambio de datos* [s7DBTTX68Lk] contiene todos los IP que están asignados a los elementos de datos agregados de destino correspondientes para su análisis. @@ -458,7 +457,7 @@ Los indicadores de programa se organizan en dos grupos de indicadores de program As described in the section on [Hidden Data Elements & Assigned Values](#Hidden-Data-Elements-&-Assigned-Values-to-Data-Elements), program rules are used to assign and copy the TEI’s key population group recorded in the initial case report to a hidden data element field on the repeatable Visit program stage. This allows for all program indicator calculations based on key population group to be configured, namely by using the auto-assigned data element as a filter in the program indicator. Note that in adjusting program indicators that filter based on Key Population group, you must use the set of data elements containing the postfix “- VISIT”. -- IH - Población clave - Hombres que tienen relaciones sexuales con hombres - VISITAS [kXutCUTOxcq] +- VIH - Población clave - Hombres que tienen relaciones sexuales con hombres - VISITAS [kXutCUTOxcq] - VIH - Población clave - Personas que se inyectan drogas - VISITAS [GSSOfwzb0DQ] - VIH - Población clave - Personas que viven en prisiones y otros entornos cerrados - VISITAS [iqXxZbRDhYG] - VIH - Población clave - Trabajador sexual - VISITAS [kICLXq7IEuP] @@ -514,7 +513,7 @@ Se crea un elemento de datos que informa VERDADERO en caso de que la primera pru Además, se crea otro elemento de datos que informa la fecha de la primera prueba de TB (si es un mWRD) y el valor reportado en los siguientes eventos **ITS.8 Repetición del diagnóstico del síndrome de ITS** -El período del informe del indicador se ha establecido como los “últimos 12 meses”, por lo que el resultado será la proporción de clientes diagnosticados con un síndrome de ITS concreto dos o más veces en los últimos 12 meses. +El período de informe del indicador se ha establecido como los “últimos 12 meses”, por lo que el resultado será la proporción de clientes diagnosticados con un síndrome de ITS concreto dos o más veces en los últimos 12 meses. En el numerador necesitamos calcular el número de personas que asisten a los servicios de prevención del VIH diagnosticadas con un síndrome de ITS concreto dos o más veces. Este filtro se basa en los elementos de datos ocultos asignados con valores para la "fecha del último diagnóstico": - VIH - ITS: Fecha del último diagnóstico del síndrome de secreción uretral [DI8O2sFAjIZ] @@ -551,7 +550,7 @@ Véase [Documentación para el usuario DHIS2 sobre cómo utilizar la aplicación Véase [Documentación para desarrolladores de DHIS2 sobre las API de DHIS2 para el intercambio de datos agregados](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-240/data-exchange.html?h=aggregate+data+exchange+2.40#create-aggregate-data-exchange) para obtener más información. -Los metadatos se han alineado con los diccionarios de datos y las referencias de indicadores publicados en el kit de adaptación digital (DAK) para el VIH de la OMS, segunda edición (véase el Anexo A de la Web del kit de adaptación digital para el diccionario de datos). Tenga en cuenta que el Tracker no está diseñado para respaldar todos los aspectos de las directrices de atención clínica y la gestión de casos, algunos de los cuales están contenidos en el VIH DAK, ni para reemplazar los EMR sólidos de los establecimientos; sin embargo, los datos de los EMR se pueden incorporar al registro nacional del VIH para su análisis y uso. +Los metadatos se han alineado con los diccionarios de datos y las referencias de indicadores publicados en el kit de adaptación digital (DAK) para el VIH de la OMS, segunda edición (véase el Anexo A de la Web del kit de adaptación digital para el diccionario de datos). Tenga en cuenta que el Tracker no está diseñado para respaldar todos los aspectos de las directrices de atención clínica y la gestión de casos, algunos de los cuales están contenidos en el DAK VIH, ni para reemplazar los EMR sólidos de los establecimientos; sin embargo, los datos de los EMR se pueden incorporar al registro nacional del VIH para su análisis y uso. Here you can find the mapping between the DHIS2 metadata and the HIV DAK data dictionary. @@ -567,15 +566,15 @@ Cuando la seguridad y la posibilidad de desalentar el acceso a los servicios sea ### Adaptación de la estructura del tracker { #tracker-structure-adaptation } -La estructura de seguimiento de la vigilancia de casos de VIH es en su mayor parte una estructura plana con una sola etapa principal repetible para registrar las actividades de cualquier tipo de visita de prevención. Esta estructura intencionalmente simplificada permite una mayor flexibilidad para la adaptación y personalización local. Por ejemplo: +La estructura de seguimiento de la vigilancia de casos de VIH es principalmente una estructura plana con una sola etapa principal repetible para registrar las actividades de cualquier tipo de visita de prevención. Esta estructura intencionalmente simplificada permite una mayor flexibilidad para la adaptación y personalización local. Por ejemplo: - Las secciones se pueden traducir fácilmente en etapas en caso de que distintos usuarios tengan que ingresar información diferente (como se ha detallado anteriormente, el servicio de vigilancia de casos de VIH es muy transversal y puede tener varios actores involucrados en la distribución de los servicios) - Cantidad reducida de reglas de programa y bien identificadas por la sección a la que se dirige - Si una actividad específica (intervención de atención del VIH, como el cáncer de cuello uterino) no es relevante para el paquete de servicios de atención y tratamiento del VIH que ofrece su país, simplemente puede eliminar una sección completa sin repercusiones en el resto del modelo de datos. #### Integración de la vigilancia de casos de VIH y del tracker de prevención del VIH { #integration-of-hiv-case-surveillance-and-hiv-prevention-tracker } -Depending on local context, some implementations may wish to integrate prevention and case surveillance into a single DHIS2 Tracker Program. An integrated tracker design option was considered for the global design guide, but ultimately discarded in favor of two Tracker programs for the following reasons: -- Scale: the number of persons (TEIs) enrolled in a prevention program is likely to be much, much greater than the number of persons (TEIs) diagnosed as positive and enrolled in a Case Surveillance program. This may have an impact on performance and also requires adequate server infrastructure for large-scale Tracker deployment. +Dependiendo del contexto local, algunas implementaciones pueden desear integrar la prevención y la vigilancia de casos en un único Programa Tracker DHIS2. Se consideró una opción de diseño de tracker integrado para la guía de diseño global, pero finalmente se descartó en favor de dos programas de tracker por las siguientes razones: +- Escala: es probable que el número de personas (TEIs) inscritas en un programa de prevención sea mucho, mucho mayor que el número de personas (TEIs) diagnosticadas como positivas e inscritas en un programa de Vigilancia de Casos. Esto puede tener un impacto en el rendimiento y también requiere una infraestructura de servidor adecuada para la implementación de Tracker a gran escala. - Tipos de proveedores de servicios: en muchos contextos nacionales, una gran escala y variedad de proveedores de servicios pueden participar en los servicios de prevención del VIH, como trabajadores comunitarios de salud, ONG/OSC como socios implementadores, etc. A menudo, estos proveedores de servicios de prevención no son responsables de dar seguimiento al caso de VIH a través de un tratamiento de por vida y no deben tener acceso a los datos de salud del cliente después de haber sido identificado como un cliente VIH positivo. Por lo tanto, separar los programas Tracker se adapta a la variedad y ayuda a garantizar la protección y la confidencialidad de los datos de las personas que viven con el VIH. - Los indicadores incluidos en las directrices SI y DAK de la OMS no requieren un análisis “entre programas”; todos los indicadores pueden generarse dentro de DHIS2 utilizando dos programas separados. - Un flujo de trabajo típico desde los servicios de prevención hasta la vigilancia de casos de VIH está bien respaldado al cerrar la inscripción en un programa de tracker de prevención DHIS2 y abrir una nueva inscripción en el programa de vigilancia de casos. La persona (TEI) está vinculada a los programas de prevención y vigilancia de casos, esto en caso de que se requiera un análisis ad hoc para el análisis avanzado de datos programáticos realizado fuera de DHIS2. @@ -594,15 +593,15 @@ Los metadatos del tracker que son comunes entre los tracker de prevención del V #### Análisis de propiedad { #ownership-analytics } -From DHIS2 v40, new functionality is available that allows for program indicator calculations to be made based on the ‘ownership’ org unit of a given enrollment. For example, you can count the number of unique clients that are receiving HIV prevention services at a facility even if they were not originally enrolled in care at that facility or officially transferred. +A partir de DHIS2 v40, se dispone de una nueva funcionalidad que permite realizar cálculos de indicadores de programa en función de la unidad organizativa "propietaria" de una inscripción determinada. Por ejemplo, se puede contar el número de clientes únicos que están recibiendo servicios de prevención del VIH en un establecimiento, incluso si no estaban originalmente inscritos en la atención de ese establecimiento ni hubieran sido transferidos oficialmente. Los indicadores de programa pueden definir qué **dimensión de unidad organizativa** se utilizará en el análisis. Las opciones incluyen la unidad organizativa para el evento, inscripción, registro, el elemento de datos de la unidad organizativa y la propiedad de la instancia de entidad tracker al inicio o al final del período del informe. Los análisis de propiedad se aplican solo a los indicadores de programa configurados en *función de la inscripción*. Encontrará información más detallada sobre el análisis de la propiedad en la [Guía de diseño del Tracker](https://docs.dhis2.org/en/implement/database-design/tracker-system-design/tracker-analytics.html#common-challenge-3-transfers-and-ownership). ->**Note:** +>**Nota:** > ->for implementations using DHIS2 software version 2.39 or lower, program indicators generated at any level below national will not reflect the current ‘ownership’ org unit. This means that if a TEI (person) who has been permanently transferred from one organisation unit (Health Facility A) to another (Health Facility B) for a given Tracker program enrollment *will still be counted as belonging to Health Facility A* for the purposes of program indicators. In practical terms, this means that when a patient has moved between sites, all longitudinal indicators for this patient are not re-assigned to the patient’s latest site, and remain assigned to the initial site where the patient first entered the program. This is a critical limitation for typical HIV use cases, where site level performance metrics such as lost-to-follow-up must be generated accurately at a subnational or facility level. If your implementation uses DHIS2 v2.39 or lower, please review your configuration carefully to see if you have accounted for the exclusion of persons ‘transferred out’ based on the org unit enrollment ownership. +>para implementaciones que utilicen el software DHIS2 versión 2.39 o inferior, los indicadores de programa generados en cualquier nivel por debajo del nacional no reflejarán la unidad organizativa de "propiedad" actual. Esto significa que si un TEI (persona) que ha sido transferido permanentemente de una unidad organizativa (Establecimiento de salud A) a otro (Establecimiento de salud B) para una determinada inscripción en el programa Tracker *aún se contará como perteneciente al Establecimiento de salud A* para el propósitos de los indicadores de programa. En términos prácticos, esto significa que cuando un paciente se ha movido entre sitios, todos los indicadores longitudinales para este paciente no se reasignan al último sitio del paciente y permanecen asignados al sitio inicial donde el paciente ingresó por primera vez al programa. Esta es una limitación crítica para los casos de uso típicos del VIH, donde las métricas de desempeño a nivel de sitio, como las pérdidas de seguimiento, deben generarse con precisión a nivel subnacional o de establecimiento. Si su implementación utiliza DHIS2 v2.39 o anterior, revise su configuración cuidadosamente para comprobar si ha tenido en cuenta la exclusión de personas "transferidas" en función de la propiedad de inscripción de la unidad organizativa. #### Fecha del evento vs fecha personalizada { #event-date-vs-custom-date } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__installation-md index 9c7bd744b..0e2779190 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-CASE-SURVEILLANCE__installation-md @@ -9,36 +9,36 @@ tags: Package Version 2.0.0 -System default language: English +Idioma predeterminado del sistema: Inglés ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. 3. [Configuring](#configuration) the imported metadata. 4. [Adapting](#adapting-the-tracker-program) the program after being imported -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata (No other versions of HIV Case Surveillance tracker imported previously). 3. Update existing/older version of the HIV Case Surveillance tracker. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](http://dhis2.org/documentation). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section [Importing a metadata file into DHIS2](#importing-metadata) -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension (if applicable) { #default-data-dimension-if-applicable } @@ -46,39 +46,39 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:----------------------------|:------------|:----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into , the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. **_Note that this search and replace operation must be done with a plain text editor_**, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-----------|:------------|:-------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | | Rate (factor=1)| k4RGC3sMTzO | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1`| | Per 10 000 | FWTvArgP0jt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:10000`| -| Numerator only (number) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| +| Sólo numerador (número) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-------|:------------|:-------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. Some visualizations and maps may contain references to organisation unit levels. Maps that consist of several map views may contain various Organisation unit level references based on the configuration of the map layer. Adjust the organisation unit level references in the metadata json file to match the organisation unit structure in the target instance before importing the metadata file. @@ -92,97 +92,97 @@ The process of upgrading an existing package to a newer version in a working DHI - the new objects are created; - assignment of users to relevant user groups is reviewed. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/master/en/user/html/import_export.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } > NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to conflict with. Follow the instructions to import the metadata then please proceed to the “[Configuration](#configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros A metadata package usually contains several user groups: -* HIV PREV - Access -* HIV PREV - Admin -* HIV PREV - Data capture +* VIH PREV - Acceso +* VIH PREV - Admin +* VIH PREV - Captura de datos By default, the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | HIV CS - Access | HIV CS - Admin | HIV CS - Data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/master/en/dhis2_user_manual_en/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. ## Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__DESIGN__hiv-prevention-tracker-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__DESIGN__hiv-prevention-tracker-md index 0d6194328..14ecb339a 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__DESIGN__hiv-prevention-tracker-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__DESIGN__hiv-prevention-tracker-md @@ -5,71 +5,71 @@ tags: - Implementar --- -# HIV Prevention Design {#hiv-prev-design} +# Diseño de prevención del VIH {#hiv-prev-design} ## Introducción { #introduction } -The prevention component of the **DHIS2 Toolkit for HIV** is based on the latest WHO Consolidated guidelines on person-centred HIV strategic information: strengthening routine data for impact [https://www.who.int/publications/i/item/9789240055315](https://www.who.int/publications/i/item/9789240055315) (2022) and the Digital adaptation kit for HIV: operational requirements for implementing WHO recommendations and standards within digital systems, second edition. +El componente de prevención del **kit de herramientas para el VIH de DHIS2** se basa en las últimas directrices consolidadas de la OMS sobre información estratégica del VIH centrada en la persona: fortalecimiento de los datos de rutina para generar impacto [https://www.who.int/publications/i/item/9789240055315] (https://www.who.int/publications/i/item/9789240055315) (2022) y el Kit de adaptación digital para el VIH: requisitos operativos para implementar las recomendaciones y estándares de la OMS dentro de los sistemas digitales, segunda edición. -This toolkit includes +Este kit de herramientas incluye -- WHO-recommended dashboard analyses and core indicators for monitoring HIV prevention initiatives and using key metrics to adjust programming & drive impact -- DHIS2 Tracker program aligned with the WHO Digital Adaptation Kit data standards for individual level data collection and operational person-centred monitoring at facility and community levels -- Aggregate data sets and data elements to model aggregated tracker data for performant, anonymized analytics -- Data exchange mapping for aggregating DHIS2 tracker data for prevention indicators and integration of key indicators with national HMIS +- Análisis de tableros e indicadores básicos recomendados por la OMS para monitorear las iniciativas de prevención del VIH y utilizar métricas clave para ajustar la programación e impulsar el impacto +- El programa Tracker DHIS2 está alineado con los estándares de datos del kit de adaptación digital de la OMS para la recopilación de datos a nivel individual y el monitoreo operativo centrado en la persona a nivel de establecimiento y comunidad +- Set de datos agregados y elementos de datos para el modelo de datos tracker agregados para análisis anónimos y de alto rendimiento +- Mapeo de intercambio de datos para agregar datos del Tracker DHIS2 para indicadores de prevención e integración de indicadores clave con HMIS nacional -The HIV toolkit is optimised for improving strategic information systems in countries to facilitate data-driven decision-making, as well as streamlining routine data management processes. The DHIS2 HIV prevention tracker is *not* designed to provide clinical decision-support for prevention services, but rather serves as an operational tool and a source of individual level data for person-centred monitoring. +El kit de herramientas VIH está optimizado para mejorar los sistemas de información estratégica en los países para facilitar la toma de decisiones basada en datos, así como para agilizar los procesos rutinarios de gestión de datos. El tracker de prevención del VIH DHIS2 *no* está diseñado para brindar apoyo a las decisiones clínicas para los servicios de prevención, sino que sirve como una herramienta operativa y una fuente de datos a nivel individual para el monitoreo centrado en la persona. -The system design document explains the reference configuration in DHIS2 for the HIV prevention use case, including a detailed description of DHIS2 Tracker configuration, dashboard design, use of program indicators, mapping of tracker data to the aggregate data model, and data exchange mechanisms. This document also does not consider the resources and infrastructure needed to implement such a system, such as servers, power, internet connections, backups, training and user support, which can be found in the [DHIS2 Tracker Implementation Guide](https://docs.dhis2.org/en/implement/tracker-implementation/target-audience.html). +El documento de diseño del sistema explica la configuración de referencia en DHIS2 para el caso de uso de prevención del VIH, incluida una descripción detallada de la configuración del Tracker DHIS2, el diseño del tablero, el uso de indicadores del programa, el mapeo de los datos de tracker al modelo de datos agregados y los mecanismos de intercambio de datos. Este documento tampoco considera los recursos e infraestructura necesarios para implementar dicho sistema, como servidores, energía, conexiones a Internet, respaldos, formación y soporte al usuario, los cuales pueden consultarse en la [Guía de Implementación Tracker DHIS2](https://docs.dhis2.org/en/implement/tracker-implementation/target-audience.html). Los metadatos de referencia para este kit de herramientas están disponibles en: [dhis2.org/metadata-downloads](https://dhis2.org/metadata-downloads/). ### Agradecimientos { #acknowledgements } -The HIV prevention toolkit has been developed in partnership with the WHO Global HIV Programme and the Pan American Health Organization (PAHO) with support from The Global Fund. We are grateful to WHO and PAHO for providing subject matter expertise in the design and development of these tools, as well as to the many countries who have shared their implementation experience with us. +El kit de herramientas de prevención del VIH ha sido desarrollado en colaboración con el Programa Mundial de VIH de la OMS y la Organización Panamericana de la Salud (OPS) con el apoyo del Fondo Mundial. Agradecemos a la OMS y la OPS por brindar experiencia en el diseño y desarrollo de estas herramientas, así como a los muchos países que han compartido su experiencia de implementación con nosotros. ## Descripción general del diseño del sistema { #system-design-overview } ### Antecedentes { #background } -Efforts to end the HIV epidemic by 2030 face persistent challenges, with 1.5 million new infections in 2020 alone. Key populations and their sexual partners constituted 70% of global new infections in 2021 (UNAIDS, 2022), highlighting barriers to equitable access. Paramount importance is to emphasise routine programmatic data for tracking service delivery, identifying at-risk individuals, and achieving universal access through a person-centred approach. Confidentiality and data privacy is crucial, especially for vulnerable populations that may be stigmatised, necessitating a cautious approach to individual-level data collection and anonymization for data use needs above the service delivery level. +Los esfuerzos para poner fin a la epidemia de VIH para 2030 enfrentan desafíos persistentes, con 1,5 millones de nuevas infecciones solo en 2020. Las poblaciones clave y sus parejas sexuales constituyeron el 70% de las nuevas infecciones mundiales en 2021 (ONUSIDA, 2022), lo que pone de relieve las barreras al acceso equitativo. Es de suma importancia hacer hincapié en los datos programáticos de rutina para hacer seguimiento de la prestación de servicios, identificar a las personas en riesgo y lograr el acceso universal a través de un enfoque centrado en la persona. La confidencialidad y la privacidad de los datos son cruciales, especialmente para las poblaciones vulnerables que pueden ser estigmatizadas, lo que requiere un enfoque cauteloso en la recopilación de datos a nivel individual y la anonimización para las necesidades de uso de datos por encima del nivel de prestación de servicios. -A person-centered monitoring approach offers distinct advantages for longitudinal HIV data collection that can track and record prevention services provided to an individual over time and space (e.g. different service delivery sites and touchpoints with prevention programmes). Scaling up individual level data collection allows for flexible disaggregation and enhanced analysis by various factors such as time, location, age, gender, those at elevated risk of HIV acquisition, key population, linkage to services and more. This depth of information enhances our understanding of HIV epidemiology and facilitates ongoing monitoring of trends. Implementation of case-based electronic data is anticipated to enhance data quality by minimising data entry steps, integrating automatic calculations and validations, swiftly correcting or completing inconsistent or incomplete individual records, and facilitating de-duplication. +Un enfoque de seguimiento centrado en la persona ofrece claras ventajas para la recopilación longitudinal de datos sobre el VIH que permitan seguir y registrar los servicios de prevención proporcionados a una persona a lo largo del tiempo y el espacio (por ejemplo, diferentes sitios de prestación de servicios y puntos de contacto con programas de prevención). La ampliación de la recopilación de datos a nivel individual permite un desglose flexible y un análisis mejorado en función de diversos factores, como el tiempo, ubicación, edad, género, las personas con un riesgo elevado de contraer el VIH, población clave, vinculación a los servicios y más. Esta profundidad de información mejora nuestra comprensión de la epidemiología del VIH y facilita el seguimiento continuo de las tendencias. Se prevé que la implementación de datos electrónicos basados ​​en casos mejorará la calidad de los datos al minimizar los pasos de ingreso de datos, integrar cálculos y validaciones automáticos, corregir o completar rápidamente registros individuales inconsistentes o incompletos y facilitar la deduplicación. -However, in most LMICs, the digitization of individual-level data systems managed by Ministries of Health often takes years to reach scale, and must be matched by substantial in-country resources to sustain the system over time. At the same time, implementing partners such as iNGOs and civil society also play a role in delivering HIV prevention services and may use their own digital tools for data collection and management. Furthermore, historical data and other programmatic data are often collected or represented through the aggregate data model – such as denominators based on Spectrum estimates for people living with HIV and aggregated reporting from paper-based service delivery sites with low/no connectivity, limited availability of devices and/or weak infrastructure. +Sin embargo, en la mayoría de los PIBM, la digitalización de los sistemas de datos a nivel individual administrados por los Ministerios de Salud a menudo tarda años en alcanzar a escalar y debe ir acompañada de recursos sustanciales en el país para sostener el sistema a lo largo del tiempo. Al mismo tiempo, los socios implementadores, como las ONG internacionales y la sociedad civil, también desempeñan un papel en la prestación de servicios de prevención del VIH y pueden utilizar sus propias herramientas digitales para la recopilación y gestión de datos. Además, los datos históricos y otros datos programáticos a menudo se recopilan o representan a través del modelo de datos agregados, como denominadores basados ​​en estimaciones de Spectrum para personas que viven con el VIH e informes agregados basados en papel de sitios de prestación de servicios con conectividad baja o nula, disponibilidad limitada de dispositivos y/o infraestructura deficiente. -Therefore, the HIV prevention toolkit leverages all DHIS2 applications and data models to support practical, implementable approaches to collecting, analysing and using HIV prevention data effectively to prevent HIV infections and link newly identified HIV cases into treatment programs and national HIV case surveillance systems. These tools can be used in a modular way to meet the needs of any country along the maturity model for digitization of health data – including hybrid implementation of paper-based and digitized systems, as well as incorporating data from other electronic tools like hospital EMRs where these may be used. +Por lo tanto, el kit de herramientas de prevención del VIH aprovecha todas las aplicaciones y modelos de datos de DHIS2 para respaldar enfoques prácticos y aplicables para recopilar, analizar y utilizar datos de prevención del VIH de manera efectiva para prevenir infecciones por VIH y vincular los casos de VIH recientemente identificados con programas de tratamiento y sistemas nacionales de vigilancia de casos de VIH. Estas herramientas se pueden utilizar de forma modular para satisfacer las necesidades de cualquier país a lo largo del modelo de madurez para la digitalización de datos de salud, incluida la implementación híbrida de sistemas basados en papel y digitalizados, así como la incorporación de datos de otras herramientas electrónicas como los EMR hospitalarios donde estos pueden usarse. ### Caso de uso { #use-case } -The HIV Prevention toolkit is designed to support routine data collection for programmes that support people identified as at-risk for HIV infection to enroll in a prevention program and receive HIV prevention services. The system is designed to bring data together to generate granular HIV prevention indicators and their disaggregations for routine data analysis, person-centered monitoring and strategic information through flexible dashboards and ad-hoc analysis with DHIS2 analytics tools. +El kit de herramientas de prevención del VIH está diseñado para respaldar la recopilación de datos de rutina para programas que ayudan a las personas identificadas como en riesgo de infección por el VIH a inscribirse en un programa de prevención y recibir servicios de prevención del VIH. El sistema está diseñado para reunir datos con el fin de generar indicadores granulares de prevención del VIH y sus desgloses para análisis de datos de rutina, monitoreo centrado en la persona e información estratégica a través de tableros flexibles y análisis ad hoc con herramientas de análisis DHIS2. -The data capture components of the system design allows for staff at service delivery sites, or higher levels depending on local contexts, to capture the core data elements during routine interactions with prevention programme participants that will allow HIV programme staff to generate key performance indicators as detailed in WHO’s *Consolidated guidelines for person-centred HIV strategic information* (WHO, 2022). This component uses the DHIS2 Tracker data model. While DHIS2 HIV prevention tracker program is not optimized to support clinical case management or decision support, it serves as a useful electronic registry that supports decentralised electronic data capture of HIV prevention data down to health facility or any other point of service from all types of actors. Individual level tracker data are aggregated using DHIS2 program indicators; which are mapped to aggregate data elements and data sets for populating core indicators and serving the analytical dashboards with anonymized data. +Los componentes de captura de datos del diseño del sistema permiten al personal de los sitios de prestación de servicios, o a niveles superiores dependiendo de los contextos locales, capturar los elementos de datos básicos durante las interacciones rutinarias con los participantes del programa de prevención que permitirán al personal del programa de VIH generar indicadores clave de desempeño tal como se detalla en las *Directrices consolidadas sobre información estratégica del VIH centrada en la persona* (OMS, 2022). Este componente utiliza el modelo de datos Tracker DHIS2. Si bien el programa de seguimiento de la prevención del VIH DHIS2 no está optimizado para respaldar la gestión de casos clínicos o el apoyo a la toma de decisiones, sirve como un registro electrónico útil que da soporte a la captura electrónica descentralizada de datos de prevención del VIH hasta el establecimiento de salud o cualquier otro punto de servicio procedente de todo tipo de actores. Los datos de seguimiento a nivel individual se agregan utilizando los indicadores de programa DHIS2; que se asignan a elementos de datos agregados y set de datos para completar los indicadores básicos y servir a los tableros analíticos con datos anónimos. La estructura del programa tracker DHIS2 se ha armonizado y sigue la misma lógica que el tracker de vigilancia de casos de VIH, lo que permite que una persona inscrita en un programa de prevención ingrese al programa de vigilancia de casos con un diagnóstico de VIH positivo. En algunos contextos, puede ser deseable integrar la prevención y la vigilancia de casos en un único programa de seguimiento. La armonización de los elementos de datos entre los dos trackers permitirá la adaptación e integración local, que se describe más adelante en la sección "Implementar" de este documento. #### Usuarios objetivo { #intended-users } -The HIV prevention system design focuses on meeting the needs of end users at all levels of the health system, including those responsible for implementing HIV prevention programmes in countries. These users may include: +El diseño del sistema de prevención del VIH se centra en satisfacer las necesidades de los usuarios finales en todos los niveles del sistema de salud, incluidos los responsables de implementar los programas de prevención del VIH en los países. Estos usuarios pueden incluir: -- **HIV program managers & staff (national & sub-national):** data users who are responsible for routine analysis of data, using data to improve operations and programme strategies, and providing data-driven feedback to programme staff, including implementing partners, facilities, and other service delivery points +- **Directores y personal del programa de VIH (nacional y subnacional)**: usuarios de datos que son responsables del análisis rutinario de los datos, de su utilización para mejorar las operaciones y las estrategias del programa, y ​​de proporcionar al personal del programa retroalimentación basada en datos, incluidos los socios implementadores, instalaciones y otros puntos de prestación de servicios - **Administradores de datos del programa de VIH**: usuarios responsables de supervisar la recopilación, gestión, calidad de los datos, funciones de análisis y presentación de informes para el programa nacional de VIH - **Administradores de sistemas/puntos focales de HMIS**: personal del Ministerio de Salud y/o equipo central de DHIS2 responsable de mantener y mejorar los sistemas de datos para programas de salud, integrar flujos de datos en plataformas nacionales, brindar soporte técnico para el diseño del sistema, adaptación y soporte al usuario final; y mantenimiento del sistema DHIS2 a lo largo del tiempo -- **Service delivery sites:** Staff at service delivery sites may use the DHIS2 Tracker program to record data for routine visits with prevention clients, as well as use DHIS2 tools like working lists and line-list to follow up with clients and monitor individual-level uptake of services. -- **Implementing partners**: organizations who provide technical assistance to the national HIV programme, collect and analyze data on behalf of the overall national programme strategy, and may be responsible for the operations of service delivery networks such as HIV counseling, educational outreach, community health workers. +- **Sitios de prestación de servicios:** El personal de los sitios de prestación de servicios puede utilizar el programa Tracker DHIS2 para registrar datos de visitas de rutina con clientes de prevención, así como utilizar herramientas de DHIS2 como listas de trabajo y listados para realizar un seguimiento de los clientes y monitorear la aceptación de los servicios a nivel individual. +- **Socios implementadores**: organizaciones que brindan asistencia técnica al programa nacional de VIH, recopilan y analizan datos en nombre de la estrategia general del programa nacional y pueden ser responsables de las operaciones de las redes de prestación de servicios como asesoramiento sobre VIH, difusión educativa, trabajadores de salud comunitarios. ### Estructura de diseño { #design-structure } -The DHIS2 HIV Prevention configuration is structured in three major components: +La configuración de Prevención del VIH de DHIS2 está estructurada en tres componentes principales: -- **Dashboards & Indicators:** the HIV prevention dashboards and indicators are all served by the aggregate data model in DHIS2. Prevention dashboards are shared with the HIV HMIS module. -- **Aggregate data sets:** aggregate datasets, data elements and associated category combinations are configured according to the WHO’s HIV analysis framework to populate the core indicators. Three datasets are designed to receive aggregated tracker data (e.g. via program indicators) and model this data in a performant way, leveraging the advantages of the aggregate data model in DHIS2 for analysis. Alternatively, these datasets can also be used for aggregate paper-based reporting; or to store data reported routinely from other individual-level data systems in use, such as sites using EMRs or other mobile applications. +- **Tableros e indicadores:** los tableros e indicadores de prevención del VIH se basan en el modelo de datos agregados de DHIS2. Los tableros de prevención se comparten con el módulo HMIS de VIH. +- **Sets de datos agregados**: los sets de datos agregados, elementos de datos y las combinaciones de categorías asociadas se configuran de acuerdo con el marco de análisis del VIH de la OMS para completar los indicadores básicos. Tres sets de datos están diseñados para recibir datos tracker agregados (por ejemplo, a través de indicadores de programa) y modelar estos datos de manera eficiente, aprovechando las ventajas del modelo de datos agregados en DHIS2 para el análisis. Alternativamente, estos sets de datos también se pueden utilizar para informes agregados basados en papel; o para almacenar datos reportados rutinariamente desde otros sistemas de datos a nivel individual en uso, como sitios que utilizan EMR u otras aplicaciones móviles. - Prevención VIH (mensual) - Prevención VIH (anual) - - Population estimates + - Estimaciones de población - **Programa Tracker**: se ha configurado un programa Tracker DHIS2 para la recopilación de datos longitudinales a nivel individual. El programa Tracker se puede utilizar con la web DHIS2 o con clientes Android. -These modular components are designed based on the heterogeneous nature of HIV data systems in countries and support the typical architecture for implementing case-based data systems alongside integrated national HMIS infrastructure: +Estos componentes modulares están diseñados en función de la naturaleza heterogénea de los sistemas de datos VIH en los países y respaldan la arquitectura típica para implementar sistemas de datos basados ​​en casos junto con la infraestructura nacional integrada del HMIS: ![VIH arquitectura ilustrativa](resources/images/hiv_architecture_simple.png) @@ -79,152 +79,152 @@ These modular components are designed based on the heterogeneous nature of HIV d La estructura de programa Tracker es la siguiente: -![Prevention Tracker Program Structure](resources/images/Overview_of_stage_and_sections.png) +![Estructura de programa Tracker de prevención](resources/images/Overview_of_stage_and_sections.png) | **Etapa** | **Descripción** | | ------------------- | ------------------------------------------------------------ | -| Inscripción | The enrollment stage collects the basic demographic data about a person, including unique identifiers, as Tracked Entity Attributes (TEAs). Several of these core TEAs such as Family Name and Given name are shared across DHIS2 Tracker programs. The Tracked Entity Type for the HIV Prevention program is ‘Person’. **The stage is non-repeatable.** | -| Informe de caso inicial | The stage can be filled at the same time as the enrollment of the patient.This stage contains the information related to key population groups. **The stage is non-repeatable.** | +| Inscripción | La etapa de inscripción recopila los datos demográficos básicos sobre una persona, incluidos identificadores únicos, como Atributos de Entidad Tracker (TEA). Varios de estos TEA principales, como Apellido y Nombre, se comparten entre los programas Tracker DHIS2. El tipo de entidad tracker para el programa de prevención del VIH es "Persona". **La etapa no es repetible.** | +| Informe de caso inicial | La etapa se puede llenar al mismo tiempo que el registro del paciente. Esta etapa contiene la información relacionada con los grupos de población clave. **La etapa no es repetible.** | | Visita | Escenario principal que recoge toda la información necesaria para el seguimiento del paciente y del programa. **La etapa es repetible** | -### Tipo de entidad Tracked { #tracked-entity-type } +### Tipo de entidad Tracked { #tracked-entity-type } -The DHIS2 HIV Prevention tracker program allows for the enrollment of a tracked entity type [TET] ‘person’ into the HIV prevention program. The TET type is shared with the HIV Case Surveillance tracker to allow enrollment of the same TEI in both programs, in the case that a person receiving prevention services receives a positive HIV diagnosis. +El programa tracker de prevención del VIH DHIS2 permite la inscripción de una "persona" del tipo de entidad tracker [TET] en el programa de prevención del VIH. El tipo de TET se comparte con el tracker de Vigilancia de Casos de VIH para permitir la inscripción del mismo TEI en ambos programas, en el caso de que una persona que recibe servicios de prevención reciba un diagnóstico positivo de VIH. ### Inscripción { #enrollment } -It is assumed that the HIV prevention workflow begins by enrolling any person identified at risk for HIV infection with an *unknown HIV status* or *known HIV negative status*. Persons presenting with a known HIV positive status should be enrolled into the HIV Case Surveillance Tracker program. +Se supone que el flujo de trabajo de prevención del VIH comienza con la inscripción de cualquier persona identificada en riesgo de infección por VIH con un *estado de VIH desconocido* o *un estado de VIH negativo conocido*. Las personas que presenten un estado VIH positivo conocido deben inscribirse en el programa tracker de vigilancia de casos de VIH. -When a person is enrolled in the HIV Prevention program as a Tracked Entity Instance (TEI), Tracked Entity Attributes (TEA) are recorded to form the case profile. All TEAs are aligned and harmonised with those included in the HIV Case surveillance tracker allowing for enrollment in both programs or for integration into a single tracker program if desired at the local implementation level. Note that several TEAs are shared across non-HIV DHIS2 Tracker programs; these are configured with a prefix ‘GEN’ (general) to indicate they are shared between tracker programs. Check out the [Common Metadata Library](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html) for more information on shared tracker metadata. +Cuando una persona está inscrita en el programa de prevención del VIH como instancia de entidad tracker (TEI), los atributos de entidad tracker (TEA) se registran para formar el perfil del caso. Todos los TEA están alineados y armonizados con los incluidos en el tracker de vigilancia de casos de VIH, lo que permite la inscripción en ambos programas o la integración en un único programa tracker si se desea a nivel de implementación local. Tenga en cuenta que varios TEA se comparten entre programas Tracker DHIS2 que no son VIH; estos están configurados con un prefijo 'GEN' (general) para indicar que se comparten entre programas de tracker. Consulte la [Biblioteca de metadatos comunes](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html) para obtener más información sobre los metadatos de tracker compartidos. -The TEA **program UID** attribute refers to an HIV program specific identifier. It has been kept intentionally blank as coding processes are dependent on local context. Refer to the [DHIS2 User Documentation on configuring system-wide unique identifiers as DHIS2 TEAs](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-238/configuring-the-system/programs.html#configure_tracked_entity). The use of anonymous UID codes allows individuals accessing HIV prevention services to be uniquely identified and followed longitudinally, without the collection of other types of personally identifying information (WHO, 2022). +El atributo **program UID** de TEA se refiere a un identificador específico del programa de VIH. Se ha mantenido intencionalmente en blanco ya que los procesos de codificación dependen del contexto local. Consulte la [Documentación del usuario de DHIS2 sobre la configuración de identificadores únicos en todo el sistema como TEA DHIS2](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-238/configuring-the-system/programs.html#configure_tracked_entity). El uso de códigos UID anónimos permite identificar de forma única a las personas que acceden a los servicios de prevención del VIH y realizar un seguimiento longitudinal, sin recopilar otros tipos de información de identificación personal (OMS, 2022). La **fecha de nacimiento y edad** se puede asignar de dos formas diferentes: - Fecha de nacimiento conocida: seleccione la fecha de nacimiento -- Unknown date of birth: select the Date of birth - Unknown option and then enter the age either in years or months. +- Fecha de nacimiento desconocida: seleccione la opción fecha de nacimiento -Desconocida y luego ingrese la edad en años o meses. Una vez hecho esto, se asigna una edad de nacimiento "probable" a la fecha de nacimiento en función del valor ingresado en los años o el mes TEA. -![Date of Birth](/resources/images/Data_of_birth_unknown.gif) +![Fecha de nacimiento](/resources/images/Data_of_birth_unknown.gif) ->**Note:** +>**Nota:** > ->The date of birth is configured as mandatory; it must always have a value because it is used in the calculation of all program indicators involving age groups +>La fecha de nacimiento está configurada como obligatoria; siempre debe tener un valor porque se utiliza en el cálculo de todos los indicadores del programa que involucran grupos de edad ### Etapa 1: Informe de caso inicial (no repetible) { #stage-1-initial-case-report-non-repeatable } -The data acquired at this stage pertains to the identification of clients belonging to one or multiple key population groups. We recommend implementations to refer to WHO’s 2022 *Consolidated guidelines on person-centred HIV strategic information*, and specifically sections 2.2.2 for guidance on collecting information on key populations for prevention interventions to allow for this disaggregation, further considerations in section 5.1.1, and section 6.4 on maintaining data privacy, security and confidentiality as it relates to key population data captured. +Los datos adquiridos en esta etapa se refieren a la identificación de clientes que pertenecen a uno o varios grupos de población clave. Recomendamos que las implementaciones se remitan a las *Directrices consolidadas sobre información estratégica del VIH centrada en la persona* de la OMS de 2022, y específicamente a las secciones 2.2.2 para obtener orientación sobre la recopilación de información sobre poblaciones clave para intervenciones de prevención que permitan este desglose; consideraciones adicionales en la sección 5.1.1 y la sección 6.4 sobre el mantenimiento de la privacidad, seguridad y confidencialidad de los datos en relación con los datos de poblaciones clave capturados. -Key population data is collected as a program stage in order to further protect the sensitive nature of this data. Specifically, by including this data only in the program stage, it is not accessible for searching a TEI – where users may have broader access to search for clients. +Los datos de la poblacion clave se recopilan como una etapa del programa con el fin de proteger aún más la naturaleza sensible de estos datos. Específicamente, al incluir estos datos solo en la etapa del programa, no son accesibles para buscar una TEI, donde los usuarios pueden tener un acceso más amplio para buscar clientes. -![Key Population Groups](resources/images/key_population_group.png) +![Grupos de población clave](resources/images/key_population_group.png) -In some implementations, instead of having the different key population groups listed as selectable categories, a set of questions has been proposed and according to the answer a key population identification is assigned to the clients. [See the section Implementation Considerations & Local Adaptation in this document](https://docs.google.com/document/d/1h7KBCLA99jVoTmDTBttIiSk4SKKD7tcIw7yq5A3yH68/edit#heading=h.7690t3h1dai8). +En algunas implementaciones, en lugar de tener los diferentes grupos de poblacion clave listados como categorías seleccionables, se ha propuesto un conjunto de preguntas y según la respuesta se asigna una identificación de población clave a los clientes. [Ver la sección consideraciones de implementación y adaptación local en este documento](https://docs.google.com/document/d/1h7KBCLA99jVoTmDTBttIiSk4SKKD7tcIw7yq5A3yH68/edit#heading=h.7690t3h1dai8). -For an individual enrolled in an HIV prevention program, it is possible that their association with a key population group may change over time, as an individual’s risk of HIV acquisition, participation in high risk behaviours, and HIV prevention needs vary over time. The program stage is intentionally designed as non-repeatable to allow optimized analytics based on the key population group. However, a user may revisit this stage and modify the key population groups as needed. +Para una persona inscrita en un programa de prevención del VIH, es posible que su asociación con un grupo de población clave cambie con el tiempo, ya que el riesgo de una persona de contraer el VIH, su participación en conductas de alto riesgo y sus necesidades de prevención del VIH varían con el tiempo. La etapa del programa se ha diseñado intencionalmente como no repetible para permitir un análisis optimizado basado ​​en el grupo de población clave. Sin embargo, un usuario puede volver a visitar esta etapa y modificar los grupos de población clave según sea necesario. -When using data from this program stage to derive denominators for individuals at risk or in need of HIV prevention, inclusion criteria should be considered when the data on prevention need were collected. Data collected in the past may not reflect current need for prevention interventions; information collected within the last three to six months is more likely to be pertinent (WHO, 2022). See section 2.2.5 of WHO’s 2022 *Consolidated guidelines on person-centred HIV strategic information guidelines* (WHO, 2022) for more information. +Cuando se utilizan datos de esta etapa del programa para obtener denominadores de personas en riesgo o que necesitan prevención del VIH, se deben considerar los criterios de inclusión cuando se recopilaron los datos sobre la necesidad de prevención. Es posible que los datos recopilados en el pasado no reflejen la necesidad actual de intervenciones de prevención; es más probable que la información recopilada en los últimos tres a seis meses sea pertinente (OMS, 2022). Para más información, véase 2.2.5 de las *Directrices consolidadas sobre directrices de información estratégica del VIH centradas en la persona* (OMS, 2022). ### Etapa 2: Visita [repetible] { #stage-2-visit-repeatable } #### Configuración de fechas { #configuration-of-dates } -This repeatable program stage captures all information relevant to visits/encounters for the person receiving prevention services, regardless of which type of service they access. It allows for capturing multiple types of services provided in a visit. This is integral for a comprehensive, person-centred management and reporting system. +Esta etapa repetible del programa captura toda la información relevante de las visitas/encuentros de la persona que recibe servicios de prevención, independientemente del tipo de servicio al que acceda. Permite capturar múltiples tipos de servicios prestados en una visita. Esto es fundamental para un sistema integral de gestión y presentación de informes centrado en la persona. -In this program stage, the DHIS2 program ‘event date’ (or default ‘report date’ in the Maintenance app for program configuration) has been renamed to represent ‘Visit date.’ This means that all analytics based on the event date will evaluate based on the date of the person’s encounter (visit) with the prevention service provider. +En esta etapa del programa, la 'fecha de evento' del programa DHIS2 (o 'fecha de informe' por defecto en la aplicación de Mantenimiento para la configuración del programa) ha sido renombrada para representar la 'Fecha de visita'. Esto significa que todos los análisis basados en la fecha del evento se evaluarán en función de la fecha del encuentro (visita) de la persona con el proveedor de servicios de prevención. ![Fecha de evento DHIS2](resources/images/event_date_visit_date.png) -In addition to the visit date, additional key dates have been configured as Tracker domain data elements related to these activities (e.g., HIV test date, STI test date, etc.) and these should be reported to enable additional time-based analytics. +Además de la fecha de la visita, se han configurado fechas clave adicionales como elementos de datos del dominio Tracker relacionados con estas actividades (por ejemplo, fecha de la prueba de VIH, fecha de la prueba de ITS, etc.) y estas deben informarse para permitir análisis adicionales basados ​​en el tiempo. #### Detalles de la visita { #visit-details } -The initial Visit Details section allows the user to select which prevention services will be recorded for this visit report. A series of program rules will show/hide the desired sections depending on which type of prevention details will be recorded. It is generally assumed that the user will create a new Event in the Visit stage for each time they interact with a service provider, regardless of how many prevention services they access during the visit. +La sección inicial de Detalles de la visita permite al usuario seleccionar qué servicios de prevención se registrarán para este informe de visita. Una serie de reglas de programa mostrarán/ocultarán las secciones deseadas en función del tipo de detalles de prevención que se registrarán. Generalmente se asume que el usuario creará un nuevo Evento en la etapa Visita cada vez que interactúe con un proveedor de servicios, independientemente de a cuántos servicios de prevención acceda durante la visita. -The data element representing VMMC services will only show for persons enrolled with TEA ‘Sex assigned at birth’ as ‘Male’ or ‘Other’, based on program rules. +El elemento de datos que representa los servicios de CMMV solo se mostrará para las personas inscritas en TEA "Sexo asignado al nacer" como "Masculino" u "Otro", según las reglas del programa. -![Select prevention activities for the visit](resources/images/visit_sections_selections.gif) +![Seleccionar actividades de prevención para la visita](resources/images/visit_sections_selections.gif) >**Nota:** > >Ocultar una sección no borra los datos que allí están registrados y todos los indicadores del programa NO se filtran por la selección o no de la sección. En caso de que exista algún dato que se haya introducido por error, será necesario eliminarlo manualmente uno a uno y no simplemente quitando la sección. -#### Risk assessment { #risk-assessment } +#### Evaluación de riesgos { #risk-assessment } -The risk assessment section contains a set of questions designed to ascertain whether the client is at elevated risk for HIV acquisition. If any of these questions are answered with a "Yes," the TEI will be classified as ‘at elevated risk for HIV acquisition’. The questions within the risk assessment section constitute one component utilised to evaluate the existence of elevated risk. The comprehensive list of metadata employed in defining those at elevated risk can be found here. +La sección de evaluación de riesgos contiene una serie de preguntas diseñadas para determinar si el cliente tiene un riesgo elevado de contraer el VIH. Si alguna de estas preguntas se responde con un "Sí", el TEI se clasificará como "con riesgo elevado de contraer el VIH". Las preguntas dentro de la sección de evaluación de riesgos constituyen un componente utilizado para evaluar la existencia de un riesgo elevado. La lista completa de metadatos empleados para definir a las personas con riesgo elevado se puede encontrar aquí. -![Risk Assessment](resources/images/risk_assessment.png) +![Evaluación de riesgos](resources/images/risk_assessment.png) -These questions are one example of establishing an individual’s risk of acquiring HIV following an HIV-negative test (see Box 2.3 within WHO SI 2022 guidelines) in order to prioritize follow-up through appropriate prevention services. It is expected that the risk assessment section may be adapted to country context. Since an individual’s risk of HIV acquisition and HIV prevention needs vary over time, it is important to record the date that any information on risk differentiation was collected and to consider this when assessing an individual’s likely current prevention needs. When deriving indicator denominators for individuals at risk or in need of HIV prevention, inclusion criteria should consider when the data on prevention need were collected. The WHO guidelines note that data collected in the past may not reflect *current* need for prevention interventions; whereas information collected within the last three to six months is more likely to be pertinent. Therefore, is is most appropriate to include this section in a repeatable program stage where an individual’s risk can be re-assessed over time. +Estas preguntas son un ejemplo de cómo establecer el riesgo de que una persona contraiga el VIH después de una prueba de VIH negativa (véase el recuadro 2.3 de las directrices SI de la OMS 2022) con el fin de priorizar el seguimiento a través de servicios de prevención adecuados. Se espera que la sección de evaluación de riesgos pueda adaptarse al contexto del país. Dado que el riesgo de una persona de contraer el VIH y las necesidades de prevención del VIH varían con el tiempo, es importante registrar la fecha en que se recopiló cualquier información sobre la diferenciación de riesgos y considerarla al evaluar las probables necesidades de prevención actuales de una persona. Al derivar denominadores de indicadores para personas en riesgo o que necesitan prevención del VIH, los criterios de inclusión deben considerar cuándo se recopilaron los datos sobre la necesidad de prevención. Las directrices de la OMS señalan que los datos recopilados en el pasado pueden no reflejar la necesidad *actual* de intervenciones de prevención; mientras que la información recopilada en los últimos tres a seis meses tiene más probabilidades de ser pertinente. Por lo tanto, lo más apropiado es incluir esta sección en una etapa de programa repetible donde el riesgo de un individuo pueda reevaluarse con el tiempo. -#### Condoms { #condoms } +#### Condones { #condoms } -This section contains key information related to the type and quantity of condoms distributed to individuals enrolled in prevention programs. Note that due to its inclusion within a Tracker program targeting a cohort of individuals enrolling in prevention services, this section does *not* inherently account for condoms distributed through other channels, such as campaigns or private sector commodity distribution points. It is assumed here that the date of condom distribution is the same as the ‘Visit Date’ (DHIS2 event date). +Esta sección contiene información clave relacionada con el tipo y la cantidad de condones distribuidos a personas inscritas en programas de prevención. Tenga en cuenta que, debido a su inclusión dentro de un programa Tracker dirigido a una cohorte de personas inscritas en servicios de prevención, esta sección *no* incluye de forma inherente los condones distribuidos a través de otros canales, como campañas o puntos de distribución de productos del sector privado. Se asume aquí que la fecha de distribución del condón es la misma que la "Fecha de visita" (fecha del evento DHIS2). -![Condom Distribution](resources/images/condoms.png) +![Distribución de condones](resources/images/condoms.png) -#### HIV test { #hiv-test } +#### Prueba de VIH { #hiv-test } -In this section, all information regarding HIV testing with details required for disaggregation of HIV testing service indicators are included. +En esta sección se incluye toda la información sobre las pruebas de VIH con los detalles necesarios para la desagregación de los indicadores del servicio de pruebas de VIH. -Note that a positive HIV test result does not necessarily confirm an HIV case during real-world country implementation; each country may use their own algorithms for confirming an HIV case based on one or more test results. This section may be adapted to capture additional information on the number, type and sequencing of HIV tests provided. Please also ensure that program indicator definitions are updated according to country context for confirming an HIV positive case that was enrolled in the HIV prevention program. +Tenga en cuenta que un resultado positivo de la prueba del VIH no necesariamente confirma un caso de VIH durante la implementación en el país en el mundo real; cada país puede utilizar sus propios algoritmos para confirmar un caso de VIH basándose en uno o más resultados de pruebas. Esta sección puede adaptarse para capturar información adicional sobre la cantidad, el tipo y la secuencia de las pruebas de VIH proporcionadas. Asegúrese también de que las definiciones de los indicadores de programa se actualicen de acuerdo con el contexto del país para confirmar un caso VIH positivo que se inscribió en el programa de prevención del VIH. -![HIV_testing_services](resources/images/HIV_testing_prevention.png) +![Servicio_de pruebas_de VIH](resources/images/HIV_testing_prevention.png) #### PrEP { #prep } -Within the PrEP (HIV Pre-exposure Prophylaxis) section, information related to PrEP usage, adverse effects and the delivery/administration of PrEP are requested. +Dentro de la sección PrEP (Profilaxis previa a la exposición al VIH), se solicita información relacionada con el uso de PrEP, los efectos adversos y la entrega/administración de PrEP. -The option sets assigned to the Data Element **Specify adverse effect** have been kept generic, l as these options are intended to be configured within the context of the implementation. These will need to be customised prior to implementation. +El set de opciones asignado al elemento de datos **Especificar efecto adverso** se ha mantenido genérico, ya que estas opciones deben configurarse dentro del contexto de la implementación. Estos deberán personalizarse antes de su implementación. -![Placeholder option set for adverse events](resources/images/specify_adverse_effect_config.png) +![Marcador set de opciones para eventos adversos](resources/images/specify_adverse_effect_config.png) #### PEP { #pep } -Within the PEP (Post Exposure Prophylaxis) section, basic information related to initiation of post-exposure prophylaxis and the HIV exposure type are requested. It is expected that PEP follow-up visits are recorded during repeated events. Program rules have been configured to calculate and assign the next scheduled PEP visit 28 days following the initiation of PEP, in accordance with the WHO recommendations. This is represented by the ‘due date’ in DHIS2 tracker. +Dentro del apartado PEP (profilaxis posterior a la exposición) se solicita información básica relacionada con el inicio de la profilaxis posterior a la exposición y el tipo de exposición al VIH. Se espera que las visitas de seguimiento de PEP se registren durante eventos repetidos. Las reglas del programa se han configurado para calcular y asignar la próxima visita de PEP programada 28 días después del inicio de la PEP, de acuerdo con las recomendaciones de la OMS. Esto está representado por la "fecha de vencimiento" en el tracker DHIS2. -![Schedule next PEP visit date](resources/images/HIV_PEP_schedule_date.png) +![Programar la fecha de próxima visita PEP](resources/images/HIV_PEP_schedule_date.png) -#### NSP { #nsp } +#### PAJ { #nsp } -Within the Needle-Syringe Program (NSP) section, basic information on access to NSP services and needle-syringes received by the client are requested +Dentro de la sección Programa Aguja-Jeringa (PAJ) se solicita información básica sobre el acceso a los servicios del PAJ y las agujas-jeringa recibidas por el cliente -![NSP data collection](resources/images/NSP.png) +![Recopilación de datos PAJ](resources/images/NSP.png) -#### OAMT { #oamt } +#### TMAO { #oamt } -Within the Opioid Agonist Maintenance Treatment (OAMT) section, information related to the status of the OAMT treatment, doses administered, maintenance doses and multiple dose dispensing are collected. +Dentro de la sección tratamiento de mantenimiento con agonistas opioides (TMAO), se recopila información relacionada con el estado del tratamiento con TMAO, las dosis administradas, las dosis de mantenimiento y la dispensación de múltiples dosis. -![OAMT data collection](resources/images/OAMT.png) +![Recopilación de datos TMAO](resources/images/OAMT.png) -#### VMMC { #vmmc } +#### CMMV { #vmmc } -In the Voluntary Medical Male Circumcision (VMMC) section, information related to the procedure performed and any adverse event experienced are collected. +En la sección Circuncisión Médica Masculina Voluntaria (CMMV), se recoge información relacionada con el procedimiento realizado y cualquier evento adverso experimentado. -The data element **VMMC** in the Visit details section is visible only for the TEI that has selected “Male” or “Other” option in the TEA **Sex assigned at birth.** +El elemento de datos **CMMV** en la sección detalles de la visita es visible solo para la TEI que ha seleccionado la opción “Masculino” u “Otro” en la TEA **Sexo asignado al nacer.** -![VMMC Data Collection](resources/images/VMMC.png) +![Recopilación de datos CMMV](resources/images/VMMC.png) #### ITS { #sti } -In the Sexually Transmitted Infections (STI) section, information related to the STI syndrome diagnosed, STI test performed and treatment administered are collected among clients enrolled in the HIV prevention program. +En la sección de Infecciones de Transmisión Sexual (ITS), se recoge información relacionada con el síndrome de ITS diagnosticado, la prueba de ITS realizada y el tratamiento administrado entre los clientes inscritos en el programa de prevención del VIH. -![STI Data Collection](resources/images/STI.png) +![Recopilación de datos ITS](resources/images/STI.png) #### Hepatitis viral { #viral-hepatitis } -In the Viral hepatitis section, information related to HBsAG and HCV tests performed and test results are collected among clients enrolled in the HIV prevention program. +En la sección Hepatitis viral, se recoge información relacionada con las pruebas AGsHB y VHC realizadas y los resultados de las pruebas entre los clientes inscritos en el programa de prevención del VIH. ![Hepatitis viral](resources/images/viral_hepatitis.png) ### Elemento de datos Tracker { #tracker-data-elements } -All data elements configured for the Tracker domain are also included in the Data Element Group ‘HIV prevention (tracker)’ [Mx8yzdlahth]. This serves as a de facto DHIS2 data dictionary for the HIV prevention tracker use case. It allows for the data elements to be exported from DHIS2 and used independently of the Tracker program configuration, for example in the case that an implementation redesigns their Tracker from scratch for local workflows and still wants to maintain compliance with the core WHO-recommended data dictionary included in the Digital Adaptation Kit. +Todos los elementos de datos configurados para el dominio Tracker también se incluyen en el grupo de elementos de datos "Prevención del VIH (tracker)" [Mx8yzdlahth]. Esto sirve como un diccionario de datos DHIS2 de facto para el caso de uso del seguimiento de prevención del VIH. Permite exportar los elementos de datos desde DHIS2 y utilizarlos independientemente de la configuración del programa Tracker, por ejemplo, en el caso de que una implementación rediseñe su Tracker desde cero para los flujos de trabajo locales y aún quiera mantener el cumplimiento con el diccionario de datos básico recomendado por la OMS incluido en el Kit de Adaptación Digital. #### Elementos de datos clonados para la selección de opciones múltiples { #cloned-data-elements-for-multiple-option-selection } -Within the repeatable program stagefor ‘Visits’, there are a number of data elements that are cloned to allow the selection of multiple options for a given concept, sharing the same option set. This design is implemented as follows: +Dentro de la etapa del programa repetible para "Visitas", hay una serie de elementos de datos que se clonan para permitir la selección de múltiples opciones para un concepto determinado, compartiendo el mismo conjunto de opciones. Este diseño se implementa de la siguiente manera: - Clonación de elementos de datos elegibles para elección de opciones múltiples - El número de clones del elemento de datos debe ser el mismo que el número de opciones presentes en el set de opciones relacionado @@ -233,112 +233,112 @@ Within the repeatable program stagefor ‘Visits’, there are a number of data - Ocultar los elementos de datos consecuentes si los anteriores no han sido seleccionados - Mostrar error en caso de que la misma Opción haya sido seleccionada más de una vez en el mismo grupo de Elementos de Datos -For example, to capture multiple STI syndromes diagnosed, there are a series of data elements that are cloned to represent each discrete diagnosis: +Por ejemplo, para capturar múltiples síndromes de ITS diagnosticados, hay una serie de elementos de datos que se clonan para representar cada diagnóstico discreto: -- HIV - STI syndrome diagnosed - 1 [HSzzcPJpA6I] -- HIV - STI syndrome diagnosed - 2 [D4IIo7OwOXb] -- HIV - STI syndrome diagnosed - 3 [c1e15eg6ddB] -- HIV - STI syndrome diagnosed - 4 [BE7dAhKw3bl] +- VIH - Síndrome de ITS diagnosticado - 1 [HSzzcPJpA6I] +- VIH - Síndrome de ITS diagnosticado - 2 [D4IIo7OwOXb] +- VIH - Síndrome de ITS diagnosticado - 3 [c1e15eg6ddB] +- VIH - Síndrome de ITS diagnosticado - 4 [BE7dAhKw3bl] #### Elementos de datos ocultos y valores asignados a elementos de datos { #hidden-data-elements-assigned-values-to-data-elements } -All the Data Elements mentioned hereunder are “hidden” and therefore not visible during the data entry process; however they are required for the calculation of program indicators. +Todos los elementos de datos mencionados a continuación están "ocultos" y, por lo tanto, no son visibles durante el proceso de ingreso de datos; sin embargo, son necesarios para el cálculo de los indicadores de programa. -Here we provide an overview of all the “hidden” data elements which are contained in the repeatable Visit stage, where program rules are used to assign a value. In many cases, the program rule simply assigns a value from a previous program stage (such as Initial Report) in order to allow the program indicators to calculate correctly. +Aquí proporcionamos una descripción general de todos los elementos de datos "ocultos" que están contenidos en la etapa Visita repetible, donde las reglas de programa son utilizadas para asignar un valor. En muchos casos, la regla del programa simplemente asigna un valor de una etapa de programa previa (como el Informe inicial) para permitir que los indicadores del programa se calculen correctamente. -**Assigning key population data element value to Visit Stage** +**Asignación del valor del elemento de datos de población clave a la etapa de visita** -Program rules are used to copy and assign the value of the TEI’s key population group recorded in the initial case report to a hidden data element field on the repeatable ‘Visit’ program stage. This allows for all calculations and disaggregations based on key population group to be configured namely by using the autoassigned data element as a filter in the program indicator. +Las reglas del programa se utilizan para copiar y asignar el valor del grupo de población clave de TEI registrado en el informe de caso inicial a un campo de elemento de datos oculto en la etapa de programa "Visita" repetible. Esto permite configurar todos los cálculos y desgloses basados ​​en grupo de población clave, es decir, utilizando el elemento de datos autoasignado como filtro en el indicador del programa. -These Data Elements are identified with the postfix “- VISIT” and are the ones used for all program indicators that filter by a key population group: +Estos elementos de datos se identifican con el sufijo “- VISITA” y son los que se utilizan para todos los indicadores del programa que filtran por grupo de población clave: -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | -------------------------------------------------------- | -| Elemento de datos | OF0nynhdcwZ | HIV - Key population - Injection drug user - VISIT | -| Elemento de datos | qYfitZEUOAb | HIV - Key population - Men who have sex with men - VISIT | -| Elemento de datos | Eu3UmwQ1EUO | HIV - Key population - Prisoner - VISIT | -| Elemento de datos | KM0Zn4zYUwa | HIV - Key population - Sex worker - VISIT | -| Elemento de datos | A57Hv80XrzD | HIV - Key population - Transgender - VISIT | -| Regla de programa | em8GjAu2wZY | HIV - Assign true value to Injection drug user | -| Regla de programa | NIL9zQMI3bS | HIV - Assign true value to Men who have sex with men | -| Regla de programa | iIvwL5mWU7s | HIV - Assign true value to Prisoner | -| Regla de programa | TFF0E0N9MrO | HIV - Assign true value to Sex worker | -| Regla de programa | ZzdKaWHJiZp | HIV - Assign true value to Transgender | -| Regla de programa | JQU9DwfMlxt | HIV - Assign false value to Injection drug user | -| Regla de programa | nQk50JoDdpg | HIV - Assign false value to Men who have sex with men | -| Regla de programa | hmrzByEYkOz | HIV - Assign false value to Prisoner | -| Regla de programa | Ac3UWsrP943 | HIV - Assign false value to Sex worker | -| Regla de programa | O9WsIRxxS4Y | HIV - Assign false value to Transgender | - -**Calculating & Assigning Substantial Risk** - -The denominators for several WHO SI coverage indicators should count all the clients that have tested HIV negative and that are considered at elevated risk for HIV acquisition. To be able to identify the clients at elevated risk for HIV acquisition, a Data Element populated by a Program Rule has been created. - -The following Data Elements are assigned values based on a series Program Rules which embed the logic above from the WHO guideline: - -| **Metadata** | **UID** | **Nombre** | +| Elemento de datos | OF0nynhdcwZ | VIH - Población clave - Consumidor de drogas inyectables - VISITA | +| Elemento de datos | qYfitZEUOAb | VIH - Población clave - Hombres que tienen relaciones sexuales con hombres - VISITA | +| Elemento de datos | Eu3UmwQ1EUO | VIH - Población clave - Prisionero - VISITA | +| Elemento de datos | KM0Zn4zYUwa | VIH - Población clave - Trabajador sexual - VISITA | +| Elemento de datos | A57Hv80XrzD | VIH - Población clave - Transgénero - VISITA | +| Regla de programa | em8GjAu2wZY | VIH - Asignar valor verdadero a consumidor de drogas inyectables | +| Regla de programa | NIL9zQMI3bS | VIH - Asignar valor verdadero a los hombres que tienen relaciones sexuales con hombres | +| Regla de programa | iIvwL5mWU7s | VIH - Asignar valor verdadero a prisionero | +| Regla de programa | TFF0E0N9MrO | VIH - Asignar valor verdadero a trabajador sexual | +| Regla de programa | ZzdKaWHJiZp | VIH - Asignar valor verdadero a Transgénero | +| Regla de programa | JQU9DwfMlxt | VIH - Asignar valor falso a consumidor de drogas inyectables | +| Regla de programa | nQk50JoDdpg | VIH - Asignar valor falso a los hombres que tienen relaciones sexuales con hombres | +| Regla de programa | hmrzByEYkOz | VIH - Asignar valor falso a prisionero | +| Regla de programa | Ac3UWsrP943 | VIH - Asignar valor falso a trabajador sexual | +| Regla de programa | O9WsIRxxS4Y | VIH - Asignar valor falso a Transgénero | + +**Cálculo y asignación del riesgo sustancial** + +Los denominadores de varios indicadores de cobertura del SI de la OMS deben contar a todos los clientes que han dado resultados negativos en la prueba del VIH y que se consideran en riesgo elevado de contraer el VIH. Para poder identificar a los clientes con riesgo elevado de contraer el VIH, se ha creado un elemento de datos rellenado por una regla de programa. + +A los siguientes elementos de datos se les asignan valores basados en una serie de reglas de programa que incorporan la lógica anterior de la directriz de la OMS: + +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ------------------------------------------------------------ | -| Elemento de datos | oB4grCEIFR1 | HIV - Substantial risk | -| Elemento de datos | E0nHuSKo5W7 | HIV - Substantial risk date | -| Regla de programa | k7yGfQKHtkI | HIV - Assign substantial risk if fulfill the requirements | -| Regla de programa | Sohs3L2e0Pp | HIV - NO assign substantial risk if not fulfill the requirements | -| Regla de programa | w57icNuGhrO | HIV - If substantial risk already present in previous visit, assign it to the following ones | -| Regla de programa | yvoEj9R5mq3 | HIV - Assign date of substantial risk when become positive | -| Regla de programa | GJr1NJjm7OD | HIV - NO assign date of substantial risk if not positive | -| Regla de programa | oxzemvnhyo4 | HIV - If date of substantial risk already present in previous visit, assign it to the following ones | +| Elemento de datos | oB4grCEIFR1 | VIH - Riesgo sustancial | +| Elemento de datos | E0nHuSKo5W7 | VIH - Fecha de riesgo sustancial | +| Regla de programa | k7yGfQKHtkI | VIH - Asignar riesgo sustancial si se cumplen los requisitos | +| Regla de programa | Sohs3L2e0Pp | VIH - NO asignar riesgo sustancial si no se cumplen los requisitos | +| Regla de programa | w57icNuGhrO | VIH - Si el riesgo sustancial ya está presente en la visita anterior, asígnelo a las siguientes | +| Regla de programa | yvoEj9R5mq3 | VIH - Asignar fecha de riesgo sustancial cuando se vuelve positivo | +| Regla de programa | GJr1NJjm7OD | VIH - NO asignar fecha de riesgo sustancial si no es positivo | +| Regla de programa | oxzemvnhyo4 | VIH - Si la fecha de riesgo sustancial ya está presente en la visita anterior, asígnela a las siguientes | -**PRV.6 PEP completion** +**PRV.6 Finalización de la PEP** -The denominator counts all the clients that are due to finish their course of PEP. To be able to allow this calculation, a Data Element which contains the assigned value of the date of expected PEP completion is used; +El denominador cuenta a todos los clientes que deben terminar su curso de PEP. Para poder permitir este cálculo, se utiliza un Elemento de Datos que contiene el valor asignado de la fecha de finalización esperada del PEP; -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ---------------------------- | -| Elemento de datos | P9mYEN2N9wB | HIV - PEP: Due date | -| Regla de programa | CEswruYRK1D | HIV - Assign date of due PEP | +| Elemento de datos | P9mYEN2N9wB | VIH - PEP: Fecha de vencimiento | +| Regla de programa | CEswruYRK1D | VIH - Asignar fecha de vencimiento de PEP | -**PRV.7 HIV in PEP recipients** +**PRV.7 VIH en receptores de PEP** -The numerator is a program indicator of type EVENT in which we count the number of clients that have received a positive HIV result within the three months after the last PEP initiation. +El numerador es un indicador de programa de tipo EVENTO en el que contamos el número de clientes que han recibido un resultado positivo de VIH dentro de los tres meses posteriores al último inicio de PEP. -To be able to allow this calculation a Data Element is assigned a value for last date of PEP initiation through a series of program rules: +Para poder permitir este cálculo se asigna a un Elemento de Datos un valor para la última fecha de inicio del PEP a través de una serie de reglas de programa: -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ------------------------------------------------------------ | -| Elemento de datos | ju1A4XKItfG | HIV - PEP: Last PEP initiation date | -| Regla de programa | XLJZnf8NAc3 | HIV - Assign the PEP initiation date if is assigned | -| Regla de programa | rxXSdsALs5Q | HIV - Assign PEP last initiation date only if has value and if there is no new initiation date | +| Elemento de datos | ju1A4XKItfG | VIH - PEP: Última fecha de inicio de PEP | +| Regla de programa | XLJZnf8NAc3 | VIH - Asignar la fecha de inicio de PEP si está asignada | +| Regla de programa | rxXSdsALs5Q | VIH - Asignar la última fecha de inicio de PEP solo si tiene valor y si no hay nueva fecha de inicio | -**PRV.9 Regular NSP (Needle-Syringe Programme) access** +**PRV.9 Acceso regular al PAJ (Programa aguja-jeringa)** -The numerator is a program indicator of type EVENT in which we count the number of clients regularly accessing (within 30 days from a visit to another one) an NSP service. +El numerador es un indicador de programa de tipo EVENTO en el que contamos el número de clientes que acceden regularmente (dentro de los 30 días de una visita a otra) a un servicio PAJ. -To be able to identify the clients that are to be considered as regular NSP clients, a Data Element of type BOOLEAN has been created. This element will be populated with a true answer if the difference on the date between the current visit and the last one is less than 30 days. This allows for program indicators to count only the TEIs with a True data value a regular NSP access. +Para poder identificar los clientes que van a ser considerados clientes PAJ habituales se ha creado un Elemento de Datos de tipo BOOLEAN. Este elemento se completará con una respuesta verdadera si la diferencia en la fecha entre la visita actual y la última es inferior a 30 días. Esto permite que los indicadores del programa cuenten solo los TEIs con un valor de datos verdadero en un acceso PAJ regular. -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ------------------------------------------------------------ | -| Elemento de datos | wuzgcIPtyzn | HIV - NSP: Regular access | -| Regla de programa | QnbEfRbLhNf | HIV - Assign true value to regular NSP if last NSP visit happened in less than 30 days | -| Regla de programa | gul8LxgrJBo | HIV - Assign false value to regular NSP if last NSP visit happened in more than 30 days | +| Elemento de datos | wuzgcIPtyzn | VIH - PAJ: Acceso regular | +| Regla de programa | QnbEfRbLhNf | VIH - Asignar valor verdadero al PAJ regular si la última visita al PAJ ocurrió en menos de 30 días | +| Regla de programa | gul8LxgrJBo | VIH - Asignar un valor falso al PAJ regular si la última visita al PAJ ocurrió en más de 30 días | -**PRV. 13 OAMT minimum duration** +**PRV. 13 Duración mínima de TMAO** -The numerator should count the “Number of people in the cohort retained in OAMT for at least six months”. In order to calculate this in DHIS2, a Data Element value is assigned based on program rules to provide the sum of the days in which the client has been (without interruption) in OAMT. +El numerador debe contar el “Número de personas de la cohorte retenidas en la TMAO durante al menos seis meses”. Para calcular esto en DHIS2, se asigna un valor de Elemento de Datos basado en reglas del programa para proporcionar la suma de los días en los que el cliente ha estado (sin interrupción) en TMAO. -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ------------------------------------------------------------ | -| Elemento de datos | z2hpmQAUMrX | HIV - OAMT: Retained on OAMT from last visit | -| Elemento de datos | LADmjz85wZx | HIV - OAMT: Days since start that has be retained | -| Elemento de datos | YL74GURXFMz | HIV - OAMT: Cumulative days | -| Elemento de datos | vJ53ZrxOuox | HIV - OAMT: Last day with OAMT | -| Regla de programa | WSCAWO1ubIE | HIV - Assign true value to retained on OAMT if the clients has been covered with OAMT untill the current visit | -| Regla de programa | Al2clr4leFf | HIV - Assign days between the two administrations of OAMT | -| Regla de programa | lSrYHJE0NN5 | HIV - Assign the date of last day with OAMT | +| Elemento de datos | z2hpmQAUMrX | VIH - TMAO: Retenido en TMAO desde la última visita | +| Elemento de datos | LADmjz85wZx | VIH - TMAO: Días desde el inicio que se ha retenido | +| Elemento de datos | YL74GURXFMz | VIH - TMAO: Días acumulados | +| Elemento de datos | vJ53ZrxOuox | VIH - TMAO: Último día con TMAO | +| Regla de programa | WSCAWO1ubIE | VIH - Asignar valor verdadero a retenido en TMAO si los clientes han estado cubiertos con TMAO hasta la visita actual | +| Regla de programa | Al2clr4leFf | VIH - Asignar días entre las dos administraciones de TMAO | +| Regla de programa | lSrYHJE0NN5 | VIH - Asignar la fecha del último día con TMAO | -**STI. 8 Repeat diagnosis of STI syndrome** +**ITS.8 Repetición del diagnóstico del síndrome de ITS** -In the numerator we need to calculate the number of people attending HIV prevention services diagnosed with a particular STI syndrome two or more times. Data elements assigned with the last date in which a specific STI syndrome was reported are used in the PI filter to compare the date of the last diagnosis with the actual diagnosis; if the difference is lower than 12 months then our client will be counted. This is achieved with five (5) DEs assigned with “last diagnosis date” for each possible STI syndrome diagnosed. +En el numerador necesitamos calcular el número de personas que asisten a los servicios de prevención del VIH diagnosticadas con un síndrome de ITS concreto dos o más veces. Los elementos de datos asignados con la última fecha en la que se informó un síndrome de ITS específico se utilizan en el filtro IP para comparar la fecha del último diagnóstico con el diagnóstico real; si la diferencia es inferior a 12 meses, se contará como nuestro cliente. Esto se logra con cinco (5) ED asignados con “fecha del último diagnóstico” para cada posible síndrome de ITS diagnosticado. -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ------------------------------------------------------------ | | Elemento de datos | DI8O2sFAjIZ | VIH - ITS: Fecha del último diagnóstico del síndrome de secreción uretral | | Elemento de datos | PMYnHPcLOrg | VIH - ITS: Fecha del último diagnóstico del síndrome de flujo vaginal | @@ -356,105 +356,105 @@ In the numerator we need to calculate the number of people attending HIV prevent | Regla de programa | OeNAKcHY0lt | VIH - Asignar la última fecha de secreción anorrectal si se diagnostica | | Regla de programa | C1XGpyBdVQ3 | VIH - Asignar fecha previa de secreción anorrectal si no hay nuevo diagnóstico | -**HTS. 7 HTS linkage to prevention** +**SPV. 7 SPV vinculación con la prevención** -In the denominator, only the clients HIV negative deemed at elevated risk for HIV acquisition should be counted (see substantial risk classification above) and it refers to all clients tested for HIV in the last 12 months. +En el denominador, solo se deben contar los clientes VIH negativos considerados en riesgo elevado de contraer el VIH (consulte la clasificación de riesgo sustancial más arriba) y se refiere a todos los clientes que se hicieron la prueba del VIH en los últimos 12 meses. -In the numerator, we must count all clients that have received any HIV prevention activities within seven days from the HIV negative test result. The days of receiving any HIV prevention activity is considered as the visit date (EVENT_DATE). To be able to allow this calculation, a Data Element is assigned the value of the date of the last HIV test. +En el numerador, debemos contar todos los clientes que han recibido alguna actividad de prevención del VIH dentro de los siete días posteriores al resultado negativo de la prueba del VIH. Los días de recepción de cualquier actividad de prevención del VIH se consideran como fecha de visita (EVENT_DATE). Para poder realizar este cálculo, se le asigna a un Elemento de Datos el valor de la fecha de la última prueba de VIH. -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ------------------------------------------------------ | -| Elemento de datos | LhZ48Bjj6RD | HIV - HIV test: Date of last HIV test | -| Regla de programa | bCWATvG0UAw | HIV - Assign previous last date of HIV test if present | -| Regla de programa | vHiVERMQaGX | HIV - Assign previous date of HIV test if present | +| Elemento de datos | LhZ48Bjj6RD | VIH - Prueba de VIH: Fecha de la última prueba de VIH | +| Regla de programa | bCWATvG0UAw | VIH - Asignar última fecha anterior de la prueba de VIH si está presente | +| Regla de programa | vHiVERMQaGX | VIH - Asignar fecha anterior de la prueba de VIH si está presente | -**HTS. 8 HIV retesting coverage** +**SPV. 8 Cobertura de repetición de pruebas del VIH** -In the denominator, only the clients HIV negative and deemed at elevated risk for HIV acquisition should be counted (see substantial risk classification above) and it refers to all clients tested in the last 12 months. +En el denominador, solo se deben contar los clientes VIH negativos y considerados en riesgo elevado de contraer el VIH (consulte la clasificación de riesgo sustancial más arriba) y se refiere a todos los clientes que se hicieron la prueba en los últimos 12 meses. -In the numerator, we want to count all clients that have received another HIV test (independently from the result) within 12 months from the HIV negative test result. To be able to allow this calculation a Data Element is assigned the value of the date of the last HIV test using the following program rules: +En el numerador, queremos contar todos los clientes que han recibido otra prueba de VIH (independientemente del resultado) dentro de los 12 meses posteriores al resultado negativo de la prueba de VIH. Para poder realizar este cálculo se le asigna a un Elemento de Datos el valor de la fecha de la última prueba de VIH utilizando las siguientes reglas de programa: -| **Metadata** | **UID** | **Nombre** | +| **Metadatos** | **UID** | **Nombre** | | ------------ | ----------- | ------------------------------------------------------ | -| Elemento de datos | LhZ48Bjj6RD | HIV - HIV test: Date of last HIV test | -| Regla de programa | bCWATvG0UAw | HIV - Assign previous last date of HIV test if present | -| Regla de programa | vHiVERMQaGX | HIV - Assign previous date of HIV test if present | +| Elemento de datos | LhZ48Bjj6RD | VIH - Prueba de VIH: Fecha de la última prueba de VIH | +| Regla de programa | bCWATvG0UAw | VIH - Asignar última fecha anterior de la prueba de VIH si está presente | +| Regla de programa | vHiVERMQaGX | VIH - Asignar fecha anterior de la prueba de VIH si está presente | ### Indicadores de programa { #program-indicators } -**Program indicators** are used to aggregate individual-level data captured in the tracker data model; and map these to the aggregate data model for presentation, consumption and use in the DHIS2 analytics apps and dashboards. The use of the DHIS2 Data Exchange App for transferring program indicator values to aggregate data elements is described further in the section on Metadata Mapping & Data Exchange. +Los **indicadores del programa** se utilizan para agregar datos a nivel individual capturados en el modelo de datos del tracker; y asignarlos al modelo de datos agregados para su presentación, consumo y uso en las aplicaciones y tableros de análisis de DHIS2. El uso de la aplicación Data Exchange DHIS2 para transferir valores de los indicadores de programa a elementos de datos agregados se describe con más detalle en la sección sobre mapeo de metadatos e intercambio de datos. -Program indicators are organized into two program indicator groups: +Los indicadores de programa se organizan en dos grupos de indicadores de programa: -- ‘HIV Prevention - Data Exchange’ [C2IoD2V2uwS] contains all PIs that are mapped to a corresponding target aggregate data elements for analysis. -- ‘HIV Prevention - WHO standard list’ [anCMZxE3c77] contains all PIs that are part of the WHO standard list of indicators (each PI typically represents a numerator or denominator from the SI guidelines standard list) +- ‘Prevención del VIH - Intercambio de datos’ [C2IoD2V2uwS] contiene todos los IP que están asignados a los elementos de datos agregados de destino correspondientes para su análisis. +- *Prevención del VIH - lista estándar de la OMS* [anCMZxE3c77] contiene todos los IP que forman parte de la lista estándar de indicadores de la OMS (cada IP normalmente representa un numerador o denominador de la lista estándar de las directrices SI) ->**Warning** +>**Advertencia** > ->The majority of Program indicators are EVENT-based and use CUSTOM period boundaries requiring some adaptation. We have provided accurate representations of the program indicators based on the generic data model; however, It is the responsibility of the implementing organization to decide what type of organisation unit dimension to assign to each program indicator, according to national guidelines and in consultation with end users. Please review the section on local adaptation and implementation considerations for more information on how to adjust program indicators and calculations during localization and country adaptation. +>La mayoría de los indicadores del Programa se basan en EVENTOS y utilizan límites de períodos PERSONALIZADOS que requieren cierta adaptación. Hemos proporcionado representaciones precisas de los indicadores del programa basadas en el modelo de datos genérico; sin embargo, es responsabilidad de la organización implementadora decidir qué tipo de dimensión de unidad organizativa asignar a cada indicador de programa, de acuerdo con las directrices nacionales y en consulta con los usuarios finales. Revise la sección sobre adaptación local y consideraciones de implementación para obtener más información sobre cómo ajustar los indicadores de programa y cálculos durante la localización y la adaptación del país. #### Filtro de población clave en indicadores de programa{ #key-population-filter-in-program-indicators } -As described in the section on Hidden Data Elements & Assigned Values, program rules are used to assign and copy the TEI’s key population group recorded in the initial case report to a hidden data element field on the repeatable Visit program stage. This allows for all program indicator calculations based on key population group to be configured, namely by using the auto-assigned data element as a filter in the program indicator. +Como se describe en la sección sobre elementos de datos ocultos y valores asignados, las reglas del programa se utilizan para asignar y copiar el grupo de población clave de la TEI registrado en el informe de caso inicial a un campo de elemento de datos ocultos en la etapa de programa visita repetible. Esto permite configurar todos los cálculos de indicadores de programa basados ​​en el grupo de población clave, concretamente utilizando el elemento de datos asignado automáticamente como filtro en el indicador de programa. -Note that in adjusting program indicators that filter based on Key Population group, you must use the set of data elements containing the postfix “- VISIT”. +Tenga en cuenta que al ajustar los indicadores de programa que filtran en función del grupo de población clave, debe utilizar el conjunto de elementos de datos que contienen el sufijo “- VISITA”. -- HIV - Key population - Injection drug user - VISIT [OF0nynhdcwZ] -- HIV - Key population - Men who have sex with men - VISIT [qYfitZEUOAb] -- HIV - Key population - Prisoner - VISIT [Eu3UmwQ1EUO] -- HIV - Key population - Sex worker - VISIT [KM0Zn4zYUwa] -- HIV - Key population - Transgender - VISIT [A57Hv80XrzD] +- VIH - Población clave - Consumidor de drogas inyectables - VISITA [OF0nynhdcwZ] +- VIH - Población clave - Hombres que tienen relaciones sexuales con hombres - VISITA [qYfitZEUOAb] +- VIH - Población clave - Prisionero - VISITA [Eu3UmwQ1EUO] +- VIH - Población clave - Trabajador sexual - VISITA [KM0Zn4zYUwa] +- VIH - Población clave - Transgénero - VISITA [A57Hv80XrzD] -#### Coverage denominators for substantial risk population { #coverage-denominators-for-substantial-risk-population } +#### Denominadores de cobertura para población de riesgo sustancial { #coverage-denominators-for-substantial-risk-population } -Several coverage indicators from WHO HIV SI guidelines require a denominator that represents all clients with a negative HIV test result that are considered at elevated risk for HIV acquisition. +Varios indicadores de cobertura de las directrices VIH SI de la OMS requieren un denominador que represente a todos los clientes con un resultado negativo en la prueba del VIH que se consideran en riesgo elevado de contraer el VIH. -- PRV.3 PrEP coverage -- HTS.7 HTS linkage to prevention -- HTS.8 HIV retesting coverage denominators +- PRV.3 Cobertura PrEP +- SPV.7 SPV vinculación con la prevención +- SPV.8 Denominadores de cobertura de repetición de pruebas del VIH -Calculating a client’s eligibility for categorization of substantial risk is based on the WHO’s SI guideline. These data on HIV prevention demand can be used to derive denominators for a range of indicators examining the population of individuals accessing services (see section 2.4 of WHO, 2022). +El cálculo de la elegibilidad de un cliente para la categorización de riesgo sustancial se basa en la directriz SI de la OMS. Estos datos sobre la demanda de prevención del VIH se pueden utilizar para obtener denominadores para una variedad de indicadores que examinan la población de personas que acceden a los servicios (véase sección 2.4 de OMS, 2022). -![WHO guideline on for indicating substantial risk](resources/images/substantial_risk.png) +![Directriz de la OMS para indicar un riesgo sustancial](resources/images/substantial_risk.png) -The following program indicators are calculated to provide denominators for the relevant coverage WHO indicators. +Los siguientes indicadores de programa se calculan para proporcionar denominadores para los indicadores de cobertura pertinentes de la OMS. -| UID | DHIS2 Name | +| UID | Nombre DHIS2 | | ----------- | ------------------------------------------------------------ | -| pbkiUBVI6jk | HIV PREV - HIV negative clients with substantial risk | -| GCFreP95zUO | HIV PREV - Clients with substantial risk retested within 12 months after receiving a negative HIV test result, monthly | -| PLsp1dpY7jp | HIV PREV - HIV negative clients with substantial risk (last 12 months), monthly | -| aaRiVYd3Nqg | HIV PREV - Clients with substantial risk retested after receiving a negative HIV test result, yearly | +| pbkiUBVI6jk | VIH PREV - Clientes VIH negativos con riesgo sustancial | +| GCFreP95zUO | VIH PREV - Clientes con riesgo sustancial repiten la prueba dentro de los 12 meses posteriores a recibir un resultado negativo de la prueba del VIH, mensual | +| PLsp1dpY7jp | VIH PREV - Clientes VIH negativos con riesgo sustancial (últimos 12 meses), mensual | +| aaRiVYd3Nqg | VIH PREV - Clientes con riesgo sustancial repiten la prueba después de recibir un resultado negativo de la prueba del VIH, anual | -#### Notable program indicator configuration { #notable-program-indicator-configuration } +#### Configuración de indicadores de programas notables { #notable-program-indicator-configuration } -**PRV.6 PEP completion** +**PRV.6 Finalización de la PEP** -The denominator is a program indicator of type EVENT in which we need to count all the clients that are due to finish their course of PEP, based on the assigned DE value ‘HIV - PEP: Due date’ [P9mYEN2N9wB]. +El denominador es un indicador de programa de tipo EVENTO en el que necesitamos contar todos los clientes que deben finalizar su curso de PEP, en función del valor ED asignado 'VIH - PEP: Fecha de vencimiento' [P9mYEN2N9wB]. -**PRV.7 HIV in PEP recipients** +**PRV.7 VIH en receptores de PEP** -The numerator is a program indicator of type EVENT in which we count the number of clients that have received a positive HIV result within the three months after the last PEP initiation, based on the assigned DE value for ‘HIV - PEP: Last PEP initiation date’ [ju1A4XKItfG]. +El numerador es un indicador de programa de tipo EVENTO en el que contamos el número de clientes que han recibido un resultado positivo de VIH dentro de los tres meses posteriores al último inicio de PEP, basado en el valor ED asignado para 'VIH - PEP: Última fecha de inicio de PEP' [ju1A4XKItfG]. -**PRV.9 Regular NSP (Needle-Syringe Programme) access** +**PRV.9 Acceso regular al PAJ (Programa aguja-jeringa)** -The numerator is a program indicator of type EVENT in which we count the number of clients regularly accessing (within 30 days from a visit to another one) an NSP service. The numerator is based on the assigned value of the Boolean (Y/N) data element ‘HIV - NSP: Regular access’ [wuzgcIPtyzn], which captures the number of events where days between the current visit and previous visit is less than 30 days. +El numerador es un indicador de programa de tipo EVENTO en el que contamos el número de clientes que acceden regularmente (dentro de los 30 días de una visita a otra) a un servicio PAJ. El numerador se basa en el valor asignado del elemento de datos booleano (S/N) 'VIH - PAJ: Acceso regular' [wuzgcIPtyzn], que captura el número de eventos en los que los días entre la visita actual y la visita anterior son inferiores a 30 días. -**PRV.11 OAMT(Opioid agonist maintenance treatment) coverage** +**PRV.11 Cobertura TMAO(Tratamiento de mantenimiento con agonistas opioides)** -The WHO indicator definition states that the indicator reports the “Proportion of opioid dependent people receiving OAMT at a specific date”. The “specific date” used in the calculation of the numerator is ;therefore the information that this indicator will provide will be up to today. +La definición del indicador de la OMS establece que el indicador informa la "proporción de personas dependientes de opioides que reciben TMAO en una fecha específica". La “fecha específica” es utilizada en el cálculo del numerador; por lo que la información que proporcionará este indicador será hasta el día de hoy. -A client is considered as an opioid dependent person if they have been clinically assessed as being opioid dependent or if they are in OAMT. +Un cliente se considera persona dependiente de opioides si ha sido evaluado clínicamente como dependiente de opioides o si está en TMAO. -**PRV.13 OAMT minimum duration** +**PRV.13 Duración mínimal de TMAO** -The denominator definition states that the program indicator should count the “Number of people starting OAMT during defined cohort recruitment period”. The “cohort recruitment period” has been set-up as the “last 12 months” for both denominator and numerator (see more on period boundaries in the section on **Implementation Considerations & Local Adaptation**) +La definición del denominador establece que el indicador de programa debe contar el "Número de personas que inician TMAO durante el período de reclutamiento de cohorte definido". El “período de reclutamiento de cohorte” se ha establecido como los “últimos 12 meses” tanto para el denominador como para el numerador (véase más información sobre los límites del período en la sección sobre **Consideraciones de implementación y adaptación local**) -The numerator states that the program indicator should count the “Number of people in the cohort retained in OAMT for at least six months”. This is configured as a count of ENROLLMENTS, where the assigned value to the hidden data element ‘HIV - OAMT: Cumulative days’ [YL74GURXFMz] is greater than or equal to 180/ +El numerador establece que el indicador de programa debe contar el “Número de personas de la cohorte retenidas en TMAO durante al menos seis meses”. Esto se configura como un conteo de INSCRIPCIONES, donde el valor asignado al elemento de datos oculto ‘VIH - TMAO: Días acumulados’ [YL74GURXFMz] es mayor o igual a 180/ -**STI.8** **Repeat diagnosis of STI syndrom**e +**ITS.8** **Repetición del diagnóstico del síndrome de ITS** -The reporting period of the indicator has been set-up as the “last 12 months” therefore the output will be the proportion of clients diagnosed with a particular STI syndrome two or more times within the last 12 months. +El período de informe del indicador se ha establecido como los “últimos 12 meses”, por lo que el resultado será la proporción de clientes diagnosticados con un síndrome de ITS en concreto dos o más veces en los últimos 12 meses. En el numerador necesitamos calcular el número de personas que asisten a los servicios de prevención del VIH diagnosticadas con un síndrome de ITS concreto dos o más veces. Este filtro se basa en los elementos de datos ocultos asignados con valores para la "fecha del último diagnóstico": @@ -466,70 +466,70 @@ En el numerador necesitamos calcular el número de personas que asisten a los se En caso de que sea necesario agregar/eliminar algún síndrome de ITS según las necesidades de implementación, el modelo de datos debe replicarse para diagnósticos adicionales de ITS; o eliminarse de los cálculos de IP para los diagnósticos de ITS que no son relevantes. -**HTS. 7 HTS linkage to prevention** +**SPV. 7 SPV vinculación con la prevención** -In the denominator, only the clients HIV negative deemed at elevated risk for HIV acquisition should be counted (see substantial risk classification) and it refers to all clients tested for HIV in the last 12 months. +En el denominador, solo se deben contar los clientes VIH negativos considerados en riesgo elevado de contraer el VIH (consulte la clasificación de riesgo sustancial) y se refiere a todos los clientes que se hicieron la prueba del VIH en los últimos 12 meses. -In the numerator we count all clients that have received any HIV prevention activities within seven days from the HIV negative test result. The days of receiving any HIV prevention activity is considered as the visit date (EVENT_DATE). The program indicator uses the assigned valyue of the Data Element ‘HIV - HIV test: Date of last HIV test’ [LhZ48Bjj6RD]. +En el numerador contamos todos los clientes que han recibido alguna actividad de prevención del VIH dentro de los siete días posteriores al resultado negativo de la prueba del VIH. Los días de recepción de cualquier actividad de prevención del VIH se consideran como fecha de visita (EVENT_DATE). El indicador de programa utiliza el valor asignado del Elemento de Datos 'VIH - Prueba de VIH: Fecha de la última prueba de VIH' [LhZ48Bjj6RD]. -**HTS. 8 HIV retesting coverage** +**SPV. 8 Cobertura de repetición de pruebas del VIH** -In the denominator, only the clients HIV negative and deemed at elevated risk for HIV acquisition should be counted (see substantial risk classification) and it refers to all clients tested in the last 12 months. +En el denominador, solo se deben contar los clientes VIH negativos y considerados en riesgo elevado de contraer el VIH (consulte la clasificación de riesgo sustancial) y se refiere a todos los clientes que se hicieron la prueba en los últimos 12 meses. -In the numerator we are counting all clients that have received another HIV test (independently from the result) within 12 months from the HIV negative test result. This program indicator uses the calculated value of the data element ‘HIV - HIV test: Date of last HIV test’ [LhZ48Bjj6RD]. +En el numerador contamos todos los clientes que han recibido otra prueba de VIH (independientemente del resultado) dentro de los 12 meses posteriores al resultado negativo de la prueba de VIH. Este indicador de programa utiliza el valor calculado del elemento de datos "VIH - Prueba de VIH: Fecha de la última prueba de VIH" [LhZ48Bjj6RD]. ## Mapeo de metadatos e intercambio de datos { #metadata-mapping-data-exchange } -As described above, all the dashboards and indicators are supported by an aggregate data model. This allows for mixed methods of reporting from various electronic and paper-based sources, enabling all data to be brought together for the purpose of analysis and use such as in an integrated HMIS. +Como se ha descrito anteriormente, todos los tableros e indicadores están respaldados por un modelo de datos agregados. Esto permite métodos mixtos de generación de informes de diversas fuentes electrónicas y en papel, lo que permite reunir todos los datos con fines de análisis y uso, como en un HMIS integrado. -Where target aggregate data elements can be populated by aggregating the underlying Tracker data from the HIV Prevention tracker, we have pre-configured a set of program indicators and included the mapping of the target aggregate dimensions (data element UID and Category Option Combination UID). +Donde los elementos de datos agregados objetivo se pueden completar agregando los datos de seguimiento subyacentes del Tracker de Prevención del VIH, hemos preconfigurado un conjunto de indicadores del programa e incluido el mapeo de las dimensiones agregadas objetivo (UID del elemento de datos y UID de combinación de opciones de categoría). -See [DHIS2 User documentation on how to use the Data Exchange App](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-240/exchanging-data/data-exchange.html). +Véase [Documentación para el usuario DHIS2 sobre cómo utilizar la aplicación Data Exchange](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-240/exchanging-data/data-exchange.html) Véase [Documentación para desarrolladores de DHIS2 sobre las API de DHIS2 para el intercambio de datos agregados](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-240/data-exchange.html?h=aggregate+data+exchange+2.40#create-aggregate-data-exchange) para obtener más información. -Los metadatos se han alineado con los diccionarios de datos y las referencias de indicadores publicados en el kit de adaptación digital (DAK) para el VIH de la OMS, segunda edición (véase el Anexo A de la Web del kit de adaptación digital para el diccionario de datos). Tenga en cuenta que el Tracker no está diseñado para respaldar todos los aspectos de las directrices de atención clínica y la gestión de casos, algunos de los cuales están contenidos en el VIH DAK, ni para reemplazar los EMR sólidos de los establecimientos; sin embargo, los datos de los EMR se pueden incorporar al registro nacional del VIH para su análisis y uso. +Los metadatos se han alineado con los diccionarios de datos y las referencias de indicadores publicados en el kit de adaptación digital (DAK) para el VIH de la OMS, segunda edición (véase el Anexo A de la Web del kit de adaptación digital para el diccionario de datos). Tenga en cuenta que el Tracker no está diseñado para respaldar todos los aspectos de las directrices de atención clínica y la gestión de casos, algunos de los cuales están contenidos en el DAK VIH, ni para reemplazar los EMR sólidos de los establecimientos; sin embargo, los datos de los EMR se pueden incorporar al registro nacional del VIH para su análisis y uso. -You can find a detailed mapping between the DHIS2 metadata and the HIV DAK data dictionary in [this resource file](resources/files/Data_Exchange_mapping.xlsx) +Puede encontrar un mapeo detallado entre los metadatos de DHIS2 y el diccionario de datos del DAK VIH en [este archivo de recursos](resources/files/Data_Exchange_mapping.xlsx) ## Grupos de Usuarios { #user-groups } | Grupo de usuarios | Metadatos | Datos | |-----------------------|-------------------|----------------------| -| HIV PREV - Admin | Puede editar y visualizar | No Access | -| HIV PREV - Access | Solo lectura | Solo lectura | -| HIV PREV - Data capture | Solo lectura | Puede capturar y visualizar | +| VIH PREV - Admin | Puede editar y visualizar | Sin acceso | +| VIH PREV - Acceso | Solo lectura | Solo lectura | +| VIH PREV - Captura de datos | Solo lectura | Puede capturar y visualizar | ## Consideraciones de implementación y adaptación local { #implementation-considerations-local-adaptation } -This chapter describes some of the possibilities for adapting the configuration for local context and needs, as well as implementation considerations that are important for the HIV prevention use case. +Este capítulo describe algunas de las posibilidades para adaptar la configuración al contexto y las necesidades locales, así como consideraciones de implementación que son importantes para el caso de uso de la prevención del VIH. ### Privacidad y confidencialidad de los datos { #data-privacy-confidentiality } -Collecting data on key populations poses certain challenges, particularly when information is linked or shared across service providers and programmes. All individual-level health data, including those of key populations, must be classified as sensitive personal data, or personally identifiable information, that require a high standard of safety and security. All health information systems must have robust data security and confidentiality protocols in place to safeguard data, supported by laws and policies that protect health information. The processing of personal health data must address cybersecurity, trust building, accountability and governance, ethics, equity, capacity building and digital literacy. +La recopilación de datos sobre poblaciones clave plantea ciertos desafíos, particularmente cuando la información está vinculada o compartida entre proveedores de servicios y programas. Todos los datos de salud a nivel individual, incluidos los de poblaciones clave, deben clasificarse como datos personales sensibles o información de identificación personal que requieren un alto nivel de seguridad. Todos los sistemas de información de salud deben contar con protocolos sólidos de confidencialidad y seguridad de datos para salvaguardar los datos, respaldados por leyes y políticas que protejan la información de salud. El procesamiento de datos personales de salud debe abordar la ciberseguridad, el fomento de la confianza, la rendición de cuentas y la gobernanza, la ética, la equidad, el desarrollo de capacidades y la alfabetización digital. -Where safety and the potential to discourage access to services are a concern, the routine collection of key population information is not advised; and should be removed from the digitized DHIS2 Prevention Tracker Program. Similarly, before capturing personally identifiable data such as client name, birth date and other indirectly identifiable data, a risk assessment and security review of the electronic systems and SOPs for all users must be reviewed and gaps addressed. +Cuando la seguridad y la posibilidad de desalentar el acceso a los servicios sean una preocupación, no se recomienda la recopilación rutinaria de información sobre la población clave; y debe eliminarse del Programa tracker de prevención DHIS2 digitalizado. De manera similar, antes de capturar datos de identificación personal, como el nombre del cliente, la fecha de nacimiento y otros datos de identificación indirecta, se debe revisar una evaluación de riesgos y de seguridad de los sistemas electrónicos y los POE para todos los usuarios y abordar las deficiencias. ### Adaptación de la estructura del tracker { #tracker-structure-adaptation } -The HIV Prevention tracker structure is mostly a flat structure with only one main repeatable stage to record activities for any type of prevention visit. This intentionally simplified structure allows for increased flexibility for local adaptation and customization. For example: +La estructura del seguimiento de prevención del VIH es principalmente una estructura plana con una sola etapa principal repetible para registrar las actividades de cualquier tipo de visita de prevención. Esta estructura intencionalmente simplificada permite una mayor flexibilidad para la adaptación y personalización local. Por ejemplo: -- Sections can be easily translated in stages in case different user have to entered different information (as detailed previously the HIV Prevention service are very transversal and can have several actors involved on the distribution of the services) +- Las secciones se pueden traducir fácilmente en etapas en caso de que distintos usuarios tengan que ingresar información diferente (como se ha detallado anteriormente, el servicio de Prevención del VIH es muy transversal y puede tener varios actores involucrados en la distribución de los servicios) - Cantidad reducida de reglas de programa y bien identificadas por la sección a la que se dirige -- If a specific activity (prevention intervention, such as VMMC) is not relevant to your country’s package of HIV Prevention services offered, you can simply remove an entire sections without repercussions on the rest of the data model. +- Si una actividad específica (intervención de prevención, como CMMV) no es relevante para el paquete de servicios de prevención del VIH que ofrece su país, simplemente puede eliminar secciones enteras sin repercusiones en el resto del modelo de datos. #### Integración de la vigilancia de casos de VIH y del tracker de prevención del VIH { #integration-of-hiv-case-surveillance-and-hiv-prevention-tracker } -Depending on local context, some implementations may wish to integrate prevention and case surveillance into a single DHIS2 Tracker Program. An integrated tracker design option was considered for the global design guide, but ultimately discarded in favor of two Tracker programs for the following reasons: +Dependiendo del contexto local, algunas implementaciones pueden desear integrar la prevención y la vigilancia de casos en un único Programa Tracker DHIS2. Se consideró una opción de diseño de tracker integrado para la guía de diseño global, pero finalmente se descartó en favor de dos programas de tracker por las siguientes razones: -1. Scale: the number of persons (TEIs) enrolled in a prevention program is likely to be much, much greater than the number of persons (TEIs) diagnosed as positive and enrolled in a Case Surveillance program. This may have an impact on performance and also requires adequate server infrastructure for large-scale Tracker deployment. -2. Types of service providers: in many country contexts, a large scale and variety of service providers may be engaged in HIV prevention services, such as community health workers, NGOs/CSOs as implementing partners, etc. Often these prevention service providers are not responsible for following up the HIV case through lifelong treatment and should not have access to the client’s health data after being identified as an HIV positive client. Therefore, separating the Tracker programs suits the variety and helps to ensure protection & data confidentiality of people living with HIV. +1. Escala: es probable que el número de personas (TEIs) inscritas en un programa de prevención sea mucho, mucho mayor que el número de personas (TEIs) diagnosticadas como positivas e inscritas en un programa de Vigilancia de Casos. Esto puede tener un impacto en el rendimiento y también requiere una infraestructura de servidor adecuada para la implementación de Tracker a gran escala. +2. Tipos de proveedores de servicios: en muchos contextos nacionales, una gran escala y variedad de proveedores de servicios pueden participar en los servicios de prevención del VIH, como trabajadores comunitarios de salud, ONG/OSC como socios implementadores, etc. A menudo, estos proveedores de servicios de prevención no son responsables de dar seguimiento al caso de VIH a través de un tratamiento de por vida y no deben tener acceso a los datos de salud del cliente después de haber sido identificado como un cliente VIH positivo. Por lo tanto, separar los programas Tracker se adapta a la variedad y ayuda a garantizar la protección y la confidencialidad de los datos de las personas que viven con el VIH. 3. Los indicadores incluidos en las directrices SI y DAK de la OMS no requieren un análisis “entre programas”; todos los indicadores pueden generarse dentro de DHIS2 utilizando dos programas separados. -4. A typical workflow from prevention services to HIV case surveillance is well supported by closing the enrollment in a DHIS2 prevention tracker program and opening a new enrollment in the case surveillance program. The person (TEI) is linked to both Prevention and Case Surveillance programs in case ad hoc analysis will be required for advanced programmatic data analysis conducted outside of DHIS2. +4. Un flujo de trabajo típico desde los servicios de prevención hasta la vigilancia de casos de VIH está bien respaldado al cerrar la inscripción en un programa de tracker de prevención DHIS2 y abrir una nueva inscripción en el programa de vigilancia de casos. La persona (TEI) está vinculada a los programas de prevención y vigilancia de casos, esto en caso de que se requiera un análisis ad hoc para el análisis avanzado de datos programáticos realizado fuera de DHIS2. -An integrated design can be implemented leveraging many of the existing DHIS2 metadata, such as the Tracker data element library. Both Tracker programs follow a similar structure with initial case report and integrated, repeatable ‘visit’ stage for all follow-up thereafter. +Se puede implementar un diseño integrado aprovechando muchos de los metadatos DHIS2 existentes, como la biblioteca de elementos de datos Tracker. Ambos programas Tracker siguen una estructura similar con un informe inicial del caso y una etapa de "visita" integrada y repetible para todo el seguimiento posterior. -Tracker metadata that are common between the HIV prevention and HIV case surveillance trackers are shared between the two programs (using the same UIDs) as follows: +Los metadatos del tracker que son comunes entre los tracker de prevención del VIH y vigilancia de casos de VIH se comparten entre los dos programas (utilizando los mismos UID) de la siguiente manera: - Todos los atributos de la entidad tracker: todos los TEA son iguales - Informe de caso inicial: los elementos de datos relacionados con la identificación de la población clave son los mismos @@ -539,21 +539,21 @@ Tracker metadata that are common between the HIV prevention and HIV case surveil Los implementadores deben tener en cuenta los problemas de privacidad y confidencialidad relacionados con la vinculación de los datos de los pacientes desde un tracker de Prevención a un tracker de Vigilancia de Casos. Es posible que sea necesario eliminar algunos elementos de datos que contienen información confidencial del paciente, como el estado de la población clave de un paciente, si se vincula un registro de paciente. Además, no se recomendaría vincular los trackers de prevención y vigilancia de casos si no se pudiera garantizar la privacidad, la seguridad y la confidencialidad del paciente (para obtener más información, consulte el Capítulo 2: Prevención y el Capítulo 6: Datos de salud digital de la OMS 2022 "Directrices consolidadas sobre información estratégica del VIH centrada en la persona"). -![Structure for an integrated Prevention/Case Surveillance Tracker Program](resources/images/integrated_prev_cs_structure.jpg) +![Estructura para una prevención integrada/Programa de seguimiento de vigilancia de casos](resources/images/integrated_prev_cs_structure.jpg) ### Análisis y cálculo de indicadores { #analytics-indicator-calculations } #### Análisis de propiedad { #ownership-analytics } -From DHIS2 v40, new functionality is available that allows for program indicator calculations to be made based on the ‘ownership’ org unit of a given enrollment. For example, you can count the number of unique clients that are receiving HIV prevention services at a facility even if they were not originally enrolled in care at that facility or officially transferred. +A partir de DHIS2 v40, se dispone de una nueva funcionalidad que permite realizar cálculos de indicadores de programa en función de la unidad organizativa "propietaria" de una inscripción determinada. Por ejemplo, se puede contar el número de clientes únicos que están recibiendo servicios de prevención del VIH en un establecimiento, incluso si no estaban originalmente inscritos en la atención de ese establecimiento ni hubieran sido transferidos oficialmente. Los indicadores de programa pueden definir qué **dimensión de unidad organizativa** se utilizará en el análisis. Las opciones incluyen la unidad organizativa para el evento, inscripción, registro, el elemento de datos de la unidad organizativa y la propiedad de la instancia de entidad tracker al inicio o al final del período del informe. Los análisis de propiedad se aplican solo a los indicadores de programa configurados en *función de la inscripción*. Encontrará información más detallada sobre el análisis de la propiedad en la [Guía de diseño del Tracker](https://docs.dhis2.org/en/implement/database-design/tracker-system-design/tracker-analytics.html#common-challenge-3-transfers-and-ownership). ->**Note:** +>**Nota:** > ->for implementations using DHIS2 software version 2.39 or lower, program indicators generated at any level below national will not reflect the current ‘ownership’ org unit. This means that if a TEI (person) who has been permanently transferred from one organisation unit (Health Facility A) to another (Health Facility B) for a given Tracker program enrollment *will still be counted as belonging to Health Facility A* for the purposes of program indicators. In practical terms, this means that when a patient has moved between sites, all longitudinal indicators for this patient are not re-assigned to the patient’s latest site, and remain assigned to the initial site where the patient first entered the program. This is a critical limitation for typical HIV use cases, where site level performance metrics such as lost-to-follow-up must be generated accurately at a subnational or facility level. If your implementation uses DHIS2 v2.39 or lower, please review your configuration carefully to see if you have accounted for the exclusion of persons ‘transferred out’ based on the org unit enrollment ownership. +>para implementaciones que utilicen el software DHIS2 versión 2.39 o inferior, los indicadores de programa generados en cualquier nivel por debajo del nacional no reflejarán la unidad organizativa de "propiedad" actual. Esto significa que si un TEI (persona) que ha sido transferido permanentemente de una unidad organizativa (Establecimiento de salud A) a otro (Establecimiento de salud B) para una determinada inscripción en el programa Tracker *aún se contará como perteneciente al Establecimiento de salud A* para el propósitos de los indicadores de programa. En términos prácticos, esto significa que cuando un paciente se ha movido entre sitios, todos los indicadores longitudinales para este paciente no se reasignan al último sitio del paciente y permanecen asignados al sitio inicial donde el paciente ingresó por primera vez al programa. Esta es una limitación crítica para los casos de uso típicos del VIH, donde las métricas de desempeño a nivel de sitio, como las pérdidas de seguimiento, deben generarse con precisión a nivel subnacional o de establecimiento. Si su implementación utiliza DHIS2 v2.39 o anterior, revise su configuración cuidadosamente para comprobar si ha tenido en cuenta la exclusión de personas "transferidas" en función de la propiedad de inscripción de la unidad organizativa. #### Fecha del evento vs fecha personalizada { #event-date-vs-custom-date } @@ -563,9 +563,9 @@ La gran mayoría de Indicadores de Programa utilizan esta fecha en los límites #### Análisis de datos Tracker { #tracker-data-analysis } -For authorized users with access to personally identifiable data captured through the HIV Prevention tracker program, additional ad hoc analysis of tracker data can be achieved using the Line-list app and configuring working lists as part of the DHIS2 tracker program (note: only for users that have access to the Capture app for data collection). +Para los usuarios autorizados con acceso a datos de identificación personal capturados a través del programa de tracker de Prevención del VIH, se puede lograr un análisis ad hoc adicional de los datos del tracker utilizando la aplicación Listados y configurando listas de trabajo como parte del programa de seguimiento DHIS2 (nota: solo para usuarios que tienen acceso a la aplicación Capturar para la recopilación de datos). -In general, it is recommended to serve routine analytics for program monitoring through the aggregate data model, using program indicators and data exchange services, as implemented in this design. In part, this is because the aggregate data model in DHIS2 provides optimised dimensionality for analysis (e.g. the ability to slice and filter by Categories & CatCombos in Data Visualizer app). This also allows for more performant analytics, as running queries on large databases containing years worth of individual data can create unnecessary stress on the server. +En general, se recomienda generar análisis de rutina para el seguimiento de programas a través del modelo de datos agregados, utilizando indicadores del programa y servicios de intercambio de datos, como se implementa en este diseño. En parte, esto se debe a que el modelo de datos agregados en DHIS2 proporciona una dimensionalidad optimizada para el análisis (por ejemplo, la capacidad de dividir y filtrar por Categorías y Combinación de Categorias en la aplicación Visualizador de Datos). Esto también permite realizar análisis de mayor rendimiento, ya que ejecutar consultas en grandes bases de datos que contienen años de datos individuales puede generar una tensión innecesaria en el servidor. Los análisis ad hoc y la extracción a nivel individual suelen estar restringidos únicamente a los usuarios autorizados de salud pública (como los administradores de datos del programa de VIH) para análisis avanzados; y a los usuarios en el punto de prestación de servicios (establecimiento) para realizar actividades de seguimiento operativo, contactar clientes o realizar análisis y controles de calidad de datos de rutina básicos en los datos a nivel individual que son responsables de recopilar. @@ -581,11 +581,11 @@ Según los datos recopilados del cuestionario, el cliente puede ser identificado ![La OPS interpreta las respuestas para monitoreo y análisis de datos](resources/images/PAHO_key_pop_answers.png) -### Condom distribution { #condom-distribution } +### Distribución de condones { #condom-distribution } -Opportunistic condom distribution including distribution campaigns are common interventions in many countries and this type of information can be largely under reported due to its extension. In addition, condom distribution can occur through many outlets such as private non-health care related settings like groceries and bodegas which are unlikely to report into MOH data systems. +La distribución oportunista de condones, incluidas las campañas de distribución, son intervenciones comunes en muchos países y este tipo de información puede no reportarse en gran medida debido a su extensión. Además, la distribución de condones puede realizarse a través de muchos puntos de venta, como entornos privados no relacionados con la atención médica, como tiendas de comestibles y bodegas, que es poco probable que informen a los sistemas de datos del Ministerio de Salud. -Several implementations have decided to remove this section from the Tracker program and record aggregated numbers for condom distribution. The only WHO indicator requesting information on condoms distributed is PRV.1 *Condoms distributed* which requires three disaggregations that are easily implementable in an aggregate data model. +Varias implementaciones han decidido eliminar esta sección del programa Tracker y registrar números agregados para la distribución de condones. El único indicador de la OMS que solicita información sobre condones distribuidos es PRV.1 *Condones distribuidos*, que requiere tres desgloses que son fácilmente implementables en un modelo de datos agregados. ## Referencias { #references } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__installation-md index 25cb38038..5f1ebddd4 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__HIV__HIV-PREVENTION__installation-md @@ -9,36 +9,36 @@ tags: Package Version 1.0.0 -System default language: English +Idioma predeterminado del sistema: Inglés ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. 3. [Configuring](#configuration) the imported metadata. 4. [Adapting](#adapting-the-tracker-program) the program after being imported -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata (No other versions of HIV Prevention tracker imported previously). 3. Update existing/older version of the HIV Prevention tracker. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](http://dhis2.org/documentation). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section [Importing a metadata file into DHIS2](#importing-metadata) -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension (if applicable) { #default-data-dimension-if-applicable } @@ -46,39 +46,39 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:----------------------------|:------------|:----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into , the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. **_Note that this search and replace operation must be done with a plain text editor_**, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. The following table shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-----------|:------------|:-------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | | Rate (factor=1)| k4RGC3sMTzO | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1`| | Per 10 000 | FWTvArgP0jt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:10000`| -| Numerator only (number) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| +| Sólo numerador (número) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| -### Tipo de entidad Tracked { #tracked-entity-type } +### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-------|:------------|:-------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. Some visualizations and maps may contain references to organisation unit levels. Maps that consist of several map views may contain various Organisation unit level references based on the configuration of the map layer. Adjust the organisation unit level references in the metadata json file to match the organisation unit structure in the target instance before importing the metadata file. @@ -92,97 +92,97 @@ The process of upgrading an existing package to a newer version in a working DHI - the new objects are created; - assignment of users to relevant user groups is reviewed. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/master/en/user/html/import_export.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } > NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to conflict with. Follow the instructions to import the metadata then please proceed to the “[Configuration](#configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros A metadata package usually contains several user groups: -* HIV PREV - Access -* HIV PREV - Admin -* HIV PREV - Data capture +* VIH PREV - Acceso +* VIH PREV - Admin +* VIH PREV - Captura de datos By default, the following is assigned to these user groups -| Object | User Groups | User Groups | User Groups | +| Objeto | Grupos de usuarios | Grupos de usuarios | Grupos de usuarios | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| -| | HIV PREV - Access | HIV PREV - Admin | HIV PREV - Data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| | VIH PREV - Acceso | VIH PREV - Admin | VIH PREV - Captura de datos | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/master/en/dhis2_user_manual_en/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. ### [CONFIG] metadata { #config-metadata } The following metadata needs to be configured after import. -| Metadata Type | Nombre | +| Tipo de metadatos | Nombre | |---------------------|----------------------------------------------------| -| Option Sets | [CONFIG]_HIV - PrEP reason discontinuation | -| Option Sets | [CONFIG]\_HIV - PrEP adverse effect | +| Set de opciones | [CONFIG]_HIV - PrEP reason discontinuation | +| Set de opciones | [CONFIG]\_HIV - PrEP adverse effect | **Please be aware that this migh have an impact on Program Indicators and Program Rules.** @@ -190,10 +190,10 @@ The following metadata needs to be configured after import. Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__ADVERSE-EVENTS-FOLLOWING-IMMUNIZATION-AEFI__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__ADVERSE-EVENTS-FOLLOWING-IMMUNIZATION-AEFI__installation-md index d50888cd9..a600eac42 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__ADVERSE-EVENTS-FOLLOWING-IMMUNIZATION-AEFI__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__ADVERSE-EVENTS-FOLLOWING-IMMUNIZATION-AEFI__installation-md @@ -7,13 +7,13 @@ tags: # AEFI Tracker Installation Guide { #imm-aefi-installation } -## Overview { #overview } +## Visión general { #overview } The AEFI tracker package was developed using DHIS2.33.2. This was done in order to support some of the latest features in DHIS2. In order to use the package, it is recommended that you install it into a DHIS2 instance using DHIS2 2.33.2 or above. If you will be setting this up on a new instance, please refer to the [DHIS2 installation guide](https://docs.dhis2.org/master/en/dhis2_system_administration_guide/installation.html). ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -22,96 +22,96 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](http://dhis2.org/documentation). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into , the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. ***Note that this search and replace operation must be done with a plain text editor***, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|CqNPn5KzksS|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|CqNPn5KzksS|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| #### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| +|Persona|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| #### Event report organisation Unit { #event-report-organisation-unit } In the AEFI metadata package there are event reports tied to the root level unit of the organisation unit tree. The reference to the organisation unit needs to be replaced with the UID of the root unit of the organisation unit tree in your system. Table 4 shows the UID which need to be replaced, as well as the api endpoint to identify the existing organisation unit UID -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Unidad Organizativa|GD7TowwI46c|../api/organisationUnits.json?level=1| -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/master/en/user/html/import_export.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } ***NOTE***: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -127,7 +127,7 @@ There are six user groups that come with the package, the last three are recipie By default the following is assigned to these user groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_AEFI access_|_AEFI admin_|_AEFI data capture_| |_*Tracked entity type*_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and view| @@ -137,24 +137,24 @@ By default the following is assigned to these user groups You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/master/en/dhis2_user_manual_en/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/master/en/user/html/sharing.html). @@ -162,12 +162,12 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Line Listing { #line-listing } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EIR-IMMUNIZATION-EREGISTRY__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EIR-IMMUNIZATION-EREGISTRY__installation-md index f4e20de88..54fed95ff 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EIR-IMMUNIZATION-EREGISTRY__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EIR-IMMUNIZATION-EREGISTRY__installation-md @@ -11,7 +11,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,41 +20,41 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -62,15 +62,15 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |--------|-------------|--------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -79,39 +79,39 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -#### Sharing { #sharing } +#### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -124,12 +124,12 @@ A metadata package usually contains several user groups: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|------------------------------------|---------------------------------------------|------------------------------------------------| | | EIR - Immunization access | EIR - Immunization admin | EIR - Immunization data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | Please refere to the individual package installation annex for information about user groups. @@ -144,35 +144,35 @@ If your TET Person already matches the one in the package and you want to avoid * Import the package * Update sharing properties for this TET using the table above. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EPI-LOGISTICS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EPI-LOGISTICS__installation-md index 24cab2da8..16df6296e 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EPI-LOGISTICS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EPI-LOGISTICS__installation-md @@ -7,7 +7,7 @@ tags: # Aggregate Package Installation Guide { #aggregate-package-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing configuration packages for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -40,7 +40,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -59,34 +59,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -99,30 +99,30 @@ The .json metadata file is imported through the [Import/Export](#import_export) If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -140,7 +140,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -157,7 +157,7 @@ The user groups that usually come with the package include: We recommend to provide the following access to these groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_{Package Name} access_|_{Package Name} admin_|_{Package Name} data capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -165,7 +165,7 @@ We recommend to provide the following access to these groups |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EXPANDED-PROGRAMME-ON-IMMUNIZATION-EPI-AGGREGATE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EXPANDED-PROGRAMME-ON-IMMUNIZATION-EPI-AGGREGATE__installation-md index b3a41776b..479cdde94 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EXPANDED-PROGRAMME-ON-IMMUNIZATION-EPI-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__EXPANDED-PROGRAMME-ON-IMMUNIZATION-EPI-AGGREGATE__installation-md @@ -9,9 +9,9 @@ tags: This document includes an installation guide for the Immunization (EPI) HMIS package. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. @@ -21,111 +21,111 @@ The metadata package consists of the following modules: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: - Immunization access (view metadata/view data) - Immunization admin (view and edit metadata/no access to data) @@ -133,46 +133,46 @@ Three core user groups are included in the packages: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. -### Indicator mapping { #indicator-mapping } +### Mapeo de indicadores { #indicator-mapping } When implementing the _dashboard package_ only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__user-manual-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__user-manual-md index dc419ac84..6a0fe7b05 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__user-manual-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__user-manual-md @@ -139,7 +139,7 @@ This sections covers installation and configuration of the app and is intended f The Immunisation analysis app can be downloaded from the [DHIS2 App Store](https://play.dhis2.org/appstore) and manually installed, or installed directly from the App Store throught the "App Management" app of DHIS2. ![Installation](resources/images/IMM_ANSYS_epi_app_install.png). -### Configuration { #configuration } +### Configuración { #configuration } The configuration of the app is accessed by clicking the gear icon in the top right of the app (see [Overview and navigation](#Overview-and-navigation) above). diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-CAMPAIGNS__use-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-CAMPAIGNS__use-md index 5cb0377e4..3796b00f0 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-CAMPAIGNS__use-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-CAMPAIGNS__use-md @@ -23,7 +23,7 @@ The recording of the [DHIS2 Immunization toolkit for SIAs webinar](https://www.y HISP Centre would like to extend its special thanks to the external partners who provided strategic and technical guidance, contributed content, and shared field lessons lessons learned to develop this guide: MOH Uganda, MOH Bangladesh, WHO, UNICEF, UNICEF Bangladesh, US CDC, MSF, HISP Rwanda and HISP Uganda. The development of the DHIS2 SIA guidance and toolkit is supported by Gavi, the Vaccine Alliance. -## Overview { #overview } +## Visión general { #overview } The **DHIS2 Immunization Toolkit** developed in partnership with WHO, UNICEF and CDC includes a range of configuration packages, dashboard designs, and analysis apps to support the use of routine and non-routine data to improve immunisation programme performance, increase coverage and reduce the number of zero-dose children. This document outlines the DHIS2 tools that can be used and adapted for planning, implementing, real time monitoring, and evaluating SIAs. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-TRIANGULATION-DASHBOARD__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-TRIANGULATION-DASHBOARD__installation-md index 11d6cb6a6..f549b1a8a 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-TRIANGULATION-DASHBOARD__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__IMMUNIZATION-TRIANGULATION-DASHBOARD__installation-md @@ -9,9 +9,9 @@ tags: This is the installation guide for the Immunization (EPI) Triangulation package. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. The metadata package consists of one module, which is a **dashboard** package. @@ -26,85 +26,85 @@ While this dashboard package do not require that these packages are already inst ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). 4. [Adapting the metadata after import](#adapting-the-metadata) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is a type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the package. -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: - Immunization access (view metadata/view data) - Immunization admin (view and edit metadata/no access to data) @@ -113,12 +113,12 @@ Three core user groups are included in the packages: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### Indicator mapping { #indicator-mapping } +### Mapeo de indicadores { #indicator-mapping } When implementing the _dashboard package_ only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. The indicators have a "[CONFIG]" prefix to their name for easy identification, which should removed when the indicator has been configured. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__VACCINATION-CAMPAIGNS__use-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__VACCINATION-CAMPAIGNS__use-md index 63b50ac81..fd6844f19 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__VACCINATION-CAMPAIGNS__use-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__IMMUNIZATION__VACCINATION-CAMPAIGNS__use-md @@ -23,7 +23,7 @@ The recording of the [DHIS2 Immunization toolkit for SIAs webinar](https://www.y HISP Centre would like to extend its special thanks to the external partners who provided strategic and technical guidance, contributed content, and shared field lessons lessons learned to develop this guide: MOH Uganda, MOH Bangladesh, WHO, UNICEF, UNICEF Bangladesh, US CDC, MSF, HISP Rwanda and HISP Uganda. The development of the DHIS2 SIA guidance and toolkit is supported by Gavi, the Vaccine Alliance. -## Overview { #overview } +## Visión general { #overview } The **DHIS2 Immunization Toolkit** developed in partnership with WHO, UNICEF and CDC includes a range of configuration packages, dashboard designs, and analysis apps to support the use of routine and non-routine data to improve immunisation programme performance, increase coverage and reduce the number of zero-dose children. This document outlines the DHIS2 tools that can be used and adapted for planning, implementing, real time monitoring, and evaluating SIAs. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-HMIS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-HMIS__installation-md index 585faa8a9..97eb8e7f7 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-HMIS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-HMIS__installation-md @@ -9,9 +9,9 @@ tags: This document includes an installation guide for the Malaria aggregate packages. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. @@ -27,111 +27,111 @@ The metadata package consists of the following modules: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: - Malaria access (view metadata/view data) - Malaria admin (view and edit metadata/no access to data) @@ -145,46 +145,46 @@ For Malaria Stock package the groups are: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. -### Indicator mapping { #indicator-mapping } +### Mapeo de indicadores { #indicator-mapping } When implementing the _dashboard package_ only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-LOGISTICS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-LOGISTICS__installation-md index 585faa8a9..97eb8e7f7 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-LOGISTICS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-LOGISTICS__installation-md @@ -9,9 +9,9 @@ tags: This document includes an installation guide for the Malaria aggregate packages. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. @@ -27,111 +27,111 @@ The metadata package consists of the following modules: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: - Malaria access (view metadata/view data) - Malaria admin (view and edit metadata/no access to data) @@ -145,46 +145,46 @@ For Malaria Stock package the groups are: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. -### Indicator mapping { #indicator-mapping } +### Mapeo de indicadores { #indicator-mapping } When implementing the _dashboard package_ only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-SURVEILLANCE__installation-md index 733078ba9..5681e558b 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__MALARIA__MALARIA-SURVEILLANCE__installation-md @@ -9,71 +9,71 @@ tags: This document includes an installation guide for the Malaria Case Surveillance and Foci Investigation packages. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system are outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Preparing the Metadata File { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | Identify the UIDs of the default dimensions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -125,50 +125,50 @@ The Malaria CS and FOCI package contains ten option sets: > > When updating the UID of a metadata element in the existing DHIS2 instance, you will need to run an SQL command in the database and additionally replace all occurrences and references of its UID in other metadata objects: predictor, indicator, validation rule expressions, etc. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -201,42 +201,42 @@ Relationship types for 'MAL - Case-to-case' and 'MAL - Case-to-focus' have been ![Configure malaria case-to-focus relationship "from" constraint](resources/images/MAL_CS_relationshipType_casetofocus2.png) -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring organisation unit access. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadata requires advanced knowledge of DHIS2 and various dependencies. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__design-md index 6de04a46c..a71b52744 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__design-md @@ -195,7 +195,7 @@ The users are assigned to the appropriate user group based on their role within | Grupo de usuarios | Tablero (Dashboard) | Program Metadata | Program data | |-|-|-|-| -| HTN admin | Puede editar y visualizar | Puede editar y visualizar | No Access | +| HTN admin | Puede editar y visualizar | Puede editar y visualizar | Sin acceso | | HTN access | Puede editar y visualizar | Solo lectura | Solo lectura | | HTN data capture | No access | Solo lectura | Puede capturar y visualizar | diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__installation-md index f79b55217..3acae67ed 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__HYPERTENSION-CONTROL__installation-md @@ -9,7 +9,7 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -18,84 +18,84 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. ***Note that this search and replace operation must be done with a plain text editor***, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| #### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| +|Persona|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| #### Visualizations using Root Organisation Unit { #visualizations-using-root-organisation-unit } Visualizations, if included in a package, may contain a placeholder for a Root Organisation Unit. The placeholder label example is . Before attempting to import the package you need to replace this label with the UID of the Root Organisation Unit in your system. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } ***NOTE***: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Known Import Issues { #known-import-issues } @@ -119,13 +119,13 @@ A third and more complicated approach is to modify the .json file to re-use exis ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -138,7 +138,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_Access_|_Admin_|_Data capture_| |_*Tracked entity type*_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and view| @@ -148,24 +148,24 @@ By default the following is assigned to these user groups You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -173,10 +173,10 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__SENSORY-FUNCTION-EYE-AND-EAR-CARE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__SENSORY-FUNCTION-EYE-AND-EAR-CARE__installation-md index d0b8701d1..c31918993 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__SENSORY-FUNCTION-EYE-AND-EAR-CARE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NON-COMMUNICABLE-DISEASES__SENSORY-FUNCTION-EYE-AND-EAR-CARE__installation-md @@ -9,9 +9,9 @@ tags: This document includes an installation guide for the Sensory function: Eye and Ear care aggregate package. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. @@ -22,110 +22,110 @@ The metadata package consists of the following modules: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file) 2. [Importing the metadata file into DHIS2](#importing-metadata) 3. [Configuring the imported metadata](#configuration) -4. [Adapting the program after import](#adapting-the-program) +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Rate (factor=1) | `k4RGC3sMTzO` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Porcentaje | `hmSnCXmLYwt` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:100` | | Per 10 000 | `FWTvArgP0jt` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:10000` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: | Nombre | UID | Access rights | |-----|------|---------------| @@ -135,41 +135,41 @@ Three core user groups are included in the packages: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } Users will need specific user roles in order to engage with the various applications within DHIS2. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. ### Mapping { #mapping } When implementing the dashboard package only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could influence their functionality. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NUTRITION__NUTRITION-AGGREGATE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NUTRITION__NUTRITION-AGGREGATE__installation-md index 218a555c4..445b51532 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NUTRITION__NUTRITION-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__NUTRITION__NUTRITION-AGGREGATE__installation-md @@ -9,113 +9,113 @@ tags: This document includes an installation guide for the Nutrition aggregate package. -System default language: English +Idioma predeterminado del sistema: Inglés ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -125,46 +125,46 @@ Three core user groups are included in the package: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. -### Indicator mapping { #indicator-mapping } +### Mapeo de indicadores { #indicator-mapping } When implementing the _dashboard package_ only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__REHABILITATION__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__REHABILITATION__installation-md index 2c62e0189..672d7b380 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__REHABILITATION__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__REHABILITATION__installation-md @@ -9,68 +9,68 @@ tags: This document includes an installation guide for the Rehabilitation aggregate package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese, Arabic ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file) 2. [Importing the metadata file into DHIS2](#importing-metadata) 3. [Configuring the imported metadata](#configuration) -4. [Adapting the program after import](#adapting-the-program) +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Preparing the Metadata File { #preparing-the-metadata-file } -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Visualizations using root organisation unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -277,50 +277,50 @@ All validation rule groups and the corresponding validation rules are listed in The organisation unit groups for all validation rules are set to facility level. The facility level value is located in the `"organisationUnitLevels"` property of each validation rule. It is set to `4` by default. Adjust these levels in the metadata file to match the facility level in the target instance befre importing the package. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -330,16 +330,16 @@ Three core user groups are included in the package: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. The table below provides information about organisation unit assignment for Rehabilitation data sets: @@ -415,35 +415,35 @@ The level of data collection for **incidence** data has to be the same or lower The organisation unit assignmnet of the **Personnel density** data set should remain at facility level for the purpose of analytical outputs. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -### Indicator mapping { #indicator-mapping } +### Mapeo de indicadores { #indicator-mapping } For partial implementation of the Rehabilitation package, i.e. implementation of a customized WHO core indicator set, please refer to the [WHO-to-DHIS2 indicator mapping table](resources/rehab_indicator_mapping.xlsx). When adapting metadata, make sure to identify visualizations and dashboards where applicable indicators are used, as well as data elements and category combinations used in the corresponding data sets. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadata requires advanced knowledge of DHIS2 and various dependenies. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__design-md index a82c1f424..a47b1186f 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__design-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__design-md @@ -18,7 +18,7 @@ The RMNCAH package includes two main components: This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the configuration package while adhering to the design principles set forth. -## Overview { #overview } +## Visión general { #overview } The RMNCAH configuration package for aggregate reporting contains the following datasets for entering input data: diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__installation-md index 24cab2da8..16df6296e 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-AGGREGATE__installation-md @@ -7,7 +7,7 @@ tags: # Aggregate Package Installation Guide { #aggregate-package-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing configuration packages for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -40,7 +40,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -59,34 +59,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -99,30 +99,30 @@ The .json metadata file is imported through the [Import/Export](#import_export) If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -140,7 +140,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -157,7 +157,7 @@ The user groups that usually come with the package include: We recommend to provide the following access to these groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_{Package Name} access_|_{Package Name} admin_|_{Package Name} data capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -165,7 +165,7 @@ We recommend to provide the following access to these groups |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-ANTENATAL-CARE-REGISTRY__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-ANTENATAL-CARE-REGISTRY__installation-md index 6bc25755d..a7008d22e 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-ANTENATAL-CARE-REGISTRY__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__RMNCAH__RMNCAH-ANTENATAL-CARE-REGISTRY__installation-md @@ -9,7 +9,7 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -18,51 +18,51 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. ***Note that this search and replace operation must be done with a plain text editor***, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| #### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| +|Persona|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| #### Visualizations using Root Organisation Unit { #visualizations-using-root-organisation-unit } @@ -77,34 +77,34 @@ As noted in the system design guide, the ANC DAK provides concept mappings of th When importing the package into your DHIS2 instance, these Attributes will be imported first. If you have other metadata in this instance, you will see six "Attributes" fields underneath data elements and TEI attributes in maintenance. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } ***NOTE***: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Known Import Issues { #known-import-issues } @@ -128,13 +128,13 @@ A third and more complicated approach is to modify the .json file to re-use exis ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -147,7 +147,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_Access_|_Admin_|_Data capture_| |_*Tracked entity type*_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and view| @@ -157,24 +157,24 @@ By default the following is assigned to these user groups You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__ANTI-TUBERCULOSIS-DRUG-RESISTANCE-SURVEY-DRS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__ANTI-TUBERCULOSIS-DRUG-RESISTANCE-SURVEY-DRS__installation-md index 3ba6082f7..83adabeb6 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__ANTI-TUBERCULOSIS-DRUG-RESISTANCE-SURVEY-DRS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__ANTI-TUBERCULOSIS-DRUG-RESISTANCE-SURVEY-DRS__installation-md @@ -9,13 +9,13 @@ tags: Package Version 1.0.1 -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese -## Overview { #overview } +## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -57,7 +57,7 @@ When importing this package into a new/blank instance, please refer to the [DHIS ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -66,52 +66,52 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section [Importing a metadata file into DHIS2](#importing-metadata) -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|----------------------------------------| -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Sort order for options { #sort-order-for-options } @@ -147,45 +147,45 @@ Ejemplo: | `PazB6GSITwK` | Missing data report | visualization (pivot table) | 4 | Facility | | `GinRhTtdKnI` | Percentage of samples rejected on arrival at NTRL | visualization (pivot table) | 1,2,3,4 | Country, Region, District, Facility | -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -198,39 +198,39 @@ There are four user groups that come with the package: By default the following is assigned to these user groups -|Object|User Groups| | | +|Objeto|Grupos de usuarios| | | |:--|:--|:--|:--| | |TB access|TB admin|TB data capture| -|Tracked entity type|**Metadata:** can view
**Data:** can view|**Metadata:** can edit and view
**Data:** can view|**Metadata:** can view
**Data:** can capture and view| +|Tipo de entidad Tracked|**Metadata:** can view
**Data:** can view|**Metadata:** can edit and view
**Data:** can view|**Metadata:** can view
**Data:** can capture and view| |Programa|**Metadata:** can view
**Data:** can view|**Metadata:** can edit and view
**Data:** can view|**Metadata:** can view
**Data:** can capture and view| -|Program Stages|**Metadata:** can view
**Data:** can view|**Metadata:** can edit and view
**Data:** can view|**Metadata:** can view
**Data:** can capture and view| +|Etapas del programa|**Metadata:** can view
**Data:** can view|**Metadata:** can edit and view
**Data:** can view|**Metadata:** can view
**Data:** can capture and view| |Tableros|**Metadata:** can view
**Data:** can view|**Metadata:** can edit and view
**Data:** can view|**Metadata:** can view
**Data:** can view| You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html) for more information on configuring sharing. ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Constants { #constants } @@ -398,10 +398,10 @@ You must configure tracker capture dashboard after the package has been installe Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__installation-md index 5e19ddb7f..aaf75aa94 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__installation-md @@ -9,78 +9,78 @@ tags: Package Version 2.0.0 -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. 4. [Configuring](#configuration) the imported metadata. 5. [Adapting](#adapting-the-tracker-program) the program after being imported -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata (No other versions of TB Case Surveillance tracker imported previously). 3. Update existing/older version of the TB Case Surveillance tracker. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, a DHIS2 administrator user account is required. Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system are outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } The metadata reference and metadata json files provide technical details on package version and content. While not always necessary, it can often required to make certain modifications to the metadata file before importing it into DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } It is recommended to import the DHIS2 Common HIS metadata library into the target instance before using and adapting any DHIS2 metadata packages. Common HIS Metadata package is available for download in the supported versions of DHIS2 at [Metadata Package Downloads](https://dhis2.org/metadata-package-downloads) -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | Identify the UIDs of the default dimensions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|----------------------------------------| -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Option codes { #option-codes } @@ -124,9 +124,9 @@ Make sure that no options within an option set have the same sort order. This ca In order to fix sort order in option sets containing large numbers of options, please refer to this [SQL script](https://github.com/dhis2/dhis2-utils/blob/master/resources/sql/clean_up_option_sort_order.sql). -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. Some visualizations and maps may contain references to organisation unit levels. Maps that consist of several map views may contain vaious Organisation unit level references based on the configuration of the map layer. Adjust the organisation unit level references in the metadata json file to match the organisation unit structure in the target instance before importing the metadata file. @@ -142,35 +142,35 @@ The process of upgrading an existing package to a newer version in a working DHI The [diff file](resources/tb_cs-1.0.1-vs-2.0.0.xlsx) will help the implementer identify the necessary changes. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Upgrading earlier versions of TB CS Tracker program { #upgrading-earlier-versions-of-tb-cs-tracker-program } @@ -208,18 +208,18 @@ For demo and training purposes, the following upgrade process is recommended: 5. Import mapped and missing data. 6. Test data entry, dashboards and general functionality. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: * Tableros -* Visualizations, maps, event reports and report tables -* Data sets -* Category options +* Visualizaciones, mapas, informes de eventos y tablas de informes +* Sets de datos +* Opciones de categoría * Programs and program stages These core user groups are included in the package: @@ -232,37 +232,37 @@ These core user groups are included in the package: By default the following is assigned to these user groups -|Object|User Groups| | | | | +|Objeto|Grupos de usuarios| | | | | |:-|:-|:-|:-|:-|:-| | | TB access | TB lab access | TB admin | TB data capture | TB lab data capture | -| Tracked entity type | **Metadata:** can view
**Data:** can view | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | **Metadata:** can view
**Data:** can capture and view | +| Tipo de entidad Tracked | **Metadata:** can view
**Data:** can view | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | **Metadata:** can view
**Data:** can capture and view | | Programa | **Metadata:** can view
**Data:** can view | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | **Metadata:** can view
**Data:** can capture and view | -| Program Stages | **Metadata:** can view
**Data:** can view | **Group access is limited to stages: TB Registration, Diagnostic and Laboratory Results**
**Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | **Group access is limited to stages: TB Registration and Laboratory Results**
**Metadata:** can view
**Data:** can capture and view | +| Etapas del programa | **Metadata:** can view
**Data:** can view | **Group access is limited to stages: TB Registration, Diagnostic and Laboratory Results**
**Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | **Group access is limited to stages: TB Registration and Laboratory Results**
**Metadata:** can view
**Data:** can capture and view | | Tableros | **Metadata:** can view
**Data:** can view | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | No access | No access | Users need to be assigned to the aplicable user group based on their role within the system. Sharing for other objects in the package should be set up depending on requirements. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/sharing.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } Program must be assigned to applicable organisation units within the organisation unit hierarchy. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. ### Constants { #constants } @@ -320,10 +320,10 @@ The **program indicators** in the TB Case Surveillance and Laboratory package ar Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-COVID-19-IMPACT-ASSESSMENT__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-COVID-19-IMPACT-ASSESSMENT__installation-md index 37984e137..8eb251e69 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-COVID-19-IMPACT-ASSESSMENT__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-COVID-19-IMPACT-ASSESSMENT__installation-md @@ -9,9 +9,9 @@ tags: This document includes an installation guide for the TB - COVID-19 Impact Assessment aggregate package. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. @@ -22,109 +22,109 @@ The metadata package consists of the following modules: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file) 2. [Importing the metadata file into DHIS2](#importing-metadata) 3. [Configuring the imported metadata](#configuration) -4. [Adapting the program after import](#adapting-the-program) +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. The module includes the same standard user groups as the TB HMIS package. @@ -136,18 +136,18 @@ The module includes the same standard user groups as the TB HMIS package. The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } Users will need specific user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: 1. Tracker data analysis: Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. 2. Tracker data capture: Can add data values, update tracked entities, search tracked entities across org units and access tracker capture -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. ### Mapping { #mapping } @@ -155,29 +155,29 @@ When implementing the complete package, please refer to the [mapping guide](reso When implementing the *dashboard package* only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the design guide the description of numerators and denominators within the metadata objects as well as in the [mapping guide](resources/tb_impax-mapping.xlsx). -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could influence their functionality. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__DESIGN__tb-notifications-and-outcomes-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__DESIGN__tb-notifications-and-outcomes-md index 0c02a93d1..4ba78b7da 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__DESIGN__tb-notifications-and-outcomes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__DESIGN__tb-notifications-and-outcomes-md @@ -14,7 +14,7 @@ Version 2.0.0 This document describes the system design for **TB programmes to integrate routine aggregate reporting into the HMIS**. Depending on the local context, this data may be populated by paper-based reporting or by aggregating data from electronic individual-level systems such as DHIS2 Tracker or other tools. In particular, the TB aggregate version 2.0.0 aims at outlining the updates made in definitions and data entry forms as a result of the publishing of the Consolidated guidance on tuberculosis data generation and use (the link will be provided upon publication on the WHO website). -## Overview { #overview } +## Visión general { #overview } | Dataset name | Periodicity | Purpose | |:-------------------------------------:|:-----------:|:---------------------:| diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__installation-md index c8155d8f3..d0e706b20 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HMIS__installation-md @@ -9,9 +9,9 @@ tags: This document includes an installation guide for TB HMIS packages. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The package includes metadata json files containing the following components: @@ -27,68 +27,68 @@ The package includes metadata json files containing the following components: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } Visualizations, report tables, maps, validation rules that reference a specific organisation unit level or organisation unit group, contain placeholders eg. `` or ``. Use the search function in the .json file editor to identify such placeholders and replace `` with the UID of the level 1 organisation unit in the target instance and `` with the UID of the facility organisation unit level . -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Updating TB HMIS to version 2.0.0 from previous versions { #updating-tb-hmis-to-version-200-from-previous-versions } @@ -104,48 +104,48 @@ An update of the TB HMIS package from previous versions is possible with followi If you are implementing tracker to aggregate data transfer between TB tracker and TB HMIS packages, please consider that the configuration of such transfer has to be reconfigured based on new guidelines, data element definitions, data element codes, etc. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros - Visualizations, maps, report tables -- Data sets -- Category options +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: - TB access (view metadata/view data) - TB admin (view and edit metadata/no access to data) @@ -159,46 +159,46 @@ For TB Stock package the groups are: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. ### Indicator mapping (dashboard package) { #indicator-mapping-dashboard-package } When implementing the _dashboard package_ only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database where other metadata is already present. If you are working in a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could "break" their functionality. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadata requires advanced knowledge of DHIS2 and various dependencies. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HOUSEHOLD-CONTACTS-INVESTIGATION__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HOUSEHOLD-CONTACTS-INVESTIGATION__installation-md index a819afec3..c94a9b901 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HOUSEHOLD-CONTACTS-INVESTIGATION__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-HOUSEHOLD-CONTACTS-INVESTIGATION__installation-md @@ -9,76 +9,76 @@ tags: Package Version 1.0.0 -System default language: English +Idioma predeterminado del sistema: Inglés ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. 4. [Configuring](#configuration) the imported metadata. 5. [Adapting](#adapting-the-tracker-program) the program after being imported -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata (No other versions of TB Case Surveillance tracker imported previously). 3. Update existing/older version of the TB Case Surveillance tracker. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, a DHIS2 administrator user account is required. Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system are outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } The metadata reference and metadata json files provide technical details on package version and content. While not always necessary, it can often required to make certain modifications to the metadata file before importing it into DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } It is recommended to import the DHIS2 Common HIS metadata library into the target instance before using and adapting any DHIS2 metadata packages. Common HIS Metadata package is available for download in the supported versions of DHIS2 at [Metadata Package Downloads](https://dhis2.org/metadata-package-downloads) -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | Identify the UIDs of the default dimensions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|----------------------------------------| -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Option codes { #option-codes } @@ -122,9 +122,9 @@ Make sure that no options within an option set have the same sort order. This ca In order to fix sort order in option sets containing large numbers of options, please refer to this [SQL script](https://github.com/dhis2/dhis2-utils/blob/master/resources/sql/clean_up_option_sort_order.sql). -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. Some visualizations and maps may contain references to organisation unit levels. Maps that consist of several map views may contain vaious Organisation unit level references based on the configuration of the map layer. Adjust the organisation unit level references in the metadata json file to match the organisation unit structure in the target instance before importing the metadata file. @@ -138,35 +138,35 @@ The process of upgrading an existing package to a newer version in a working DHI - the new objects are created; - assignment of users to relevant user groups is reviewed. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Linking the TB Household Contacts Investigation package to an existing TB Case Surveillance module { #linking-the-tb-household-contacts-investigation-package-to-an-existing-tb-case-surveillance-module } @@ -285,17 +285,17 @@ Tracked Entity Attributes to be displayed in the relationship widget have to be 'Display in list without program' option has to be activated for the relevant Tracked Entity Attributes. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: * Dashboards (Visualizations, maps, event reports and report tables) -* Data sets -* Category options +* Sets de datos +* Opciones de categoría * Programs and program stages These core user groups are included in the package: @@ -306,37 +306,37 @@ These core user groups are included in the package: By default the following is assigned to these user groups -|Object|User Groups| | | | | +|Objeto|Grupos de usuarios| | | | | |:-|:-|:-|:-|:-|:-| | | TB access | TB admin | TB data capture | -| Tracked entity type | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | +| Tipo de entidad Tracked | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | | Programa | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | -| Program Stages | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | +| Etapas del programa | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | **Metadata:** can view
**Data:** can capture and view | | Tableros | **Metadata:** can view
**Data:** can view | **Metadata:** can edit and view
**Data:** no access | no access | Users need to be assigned to the aplicable user group based on their role within the system. Sharing for other objects in the package should be set up depending on requirements. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/sharing.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } Program must be assigned to applicable organisation units within the organisation unit hierarchy. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. ### Configuring tracker capture interface, widgets and top bar { #configuring-tracker-capture-interface-widgets-and-top-bar } @@ -366,10 +366,10 @@ The default configuration is set to internal data exchange, i.e. when the tracke Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-LOGISTICS__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-LOGISTICS__installation-md index c8155d8f3..d0e706b20 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-LOGISTICS__installation-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-LOGISTICS__installation-md @@ -9,9 +9,9 @@ tags: This document includes an installation guide for TB HMIS packages. -System default language: English +Idioma predeterminado del sistema: Inglés -## Overview { #overview } +## Visión general { #overview } The package includes metadata json files containing the following components: @@ -27,68 +27,68 @@ The package includes metadata json files containing the following components: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } Visualizations, report tables, maps, validation rules that reference a specific organisation unit level or organisation unit group, contain placeholders eg. `` or ``. Use the search function in the .json file editor to identify such placeholders and replace `` with the UID of the level 1 organisation unit in the target instance and `` with the UID of the facility organisation unit level . -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Updating TB HMIS to version 2.0.0 from previous versions { #updating-tb-hmis-to-version-200-from-previous-versions } @@ -104,48 +104,48 @@ An update of the TB HMIS package from previous versions is possible with followi If you are implementing tracker to aggregate data transfer between TB tracker and TB HMIS packages, please consider that the configuration of such transfer has to be reconfigured based on new guidelines, data element definitions, data element codes, etc. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros - Visualizations, maps, report tables -- Data sets -- Category options +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: - TB access (view metadata/view data) - TB admin (view and edit metadata/no access to data) @@ -159,46 +159,46 @@ For TB Stock package the groups are: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. ### Indicator mapping (dashboard package) { #indicator-mapping-dashboard-package } When implementing the _dashboard package_ only, the indicator numerators and denominators have to be configured using the metadata objects in the existing instance. Configuration information is available in the documentation and the description of numerators and denominators in the metadata file. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database where other metadata is already present. If you are working in a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could "break" their functionality. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadata requires advanced knowledge of DHIS2 and various dependencies. diff --git a/projects/docs-full-site/es_419/IMPLEMENT__MAINTENANCE-AND-USE__localization-of-dhis2-md b/projects/docs-full-site/es_419/IMPLEMENT__MAINTENANCE-AND-USE__localization-of-dhis2-md new file mode 100644 index 000000000..721b0b639 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__MAINTENANCE-AND-USE__localization-of-dhis2-md @@ -0,0 +1,218 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/maintenance_use/localization-of-dhis2.md" +revision_date: '2022-08-08' +tags: +- Implementar +--- + +# Localization of DHIS 2 { #localization-of-dhis-2 } + +## DHIS 2 localization concepts { #localization-intro } + +Localization involves the adaptation of an application to a specific +location. When implementing DHIS 2 in a given country, adequate resources +should be allocated to translate and localize the application if required. +Translation of the user interface elements, messages, layout, date and +time formats, currency and other aspects must be considered. In addition +to translation of the user interface itself, metadata content which is +contained in the database must also be considered to be translated. + +Interface translations are compiled into the system itself, such that new translations +can only be accessed by taking a newer version of DHIS 2. +Database translations, on the other hand, are specific to your implementation +and can be added to your existing DHIS 2 instance. + +These two aspects are managed independently and the processes and tools are outlined +below. + + +## User Interface localization { #user-interface-localization } + +### Visión general { #overview } + +DHIS 2 supports internationalization (i18n) of the user interface through +the use of Java property strings and PO files. Java property files are used +when messages originate from the back-end Java server, while PO files +are used for front-end apps written in JavaScript. +The DHIS 2 Android apps use a specific XML format. + +> **Note** +> +> The translator need not worry about the different resource file formats; +> the translation platform hides the details, and only displays the strings +> that require translation. +> For example, the figure below shows the source and target strings when +> translating a resource to French. +> +> ![](resources/images/translation_ui.jpg) + +There should always be an English string for all messages in DHIS 2. +When the user selects a given language, and a translation is present in that +language, then the translation will be shown. However, if the string in the +desired language is missing then fallback rules will be applied. In cases when +two given translations, such as Portuguese and Brazilian Portuguese share +common messages, it is not required to perform a full translation in the +variant language. Only messages which are different should be translated. +Fallback rules are then applied in the following manner (assuming the user has +chooses Brazilian Portuguese as their language: + +1. Display the message in Brazilian Portuguese if it exists. + +2. If it does not exist in the variant language, then use the Portuguese + message, if it exists. + +3. If there is no message in either the base language or the variant language, + choose the ultimate fallback language, English. + + +> **Important** +> +> There are a number of source strings such as "dd MMM yyyy 'to '" which are used +> for date/time formatting in various parts of DHIS 2. Part of the value +> should not be translated because it is actually a special formatting +> field used by either Java or JavaScript to interpolate or format a string. +> In this example the part of the value which **can** be translated would be +> "to", for instance to "a" in Spanish. The special string which should **not** +> be translated is "dd MMM yyyy". If these date format template +> strings are translated, it may result in errors in the application! + +> **Important** +> +> Some special variables (e.g. {0} ) use curly brackets. This +> denotes a variable which will be replaced by a number or other +> value by the application. You must place this variable notation in +> the correct position and be sure not to modify it. + +### Translation Platform { #translation-server } + +DHIS2 is now using [transifex](https://www.transifex.com) as our main platform for +managing translations. You can access the DHIS2 resources at +[translate.dhis2.org](https://translate.dhis2.org), or directly at +https://www.transifex.com/hisp-uio/public. + +### How do I contribute to translations? { #how-do-i-contribute-to-translations } + +#### Register as a translator { #register-as-a-translator } + +The first step is to get access to the project. There are two ways to do this: + +1. Navigate to the platform and create an account with transifex, then + - request access to our organisation "HISP UiO" as a member of the "DHIS 2 Core Apps" translation team. + Transifex +have some useful instructions here: +[Getting Started as a Translator](https://docs.transifex.com/getting-started-1/translators) + +1. Email the DHIS 2 team at translate@dhis2.org to request access. +Please provide: + - the name, email address and translation language of the user(s) you would like us to give access to, and + - a little bit of information about why you are interested in contributing to the DHIS 2 translations + +#### Edit translations { #edit-translations } + +Once you have access as a translator, you can start translating through the transifex Web Editor. + +Transifex have a useful guide here: +[Translating Online with the Web Editor](https://docs.transifex.com/translation/translating-with-the-web-editor) + +As far as possible, the projects represent DHIS 2 apps one-to-one. For example, the **APP: Data Visualizer** project contains the translation strings for the Data Visualizer app. + +Our transifex projects for DHIS2 User Interface all start with one of the following: + +- **APP:** indicates that the project contains strings for a specific app +- **APP-COMPONENT:** indicates that the project is a component library used by the apps +- **ANDROID:** indicates that the project is an Andriod app + +In addition, **APP: Server-Side Resources** contains some strings that are used by several apps; namely: +- "Data Entry" +- "Maintenance" +- "Pivot Tables" +- "Reports" + +Within the projects we have resources, which represent localization files in the source code. In order to support multiple DHIS2 versions, with the same localization files, the _version_ is associated with each instance of the file. So, for **APP: Data Visualizer** the list of resources looks like this in the Web Editor: + +![](resources/images/transifex_data_vis.jpg) + +i.e. there is only one source resource for the app (`en.pot`), but we have added the versions from 2.31 (v31) up to the latest development (master). The version is shown in the "Category" field, and is also visible as a prefix to the resource name, e.g. `v31--en-pot`. + +> **Note** +> +> In general, we request translators focus on the "**master**" resource; it usually contains all strings from previous versions, and when translations are added the platform will fill in matching translations on the previous versions too. See the [localization](https://dhis2.org/localization/#section-2) +section of our website. + +> **Tip** { .tip } +> +> For a specific language and DHIS2 version, you can get an overview of the tranlation coverage, as well as direct links to all relevant resources on transifex, from the [localization](https://dhis2.org/localization/#section-2) section of our website. + +### When will new translations be available in the system? { #when-will-new-translations-be-available-in-the-system } + +We have a nightly service that pulls new translations from the transifex platform and opens a pull request on the source code. + +The service loops over all projects and supported languages and does the following: + +1. Pulls localization files from transifex (**where translations are more than 20% complete**) +2. Raises a pull request on the source code if changes are found for the language + +The pull requests are reviewed and merged into the code base as part of the normal development process. + +> **Info** +> +> The translations added to transifex will, in general, be in the next available stable release for all supported DHIS 2 versions +> +> _If you need to ensure that your translations are in the next stable release, contact us (translate@dhis2.org) expalining your needs, and we'll let you know what we can do._ + +> **Tip** +> +> The translations you add in transifex should be visible in all development demo versions on our play server (https://play.dhis2.org) within a few days, in most cases. + +### How do I add a new language? { #how-do-i-add-a-new-language } + +Please contact us via email translate@dhis2.org, or on the [Community of Practice](https://community.dhis2.org/c/translation) and we'll add that language to the projects on transifex. + +Once resources for that language are more than 20% translated, they will start to be pulled into the system. They will then +become visible in the development demo versions, and be available in future releases. + +> **Note** +> +> DHIS 2 manages metadata (database) locales independently from the UI. _See the following section._ + + +## Metadata/Database translations { #metadata-database-translations } + +In addition to translation of the user interface, DHIS 2 also supports +the localization of the metadata content in the database. It is possible +to translate individual objects through the **Maintenance app**, but in +order to better support a standard translation workflow, a specialized +app has been developed for this purpose. + +New metadata locales can be added in **Maintenance app > Locales**. + +### DHIS 2 Translations app { #translations-app } + +The DHIS 2 **Translation app** can +be used to translate all metadata (data elements, categories, +organization units, etc) into any locale which is present in the +database. + +To get started, simply choose the **Translations app** from the top level +menu. + +![](resources/images/translations_app.png) + +1. Choose the type of object you wish to translate from the **Object** + drop-down menu, such as "Data elements". + +2. Be sure you have set the **Target Locale** to the correct language. + +3. Choose the specific object you wish to translate, and translate each + of the properties (Name, Short name, Description, etc). These + properties vary from object to object. + +4. Press "Save" when you are done translating the specific object to + save your changes. + + +> **Note** +> +> You can search for a specific term using the search feature in the +upper right hand corner of the app. + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__UNDERSTANDING-DHIS2-IMPLEMENTATION__localization-of-dhis-2-md b/projects/docs-full-site/es_419/IMPLEMENT__UNDERSTANDING-DHIS2-IMPLEMENTATION__localization-of-dhis-2-md new file mode 100644 index 000000000..3bcdf787f --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__UNDERSTANDING-DHIS2-IMPLEMENTATION__localization-of-dhis-2-md @@ -0,0 +1,227 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/commonmark/en/content/implementation/localization-of-dhis2.md" +revision_date: '2019-12-02' +--- + +# Localization of DHIS 2 { #localization-of-dhis-2 } + +## DHIS 2 localization concepts { #localization-intro } + + + +Localization involves the adaptation of an application to a specific +location. When implementing DHIS 2 in a given country, adequate resources +should be allocated to translate and localize the application if required. +Translation of the user interface elements, messages, layout, date and +time formats, currency and other aspects must be considered. In addition +to translation of the user interface itself, metadata content which is +contained in the database must also be considered to be translated. + +Interface translations are compiled into the system itself, such that new translations +can only be accessed by taking a newer version of DHIS 2. +Database translations, on the other hand, are specific to your implementation +and can be added to your existing DHIS 2 instance. + +These two aspects are managed independently and the processes and tools are outlined +below. + + +## User Interface localization { #user-interface-localization } + +### Visión general { #overview } + +DHIS 2 supports internationalization (i18n) of the user interface through +the use of Java property strings and PO files. Java property files are used +when messages originate from the back-end Java server, while PO files +are used for front-end apps written in JavaScript. +The DHIS 2 Android apps use a specific XML format. + +> **Note** +> +> The translator need not worry about the different resource file formats; +> the translation platform hides the details, and only displays the strings +> that require translation. +> For example, the figure below shows the source and target strings when +> translating a resource to French. +> +> ![](resources/images/i18n/translation_ui.jpg) + +There should always be an English string for all messages in DHIS 2. +When the user selects a given language, and a translation is present in that +language, then the translation will be shown. However, if the string in the +desired language is missing then fallback rules will be applied. In cases when +two given translations, such as Portuguese and Brazilian Portuguese share +common messages, it is not required to perform a full translation in the +variant language. Only messages which are different should be translated. +Fallback rules are then applied in the following manner (assuming the user has +chooses Brazilian Portuguese as their language: + +1. Display the message in Brazilian Portuguese if it exists. + +2. If it does not exist in the variant language, then use the Portuguese + message, if it exists. + +3. If there is no message in either the base language or the variant language, + choose the ultimate fallback language, English. + + +> **Important** +> +> There are a number of source strings such as "dd MMM yyyy 'to '" which are used +> for date/time formatting in various parts of DHIS 2. Part of the value +> should not be translated because it is actually a special formatting +> field used by either Java or JavaScript to interpolate or format a string. +> In this example the part of the value which **can** be translated would be +> "to", for instance to "a" in Spanish. The special string which should **not** +> be translated is "dd MMM yyyy". If these date format template +> strings are translated, it may result in errors in the application! + +> **Important** +> +> Some special variables (e.g. {0} ) use curly brackets. This +> denotes a variable which will be replaced by a number or other +> value by the application. You must place this variable notation in +> the correct position and be sure not to modify it. + +### Translation Platform { #translation-server } + + + +DHIS2 is now using [transifex](www.transifex.com) as our main platform for +managing translations. You can access the DHIS2 resources at +[translate.dhis2.org](https://translate.dhis2.org), or directly at +https://www.transifex.com/hisp-uio/public. + +### How do I contribute to translations? { #how-do-i-contribute-to-translations } + +#### Register as a translator { #register-as-a-translator } + +The first step is to get access to the project. There are two ways to do this: + +1. Navigate to the platform and create an account with transifex, then + - request access to our organisation "HISP UiO" as a member of the "DHIS 2 Core Apps" translation team. + Transifex +have some useful instructions here: +[Getting Started as a Translator](https://docs.transifex.com/getting-started-1/translators) + +1. Email the DHIS 2 team at translate@dhis2.org to request access. +Please provide: + - the name, email address and translation language of the user(s) you would like us to give access to, and + - a little bit of information about why you are interested in contributing to the DHIS 2 translations + +#### Edit translations { #edit-translations } + +Once you have access as a translator, you can start translating through the transifex Web Editor. + +Transifex have a useful guide here: +[Translating Online with the Web Editor](https://docs.transifex.com/translation/translating-with-the-web-editor) + +As far as possible, the projects represent DHIS 2 apps one-to-one. For example, the **APP: Data Visualizer** project contains the translation strings for the Data Visualizer app. + +Our transifex projects for DHIS2 User Interface all start with one of the following: + +- **APP:** indicates that the project contains strings for a specific app +- **APP-COMPONENT:** indicates that the project is a component library used by the apps +- **ANDROID:** indicates that the project is an Andriod app + +In addition, **APP: Server-Side Resources** contains some strings that are used by several apps; namely: +- "Data Entry" +- "Maintenance" +- "Pivot Tables" +- "Reports" + +> **Tip** +> +> To ensure that there are full translations for a particular app, e.g. "Tracker Capture", you need to make sure translations are complete in: +> - The app project: **APP: Tracker Capture** +> - Any projects starting with **APP-COMPONENTS** +> - **APP: Server-Side Resources**, if required. For Tracker Capture this is **not required**. + + +Within the projects we have resources, which represent localization files in the source code. In order to support multiple DHIS2 versions, with the same localization files, the _version_ is associated with each instance of the file. So, for **APP: Data Visualizer** the list of resources looks like this in the Web Editor: + +![](resources/images/implementation_guide/transifex_data_vis.jpg) + +i.e. there is only one source resource for the app (`en.pot`), but we have added the versions from 2.31 (v31) up to the latest development (master). The version is shown in the "Category" field, and is also visible as a prefix to the resource name, e.g. `v31--en-pot`. + +> **Note** +> +> In general, we request translators focus on the "**master**" resource; it usually contains all strings from previous versions, and when translations are added the platform will fill in matching translations on the previous versions too. + + +### When will new translations be available in the system? { #when-will-new-translations-be-available-in-the-system } + +We have a nightly service that pulls new translations from the transifex platform and opens a pull request on the source code. + +The service loops over all projects and supported languages and does the following: + +1. Pulls localization files from transifex (**where translations are more than 20% complete**) +2. Raises a pull request on the source code if changes are found for the language + +The pull requests are reviewed and merged into the code base as part of the normal development process. + +> **Info** +> +> The translations adde to transifex will, in general, be in the next available stable release for all supported DHIS 2 versions +> +> _If you need to ensure that your translations are in the next stable release, contact us (translate@dhis2.org) expalining your needs, and we'll let you know what we can do._ + +> **Tip** +> +> The translations you add in transifex should be visible in all development demo versions on our play server (https://play.dhis2.org) within a few days, in most cases. + +### How do I add a new language? { #how-do-i-add-a-new-language } + +Please contact us via email translate@dhis2.org, or on the [Community of Practice](https://community.dhis2.org/c/translation) and we'll add that language to the projects on transifex. + +Once resources for that language are more than 20% translated, they will start to be pulled into the system. They will then +become visible in the development demo versions, and be available in future releases. + +> **Note** +> +> DHIS 2 manages metadata (database) locales independently from the UI. _See the following section._ + + +## Metadata/Database translations { #metadata-database-translations } + + + +In addition to translation of the user interface, DHIS 2 also supports +the localization of the metadata content in the database. It is possible +to translate individual objects through the **Maintenance app**, but in +order to better support a standard translation workflow, a specialized +app has been developed for this purpose. + +New metadata locales can be added in **Maintenance app > Locales**. + +### DHIS 2 Translations app { #translations-app } + + + +The DHIS 2 **Translation app** can +be used to translate all metadata (data elements, categories, +organization units, etc) into any locale which is present in the +database. + +To get started, simply choose the **Translations app** from the top level +menu. + +![](resources/images/i18n/translations_app.png) + +1. Choose the type of object you wish to translate from the **Object** + drop-down menu, such as "Data elements". + +2. Be sure you have set the **Target Locale** to the correct language. + +3. Choose the specific object you wish to translate, and translate each + of the properties (Name, Short name, Description, etc). These + properties vary from object to object. + +4. Press "Save" when you are done translating the specific object to + save your changes. + + +> **Note** +> +> You can search for a specific term using the search feature in the +upper right hand corner of the app. diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-237__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-237__installation-md index 4baa111dd..ca8871cb0 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-237__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-237__installation-md @@ -816,7 +816,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md index 8d7b12404..6002435f4 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/audit.md" revision_date: '2021-12-02' tags: -- Gestionar - DHIS core version 2.38 +- Gestionar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md index 7d0782957..0b77f5173 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/installation.md" revision_date: '2024-02-16' tags: -- Gestionar - DHIS core version 2.38 +- Gestionar --- # Instalación { #installation } @@ -830,7 +830,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md index 78f335879..a81da17a7 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- Gestionar - DHIS core version 2.38 +- Gestionar --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md index a6ed58fd5..7555ec135 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/upgrading.md" revision_date: '2021-08-18' tags: -- Gestionar - DHIS core version 2.38 +- Gestionar --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md index bd62c6883..bbc0f54da 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/SMS-reporting.md" revision_date: '2021-06-14' tags: -- Gestionar - DHIS core version 2.38 +- Gestionar --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md index f802c8a9b..a74617786 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- Gestionar - DHIS core version 2.39 +- Gestionar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md index bcc6c1d57..fa2a934ea 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/installation.md" revision_date: '2024-02-16' tags: -- Gestionar - DHIS core version 2.39 +- Gestionar --- # Instalación { #installation } @@ -834,7 +834,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md index d0a24dbd8..0e82eb189 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- Gestionar - DHIS core version 2.39 +- Gestionar --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md index 5f18d07c1..e3a4178f5 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Gestionar - DHIS core version 2.39 +- Gestionar --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md index b6c978390..09fd00713 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Gestionar - DHIS core version 2.39 +- Gestionar --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md index f10bf8073..a2b3120b5 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- Gestionar - DHIS core version 2.40 +- Gestionar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md index f3a02e02b..57da9f8ed 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md @@ -2,13 +2,13 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Gestionar - DHIS core version 2.40 +- Gestionar --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } -## Overview { #overview } +## Visión general { #overview } User impersonation, also known as user switching, is a powerful feature provided in DHIS2 for administrative users to log in as another user. This feature is especially useful for troubleshooting or resolving user-related issues, as it @@ -57,7 +57,7 @@ Follow these steps to use the user impersonation feature: 6. When you're finished, navigate to the URL to end impersonation (e.g., `/impersonateExit`). Your session will be switched back to your original administrative user. -## Configuration { #configuration } +## Configuración { #configuration } The user impersonation feature configuration options. diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md index d8a602814..67cd3c898 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- Gestionar - DHIS core version 2.40 +- Gestionar --- # Instalación { #installation } @@ -834,7 +834,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md index 3c08c5d7e..285a52232 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- Gestionar - DHIS core version 2.40 +- Gestionar --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md index 4b46a40e7..9b69a8937 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Gestionar - DHIS core version 2.40 +- Gestionar --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md index bf5bb113e..3689506dc 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Gestionar - DHIS core version 2.40 +- Gestionar --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md index b33fe2e52..49343282d 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- Gestionar - DHIS core version 2.41 +- Gestionar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md index 17adc9296..b5c439933 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md @@ -2,13 +2,13 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Gestionar - DHIS core version 2.41 +- Gestionar --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } -## Overview { #overview } +## Visión general { #overview } User impersonation, also known as user switching, is a powerful feature provided in DHIS2 for administrative users to log in as another user. This feature is especially useful for troubleshooting or resolving user-related issues, as it @@ -57,7 +57,7 @@ Follow these steps to use the user impersonation feature: 6. When you're finished, navigate to the URL to end impersonation (e.g., `/impersonateExit`). Your session will be switched back to your original administrative user. -## Configuration { #configuration } +## Configuración { #configuration } The user impersonation feature configuration options. diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md index e23e907b5..1bccc3746 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- Gestionar - DHIS core version 2.41 +- Gestionar --- # Instalación { #installation } @@ -883,7 +883,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md index 50df28773..a025838e2 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/monitoring.md" revision_date: '2023-09-25' tags: -- Gestionar - DHIS core version 2.41 +- Gestionar --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md index fe6838db7..f5d7597d8 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Gestionar - DHIS core version 2.41 +- Gestionar --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md index 80389d2c9..8464e7dca 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Gestionar - DHIS core version 2.41 +- Gestionar --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index fd1b0cc2a..b67387985 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- Gestionar - DHIS core version master +- Gestionar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index 7856db8f7..3646f6a89 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md @@ -2,13 +2,13 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Gestionar - DHIS core version master +- Gestionar --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } -## Overview { #overview } +## Visión general { #overview } User impersonation, also known as user switching, is a powerful feature provided in DHIS2 for administrative users to log in as another user. This feature is especially useful for troubleshooting or resolving user-related issues, as it @@ -57,7 +57,7 @@ Follow these steps to use the user impersonation feature: 6. When you're finished, navigate to the URL to end impersonation (e.g., `/impersonateExit`). Your session will be switched back to your original administrative user. -## Configuration { #configuration } +## Configuración { #configuration } The user impersonation feature configuration options. diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index d32e75d6d..364e7cd01 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/installation.md" revision_date: '2024-06-18' tags: -- Gestionar - DHIS core version master +- Gestionar --- # Instalación { #installation } @@ -883,7 +883,7 @@ The DHIS2 Android client is such a type of client and have to use JWT authentica > DHIS2 currently only supports using Google as an OIDC provider when using JWT tokens -### Requirements { #requirements } +### Requisitos { #requirements } * Configure your Google OIDC provider as described above * Disable the config parameter ```oauth2.authorization.server.enabled``` by setting it to 'off' * Enable the config parameter ```oidc.jwt.token.authentication.enabled``` by setting it to 'on' diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md index 88d432ad9..efdbe3e70 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CHIS-COMMUNITY-HEALTH-INFORMATION-SYSTEM__installation-md @@ -7,7 +7,7 @@ tags: # CHIS Installation Guide { #chis-agg-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing configuration packages for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -40,7 +40,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -59,34 +59,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -99,30 +99,30 @@ The .json metadata file is imported through the [Import/Export](#import_export) If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -140,7 +140,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -157,7 +157,7 @@ The user groups that usually come with the package include: We recommend to provide the following access to these groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_{Package Name} access_|_{Package Name} admin_|_{Package Name} data capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -165,7 +165,7 @@ We recommend to provide the following access to these groups |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md index 394cb8bc1..7d84e84d9 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -7,7 +7,7 @@ tags: # Aggregate Package Installation Guide { #c19-agg-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing the COVID-19 standard configuration package for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -39,7 +39,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -58,34 +58,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -98,30 +98,30 @@ The .json metadata file is imported through the [Import/Export](https://docs.dhi If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -139,7 +139,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -156,7 +156,7 @@ There are three user groups that come with the package: We recommend the following access -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -164,7 +164,7 @@ We recommend the following access |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE-TRACKER__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE-TRACKER__installation-md index 534d05edc..da82bc3f2 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE-TRACKER__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE-TRACKER__installation-md @@ -16,7 +16,7 @@ You will have to follow the instructions in full for each separate package that ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -35,7 +35,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension { #default-data-dimension } @@ -43,12 +43,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. @@ -58,18 +58,18 @@ You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | #### Tracked Entity Type { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | ------ | ----------- | ---------------------------------------------------- | -| Person | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | +| Persona | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | ## Importing metadata { #importing-metadata } @@ -87,27 +87,27 @@ Rename the existing object in your DHIS2 database for which there is a conflict. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros @@ -120,7 +120,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _COVID19 access_ | _COVID19 admin_ | _COVID19 data capture_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | @@ -132,10 +132,10 @@ You will want to assign your users to the appropriate user group based on their ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. @@ -147,7 +147,7 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -155,9 +155,9 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md index 863b2be91..374940989 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -7,7 +7,7 @@ tags: # COVID-19 Surveillance - Installation Guide { #c19-cs-installation } -## Overview { #overview } +## Visión general { #overview } The COVID-19 tracker package was developed using DHIS2.33.2. This was done in order to support some of the latest features in DHIS2. In order to use the package, it is recommended that you install it into a DHIS2 instance using DHIS2 2.33.2 or above. If you will be setting this up on a new instance, please refer to the [DHIS2 installation guide](https://docs.dhis2.org/en/manage/performing-system-administration/dhis-core-version-master/installation.html). This document covers the installation of the following packages: @@ -18,7 +18,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -27,89 +27,89 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. ***Note that this search and replace operation must be done with a plain text editor***, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| #### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| +|Persona|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } ***NOTE***: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -122,7 +122,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| |_*Tracked entity type*_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and view| @@ -132,24 +132,24 @@ By default the following is assigned to these user groups You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -157,10 +157,10 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 000000000..b21c4cb6a --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md @@ -0,0 +1,56 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Metadatos +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Visión general { #overview } + +We have made several updates to the existing package to align with new COVID-19 [surveillance guidelines released by the WHO on March 20, 2020](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and introduced new components to the overall package of support. Please review the notes here and contact us on the COVID-19 discussion board in the [community of practice](https://community.dhis2.org/c/implementation/covid-19/) with any questions. + +**All metadata packages and documentation can be downloaded from [dhis2.org.covid-19](https://www.dhis2.org/covid-19).** + +Packages are currently translated into French, Spanish, Portuguese and Russian, with additional languages in the pipeline (Arabic, Lao, Burmese). We can support metadata package translations in our global translation platform and invite the community to contribute if your country is interested in translating the package for a new language. [Check out our Community of Practice announcement](https://community.dhis2.org/t/the-new-dhis2-translation-platform-is-now-available/37755)and get started as a contributing translator here [by joining the DHIS2 translation platform](https://docs.dhis2.org/en/implement/understanding-dhis2-implementation/localization-of-dhis2.html). Please contact us at translate@dhis2.org. + +The new release includes: + +1. COVID-19 Case-based Surveillance Tracker program +2. COVID-19 Contact Registration & Follow-Up program +3. COVID-19 Aggregate Surveillance Reporting +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Metadata codes updated to align with the [WHO case-based reporting data dictionary](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Program indicators updated to reflect new WHO case definitions for probable cases (reference the updated case definitions in the interim surveillance guidelines updated March 20, 2020 [WHO interim surveillance guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Age legends have been updated to meet new WHO guidance for weekly reporting +4. relationshipType added to metadata package +5. Minor fixes to the metadata to enable easier installation of the package (i.e. indicatorType UID matches indicator type included in aggregate package) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. A new program stage has been added to enable repeatable ‘follow-up’ of a case contact. This was added to reflect workflows implemented in Uganda and Togo where contacts may be monitored repeatedly over the course of 14 days to determine if there are symptoms. The ***program*** is based on WHO guidelines which can be found [here](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), as well as information obtained via the [OpenWHO](https://openwho.org/courses/introduction-to-ncov) website. +2. Age legends have been updated to meet new WHO guidance for weekly reporting +3. relationshipType added to metadata package +4. Minor fixes to the metadata to enable easier installation of the package + +### COVID-19 Aggregate Surveillance Reporting { #covid-19-aggregate-surveillance-reporting } + +The following updates were made to reflect new guidance in [WHO guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), including updated global aggregate reporting to WHO (weekly & daily) + +1. Age categories updated according to new age groups +2. New indicators added for proportion of males among confirmed cases and proportion of males among confirmed deaths +3. New weekly dataset to capture classification of transmission at sub-national level one (i.e. provincial -- can be assigned to any sub-national level as appropriate in country) per updated WHO weekly reporting guidelines +4. Minor fixes to the metadata to enable easier installation of the package + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +The Points of Entry tracker program use case was designed to support the registration of travellers entering a country with a history of travel to, or residence in, a country/area/territory reporting local transmission of COVID-19 who may need to be followed up to ensure no symptoms develop. It is based on the design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health with minor changes to make the program more generic to global use and to align with the other tracker programs in the COVID-19 package. The package supports interventions at Points of Entry detailed in the WHO [technical guidance for the management of ill persons at points of entry](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings). + +Please read more about the POE program in the [system design document](https://docs.dhis2.org/en/topics/metadata/covid-19-surveillance/covid-19-poe-tracker-design.html). + diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER-DISCONTINUED__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER-DISCONTINUED__installation-md index 534d05edc..da82bc3f2 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER-DISCONTINUED__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER-DISCONTINUED__installation-md @@ -16,7 +16,7 @@ You will have to follow the instructions in full for each separate package that ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -35,7 +35,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension { #default-data-dimension } @@ -43,12 +43,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. @@ -58,18 +58,18 @@ You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | #### Tracked Entity Type { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | ------ | ----------- | ---------------------------------------------------- | -| Person | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | +| Persona | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | ## Importing metadata { #importing-metadata } @@ -87,27 +87,27 @@ Rename the existing object in your DHIS2 database for which there is a conflict. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros @@ -120,7 +120,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _COVID19 access_ | _COVID19 admin_ | _COVID19 data capture_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | @@ -132,10 +132,10 @@ You will want to assign your users to the appropriate user group based on their ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. @@ -147,7 +147,7 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -155,9 +155,9 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER__installation-md index 534d05edc..da82bc3f2 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POE-TRACKER__installation-md @@ -16,7 +16,7 @@ You will have to follow the instructions in full for each separate package that ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -35,7 +35,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension { #default-data-dimension } @@ -43,12 +43,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. @@ -58,18 +58,18 @@ You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | #### Tracked Entity Type { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | ------ | ----------- | ---------------------------------------------------- | -| Person | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | +| Persona | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | ## Importing metadata { #importing-metadata } @@ -87,27 +87,27 @@ Rename the existing object in your DHIS2 database for which there is a conflict. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros @@ -120,7 +120,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _COVID19 access_ | _COVID19 admin_ | _COVID19 data capture_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | @@ -132,10 +132,10 @@ You will want to assign your users to the appropriate user group based on their ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. @@ -147,7 +147,7 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -155,9 +155,9 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__installation-md index 534d05edc..da82bc3f2 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__installation-md @@ -16,7 +16,7 @@ You will have to follow the instructions in full for each separate package that ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -35,7 +35,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension { #default-data-dimension } @@ -43,12 +43,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through as bRowv6yZOF2. @@ -58,18 +58,18 @@ You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | #### Tracked Entity Type { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | ------ | ----------- | ---------------------------------------------------- | -| Person | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | +| Persona | MCPQUTHX1Ze | ../api/trackedEntityTypes.json?filter=name:eq:Person | ## Importing metadata { #importing-metadata } @@ -87,27 +87,27 @@ Rename the existing object in your DHIS2 database for which there is a conflict. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros @@ -120,7 +120,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _COVID19 access_ | _COVID19 admin_ | _COVID19 data capture_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | @@ -132,10 +132,10 @@ You will want to assign your users to the appropriate user group based on their ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. @@ -147,7 +147,7 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -155,9 +155,9 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__installation-md index b90480b9a..1548e370a 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__installation-md @@ -19,7 +19,7 @@ The COVID-19 event package was developed using DHIS2.33.2. This was done in orde ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -38,7 +38,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-metadata)”. -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension { #default-data-dimension } @@ -46,12 +46,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. @@ -61,7 +61,7 @@ You could then search and replace all occurrences of `HllvX50cXC0` with `bRowv6y Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Porcentaje | DadSzqgyAex | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | @@ -83,21 +83,21 @@ Rename the existing object in your DHIS2 database for which there is a conflict. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } @@ -114,7 +114,7 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _*COVID19 access*_ | _*COVID19 admin*_ | _*COVID19 data capture*_ | | _*Program*_ | Metadata: can view
Data: can view | Metadata: can edit and view
Data: can view | Metadata: can view
Data: can capture and view | @@ -126,8 +126,8 @@ You will want to assign your users to the appropriate user group based on their Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles for end-users are recommended: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. @@ -139,7 +139,7 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE**: This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to “[Adapting the tracker program](#adapting-the-event-program).” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). @@ -147,9 +147,9 @@ One important thing to keep in mind is that DHIS2 has tools that can hide some o Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 000000000..b21c4cb6a --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-SURVEILLANCE__release-note-md @@ -0,0 +1,56 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Metadatos +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Visión general { #overview } + +We have made several updates to the existing package to align with new COVID-19 [surveillance guidelines released by the WHO on March 20, 2020](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and introduced new components to the overall package of support. Please review the notes here and contact us on the COVID-19 discussion board in the [community of practice](https://community.dhis2.org/c/implementation/covid-19/) with any questions. + +**All metadata packages and documentation can be downloaded from [dhis2.org.covid-19](https://www.dhis2.org/covid-19).** + +Packages are currently translated into French, Spanish, Portuguese and Russian, with additional languages in the pipeline (Arabic, Lao, Burmese). We can support metadata package translations in our global translation platform and invite the community to contribute if your country is interested in translating the package for a new language. [Check out our Community of Practice announcement](https://community.dhis2.org/t/the-new-dhis2-translation-platform-is-now-available/37755)and get started as a contributing translator here [by joining the DHIS2 translation platform](https://docs.dhis2.org/en/implement/understanding-dhis2-implementation/localization-of-dhis2.html). Please contact us at translate@dhis2.org. + +The new release includes: + +1. COVID-19 Case-based Surveillance Tracker program +2. COVID-19 Contact Registration & Follow-Up program +3. COVID-19 Aggregate Surveillance Reporting +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Metadata codes updated to align with the [WHO case-based reporting data dictionary](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Program indicators updated to reflect new WHO case definitions for probable cases (reference the updated case definitions in the interim surveillance guidelines updated March 20, 2020 [WHO interim surveillance guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Age legends have been updated to meet new WHO guidance for weekly reporting +4. relationshipType added to metadata package +5. Minor fixes to the metadata to enable easier installation of the package (i.e. indicatorType UID matches indicator type included in aggregate package) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. A new program stage has been added to enable repeatable ‘follow-up’ of a case contact. This was added to reflect workflows implemented in Uganda and Togo where contacts may be monitored repeatedly over the course of 14 days to determine if there are symptoms. The ***program*** is based on WHO guidelines which can be found [here](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), as well as information obtained via the [OpenWHO](https://openwho.org/courses/introduction-to-ncov) website. +2. Age legends have been updated to meet new WHO guidance for weekly reporting +3. relationshipType added to metadata package +4. Minor fixes to the metadata to enable easier installation of the package + +### COVID-19 Aggregate Surveillance Reporting { #covid-19-aggregate-surveillance-reporting } + +The following updates were made to reflect new guidance in [WHO guidelines updated March 20, 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), including updated global aggregate reporting to WHO (weekly & daily) + +1. Age categories updated according to new age groups +2. New indicators added for proportion of males among confirmed cases and proportion of males among confirmed deaths +3. New weekly dataset to capture classification of transmission at sub-national level one (i.e. provincial -- can be assigned to any sub-national level as appropriate in country) per updated WHO weekly reporting guidelines +4. Minor fixes to the metadata to enable easier installation of the package + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +The Points of Entry tracker program use case was designed to support the registration of travellers entering a country with a history of travel to, or residence in, a country/area/territory reporting local transmission of COVID-19 who may need to be followed up to ensure no symptoms develop. It is based on the design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health with minor changes to make the program more generic to global use and to align with the other tracker programs in the COVID-19 package. The package supports interventions at Points of Entry detailed in the WHO [technical guidance for the management of ill persons at points of entry](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings). + +Please read more about the POE program in the [system design document](https://docs.dhis2.org/en/topics/metadata/covid-19-surveillance/covid-19-poe-tracker-design.html). + diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-100__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-100__installation-md index f09aa0ca4..b7820819b 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-100__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-100__installation-md @@ -63,7 +63,7 @@ The [Configuration](https://who.dhis2.org/documentation/installation_guide_compl **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Default data dimension { #default-data-dimension } @@ -71,12 +71,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. @@ -84,9 +84,9 @@ For example, if importing a configuration package into [https://play.dhis2.org/d Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -113,16 +113,16 @@ Rename the existing object for which there is a conflict. The advantage of this Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: - it requires expert knowledge of the detail metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. - as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -- future updates to the configuration package will be complicated. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -157,7 +157,7 @@ There are three user groups that come with the package: We recommend the following access -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _COVAC access_ | _COVAC admin_ | _COVAX capture_ | | _Data Elements/Data element group_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-110__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-110__installation-md index 0a1a6d7ed..64af1d3f0 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-110__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__VERSION-110__installation-md @@ -63,7 +63,7 @@ The [Configuration](https://who.dhis2.org/documentation/installation_guide_compl **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Default data dimension { #default-data-dimension } @@ -71,12 +71,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. @@ -84,9 +84,9 @@ For example, if importing a configuration package into [https://play.dhis2.org/d Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -113,16 +113,16 @@ Rename the existing object for which there is a conflict. The advantage of this Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: - it requires expert knowledge of the detail metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. - as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -- future updates to the configuration package will be complicated. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -157,7 +157,7 @@ There are three user groups that come with the package: We recommend the following access -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _COVAC access_ | _COVAC admin_ | _COVAX capture_ | | _Data Elements/Data element group_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md index ec36f34e7..36513aa05 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVAC-AGGREGATE__installation-md @@ -7,7 +7,7 @@ tags: # Aggregate Package Installation Guide { #cvc-agg-installation } -## Overview { #overview } +## Visión general { #overview } This document is intended to guide administrators through the process of installing the COVID-19 vaccination standard configuration package for DHIS2 for aggregate reporting. Good understanding of DHIS2 is required. @@ -39,7 +39,7 @@ Multiple configuration packages Some configuration packages have overlapping metadata, for example indicators. This means that in some situations, changes to metadata to configuration packages that have been imported previously may be overwritten when importing a different package. This can be avoided by importing "new only" metadata rather than "new and updates", but note that with either approach manual modifications will be needed. At a minimum, you must ensure that metadata used by multiple programmes are [shared](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) with the appropriate user groups for both programmes. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the configuration package, an administrator user account in DHIS2 is required, with authorities to add/edit (public) metadata objects, including (but not limited to): @@ -58,34 +58,34 @@ The configuration package can be installed in DHIS2 through the DHIS2 Health App The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Default data dimension { #default-data-dimension } +## Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| |Categoría |GLevLNI9wkl|../api/categories.json?filter=name:eq:default| |Opción de categoría|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| |Combinación de categoría|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| -|Category option combination|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| +|Combinación de opciones de categoría|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -## Indicator types { #indicator-types } +## Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -|Object|UID|API endpoint| +|Objeto|UID|API endpoint| |--|--|--| -|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Sólo numerador (número)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| |Porcentaje|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -98,30 +98,30 @@ The .json metadata file is imported through the [Import/Export](https://docs.dhi If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } **NOTE** If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the “[Additional configuration](#additional-configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes is instead done through user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: * it requires expert knowledge of the detail metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. * as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -* future updates to the configuration package will be complicated. +* las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -139,7 +139,7 @@ The data sets should be assigned to the organisation units (facilities) which ar The data sets and category options should also be shared with the relevant user group(s) of the personnel who are responsible for doing data entry for those data sets. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. Sharing should been configured for the following: @@ -156,7 +156,7 @@ There are three user groups that come with the package: We recommend the following access -|Object|User Group||| +|Objeto|User Group||| |--|--|--|--| ||_COVAC access_|_COVAC admin_|_COVAX capture_| |_Data Elements/Data element group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| @@ -164,7 +164,7 @@ We recommend the following access |_Data sets_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can capture and can view| |_Dashboards_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - whether it's a chart, indicator, data element or data element category that already exists. As was noted in the section above on resolving conflict, an important issues to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY-TRACKER__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY-TRACKER__installation-md index fad623e44..52c3527a7 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY-TRACKER__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY-TRACKER__installation-md @@ -7,13 +7,13 @@ revision_date: "2022-01-19" This document includes an installation guide for the updated COVAC Electronic Immunization Registry tracker package and a supplementary aggregate module for daily reporting based on tracker data. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -117,29 +117,29 @@ The package metadata json files contain a "package" component that provides tech ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Covid-19 Electronic Immunization Registry tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -202,42 +202,42 @@ These program indicators are part of the original package but need to be updated ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Indicator types { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número) | `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Tracked Entity Type { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -318,51 +318,51 @@ Sort order can be adjusted in the Maintenance app. ## Importing metadata { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Handling import conflicts { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Four core user groups are included in the package: @@ -373,7 +373,7 @@ Four core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | | +| Objeto | User Group | | | | | --- | --- | --- | --- | --- | | | _COVAC - COVID-19 Immunization Data Analysis_ | _COVAC - COVID-19 Immunization Data Admin_ | _COVAC - COVID-19 Immunization Data Entry_ | _COVAC - COVID-19 Immunization Metadata Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | @@ -386,12 +386,12 @@ The users are assigned to the appropriate user group based on their role within ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } @@ -403,20 +403,20 @@ The program and the data sets must be assigned to organisation units within exis > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Removing metadata { #removing-metadata } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md index 48b4e8ae3..a53482ac2 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__COVID-19-VACCINE-DELIVERY__COVID-19-ELECTRONIC-IMMUNIZATION-REGISTRY__installation-md @@ -9,35 +9,35 @@ tags: This document includes an installation guide for the updated COVAC Electronic Immunization Registry tracker package and a supplementary aggregate module for daily reporting based on tracker data. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Covid-19 Electronic Immunization Registry tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -52,7 +52,7 @@ The Covid-19 Electronic Immunization Registry tracker package includes three met > The package is not an out-of-the-box tool for tracker-to-aggregate data transfer. > The structure of the metadata package and the suggested mapping of metadata allow the implementer to set up the transfer of data based on existing tools and guidance. More information is available in the [Tracker to aggregate data Transfer Document](https://docs.dhis2.org/en/implement/maintenance-and-use/tracker-and-aggregate-data-integration.html#how-to-saving-aggregated-tracker-data-as-aggregate-data-values). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } ### Mapping guide for data transfer { #mapping-guide-for-data-transfer } @@ -100,44 +100,44 @@ These program indicators are part of the original package but need to be updated > If the original program indicators in your system were modified as part of local adaptation process, be aware that all changes will be overwritten once you import the updated set of program indicators. > If any of your modified program indicators have the same UID as the program indicators listed in the table above, make sure to duplicate the modified program indicators before import. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|----------------------------------------| -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -219,53 +219,53 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros -* Visualizations, maps, event reports and report tables -* Data sets -* Category options +* Visualizaciones, mapas, informes de eventos y tablas de informes +* Sets de datos +* Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Four core user groups are included in the package: @@ -276,7 +276,7 @@ Four core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | | +|Objeto |User Group | | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------------------------------| | | _COVAC - COVID-19 Immunization Data Analysis_ | _COVAC - COVID-19 Immunization Data Admin_ | _COVAC - COVID-19 Immunization Data Entry_ | _COVAC - COVID-19 Immunization Metadata Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | @@ -289,40 +289,40 @@ The users are assigned to the appropriate user group based on their role within ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__change-log-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__change-log-md new file mode 100644 index 000000000..91e608c14 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__change-log-md @@ -0,0 +1,82 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/changelog.md" +revision_date: "2021-09-23" +--- + +# WHO Cause of Death - Change log { #cod-change-log } + +## 1.2.0 { #120 } + +### General changes { #general-changes } + +- All SQL views have been reconfigured for the newer versions of DHIS2. + +| Nombre | id | Programa | +| :-- | --- | --- | +| CoD: Anacod export 2017 | nOrVs1Gi9Nt | Evento | +| CoD: Anacod export 2018 | iy8xEmIhMph | Evento | +| CoD: Anacod export 2019 | ojaXg9yV9is | Evento | +| CoD: Anacod export 2020 | atLa12jpN4y | Evento | +| CoD: Anacod export 2017 | fn3zQtRrETh | Tracker | +| CoD: Anacod export 2018 | KdIAkgUzCv7 | Tracker | +| CoD: Anacod export 2019 | xzxuZVKZw3A | Tracker | +| CoD: Anacod export 2020 | hMLDxoR33ej | Tracker | +| CoD: Dictionary entries mixing main- and sub-categories | Siuqk0lMzC7 | Event and Tracker | +| CoD: Dictionary entries with invalid ICD-SMoL reference | nWsSOLLJPjG | Event and Tracker | +| CoD: Dictionary entries with invalid code format | dS3uFpYtlss | Event and Tracker | +| CoD: Dictionary terms with ICD (for IRIS) | DNveLCRg2zU | Event and Tracker | +| CoD: Next dictionary index number | ekC6LY25qMk | Event and Tracker | +| CoD: Terms not found in dictionary | ZVl5kudO8Vt | Evento | +| CoD: Terms not found in dictionary | hhrfqhx47bt | Tracker | + +- Standard reports (Validation) for Event and Tracker programs have been reconfigured. It is possible to open applicable enrollments/events directly from the standard report form by using the right-click. + +- Duplicate options from **ICD-SMoL - local dictionary** option set were removed. Additional COVID-19 related options were added. See metadata reference file for details. All option names were changed to all-caps format. + +- ID replacement + +| Objeto | Property | Old value | New value | Programa | +| --- | --- | --- | --- | --- | +| option | id | CvivP1rh4ii | x9yVKkv9koc | Event and Tracker | +| option | id | PLlPgcfbL1D | R98tI2c6rF5 | Event and Tracker | +| option | id | TKD1XJ4ZhMO | pqxvAQU1z9W | Event and Tracker | +| optionSet | id | bLA3AqDKdwx | L6eMZDJkCwX | Event and Tracker | +| indicatorType | id | e1jRVY5Mcq0 | hmSnCXmLYwt | Event and Tracker | +| trackedEntityAttribute | id | flGbXLXCrEo | HAZ7VQ730yn | Tracker | +| dataElement | id | YUcJrLWmGyv | G5ljtyKdtYU | Event and Tracker | + +- French Dictionary for the localised French package + +The French localised version of the Cause of Death package uses a different **ICD-SMoL - local dictionary** than the generic package. It consists of different options and uses `INT_FRxxxxx` as a prefix in the segment 3 of the option code. See metadata reference file for the French localised package for more details. + +## 1.1.0 { #110 } + +### Tracker { #tracker } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` + +### Event { #event } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__installation-md new file mode 100644 index 000000000..c2c58b101 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER-DISCONTINUED__installation-md @@ -0,0 +1,132 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/crvs_cod-installation.md" +revision_date: "2022-09-19" +--- + +# WHO Cause of Death - Tracker Installation Guide { #crvs-cod-installation } + +## Introducción { #introduction } + +This document is intended to guide administrators though the process of installing the Cause of Death module in a DHIS 2 database. Good understanding of DHIS 2, including the Tracker (case-based) functionality is required. + +The Cause of Death module consists of a file with DHIS 2 metadata. More specifically, it includes: + +For Tracker program: + +- A tracker program with data elements, option sets, custom data entry form, program rules, program indicators etc. +- A standard report for validation of data. +- A dashboard with charts and tables for key data. +- This document describes how to install this module, and perform routine maintenance. This includes the critical task of adapting and improving the dictionary of diagnosis/medical terms, which is essential for the functioning of the module. + +In addition, a [node.js](https://nodejs.org/en/) script for linking the Cause of Death module in DHIS 2 with the [IRIS software](https://www.dimdi.de/dynamic/en/classifications/iris-institute/index.html) for semi-automatic coding of causes of death to full ICD-10 and sending the result back to the DHIS 2 database. Outputs are provided to export this again data to the ANACOD data analysis tool. This functionality is described in a separate document. + +## Description of the module { #description-of-the-module } + +This section gives an overview of the design and structure of the module. + +### The data collection form { #the-data-collection-form } + +The data collection form is created based on the International Medical Certificate of Causes of Death. As such, it uses a custom form that mimics the layout of this certificate. However, the logic built into the form for coding and validation also works without the custom form, allowing the module to be used on e.g. mobile devices with the DHIS 2 android applications. + +### Dealing with "Age" { #dealing-with-age } + +For collecting data on the age of the deceased, the data collection form supports use of both date of birth and an estimated age. To facilitate analysis of the data, an additional data element for Age in years has been added to the form, but as a disabled/read-only field. Based on what is entered either as date of birth or estimated age, program rules calculate the age in years and assigns that value to the Age in years data element. + +### Dictionary { #dictionary } + +A critical component of the module is a dictionary (ICD-SMoL - local dictionary). The dictionary functions as a link between the medical terms used in data entry, and the ICD-SMoL code used for reporting and analysis of causes of death. In DHIS 2, the dictionary is implemented as an option set. The medical term is the option name, and the option code is made up of three components: the ICD-SMoL code, the ICD-10 code, and an ID. The ID is necessary because several terms could refer to the same ICD-SMoL and ICD-10 codes, and codes need to be unique. The ID itself consists of two parts: a country code (or INT for the ones provided with the module) and a counter. Keeping track of the international and country-specific terms will make it easier in the future to e.g. identify terms used in different countries which could be proposed for the international dictionary. + +Fully localised French "Cause of Death" module uses a local dictionary that is different from the English ICD-SMoL - local dictionary. This dictionary is maintained in a different option set that is only included in the French package file. + +The dictionary is sorted by length of the term, with the shortest terms appearing first. This ensures that as users search the dictionary, the terms where the largest proportion of the medical term matches with the search term is displayed first. + +### Selecting underlying cause of death { #selecting-underlying-cause-of-death } + +Selecting the underlying cause of death is a key component of the module. This is done through four checkboxes, which indicate which of the (up to) four causes is the underlying cause. Program rules are used to ensure that only one of the checkboxes can be selected, and that each checkbox can only be used if a diagnosis has been selected for that line/cause. + +Once a cause has been selected as underlying, two read-only fields are assigned with the ICD-SMoL name and code for the selected cause. + +## Installation { #installation } + +### Requirements and preparation { #requirements-and-preparation } + +In order to install the module, an administrator user account on DHIS 2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS 2. + +Great care should be taken to ensure that the server itself and the DHIS application is well secured, to restrict access to the data being collected. Even if using this module without any direct patient identifiers like ID or names, the age, sex and health facility could be sufficient to identify an individual. Details on securing a DHIS 2 system is outside the scope of this document, and we refer to the DHIS 2 documentation. + +### Choosing a version of the module { #choosing-a-version-of-the-module } + +### Importing metadata { #importing-metadata } + +The module is imported through a `.json` file with DHIS 2 metadata, using the Metadata import feature of the DHIS 2 Import/Export app. When importing the metadata in a DHIS 2 database with existing metadata, you might see errors if you look at the detailed import summary. These could require action, for example if a data element with the same name or code already exists in the database your are importing the module into. In this case, you will either have to change the identifier (name, code) in the database, or modify the name/code in the import file. Any such modifications should be done first in a test or staging environment, to make sure the changes do not affect other parts of the system. + +### Additional configuration { #additional-configuration } + +Once all metadata has been successfully imported, there are a few steps that needs to be taken before the module is functional. + +1. The programme must be assigned to a new or existing user role before users can start entering data. In addition, users need to have the necessary authorities in order to enter and/or see tracker data. Refer to the DHIS 2 Documentation for more information on configuring user roles. + +2. The programme must be assigned to the organisation units for which data will be entered. + +3. Optionally, you might also want to use the Sharing functionality of DHIS 2 to configure which users (user groups) should see the metadata and data associated with the programme. Sharing can be configured for the program itself, data elements, program indicators, aggregate indicators, option sets, and the analytical outputs. + +### Adapting the tracker program { #adapting-the-tracker-program } + +Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that could be made include: + +- Añadir variables adicionales al formulario. +- For the tracker programme, linking the programme to an existing tracked entity type and/or modifying the tracked entity attributes. A placeholder tracked entity is included in the module. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- However, it is strongly recommended not to change or remove any of the included form/metadata. This is both because the included variables are the standard recommended variables from the international death notification form, and because there is a danger that modifications could break functionality, for example program rules and program indicators. For example almost all variables in the form are linked to one or more program rules, which would cease to function if the variable is removed or replaced. Changing the default variables could also complicate updates to the module in the future. + +### Maintenance { #maintenance } + +Maintenance of the module has two main aspects: maintenance of the dictionary of medical terms, and maintenance related to new versions of DHIS 2. Each of these aspectes will be described here. + +#### Dictionary maintenance { #dictionary-maintenance } + +The dictionary of medical terms is a key component of the module, and is critical in order to produce meaningful data. This section describes how to check the integrity of the dictionary (e.g. that the codes used are valid), list terms that have been collected which are not in the dictionary and should thus be considered for inclusion, and how to add new terms to the dictionary. Several SQL-views are included in the module to facilitate these tasks. + +#### Checking integrity of dictionary { #checking-integrity-of-dictionary } + +As described above, the dictionary is implemented as an option set in DHIS 2, with the medical term as the option name and a special format for the option code that consists of the ICD-SMoL code, ICD-10 code and an ID separated by the | (pipe) symbol. SQL-views are included to verify that all entries in the dictionary follow this format: + +- Dictionary entries with invalid code format - list entries where the code does not follow the format of `[content]|[content]|[content]`. +- Dictionary entries with invalid ICD-SMoL reference - list entries where the ICD-SMoL-part of the code is not in the ICD-SMoL list, which is provided as a separate option set. +- Dictionary entries mixing main- and sub-categories - list entries where, for the same ICD-SMoL code, some entries link to the main ICD-SMoL code and some to the specific code (e.g. some to 5-4 and 5-4.1). This can create misleading outputs when analysing data within DHIS 2 as deaths might be double counted. + +#### Adding terms to the dictionary { #adding-terms-to-the-dictionary } + +An SQL view "Terms not found in dictionary" is included that will list all medical terms that have been entered as free text, i.e. which were not found in the dictionary during data entry, and the number of times they have been entered. These are terms that should be considered for inclusion in the dictionary if they occur frequently and are meaningful. + +Before a term can be added to the dictionary, the correct ICD-SMoL and ICD-10 code must be identified. Together with the ID, these make up the code to be used in the dictionary. To find the ID, an SQL view Next dictionary index number is included that will show the next ID to use. It has two columns, termtype and nextvalue. As discussed above, it is recommended that each country uses a county code for local additions to the dictionary, in which case that code will be listed under termtype and the next number to use in the nextvalue column. If no local terms have yet been added, use [country code]00001 as the first ID, e.g. GH00001 if using GH as country code. Once the first local term has been added, the SQL view will show the next ID to use at any time. + +To ensure that the right terms are displayed first in the dictionary, it must be sorted by the length of the term. After adding new terms to the dictionary, it must be re-sorted so that the new terms are not always last in the list. This can be done with the follwing SQL query (for PostgreSQL databases): + +```sql + with ordered as ( + select + uid, + name, + code, + row_number() OVER (ORDER BY length(name),name) AS sort_order + from optionvalue + where + optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY') + ) + update optionvalue ov + set sort_order = ord.sort_order + from ordered ord + where + ov.uid = ord.uid and + ov.optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY'); +``` + +**Note** that this is an UPDATE query that must be executed directly in the database, not through the DHIS2 user interface. + +Upgrading DHIS + +When new versions of DHIS2 are released, it is important to test all functionality of the module on a staging/test server before upgrading any production instances of system. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__change-log-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__change-log-md new file mode 100644 index 000000000..91e608c14 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__change-log-md @@ -0,0 +1,82 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/changelog.md" +revision_date: "2021-09-23" +--- + +# WHO Cause of Death - Change log { #cod-change-log } + +## 1.2.0 { #120 } + +### General changes { #general-changes } + +- All SQL views have been reconfigured for the newer versions of DHIS2. + +| Nombre | id | Programa | +| :-- | --- | --- | +| CoD: Anacod export 2017 | nOrVs1Gi9Nt | Evento | +| CoD: Anacod export 2018 | iy8xEmIhMph | Evento | +| CoD: Anacod export 2019 | ojaXg9yV9is | Evento | +| CoD: Anacod export 2020 | atLa12jpN4y | Evento | +| CoD: Anacod export 2017 | fn3zQtRrETh | Tracker | +| CoD: Anacod export 2018 | KdIAkgUzCv7 | Tracker | +| CoD: Anacod export 2019 | xzxuZVKZw3A | Tracker | +| CoD: Anacod export 2020 | hMLDxoR33ej | Tracker | +| CoD: Dictionary entries mixing main- and sub-categories | Siuqk0lMzC7 | Event and Tracker | +| CoD: Dictionary entries with invalid ICD-SMoL reference | nWsSOLLJPjG | Event and Tracker | +| CoD: Dictionary entries with invalid code format | dS3uFpYtlss | Event and Tracker | +| CoD: Dictionary terms with ICD (for IRIS) | DNveLCRg2zU | Event and Tracker | +| CoD: Next dictionary index number | ekC6LY25qMk | Event and Tracker | +| CoD: Terms not found in dictionary | ZVl5kudO8Vt | Evento | +| CoD: Terms not found in dictionary | hhrfqhx47bt | Tracker | + +- Standard reports (Validation) for Event and Tracker programs have been reconfigured. It is possible to open applicable enrollments/events directly from the standard report form by using the right-click. + +- Duplicate options from **ICD-SMoL - local dictionary** option set were removed. Additional COVID-19 related options were added. See metadata reference file for details. All option names were changed to all-caps format. + +- ID replacement + +| Objeto | Property | Old value | New value | Programa | +| --- | --- | --- | --- | --- | +| option | id | CvivP1rh4ii | x9yVKkv9koc | Event and Tracker | +| option | id | PLlPgcfbL1D | R98tI2c6rF5 | Event and Tracker | +| option | id | TKD1XJ4ZhMO | pqxvAQU1z9W | Event and Tracker | +| optionSet | id | bLA3AqDKdwx | L6eMZDJkCwX | Event and Tracker | +| indicatorType | id | e1jRVY5Mcq0 | hmSnCXmLYwt | Event and Tracker | +| trackedEntityAttribute | id | flGbXLXCrEo | HAZ7VQ730yn | Tracker | +| dataElement | id | YUcJrLWmGyv | G5ljtyKdtYU | Event and Tracker | + +- French Dictionary for the localised French package + +The French localised version of the Cause of Death package uses a different **ICD-SMoL - local dictionary** than the generic package. It consists of different options and uses `INT_FRxxxxx` as a prefix in the segment 3 of the option code. See metadata reference file for the French localised package for more details. + +## 1.1.0 { #110 } + +### Tracker { #tracker } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` + +### Event { #event } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__installation-md new file mode 100644 index 000000000..c2c58b101 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH-TRACKER__installation-md @@ -0,0 +1,132 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/crvs_cod-installation.md" +revision_date: "2022-09-19" +--- + +# WHO Cause of Death - Tracker Installation Guide { #crvs-cod-installation } + +## Introducción { #introduction } + +This document is intended to guide administrators though the process of installing the Cause of Death module in a DHIS 2 database. Good understanding of DHIS 2, including the Tracker (case-based) functionality is required. + +The Cause of Death module consists of a file with DHIS 2 metadata. More specifically, it includes: + +For Tracker program: + +- A tracker program with data elements, option sets, custom data entry form, program rules, program indicators etc. +- A standard report for validation of data. +- A dashboard with charts and tables for key data. +- This document describes how to install this module, and perform routine maintenance. This includes the critical task of adapting and improving the dictionary of diagnosis/medical terms, which is essential for the functioning of the module. + +In addition, a [node.js](https://nodejs.org/en/) script for linking the Cause of Death module in DHIS 2 with the [IRIS software](https://www.dimdi.de/dynamic/en/classifications/iris-institute/index.html) for semi-automatic coding of causes of death to full ICD-10 and sending the result back to the DHIS 2 database. Outputs are provided to export this again data to the ANACOD data analysis tool. This functionality is described in a separate document. + +## Description of the module { #description-of-the-module } + +This section gives an overview of the design and structure of the module. + +### The data collection form { #the-data-collection-form } + +The data collection form is created based on the International Medical Certificate of Causes of Death. As such, it uses a custom form that mimics the layout of this certificate. However, the logic built into the form for coding and validation also works without the custom form, allowing the module to be used on e.g. mobile devices with the DHIS 2 android applications. + +### Dealing with "Age" { #dealing-with-age } + +For collecting data on the age of the deceased, the data collection form supports use of both date of birth and an estimated age. To facilitate analysis of the data, an additional data element for Age in years has been added to the form, but as a disabled/read-only field. Based on what is entered either as date of birth or estimated age, program rules calculate the age in years and assigns that value to the Age in years data element. + +### Dictionary { #dictionary } + +A critical component of the module is a dictionary (ICD-SMoL - local dictionary). The dictionary functions as a link between the medical terms used in data entry, and the ICD-SMoL code used for reporting and analysis of causes of death. In DHIS 2, the dictionary is implemented as an option set. The medical term is the option name, and the option code is made up of three components: the ICD-SMoL code, the ICD-10 code, and an ID. The ID is necessary because several terms could refer to the same ICD-SMoL and ICD-10 codes, and codes need to be unique. The ID itself consists of two parts: a country code (or INT for the ones provided with the module) and a counter. Keeping track of the international and country-specific terms will make it easier in the future to e.g. identify terms used in different countries which could be proposed for the international dictionary. + +Fully localised French "Cause of Death" module uses a local dictionary that is different from the English ICD-SMoL - local dictionary. This dictionary is maintained in a different option set that is only included in the French package file. + +The dictionary is sorted by length of the term, with the shortest terms appearing first. This ensures that as users search the dictionary, the terms where the largest proportion of the medical term matches with the search term is displayed first. + +### Selecting underlying cause of death { #selecting-underlying-cause-of-death } + +Selecting the underlying cause of death is a key component of the module. This is done through four checkboxes, which indicate which of the (up to) four causes is the underlying cause. Program rules are used to ensure that only one of the checkboxes can be selected, and that each checkbox can only be used if a diagnosis has been selected for that line/cause. + +Once a cause has been selected as underlying, two read-only fields are assigned with the ICD-SMoL name and code for the selected cause. + +## Installation { #installation } + +### Requirements and preparation { #requirements-and-preparation } + +In order to install the module, an administrator user account on DHIS 2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS 2. + +Great care should be taken to ensure that the server itself and the DHIS application is well secured, to restrict access to the data being collected. Even if using this module without any direct patient identifiers like ID or names, the age, sex and health facility could be sufficient to identify an individual. Details on securing a DHIS 2 system is outside the scope of this document, and we refer to the DHIS 2 documentation. + +### Choosing a version of the module { #choosing-a-version-of-the-module } + +### Importing metadata { #importing-metadata } + +The module is imported through a `.json` file with DHIS 2 metadata, using the Metadata import feature of the DHIS 2 Import/Export app. When importing the metadata in a DHIS 2 database with existing metadata, you might see errors if you look at the detailed import summary. These could require action, for example if a data element with the same name or code already exists in the database your are importing the module into. In this case, you will either have to change the identifier (name, code) in the database, or modify the name/code in the import file. Any such modifications should be done first in a test or staging environment, to make sure the changes do not affect other parts of the system. + +### Additional configuration { #additional-configuration } + +Once all metadata has been successfully imported, there are a few steps that needs to be taken before the module is functional. + +1. The programme must be assigned to a new or existing user role before users can start entering data. In addition, users need to have the necessary authorities in order to enter and/or see tracker data. Refer to the DHIS 2 Documentation for more information on configuring user roles. + +2. The programme must be assigned to the organisation units for which data will be entered. + +3. Optionally, you might also want to use the Sharing functionality of DHIS 2 to configure which users (user groups) should see the metadata and data associated with the programme. Sharing can be configured for the program itself, data elements, program indicators, aggregate indicators, option sets, and the analytical outputs. + +### Adapting the tracker program { #adapting-the-tracker-program } + +Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that could be made include: + +- Añadir variables adicionales al formulario. +- For the tracker programme, linking the programme to an existing tracked entity type and/or modifying the tracked entity attributes. A placeholder tracked entity is included in the module. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- However, it is strongly recommended not to change or remove any of the included form/metadata. This is both because the included variables are the standard recommended variables from the international death notification form, and because there is a danger that modifications could break functionality, for example program rules and program indicators. For example almost all variables in the form are linked to one or more program rules, which would cease to function if the variable is removed or replaced. Changing the default variables could also complicate updates to the module in the future. + +### Maintenance { #maintenance } + +Maintenance of the module has two main aspects: maintenance of the dictionary of medical terms, and maintenance related to new versions of DHIS 2. Each of these aspectes will be described here. + +#### Dictionary maintenance { #dictionary-maintenance } + +The dictionary of medical terms is a key component of the module, and is critical in order to produce meaningful data. This section describes how to check the integrity of the dictionary (e.g. that the codes used are valid), list terms that have been collected which are not in the dictionary and should thus be considered for inclusion, and how to add new terms to the dictionary. Several SQL-views are included in the module to facilitate these tasks. + +#### Checking integrity of dictionary { #checking-integrity-of-dictionary } + +As described above, the dictionary is implemented as an option set in DHIS 2, with the medical term as the option name and a special format for the option code that consists of the ICD-SMoL code, ICD-10 code and an ID separated by the | (pipe) symbol. SQL-views are included to verify that all entries in the dictionary follow this format: + +- Dictionary entries with invalid code format - list entries where the code does not follow the format of `[content]|[content]|[content]`. +- Dictionary entries with invalid ICD-SMoL reference - list entries where the ICD-SMoL-part of the code is not in the ICD-SMoL list, which is provided as a separate option set. +- Dictionary entries mixing main- and sub-categories - list entries where, for the same ICD-SMoL code, some entries link to the main ICD-SMoL code and some to the specific code (e.g. some to 5-4 and 5-4.1). This can create misleading outputs when analysing data within DHIS 2 as deaths might be double counted. + +#### Adding terms to the dictionary { #adding-terms-to-the-dictionary } + +An SQL view "Terms not found in dictionary" is included that will list all medical terms that have been entered as free text, i.e. which were not found in the dictionary during data entry, and the number of times they have been entered. These are terms that should be considered for inclusion in the dictionary if they occur frequently and are meaningful. + +Before a term can be added to the dictionary, the correct ICD-SMoL and ICD-10 code must be identified. Together with the ID, these make up the code to be used in the dictionary. To find the ID, an SQL view Next dictionary index number is included that will show the next ID to use. It has two columns, termtype and nextvalue. As discussed above, it is recommended that each country uses a county code for local additions to the dictionary, in which case that code will be listed under termtype and the next number to use in the nextvalue column. If no local terms have yet been added, use [country code]00001 as the first ID, e.g. GH00001 if using GH as country code. Once the first local term has been added, the SQL view will show the next ID to use at any time. + +To ensure that the right terms are displayed first in the dictionary, it must be sorted by the length of the term. After adding new terms to the dictionary, it must be re-sorted so that the new terms are not always last in the list. This can be done with the follwing SQL query (for PostgreSQL databases): + +```sql + with ordered as ( + select + uid, + name, + code, + row_number() OVER (ORDER BY length(name),name) AS sort_order + from optionvalue + where + optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY') + ) + update optionvalue ov + set sort_order = ord.sort_order + from ordered ord + where + ov.uid = ord.uid and + ov.optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY'); +``` + +**Note** that this is an UPDATE query that must be executed directly in the database, not through the DHIS2 user interface. + +Upgrading DHIS + +When new versions of DHIS2 are released, it is important to test all functionality of the module on a staging/test server before upgrading any production instances of system. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__installation-md new file mode 100644 index 000000000..c3b410f08 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__installation-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/crvs_cod-installation.md" +revision_date: "2022-09-19" +tags: + - Metadatos + - Version 1.2.0 +--- + +# WHO Cause of Death - Tracker Installation Guide { #crvs-cod-installation } + +## Introducción { #introduction } + +This document is intended to guide administrators though the process of installing the Cause of Death module in a DHIS 2 database. Good understanding of DHIS 2, including the Tracker (case-based) functionality is required. + +The Cause of Death module consists of a file with DHIS 2 metadata. More specifically, it includes: + +For Tracker program: + +- A tracker program with data elements, option sets, custom data entry form, program rules, program indicators etc. +- A standard report for validation of data. +- A dashboard with charts and tables for key data. +- This document describes how to install this module, and perform routine maintenance. This includes the critical task of adapting and improving the dictionary of diagnosis/medical terms, which is essential for the functioning of the module. + +In addition, a [node.js](https://nodejs.org/en/) script for linking the Cause of Death module in DHIS 2 with the [IRIS software](https://www.dimdi.de/dynamic/en/classifications/iris-institute/index.html) for semi-automatic coding of causes of death to full ICD-10 and sending the result back to the DHIS 2 database. Outputs are provided to export this again data to the ANACOD data analysis tool. This functionality is described in a separate document. + +## Description of the module { #description-of-the-module } + +This section gives an overview of the design and structure of the module. + +### The data collection form { #the-data-collection-form } + +The data collection form is created based on the International Medical Certificate of Causes of Death. As such, it uses a custom form that mimics the layout of this certificate. However, the logic built into the form for coding and validation also works without the custom form, allowing the module to be used on e.g. mobile devices with the DHIS 2 android applications. + +### Dealing with "Age" { #dealing-with-age } + +For collecting data on the age of the deceased, the data collection form supports use of both date of birth and an estimated age. To facilitate analysis of the data, an additional data element for Age in years has been added to the form, but as a disabled/read-only field. Based on what is entered either as date of birth or estimated age, program rules calculate the age in years and assigns that value to the Age in years data element. + +### Dictionary { #dictionary } + +A critical component of the module is a dictionary (ICD-SMoL - local dictionary). The dictionary functions as a link between the medical terms used in data entry, and the ICD-SMoL code used for reporting and analysis of causes of death. In DHIS 2, the dictionary is implemented as an option set. The medical term is the option name, and the option code is made up of three components: the ICD-SMoL code, the ICD-10 code, and an ID. The ID is necessary because several terms could refer to the same ICD-SMoL and ICD-10 codes, and codes need to be unique. The ID itself consists of two parts: a country code (or INT for the ones provided with the module) and a counter. Keeping track of the international and country-specific terms will make it easier in the future to e.g. identify terms used in different countries which could be proposed for the international dictionary. + +Fully localised French "Cause of Death" module uses a local dictionary that is different from the English ICD-SMoL - local dictionary. This dictionary is maintained in a different option set that is only included in the French package file. + +The dictionary is sorted by length of the term, with the shortest terms appearing first. This ensures that as users search the dictionary, the terms where the largest proportion of the medical term matches with the search term is displayed first. + +### Selecting underlying cause of death { #selecting-underlying-cause-of-death } + +Selecting the underlying cause of death is a key component of the module. This is done through four checkboxes, which indicate which of the (up to) four causes is the underlying cause. Program rules are used to ensure that only one of the checkboxes can be selected, and that each checkbox can only be used if a diagnosis has been selected for that line/cause. + +Once a cause has been selected as underlying, two read-only fields are assigned with the ICD-SMoL name and code for the selected cause. + +## Installation { #installation } + +### Requirements and preparation { #requirements-and-preparation } + +In order to install the module, an administrator user account on DHIS 2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS 2. + +Great care should be taken to ensure that the server itself and the DHIS application is well secured, to restrict access to the data being collected. Even if using this module without any direct patient identifiers like ID or names, the age, sex and health facility could be sufficient to identify an individual. Details on securing a DHIS 2 system is outside the scope of this document, and we refer to the DHIS 2 documentation. + +### Choosing a version of the module { #choosing-a-version-of-the-module } + +### Importing metadata { #importing-metadata } + +The module is imported through a `.json` file with DHIS 2 metadata, using the Metadata import feature of the DHIS 2 Import/Export app. When importing the metadata in a DHIS 2 database with existing metadata, you might see errors if you look at the detailed import summary. These could require action, for example if a data element with the same name or code already exists in the database your are importing the module into. In this case, you will either have to change the identifier (name, code) in the database, or modify the name/code in the import file. Any such modifications should be done first in a test or staging environment, to make sure the changes do not affect other parts of the system. + +### Additional configuration { #additional-configuration } + +Once all metadata has been successfully imported, there are a few steps that needs to be taken before the module is functional. + +1. The programme must be assigned to a new or existing user role before users can start entering data. In addition, users need to have the necessary authorities in order to enter and/or see tracker data. Refer to the DHIS 2 Documentation for more information on configuring user roles. + +2. The programme must be assigned to the organisation units for which data will be entered. + +3. Optionally, you might also want to use the Sharing functionality of DHIS 2 to configure which users (user groups) should see the metadata and data associated with the programme. Sharing can be configured for the program itself, data elements, program indicators, aggregate indicators, option sets, and the analytical outputs. + +### Adapting the tracker program { #adapting-the-tracker-program } + +Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that could be made include: + +- Añadir variables adicionales al formulario. +- For the tracker programme, linking the programme to an existing tracked entity type and/or modifying the tracked entity attributes. A placeholder tracked entity is included in the module. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- However, it is strongly recommended not to change or remove any of the included form/metadata. This is both because the included variables are the standard recommended variables from the international death notification form, and because there is a danger that modifications could break functionality, for example program rules and program indicators. For example almost all variables in the form are linked to one or more program rules, which would cease to function if the variable is removed or replaced. Changing the default variables could also complicate updates to the module in the future. + +### Maintenance { #maintenance } + +Maintenance of the module has two main aspects: maintenance of the dictionary of medical terms, and maintenance related to new versions of DHIS 2. Each of these aspectes will be described here. + +#### Dictionary maintenance { #dictionary-maintenance } + +The dictionary of medical terms is a key component of the module, and is critical in order to produce meaningful data. This section describes how to check the integrity of the dictionary (e.g. that the codes used are valid), list terms that have been collected which are not in the dictionary and should thus be considered for inclusion, and how to add new terms to the dictionary. Several SQL-views are included in the module to facilitate these tasks. + +#### Checking integrity of dictionary { #checking-integrity-of-dictionary } + +As described above, the dictionary is implemented as an option set in DHIS 2, with the medical term as the option name and a special format for the option code that consists of the ICD-SMoL code, ICD-10 code and an ID separated by the | (pipe) symbol. SQL-views are included to verify that all entries in the dictionary follow this format: + +- Dictionary entries with invalid code format - list entries where the code does not follow the format of `[content]|[content]|[content]`. +- Dictionary entries with invalid ICD-SMoL reference - list entries where the ICD-SMoL-part of the code is not in the ICD-SMoL list, which is provided as a separate option set. +- Dictionary entries mixing main- and sub-categories - list entries where, for the same ICD-SMoL code, some entries link to the main ICD-SMoL code and some to the specific code (e.g. some to 5-4 and 5-4.1). This can create misleading outputs when analysing data within DHIS 2 as deaths might be double counted. + +#### Adding terms to the dictionary { #adding-terms-to-the-dictionary } + +An SQL view "Terms not found in dictionary" is included that will list all medical terms that have been entered as free text, i.e. which were not found in the dictionary during data entry, and the number of times they have been entered. These are terms that should be considered for inclusion in the dictionary if they occur frequently and are meaningful. + +Before a term can be added to the dictionary, the correct ICD-SMoL and ICD-10 code must be identified. Together with the ID, these make up the code to be used in the dictionary. To find the ID, an SQL view Next dictionary index number is included that will show the next ID to use. It has two columns, termtype and nextvalue. As discussed above, it is recommended that each country uses a county code for local additions to the dictionary, in which case that code will be listed under termtype and the next number to use in the nextvalue column. If no local terms have yet been added, use [country code]00001 as the first ID, e.g. GH00001 if using GH as country code. Once the first local term has been added, the SQL view will show the next ID to use at any time. + +To ensure that the right terms are displayed first in the dictionary, it must be sorted by the length of the term. After adding new terms to the dictionary, it must be re-sorted so that the new terms are not always last in the list. This can be done with the follwing SQL query (for PostgreSQL databases): + +```sql + with ordered as ( + select + uid, + name, + code, + row_number() OVER (ORDER BY length(name),name) AS sort_order + from optionvalue + where + optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY') + ) + update optionvalue ov + set sort_order = ord.sort_order + from ordered ord + where + ov.uid = ord.uid and + ov.optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY'); +``` + +**Note** that this is an UPDATE query that must be executed directly in the database, not through the DHIS2 user interface. + +Upgrading DHIS + +When new versions of DHIS2 are released, it is important to test all functionality of the module on a staging/test server before upgrading any production instances of system. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__release-note-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__release-note-md new file mode 100644 index 000000000..a9743bfad --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-120__release-note-md @@ -0,0 +1,89 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/release_note.md" +revision_date: "2022-11-09" +tags: + - Metadatos + - Version 1.2.0 +--- + +# Release Note { #crvs-cod-release-note } + +## 1.2.1 { #121 } + +This is the last release of the WHO Cause of Death tracker which will be discontinued until the new release of the ICD-11 module. The **Cause of Death event program** is no longer included in the WHO Cause of Death package. + +## 1.2.0 { #120 } + +### General changes { #general-changes } + +- All SQL views have been reconfigured for the newer versions of DHIS2. + +| Nombre | id | Programa | +| :-- | --- | --- | +| CoD: Anacod export 2017 | nOrVs1Gi9Nt | Evento | +| CoD: Anacod export 2018 | iy8xEmIhMph | Evento | +| CoD: Anacod export 2019 | ojaXg9yV9is | Evento | +| CoD: Anacod export 2020 | atLa12jpN4y | Evento | +| CoD: Anacod export 2017 | fn3zQtRrETh | Tracker | +| CoD: Anacod export 2018 | KdIAkgUzCv7 | Tracker | +| CoD: Anacod export 2019 | xzxuZVKZw3A | Tracker | +| CoD: Anacod export 2020 | hMLDxoR33ej | Tracker | +| CoD: Dictionary entries mixing main- and sub-categories | Siuqk0lMzC7 | Event and Tracker | +| CoD: Dictionary entries with invalid ICD-SMoL reference | nWsSOLLJPjG | Event and Tracker | +| CoD: Dictionary entries with invalid code format | dS3uFpYtlss | Event and Tracker | +| CoD: Dictionary terms with ICD (for IRIS) | DNveLCRg2zU | Event and Tracker | +| CoD: Next dictionary index number | ekC6LY25qMk | Event and Tracker | +| CoD: Terms not found in dictionary | ZVl5kudO8Vt | Evento | +| CoD: Terms not found in dictionary | hhrfqhx47bt | Tracker | + +- Standard reports (Validation) for Event and Tracker programs have been reconfigured. It is possible to open applicable enrollments/events directly from the standard report form by using the right-click. + +- Duplicate options from **ICD-SMoL - local dictionary** option set were removed. Additional COVID-19 related options were added. See metadata reference file for details. All option names were changed to all-caps format. + +- ID replacement + +| Objeto | Property | Old value | New value | Programa | +| --- | --- | --- | --- | --- | +| option | id | CvivP1rh4ii | x9yVKkv9koc | Event and Tracker | +| option | id | PLlPgcfbL1D | R98tI2c6rF5 | Event and Tracker | +| option | id | TKD1XJ4ZhMO | pqxvAQU1z9W | Event and Tracker | +| optionSet | id | bLA3AqDKdwx | L6eMZDJkCwX | Event and Tracker | +| indicatorType | id | e1jRVY5Mcq0 | hmSnCXmLYwt | Event and Tracker | +| trackedEntityAttribute | id | flGbXLXCrEo | HAZ7VQ730yn | Tracker | +| dataElement | id | YUcJrLWmGyv | G5ljtyKdtYU | Event and Tracker | + +- French Dictionary for the localised French package + +The French localised version of the Cause of Death package uses a different **ICD-SMoL - local dictionary** than the generic package. It consists of different options and uses `INT_FRxxxxx` as a prefix in the segment 3 of the option code. See metadata reference file for the French localised package for more details. + +## 1.1.0 { #110 } + +### Tracker { #tracker } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` + +### Events { #events } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__installation-md new file mode 100644 index 000000000..8feec3f34 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__installation-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/crvs_cod-installation.md" +revision_date: "2022-09-19" +tags: + - Version 1.2.1 + - Metadatos +--- + +# WHO Cause of Death - Tracker Installation Guide { #crvs-cod-installation } + +## Introducción { #introduction } + +This document is intended to guide administrators though the process of installing the Cause of Death module in a DHIS 2 database. Good understanding of DHIS 2, including the Tracker (case-based) functionality is required. + +The Cause of Death module consists of a file with DHIS 2 metadata. More specifically, it includes: + +For Tracker program: + +- A tracker program with data elements, option sets, custom data entry form, program rules, program indicators etc. +- A standard report for validation of data. +- A dashboard with charts and tables for key data. +- This document describes how to install this module, and perform routine maintenance. This includes the critical task of adapting and improving the dictionary of diagnosis/medical terms, which is essential for the functioning of the module. + +In addition, a [node.js](https://nodejs.org/en/) script for linking the Cause of Death module in DHIS 2 with the [IRIS software](https://www.dimdi.de/dynamic/en/classifications/iris-institute/index.html) for semi-automatic coding of causes of death to full ICD-10 and sending the result back to the DHIS 2 database. Outputs are provided to export this again data to the ANACOD data analysis tool. This functionality is described in a separate document. + +## Description of the module { #description-of-the-module } + +This section gives an overview of the design and structure of the module. + +### The data collection form { #the-data-collection-form } + +The data collection form is created based on the International Medical Certificate of Causes of Death. As such, it uses a custom form that mimics the layout of this certificate. However, the logic built into the form for coding and validation also works without the custom form, allowing the module to be used on e.g. mobile devices with the DHIS 2 android applications. + +### Dealing with "Age" { #dealing-with-age } + +For collecting data on the age of the deceased, the data collection form supports use of both date of birth and an estimated age. To facilitate analysis of the data, an additional data element for Age in years has been added to the form, but as a disabled/read-only field. Based on what is entered either as date of birth or estimated age, program rules calculate the age in years and assigns that value to the Age in years data element. + +### Dictionary { #dictionary } + +A critical component of the module is a dictionary (ICD-SMoL - local dictionary). The dictionary functions as a link between the medical terms used in data entry, and the ICD-SMoL code used for reporting and analysis of causes of death. In DHIS 2, the dictionary is implemented as an option set. The medical term is the option name, and the option code is made up of three components: the ICD-SMoL code, the ICD-10 code, and an ID. The ID is necessary because several terms could refer to the same ICD-SMoL and ICD-10 codes, and codes need to be unique. The ID itself consists of two parts: a country code (or INT for the ones provided with the module) and a counter. Keeping track of the international and country-specific terms will make it easier in the future to e.g. identify terms used in different countries which could be proposed for the international dictionary. + +Fully localised French "Cause of Death" module uses a local dictionary that is different from the English ICD-SMoL - local dictionary. This dictionary is maintained in a different option set that is only included in the French package file. + +The dictionary is sorted by length of the term, with the shortest terms appearing first. This ensures that as users search the dictionary, the terms where the largest proportion of the medical term matches with the search term is displayed first. + +### Selecting underlying cause of death { #selecting-underlying-cause-of-death } + +Selecting the underlying cause of death is a key component of the module. This is done through four checkboxes, which indicate which of the (up to) four causes is the underlying cause. Program rules are used to ensure that only one of the checkboxes can be selected, and that each checkbox can only be used if a diagnosis has been selected for that line/cause. + +Once a cause has been selected as underlying, two read-only fields are assigned with the ICD-SMoL name and code for the selected cause. + +## Installation { #installation } + +### Requirements and preparation { #requirements-and-preparation } + +In order to install the module, an administrator user account on DHIS 2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS 2. + +Great care should be taken to ensure that the server itself and the DHIS application is well secured, to restrict access to the data being collected. Even if using this module without any direct patient identifiers like ID or names, the age, sex and health facility could be sufficient to identify an individual. Details on securing a DHIS 2 system is outside the scope of this document, and we refer to the DHIS 2 documentation. + +### Choosing a version of the module { #choosing-a-version-of-the-module } + +### Importing metadata { #importing-metadata } + +The module is imported through a `.json` file with DHIS 2 metadata, using the Metadata import feature of the DHIS 2 Import/Export app. When importing the metadata in a DHIS 2 database with existing metadata, you might see errors if you look at the detailed import summary. These could require action, for example if a data element with the same name or code already exists in the database your are importing the module into. In this case, you will either have to change the identifier (name, code) in the database, or modify the name/code in the import file. Any such modifications should be done first in a test or staging environment, to make sure the changes do not affect other parts of the system. + +### Additional configuration { #additional-configuration } + +Once all metadata has been successfully imported, there are a few steps that needs to be taken before the module is functional. + +1. The programme must be assigned to a new or existing user role before users can start entering data. In addition, users need to have the necessary authorities in order to enter and/or see tracker data. Refer to the DHIS 2 Documentation for more information on configuring user roles. + +2. The programme must be assigned to the organisation units for which data will be entered. + +3. Optionally, you might also want to use the Sharing functionality of DHIS 2 to configure which users (user groups) should see the metadata and data associated with the programme. Sharing can be configured for the program itself, data elements, program indicators, aggregate indicators, option sets, and the analytical outputs. + +### Adapting the tracker program { #adapting-the-tracker-program } + +Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that could be made include: + +- Añadir variables adicionales al formulario. +- For the tracker programme, linking the programme to an existing tracked entity type and/or modifying the tracked entity attributes. A placeholder tracked entity is included in the module. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- However, it is strongly recommended not to change or remove any of the included form/metadata. This is both because the included variables are the standard recommended variables from the international death notification form, and because there is a danger that modifications could break functionality, for example program rules and program indicators. For example almost all variables in the form are linked to one or more program rules, which would cease to function if the variable is removed or replaced. Changing the default variables could also complicate updates to the module in the future. + +### Maintenance { #maintenance } + +Maintenance of the module has two main aspects: maintenance of the dictionary of medical terms, and maintenance related to new versions of DHIS 2. Each of these aspectes will be described here. + +#### Dictionary maintenance { #dictionary-maintenance } + +The dictionary of medical terms is a key component of the module, and is critical in order to produce meaningful data. This section describes how to check the integrity of the dictionary (e.g. that the codes used are valid), list terms that have been collected which are not in the dictionary and should thus be considered for inclusion, and how to add new terms to the dictionary. Several SQL-views are included in the module to facilitate these tasks. + +#### Checking integrity of dictionary { #checking-integrity-of-dictionary } + +As described above, the dictionary is implemented as an option set in DHIS 2, with the medical term as the option name and a special format for the option code that consists of the ICD-SMoL code, ICD-10 code and an ID separated by the | (pipe) symbol. SQL-views are included to verify that all entries in the dictionary follow this format: + +- Dictionary entries with invalid code format - list entries where the code does not follow the format of `[content]|[content]|[content]`. +- Dictionary entries with invalid ICD-SMoL reference - list entries where the ICD-SMoL-part of the code is not in the ICD-SMoL list, which is provided as a separate option set. +- Dictionary entries mixing main- and sub-categories - list entries where, for the same ICD-SMoL code, some entries link to the main ICD-SMoL code and some to the specific code (e.g. some to 5-4 and 5-4.1). This can create misleading outputs when analysing data within DHIS 2 as deaths might be double counted. + +#### Adding terms to the dictionary { #adding-terms-to-the-dictionary } + +An SQL view "Terms not found in dictionary" is included that will list all medical terms that have been entered as free text, i.e. which were not found in the dictionary during data entry, and the number of times they have been entered. These are terms that should be considered for inclusion in the dictionary if they occur frequently and are meaningful. + +Before a term can be added to the dictionary, the correct ICD-SMoL and ICD-10 code must be identified. Together with the ID, these make up the code to be used in the dictionary. To find the ID, an SQL view Next dictionary index number is included that will show the next ID to use. It has two columns, termtype and nextvalue. As discussed above, it is recommended that each country uses a county code for local additions to the dictionary, in which case that code will be listed under termtype and the next number to use in the nextvalue column. If no local terms have yet been added, use [country code]00001 as the first ID, e.g. GH00001 if using GH as country code. Once the first local term has been added, the SQL view will show the next ID to use at any time. + +To ensure that the right terms are displayed first in the dictionary, it must be sorted by the length of the term. After adding new terms to the dictionary, it must be re-sorted so that the new terms are not always last in the list. This can be done with the follwing SQL query (for PostgreSQL databases): + +```sql + with ordered as ( + select + uid, + name, + code, + row_number() OVER (ORDER BY length(name),name) AS sort_order + from optionvalue + where + optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY') + ) + update optionvalue ov + set sort_order = ord.sort_order + from ordered ord + where + ov.uid = ord.uid and + ov.optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY'); +``` + +**Note** that this is an UPDATE query that must be executed directly in the database, not through the DHIS2 user interface. + +Upgrading DHIS + +When new versions of DHIS2 are released, it is important to test all functionality of the module on a staging/test server before upgrading any production instances of system. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__release-note-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__release-note-md new file mode 100644 index 000000000..eccf5c376 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__VERSION-121__release-note-md @@ -0,0 +1,89 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/release_note.md" +revision_date: "2022-11-09" +tags: + - Version 1.2.1 + - Metadatos +--- + +# Release Note { #crvs-cod-release-note } + +## 1.2.1 { #121 } + +This is the last release of the WHO Cause of Death tracker which will be discontinued until the new release of the ICD-11 module. The **Cause of Death event program** is no longer included in the WHO Cause of Death package. + +## 1.2.0 { #120 } + +### General changes { #general-changes } + +- All SQL views have been reconfigured for the newer versions of DHIS2. + +| Nombre | id | Programa | +| :-- | --- | --- | +| CoD: Anacod export 2017 | nOrVs1Gi9Nt | Evento | +| CoD: Anacod export 2018 | iy8xEmIhMph | Evento | +| CoD: Anacod export 2019 | ojaXg9yV9is | Evento | +| CoD: Anacod export 2020 | atLa12jpN4y | Evento | +| CoD: Anacod export 2017 | fn3zQtRrETh | Tracker | +| CoD: Anacod export 2018 | KdIAkgUzCv7 | Tracker | +| CoD: Anacod export 2019 | xzxuZVKZw3A | Tracker | +| CoD: Anacod export 2020 | hMLDxoR33ej | Tracker | +| CoD: Dictionary entries mixing main- and sub-categories | Siuqk0lMzC7 | Event and Tracker | +| CoD: Dictionary entries with invalid ICD-SMoL reference | nWsSOLLJPjG | Event and Tracker | +| CoD: Dictionary entries with invalid code format | dS3uFpYtlss | Event and Tracker | +| CoD: Dictionary terms with ICD (for IRIS) | DNveLCRg2zU | Event and Tracker | +| CoD: Next dictionary index number | ekC6LY25qMk | Event and Tracker | +| CoD: Terms not found in dictionary | ZVl5kudO8Vt | Evento | +| CoD: Terms not found in dictionary | hhrfqhx47bt | Tracker | + +- Standard reports (Validation) for Event and Tracker programs have been reconfigured. It is possible to open applicable enrollments/events directly from the standard report form by using the right-click. + +- Duplicate options from **ICD-SMoL - local dictionary** option set were removed. Additional COVID-19 related options were added. See metadata reference file for details. All option names were changed to all-caps format. + +- ID replacement + +| Objeto | Property | Old value | New value | Programa | +| --- | --- | --- | --- | --- | +| option | id | CvivP1rh4ii | x9yVKkv9koc | Event and Tracker | +| option | id | PLlPgcfbL1D | R98tI2c6rF5 | Event and Tracker | +| option | id | TKD1XJ4ZhMO | pqxvAQU1z9W | Event and Tracker | +| optionSet | id | bLA3AqDKdwx | L6eMZDJkCwX | Event and Tracker | +| indicatorType | id | e1jRVY5Mcq0 | hmSnCXmLYwt | Event and Tracker | +| trackedEntityAttribute | id | flGbXLXCrEo | HAZ7VQ730yn | Tracker | +| dataElement | id | YUcJrLWmGyv | G5ljtyKdtYU | Event and Tracker | + +- French Dictionary for the localised French package + +The French localised version of the Cause of Death package uses a different **ICD-SMoL - local dictionary** than the generic package. It consists of different options and uses `INT_FRxxxxx` as a prefix in the segment 3 of the option code. See metadata reference file for the French localised package for more details. + +## 1.1.0 { #110 } + +### Tracker { #tracker } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` + +### Events { #events } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__change-log-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__change-log-md new file mode 100644 index 000000000..91e608c14 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__change-log-md @@ -0,0 +1,82 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/changelog.md" +revision_date: "2021-09-23" +--- + +# WHO Cause of Death - Change log { #cod-change-log } + +## 1.2.0 { #120 } + +### General changes { #general-changes } + +- All SQL views have been reconfigured for the newer versions of DHIS2. + +| Nombre | id | Programa | +| :-- | --- | --- | +| CoD: Anacod export 2017 | nOrVs1Gi9Nt | Evento | +| CoD: Anacod export 2018 | iy8xEmIhMph | Evento | +| CoD: Anacod export 2019 | ojaXg9yV9is | Evento | +| CoD: Anacod export 2020 | atLa12jpN4y | Evento | +| CoD: Anacod export 2017 | fn3zQtRrETh | Tracker | +| CoD: Anacod export 2018 | KdIAkgUzCv7 | Tracker | +| CoD: Anacod export 2019 | xzxuZVKZw3A | Tracker | +| CoD: Anacod export 2020 | hMLDxoR33ej | Tracker | +| CoD: Dictionary entries mixing main- and sub-categories | Siuqk0lMzC7 | Event and Tracker | +| CoD: Dictionary entries with invalid ICD-SMoL reference | nWsSOLLJPjG | Event and Tracker | +| CoD: Dictionary entries with invalid code format | dS3uFpYtlss | Event and Tracker | +| CoD: Dictionary terms with ICD (for IRIS) | DNveLCRg2zU | Event and Tracker | +| CoD: Next dictionary index number | ekC6LY25qMk | Event and Tracker | +| CoD: Terms not found in dictionary | ZVl5kudO8Vt | Evento | +| CoD: Terms not found in dictionary | hhrfqhx47bt | Tracker | + +- Standard reports (Validation) for Event and Tracker programs have been reconfigured. It is possible to open applicable enrollments/events directly from the standard report form by using the right-click. + +- Duplicate options from **ICD-SMoL - local dictionary** option set were removed. Additional COVID-19 related options were added. See metadata reference file for details. All option names were changed to all-caps format. + +- ID replacement + +| Objeto | Property | Old value | New value | Programa | +| --- | --- | --- | --- | --- | +| option | id | CvivP1rh4ii | x9yVKkv9koc | Event and Tracker | +| option | id | PLlPgcfbL1D | R98tI2c6rF5 | Event and Tracker | +| option | id | TKD1XJ4ZhMO | pqxvAQU1z9W | Event and Tracker | +| optionSet | id | bLA3AqDKdwx | L6eMZDJkCwX | Event and Tracker | +| indicatorType | id | e1jRVY5Mcq0 | hmSnCXmLYwt | Event and Tracker | +| trackedEntityAttribute | id | flGbXLXCrEo | HAZ7VQ730yn | Tracker | +| dataElement | id | YUcJrLWmGyv | G5ljtyKdtYU | Event and Tracker | + +- French Dictionary for the localised French package + +The French localised version of the Cause of Death package uses a different **ICD-SMoL - local dictionary** than the generic package. It consists of different options and uses `INT_FRxxxxx` as a prefix in the segment 3 of the option code. See metadata reference file for the French localised package for more details. + +## 1.1.0 { #110 } + +### Tracker { #tracker } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` + +### Event { #event } + +- Included SQL views in metadata file +- Updated the following options: + +| id | Property | Old value | New value | +| ----------- | -------- | ----------------------- | --------------------- | +| y400ZT7P7Tk | code | 5-2\|A019\|INT00638 | 5-2\|A010\|INT00638 | +| nW8UW4mIHoj | code | 5-80\|O16/O15\|INT05700 | 5-80\|O16\|INT05700 | +| eGSBH8BXVxt | code | 5-106\|T309\|INT05605 | 5-106\|T300\|INT05605 | +| Wvw6LctDL3R | code | 5-106\|T309\|INT00043 | 5-106\|T300\|INT00043 | +| V8CuD9AucgW | code | 5-85\|O999\|INT02339 | 5-85\|O998\|INT02339 | + +- Deleted the following options: `oBOM5bEVVLk, LW7CuavQo3n, leyPoGqs597, k7XHmj3a4nT, trEzz9R11r5, OrqWo8PX6f2, HopjEbx2cdt, C0RFtymQ1zT, VOW0QufZ5NM, w4TLLFtwyMy` diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md new file mode 100644 index 000000000..7a8334d83 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__installation-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/CRVS_COD/blob/master/docs/crvs_cod-installation.md" +revision_date: '2022-09-19' +tags: +- Metadatos +--- + +# WHO Cause of Death - Tracker Installation Guide { #crvs-cod-installation } + +## Introducción { #introduction } + +This document is intended to guide administrators though the process of installing the Cause of Death module in a DHIS 2 database. Good understanding of DHIS 2, including the Tracker (case-based) functionality is required. + +The Cause of Death module consists of a file with DHIS 2 metadata. More specifically, it includes: + +For Tracker program: + +- A tracker program with data elements, option sets, custom data entry form, program rules, program indicators etc. +- A standard report for validation of data. +- A dashboard with charts and tables for key data. +- This document describes how to install this module, and perform routine maintenance. This includes the critical task of adapting and improving the dictionary of diagnosis/medical terms, which is essential for the functioning of the module. + +In addition, a [node.js](https://nodejs.org/en/) script for linking the Cause of Death module in DHIS 2 with the [IRIS software](https://www.dimdi.de/dynamic/en/classifications/iris-institute/index.html) for semi-automatic coding of causes of death to full ICD-10 and sending the result back to the DHIS 2 database. Outputs are provided to export this again data to the ANACOD data analysis tool. This functionality is described in a separate document. + +## Description of the module { #description-of-the-module } + +This section gives an overview of the design and structure of the module. + +### The data collection form { #the-data-collection-form } + +The data collection form is created based on the International Medical Certificate of Causes of Death. As such, it uses a custom form that mimics the layout of this certificate. However, the logic built into the form for coding and validation also works without the custom form, allowing the module to be used on e.g. mobile devices with the DHIS 2 android applications. + +### Dealing with "Age" { #dealing-with-age } + +For collecting data on the age of the deceased, the data collection form supports use of both date of birth and an estimated age. To facilitate analysis of the data, an additional data element for Age in years has been added to the form, but as a disabled/read-only field. Based on what is entered either as date of birth or estimated age, program rules calculate the age in years and assigns that value to the Age in years data element. + +### Dictionary { #dictionary } + +A critical component of the module is a dictionary (ICD-SMoL - local dictionary). The dictionary functions as a link between the medical terms used in data entry, and the ICD-SMoL code used for reporting and analysis of causes of death. In DHIS 2, the dictionary is implemented as an option set. The medical term is the option name, and the option code is made up of three components: the ICD-SMoL code, the ICD-10 code, and an ID. The ID is necessary because several terms could refer to the same ICD-SMoL and ICD-10 codes, and codes need to be unique. The ID itself consists of two parts: a country code (or INT for the ones provided with the module) and a counter. Keeping track of the international and country-specific terms will make it easier in the future to e.g. identify terms used in different countries which could be proposed for the international dictionary. + +Fully localised French "Cause of Death" module uses a local dictionary that is different from the English ICD-SMoL - local dictionary. This dictionary is maintained in a different option set that is only included in the French package file. + +The dictionary is sorted by length of the term, with the shortest terms appearing first. This ensures that as users search the dictionary, the terms where the largest proportion of the medical term matches with the search term is displayed first. + +### Selecting underlying cause of death { #selecting-underlying-cause-of-death } + +Selecting the underlying cause of death is a key component of the module. This is done through four checkboxes, which indicate which of the (up to) four causes is the underlying cause. Program rules are used to ensure that only one of the checkboxes can be selected, and that each checkbox can only be used if a diagnosis has been selected for that line/cause. + +Once a cause has been selected as underlying, two read-only fields are assigned with the ICD-SMoL name and code for the selected cause. + +## Instalación { #installation } + +### Requirements and preparation { #requirements-and-preparation } + +In order to install the module, an administrator user account on DHIS 2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS 2. + +Great care should be taken to ensure that the server itself and the DHIS application is well secured, to restrict access to the data being collected. Even if using this module without any direct patient identifiers like ID or names, the age, sex and health facility could be sufficient to identify an individual. Details on securing a DHIS 2 system is outside the scope of this document, and we refer to the DHIS 2 documentation. + +### Choosing a version of the module { #choosing-a-version-of-the-module } + +### Importar metadatos { #importing-metadata } + +The module is imported through a `.json` file with DHIS 2 metadata, using the Metadata import feature of the DHIS 2 Import/Export app. When importing the metadata in a DHIS 2 database with existing metadata, you might see errors if you look at the detailed import summary. These could require action, for example if a data element with the same name or code already exists in the database your are importing the module into. In this case, you will either have to change the identifier (name, code) in the database, or modify the name/code in the import file. Any such modifications should be done first in a test or staging environment, to make sure the changes do not affect other parts of the system. + +### Additional configuration { #additional-configuration } + +Once all metadata has been successfully imported, there are a few steps that needs to be taken before the module is functional. + +1. The programme must be assigned to a new or existing user role before users can start entering data. In addition, users need to have the necessary authorities in order to enter and/or see tracker data. Refer to the DHIS 2 Documentation for more information on configuring user roles. + +2. The programme must be assigned to the organisation units for which data will be entered. + +3. Optionally, you might also want to use the Sharing functionality of DHIS 2 to configure which users (user groups) should see the metadata and data associated with the programme. Sharing can be configured for the program itself, data elements, program indicators, aggregate indicators, option sets, and the analytical outputs. + +### Adapting the tracker program { #adapting-the-tracker-program } + +Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that could be made include: + +- Añadir variables adicionales al formulario. +- For the tracker programme, linking the programme to an existing tracked entity type and/or modifying the tracked entity attributes. A placeholder tracked entity is included in the module. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- However, it is strongly recommended not to change or remove any of the included form/metadata. This is both because the included variables are the standard recommended variables from the international death notification form, and because there is a danger that modifications could break functionality, for example program rules and program indicators. For example almost all variables in the form are linked to one or more program rules, which would cease to function if the variable is removed or replaced. Changing the default variables could also complicate updates to the module in the future. + +### Maintenance { #maintenance } + +Maintenance of the module has two main aspects: maintenance of the dictionary of medical terms, and maintenance related to new versions of DHIS 2. Each of these aspectes will be described here. + +#### Dictionary maintenance { #dictionary-maintenance } + +The dictionary of medical terms is a key component of the module, and is critical in order to produce meaningful data. This section describes how to check the integrity of the dictionary (e.g. that the codes used are valid), list terms that have been collected which are not in the dictionary and should thus be considered for inclusion, and how to add new terms to the dictionary. Several SQL-views are included in the module to facilitate these tasks. + +#### Checking integrity of dictionary { #checking-integrity-of-dictionary } + +As described above, the dictionary is implemented as an option set in DHIS 2, with the medical term as the option name and a special format for the option code that consists of the ICD-SMoL code, ICD-10 code and an ID separated by the | (pipe) symbol. SQL-views are included to verify that all entries in the dictionary follow this format: + +- Dictionary entries with invalid code format - list entries where the code does not follow the format of `[content]|[content]|[content]`. +- Dictionary entries with invalid ICD-SMoL reference - list entries where the ICD-SMoL-part of the code is not in the ICD-SMoL list, which is provided as a separate option set. +- Dictionary entries mixing main- and sub-categories - list entries where, for the same ICD-SMoL code, some entries link to the main ICD-SMoL code and some to the specific code (e.g. some to 5-4 and 5-4.1). This can create misleading outputs when analysing data within DHIS 2 as deaths might be double counted. + +#### Adding terms to the dictionary { #adding-terms-to-the-dictionary } + +An SQL view "Terms not found in dictionary" is included that will list all medical terms that have been entered as free text, i.e. which were not found in the dictionary during data entry, and the number of times they have been entered. These are terms that should be considered for inclusion in the dictionary if they occur frequently and are meaningful. + +Before a term can be added to the dictionary, the correct ICD-SMoL and ICD-10 code must be identified. Together with the ID, these make up the code to be used in the dictionary. To find the ID, an SQL view Next dictionary index number is included that will show the next ID to use. It has two columns, termtype and nextvalue. As discussed above, it is recommended that each country uses a county code for local additions to the dictionary, in which case that code will be listed under termtype and the next number to use in the nextvalue column. If no local terms have yet been added, use [country code]00001 as the first ID, e.g. GH00001 if using GH as country code. Once the first local term has been added, the SQL view will show the next ID to use at any time. + +To ensure that the right terms are displayed first in the dictionary, it must be sorted by the length of the term. After adding new terms to the dictionary, it must be re-sorted so that the new terms are not always last in the list. This can be done with the follwing SQL query (for PostgreSQL databases): + +```sql + with ordered as ( + select + uid, + name, + code, + row_number() OVER (ORDER BY length(name),name) AS sort_order + from optionvalue + where + optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY') + ) + update optionvalue ov + set sort_order = ord.sort_order + from ordered ord + where + ov.uid = ord.uid and + ov.optionsetid = + (select optionsetid from optionset where code = 'ICD_SMOL_DICTIONARY'); +``` + +**Note** that this is an UPDATE query that must be executed directly in the database, not through the DHIS2 user interface. + +Upgrading DHIS + +When new versions of DHIS2 are released, it is important to test all functionality of the module on a staging/test server before upgrading any production instances of system. + diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md index 9da7b2265..cb9db6c00 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__CAUSE-OF-DEATH__release-note-md @@ -42,7 +42,7 @@ The **Cause of Death event program** is no longer included in the WHO Cause of D - ID replacement -| Object | Property | Old value | New value | Programa | +| Objeto | Property | Old value | New value | Programa | |-|-|-|-|-| | option | id | CvivP1rh4ii | x9yVKkv9koc | Event and Tracker | | option | id | PLlPgcfbL1D | R98tI2c6rF5 | Event and Tracker | diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__design-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__design-md index fe9899420..cf540f9fe 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__design-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__design-md @@ -63,7 +63,7 @@ Three core user groups are included in the package. By default the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _RMS - access_ | _RMS - admin_ | _RMS - data capture_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: no access | Metadata : can view
Data: can capture and view | diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__installation-md index 129bb22f3..2a6ea366f 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE-EVENTS__installation-md @@ -7,56 +7,56 @@ revision_date: "2022-07-01" ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Preparing the metadata file { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -126,11 +126,11 @@ Sort order can be adjusted in the Maintenance app. ## Importing metadata { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Handling import conflicts { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > @@ -138,25 +138,25 @@ There are a number of different conflicts that may occur, though the most common #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } @@ -165,9 +165,9 @@ First, you will have to use the _Sharing_ functionality of DHIS2 to configure wh - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -177,7 +177,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _RMS access_ | _RMS admin_ | _RMS data capture_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: no access | Metadata : can view
Data: can capture and view | @@ -187,12 +187,12 @@ The users are assigned to the appropriate user group based on their role within ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation Units { #organisation-units } @@ -204,20 +204,20 @@ The program and the data sets must be assigned to organisation units within exis > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Removing metadata { #removing-metadata } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md index 8f8095cbf..e23fcac68 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__design-md @@ -65,7 +65,7 @@ Three core user groups are included in the package. By default the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|-----------------------------------------------------| | | _RMS - access_ | _RMS - admin_ | _RMS - data capture_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: no access | Metadata : can view
Data: can capture and view | diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md index eb8bd4f90..01a431c49 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__RAPID-MORTALITY-SURVEILLANCE__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -129,50 +129,50 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -182,7 +182,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------|---------------------------------------------------|-----------------------------------------------------| | | _RMS access_ | _RMS admin_ | _RMS data capture_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: no access | Metadata : can view
Data: can capture and view | @@ -190,16 +190,16 @@ By default, the following permissions are assigned to these user groups: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -210,22 +210,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-100__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-100__installation-md index bc2371913..f01849075 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-100__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-100__installation-md @@ -7,13 +7,13 @@ revision_date: "2022-05-27" This document includes an installation guide for the updated Vital Events tracker package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -53,29 +53,29 @@ The package metadata json files contain a "package" component that provides tech ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Vital Events tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -87,30 +87,30 @@ The Vital Events tracker package includes three metadata files. The contents and ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Indicator types { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Per 1000 | `zpa0vUC7IWd` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1000` | | Porcentaje | `hmSnCXmLYwt` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -118,13 +118,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -210,51 +210,51 @@ Sort order can be adjusted in the Maintenance app. ## Importing metadata { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Handling import conflicts { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -264,7 +264,7 @@ Three core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _VE - Access_ | _VE - Data capture_ | _VE - Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | @@ -277,12 +277,12 @@ The users are assigned to the appropriate user group based on their role within ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } @@ -294,20 +294,20 @@ The program and the data sets must be assigned to organisation units within exis > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Removing metadata { #removing-metadata } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-110__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-110__installation-md index bc2371913..f01849075 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-110__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS-TRACKER__VERSION-110__installation-md @@ -7,13 +7,13 @@ revision_date: "2022-05-27" This document includes an installation guide for the updated Vital Events tracker package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -53,29 +53,29 @@ The package metadata json files contain a "package" component that provides tech ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Vital Events tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -87,30 +87,30 @@ The Vital Events tracker package includes three metadata files. The contents and ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Indicator types { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Per 1000 | `zpa0vUC7IWd` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1000` | | Porcentaje | `hmSnCXmLYwt` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -118,13 +118,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -210,51 +210,51 @@ Sort order can be adjusted in the Maintenance app. ## Importing metadata { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Handling import conflicts { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -264,7 +264,7 @@ Three core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _VE - Access_ | _VE - Data capture_ | _VE - Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | @@ -277,12 +277,12 @@ The users are assigned to the appropriate user group based on their role within ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } @@ -294,20 +294,20 @@ The program and the data sets must be assigned to organisation units within exis > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Removing metadata { #removing-metadata } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-100__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-100__installation-md index 39d598ce4..b12ec7c80 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-100__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-100__installation-md @@ -10,13 +10,13 @@ tags: This document includes an installation guide for the updated Vital Events tracker package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -56,29 +56,29 @@ The package metadata json files contain a "package" component that provides tech ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Vital Events tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -90,30 +90,30 @@ The Vital Events tracker package includes three metadata files. The contents and ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Indicator types { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Per 1000 | `zpa0vUC7IWd` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1000` | | Porcentaje | `hmSnCXmLYwt` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -121,13 +121,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -213,51 +213,51 @@ Sort order can be adjusted in the Maintenance app. ## Importing metadata { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Handling import conflicts { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -267,7 +267,7 @@ Three core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _VE - Access_ | _VE - Data capture_ | _VE - Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | @@ -280,12 +280,12 @@ The users are assigned to the appropriate user group based on their role within ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } @@ -297,20 +297,20 @@ The program and the data sets must be assigned to organisation units within exis > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Removing metadata { #removing-metadata } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-110__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-110__installation-md index 9ec8593c7..5820e3c2d 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-110__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__VERSION-110__installation-md @@ -10,13 +10,13 @@ tags: This document includes an installation guide for the updated Vital Events tracker package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese ## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -56,29 +56,29 @@ The package metadata json files contain a "package" component that provides tech ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Vital Events tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -90,30 +90,30 @@ The Vital Events tracker package includes three metadata files. The contents and ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Indicator types { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Per 1000 | `zpa0vUC7IWd` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1000` | | Porcentaje | `hmSnCXmLYwt` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -121,13 +121,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -213,51 +213,51 @@ Sort order can be adjusted in the Maintenance app. ## Importing metadata { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Handling import conflicts { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -267,7 +267,7 @@ Three core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _VE - Access_ | _VE - Data capture_ | _VE - Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | @@ -280,12 +280,12 @@ The users are assigned to the appropriate user group based on their role within ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } @@ -297,20 +297,20 @@ The program and the data sets must be assigned to organisation units within exis > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Removing metadata { #removing-metadata } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__installation-md index 408a71a78..5260b9435 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__CRVS-MORTALITY__VITAL-EVENTS__installation-md @@ -9,13 +9,13 @@ tags: This document includes an installation guide for the updated Vital Events tracker package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French, Spanish, Portuguese -## Overview { #overview } +## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ### DHIS2.35 { #dhis235 } @@ -55,29 +55,29 @@ The package metadata json files contain a "package" component that provides tech ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. The Vital Events tracker package includes three metadata files. The contents and purposose of each individual file are described below: @@ -85,34 +85,34 @@ The Vital Events tracker package includes three metadata files. The contents and |---------------------------------------------------------------|-------------------------|--------------------| | CRVS_VE_TKR_1.1.0_DHIS2.35.11-en | Updated tracker package | New implementation | -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|---------------------------------------------------------------------------| -| Numerator only (number)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | | Per 1000 | `zpa0vUC7IWd` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1000` | | Porcentaje | `hmSnCXmLYwt` | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -120,13 +120,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|----------------------------------------| -| Person | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | `MCPQUTHX1Ze` | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -213,53 +213,53 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros -* Visualizations, maps, event reports and report tables -* Data sets -* Category options +* Visualizaciones, mapas, informes de eventos y tablas de informes +* Sets de datos +* Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -269,7 +269,7 @@ Three core user groups are included in the package: By default, the following permissions are assigned to these user groups: -| Object | User Group | | | +| Objeto | User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _VE - Access_ | _VE - Data capture_ | _VE - Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: can view | @@ -282,40 +282,40 @@ The users are assigned to the appropriate user group based on their role within ### User roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation units { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md new file mode 100644 index 000000000..65a4615c5 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__COMMON-METADATA-LIBRARY__installation-md @@ -0,0 +1,93 @@ +--- +edit_url: "https://github.com/dhis2-metadata/GEN_LIB/blob/master/docs/gen_lib-installation.md" +revision_date: '2022-07-01' +tags: +- Metadatos +--- + +# Common metadata library - Installation Guide { #gen-lib-installation } + +This document includes an installation guide for the common metadata library. + +Idioma predeterminado del sistema: Inglés + +Available translations: French, Spanish, Portuguese, Arabic + +## Instalación { #installation } + +The table below will help you identify which metadata file/s are relevant for your implementation: + +| Metadata file | Application area | +|------------------------------------|------------------| +| Common metadata library (complete) | DHIS2 environment containing both tracker and aggregate modules, implementation of published metadata packages, development of custom programs and modules that utilise common metadata | +| Common tracker metadata library | Tracker-based DHIS2 environment, implementation of published tracker packages, development of custom tracker programs that utilise common tracker metadata | +| Core case profile | Tracker-based DHIS2 environment, implementation of published tracker packages, development of custom tracker programs that utilise core case profile data (Person) | +| Common aggregate metadata | Implementation of published aggregate modules, development of custom aggregate modules that utilise common aggregate metadata | + +For more information, refer to the [Common metadata library design guide](#common-metadata-library) + +Carefully read through each section of the installation guide before importing the metadata files into your DHIS2 instance! + +### Importing common metadata into a blank DHIS2 instance { #importing-common-metadata-into-a-blank-dhis2-instance } + +The application area of the DHIS2 instance will help you identify, which metadata file/s to import. The metadata can be imported without any additional adjustments. + +### Importing common metadata into a working DHIS2 instance { #importing-common-metadata-into-a-working-dhis2-instance } + +Overwriting metadata in the target instance may change the configuration of the existing programs and may lead to errors. When you import the Common metadata library into a working DHIS2 environment, you need to make sure that you do not lose any existing configurations (ie. sharing settings, option sort order, etc). + +If the metadata objects in the common metadata library and in the target instance share the same UIDs but are not identical (eg. different aggregation type, different assigned option set, different number of options), consider assigning new UIDs to the metadata objects in the target instance, before importing the common metadata library. + +#### UIDs { #uids } + +Replacing UIDs for metadata elements in the target system to match the source metadata file can be a complex task, as the uid maybe referenced in other metadata objects, such as program rules, indicators, predictors, validation rules, etc. +Make sure to replace all occurances of the old uid with the new uid in the system before importing the metadata object. + +> **EXAMPLE** +> +> To update the uid of a category option use the following command: +> +> ```SQL +> UPDATE dataelementcategoryoption SET uid = '' WHERE uid = ''; +> ``` + +#### Tracked entity attributes, data elements, option sets and options { #tracked-entity-attributes-data-elements-option-sets-and-options } + +For option set based data elements and attributes, make sure that these option sets are identical in the source file and in the target instance. +Check that the matching option sets contain the same options. + +Check the aggregation and value types of the data elements and attributes in the source file and the target instance. + +#### Option codes { #option-codes } + +According to the DHIS2 naming conventions, the metadata codes use capital letters, underscores and no spaces. Some exceptions that may occur are specified in the corresponding package documentation. If data values in the target instance contain lower case codes, it is important to update those values directly in the database. + +The table below contains all option sets where codes were changed to upper case in the metadata package. Before importing metadata into the instance, check whether the option sets in the existing system match those in the package .json and use the same upper case option codes. + +> **Important** +> +> During the import, the existing option codes will be overwritten with the updated upper case codes. +> In order to update the existing data values, it is necessary to update the values stored in the database using database commands. +> Make sure to map existing old option codes and new option codes before replacing the values. Use staging instance first, before making adjustments on the production server. + +For data element values, use: + +```SQL +UPDATE programstageinstance +SET eventdatavalues = jsonb_set(eventdatavalues, '{"","value"}', '""') +WHERE eventdatavalues @> '{"":{"value": ""}}'::jsonb +AND programstageid=; +``` + +For tracked entity attribute values, use: + +```SQL +UPDATE trackedentityattributevalue +SET value = +WHERE trackedentityattributeid= AND value=; +``` + +#### Tracked entity type { #tracked-entity-type } + +If the tracked entity types in the Common metadata library and the target instance match, reviw the sharing settings, the assigned tracked entity type attributes and their settings, before importing the Common metadata library. + diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__common-metadata-library-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__common-metadata-library-md new file mode 100644 index 000000000..c99875a81 --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DHIS2-WHO-DIGITAL-HEALTH-DATA-TOOLKIT__common-metadata-library-md @@ -0,0 +1,60 @@ +--- +edit_url: "https://github.com/dhis2-metadata/GNRC-Common_Metadata_Library/blob/master/docs/common-metadata-library.md" +revision_date: "2022-03-02" +--- + +# Common Metadata Library { #common-metadata-library } + +## Introducción { #introduction } + +This document describes a metadata package that provides a baseline of core DHIS2 metadata for use across multiple Tracker programs. The metadata included are not programme/use case specific, but are generally expected to be shared across tracker programs as part of a harmonized HMIS. + +One key advantage of DHIS2 is that it can be used for multiple health programs, within a single, harmonized instance. There are several practical reasons to share metadata across tracker programs: + +- To reduce duplication of data entry and improve data flows, e.g. where a person’s details recorded in one program can be carried over to another program; +- To improve analytical capabilities across programs by re-using common metadata and its associated codes for core attributes like Sex; +- To facilitate maintenance of the metadata in the system + +DHIS2 metadata packages are designed and harmonized in a way which allows multiple packages to be imported into the same DHIS2 instance. This might be done to link an individual’s enrollments in different programs, or create synergies across reporting flows for different health areas. For example, a patient may be enrolled in both HIV and TB case surveillance programs, but the patient’s Sex is recorded only once at the time of first enrollment. To do this, the programs need to share the same metadata for the tracked entity attribute (Sex) plus its associated option set and options (Male, Female, and Unknown). + +Importing those common metadata together as a baseline package ensures that the Unique IDs, names, and codes for objects (e.g. tracked entity attributes, option sets, options, and data elements. In addition, if a custom program is developed within the same instance, it could re-use those metadata from the baseline package, thereby bootstrapping configuration of the new program, preventing namespace clashes and other complications during metadata import/export, and facilitating data exchange across platforms. This becomes particularly important when aligning tracker implementations that may exist across multiple instances into a shared, harmonized environment. + +## System Design Overview { #system-design-overview } + +Common tracker metadata are made available as installable metadata files that can be imported into a new or existing DHIS2 instance. These installable files contain metadata that are aligned to a few common use cases for DHIS2 Tracker: + +1. Core Case Profile + +These are used across all WHO case-based surveillance tracker programs: Immunization, HIV, Malaria, TB, VPD, and COVID-19 Case-based surveillance. The Core Case Profile was developed through an internal WHO harmonization of naming conventions for case-based registries and facility-level aggregate datasets across all WHO programmes that use DHIS2 as of September 2020. This library will be reviewed on an annual basis for possible revisions. It includes: + +- Tracked Entity Type (Person) +- Atributos de entidad Tracked +- Options +- Set de opciones + +2. DHIS2 Common Tracker Metadata library + +Common Tracker Metadata library contains all WHO Core Case Profile objects from above, plus other common metadata such as data elements, option sets, and options. This library is not exhaustive, but contains metadata concepts that are included in official DHIS2 tracker packages, and are generic enough that they could be conceivably shared across programs (e.g. option sets for a list of countries or a data element for ‘date of death’). The library is intended to provide a selection of common metadata that implementers can take at their discretion in the development of tracker programs. This library will be more frequently updated and expanded on a semi-annual basis as metadata packages are developed and deployed. + +All metadata in the Common Tracker Metadata Library comprise metadata groups containing the prefix GN (for General. The prefix helps to signify to the implementer or system admin that the metadata object is being shared across programs, and impact across programs should be considered before making changes/adjustments to shared metadata. + +- Tracked entity type (Person) +- Tracked entity attributes +- Option sets, including ISO 3166-1 alpha-2 country codes +- Options +- Data elements +- Custom attributes associated with the above (e.g. LOINC, Snomed, ICD-11) + +![Shared metadata diagram](resources/images/metadata-diagram-en.png) + +The diagram above illustrates a few points about the modular structure of the package. + +The DHIS2 Common Tracker Library includes the entirety of the WHO Core Case Profile, in addition to other metadata objects. + +A DHIS2 Metadata Package may utilize metadata found within the Core Case Profile, within the broader Common Tracker Library, or its own program-specific metadata (see HIV CS Package). + +A custom, locally-designed tracker program may also utilize metadata found within the Core Case Profile, within the broader Common Tracker Library, or develop its own program-specific metadata. + +Imagine a scenario where the NTD Surveillance program above is developed independently. The implementers then decide to import the HIV CS package into the same DHIS2 instance. There would be a number of conflicts during metadata import, because objects in each program have the same name and different UIDs (phone number, national ID, and country of birth). If the Core Case Profile had been imported prior to the configuration of a custom NTD program, there would be less work involved to configure new metadata, and fewer clashes when the HIV CS package is imported. + +Finally, note that the GEN prefix will not be visible to end users of your programs. These metadata come translated for XYZ different locales, and can be further translated to other local languages without interfering with the baseline UIDs, names, and codes. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md index e8aa6cc21..d8a79c3ac 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__installation-md @@ -11,7 +11,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,41 +20,41 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -62,15 +62,15 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |--------|-------------|--------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -79,39 +79,39 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -#### Sharing { #sharing } +#### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -124,12 +124,12 @@ A metadata package usually contains several user groups: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | AFI access | AFI admin | AFI data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | Please refere to the individual package installation annex for information about user groups. @@ -142,47 +142,47 @@ If your TET Person already matches the one in the package and you want to avoid * Import the package * Update sharing properties for this TET using the table above. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ### [CONFIG] metadata { #config-metadata } The following metadata needs to be configured after import. -| Metadata Type | Nombre | +| Tipo de metadatos | Nombre | |---------------------|----------------------------------------------------| -| Option Sets | [CONFIG]\_Race / Ethnicity / Nationality | -| Option Sets | [CONFIG]\_Occupation | -| Option Sets | [CONFIG]\_Diagnosis | +| Set de opciones | [CONFIG]\_Race / Ethnicity / Nationality | +| Set de opciones | [CONFIG]\_Occupation | +| Set de opciones | [CONFIG]\_Diagnosis | | Data Elements | [CONFIG]\_Month before illness, [Other exposure X] | | Data Elements | [CONFIG]\_Laboratory test X | | Data Elements | [CONFIG]\_Date of test X | diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__VERSION-120__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__VERSION-120__installation-md index c85b86ac0..4895b59c3 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__VERSION-120__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__VERSION-120__installation-md @@ -10,7 +10,7 @@ tags: This document includes an installation guide for the IDS aggregate package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French @@ -25,62 +25,62 @@ The metadata package consists of the following modules: ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file) 2. [Importing the metadata file into DHIS2](#importing-metadata) 3. [Configuring the imported metadata](#configuration) -4. [Adapting the program after import](#adapting-the-program) +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Preparing the Metadata File { #preparing-the-metadata-file } ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Indicator types { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número) | `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Visualizations using root organisation unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -238,44 +238,44 @@ Use the [Import/Export](#import_export) DHIS2 app to import metadata packages. I ### Handling import conflicts { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -287,12 +287,12 @@ The users are assigned to the appropriate user group based on their role within ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: 1. Aggregate data analysis : Can access dashboards, data visualizer, pivot tables, reports and maps. 2. Aggregate data capture : Can acccess the data entry app and add/modify data values, -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation unit assignment { #organisation-unit-assignment } @@ -346,18 +346,18 @@ In order to send out notifications via SMS or e-mail, you will need an [SMS gate > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. +- Añadir variables adicionales al formulario. - Adapting data element names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales - Adding dashboards/dashboard items However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example predictors or notifications. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md index dffc6c8db..7c9a4fc58 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__IDS-AGGREGATE__installation-md @@ -9,11 +9,11 @@ tags: This document includes an installation guide for the IDS aggregate package. -System default language: English +Idioma predeterminado del sistema: Inglés Available translations: French -## Overview { #overview } +## Visión general { #overview } The metadata reference and metadata json files provide technical details on package version and content. @@ -24,62 +24,62 @@ The metadata package consists of the following modules: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file) 2. [Importing the metadata file into DHIS2](#importing-metadata) 3. [Configuring the imported metadata](#configuration) -4. [Adapting the program after import](#adapting-the-program) +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Preparing the Metadata File { #preparing-the-metadata-file } -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |------------------------|---------------|-----------------------------------------------------------------------| -| Numerator only (number)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número)| `kHy61PbChXr` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Visualizations using root organisation unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -233,50 +233,50 @@ Note that all validation rule notifications for this package are all set to be s ***NB: Note that you can also change this in maintenance for each validation rule notification at any time after they are imported as you may want to demonstrate or test both strategies to select one that is appropriate for your own setting***. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } Use the [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. Three core user groups are included in the package: @@ -286,16 +286,16 @@ Three core user groups are included in the package: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: 1. Aggregate data analysis : Can access dashboards, data visualizer, pivot tables, reports and maps. 2. Aggregate data capture : Can acccess the data entry app and add/modify data values, -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation unit assignment { #organisation-unit-assignment } +### Asignación de unidades organizativas{ #organisation-unit-assignment } The data sets must be assigned to organisation units within existing hierarchy in order to be accessible for data entry and data analysis personnel. @@ -341,30 +341,30 @@ By default, notifications will be sent out to via the DHIS2 messaging app. In order to send out notifications via SMS or e-mail, you will need an [SMS gateway](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/configure-sms.html#sms-configuration-gateways) and/or an [e-mail configuration](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/system-settings.html#system_email_settings) set up within your DHIS2 instance. The settings necessary for these will vary between implementations and it is best to consult the documentation links provided here for more information. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). -## Adapting the program { #adapting-the-program } +## Adaptar el programa { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. +- Añadir variables adicionales al formulario. - Adapting data element names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales - Adding dashboards/dashboard items However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example predictors or notifications. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadata requires advanced knowledge of DHIS2 and various dependencies. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__installation-md index bd6e3dcf4..7e58066c7 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__installation-md @@ -9,7 +9,7 @@ revision_date: "2022-09-16" The VPD CS tracker package is self-contained, meaning it can be installed on its own. However, it is worth noticing that this package contains some metadata from the IDSR package. The reason for this is that there is a comparative table which makes it possible to compare the aggregated data and the tracker data. Thus, we recommend installing the aggregate disease surveillance ("IDS") package prior to this one, although it is not a mandatory requirement. -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -28,7 +28,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension { #default-data-dimension } @@ -36,12 +36,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. @@ -51,7 +51,7 @@ You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -59,13 +59,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Generic metadata { #generic-metadata } @@ -73,7 +73,7 @@ The package contains some metadata that is typically common or shared across man Generic Data Elements used in the VPD CS package -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | GEN - Population | DkmMEcubiPv | `../api/dataElements.json?filter=name:like:GEN - Population` | | GEN - Population < 15years | cPLAnOTldta | `../api/dataElements.json?filter=name:like:GEN - Population` | @@ -82,7 +82,7 @@ Generic Data Elements used in the VPD CS package Category options, categories, category Combos for ages -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | 0-4 years | UPvKbcqTEY3 | `../api/categoryOptions.json?filter=name:like:years` | | 5+ years | afpMrUgPzl3 | `../api/categoryOptions.json?filter=name:like:years` | @@ -115,21 +115,21 @@ Rename the existing object in your DHIS2 database for which there is a conflict. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } @@ -141,12 +141,12 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | | --- | --- | --- | --- | | | VPD CS access | VPD CS admin | VPD CS data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](#sharing) for more information on configuring sharing. @@ -161,10 +161,10 @@ If your TET Person already matches the one in the package and you want to avoid ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. @@ -176,17 +176,17 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__vpd-cs-installation-annex-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__vpd-cs-installation-annex-md index bd6e3dcf4..7e58066c7 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__vpd-cs-installation-annex-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE-TRACKER__vpd-cs-installation-annex-md @@ -9,7 +9,7 @@ revision_date: "2022-09-16" The VPD CS tracker package is self-contained, meaning it can be installed on its own. However, it is worth noticing that this package contains some metadata from the IDSR package. The reason for this is that there is a comparative table which makes it possible to compare the aggregated data and the tracker data. Thus, we recommend installing the aggregate disease surveillance ("IDS") package prior to this one, although it is not a mandatory requirement. -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -28,7 +28,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension { #default-data-dimension } @@ -36,12 +36,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. @@ -51,7 +51,7 @@ You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -59,13 +59,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Generic metadata { #generic-metadata } @@ -73,7 +73,7 @@ The package contains some metadata that is typically common or shared across man Generic Data Elements used in the VPD CS package -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | GEN - Population | DkmMEcubiPv | `../api/dataElements.json?filter=name:like:GEN - Population` | | GEN - Population < 15years | cPLAnOTldta | `../api/dataElements.json?filter=name:like:GEN - Population` | @@ -82,7 +82,7 @@ Generic Data Elements used in the VPD CS package Category options, categories, category Combos for ages -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | 0-4 years | UPvKbcqTEY3 | `../api/categoryOptions.json?filter=name:like:years` | | 5+ years | afpMrUgPzl3 | `../api/categoryOptions.json?filter=name:like:years` | @@ -115,21 +115,21 @@ Rename the existing object in your DHIS2 database for which there is a conflict. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } @@ -141,12 +141,12 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | | --- | --- | --- | --- | | | VPD CS access | VPD CS admin | VPD CS data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](#sharing) for more information on configuring sharing. @@ -161,10 +161,10 @@ If your TET Person already matches the one in the package and you want to avoid ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. @@ -176,17 +176,17 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md index da35245be..5a79540f8 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__DISEASE-SURVEILLANCE__VPD-CASE-SURVEILLANCE__installation-md @@ -7,11 +7,11 @@ tags: # VPD CS Tracker Installation Annex { #vpd-cs-installation } -## Overview { #overview } +## Visión general { #overview } The VPD CS tracker package is self-contained, meaning it can be installed on its own. However, it is worth noticing that this package contains some metadata from the IDSR package. The reason for this is that there is a comparative table which makes it possible to compare the aggregated data and the tracker data. Thus, we recommend installing the aggregate disease surveillance ("IDS") package prior to this one, although it is not a mandatory requirement. -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,41 +20,41 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -62,13 +62,13 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |--------|-------------|--------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Generic metadata { #generic-metadata } @@ -76,7 +76,7 @@ The package contains some metadata that is typically common or shared across man Generic Data Elements used in the VPD CS package -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------------------------|-------------|--------------------------------------------------------------| | GEN - Population | DkmMEcubiPv | `../api/dataElements.json?filter=name:like:GEN - Population` | | GEN - Population < 15years | cPLAnOTldta | `../api/dataElements.json?filter=name:like:GEN - Population` | @@ -85,7 +85,7 @@ Generic Data Elements used in the VPD CS package Category options, categories, category Combos for ages -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |--------------------|-------------|------------------------------------------------------| | 0-4 years | UPvKbcqTEY3 | `../api/categoryOptions.json?filter=name:like:years` | | 5+ years | afpMrUgPzl3 | `../api/categoryOptions.json?filter=name:like:years` | @@ -98,7 +98,7 @@ There are many predictors in the package which are using a placeholder for distr The placeholder uses the label . Before attempting to import the package you need to replace this label with the UID of the equivalent OUL in your system. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -107,35 +107,35 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } There are three user groups that come with the package: @@ -145,12 +145,12 @@ There are three user groups that come with the package: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|------------------------------------|---------------------------------------------|------------------------------------------------| | | VPD CS access | VPD CS admin | VPD CS data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](#sharing) for more information on configuring sharing. @@ -163,35 +163,35 @@ If your TET Person already matches the one in the package and you want to avoid * Import the package * Update sharing properties for this TET using the table above. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md index a93b2bbd6..3e0286fd6 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__BREEDING-SITES-MONITORING__LARVICIDING__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -113,50 +113,50 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Program stages - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -166,7 +166,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _ENTO - Field Access_ | _ENTO - Field Data Capture_ | _ENTO - Field Admin_ | | _*Tracked entity type*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: no access | @@ -176,16 +176,16 @@ By default, the following permissions are assigned to these user groups: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -196,22 +196,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md index 85f3cfb44..d72703ad6 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__CAMPAIGN__installation-md @@ -11,7 +11,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,49 +20,49 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -71,35 +71,35 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -#### Sharing { #sharing } +#### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: @@ -115,11 +115,11 @@ A metadata package usually contains several user groups: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | VC-IRS Access | VC-IRS Admin | VC-IRS Data Capture | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | Please refere to the individual package installation annex for information about user groups. @@ -127,36 +127,36 @@ Please refere to the individual package installation annex for information about You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](#sharing) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. 2. Tracker data capture : Can add data values, access capture to create events Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the event program](#adapting-the-event-program)." Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the event program { #adapting-the-event-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. * Adapting the Category Combo used in the Event program to use category options for the Partners involved in the campaign -* Adding translations to variables and/or the data entry form. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md index 60fe3d6a7..f9e0c20ef 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INDOOR-RESIDUAL-SPRAYING__RESIDUAL-EFFICACY-MONITORING__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -113,49 +113,49 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -165,7 +165,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _ENTO - Field Access_ | _ENTO - Field Data Capture_ | _ENTO - Field Admin_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: no access | @@ -173,16 +173,16 @@ By default, the following permissions are assigned to these user groups: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -193,22 +193,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md index 282dc6056..a7ccbe89e 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__BIOEFFICACY__installation-md @@ -9,56 +9,56 @@ tags: ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). -## Metadata files { #metadata-files } +## Archivos de metadatos { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -|Object | UID | API endpoint | +|Objeto | UID | API endpoint | |-----------------------------|---------------|-----------------------------------------------------------| | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ### Option codes { #option-codes } @@ -113,49 +113,49 @@ Sort order can be adjusted in the Maintenance app. 2. Open the "Options" section 3. Use "SORT BY NAME", "SORT BY CODE/VALUE" or "SORT MANUALLY" alternatives. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. > **NOTE** > > If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After importing the metadata, proceed to the “[Configuration](#configuration)” section. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } -First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: +Primero, tendrá que usar la funcionalidad *Compartir* de DHIS2 para configurar qué usuarios (grupos de usuarios) deben ver los metadatos y los datos asociados con el programa, así como quién puede registrar/introducir datos en el programa. De forma predeterminada, el uso compartido se ha configurado para lo siguiente: - Programa - Tableros -- Visualizations, maps, event reports and report tables +- Visualizaciones, mapas, informes de eventos y tablas de informes -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. The following core user groups are included in the package: @@ -165,7 +165,7 @@ The following core user groups are included in the package: By default, the following permissions are assigned to these user groups: -|Object |User Group | | | +|Objeto |User Group | | | |-------------------------|-----------------------------------------------|-----------------------------------------------------|---------------------------------------------------| | | _ENTO - Field Access_ | _ENTO - Field Data Capture_ | _ENTO - Field Admin_ | | _*Program*_ | Metadata : can view
Data: can view | Metadata : can view
Data: can capture and view | Metadata : can edit and view
Data: no access | @@ -173,16 +173,16 @@ By default, the following permissions are assigned to these user groups: The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the set up. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } The program and the data sets must be assigned to organisation units within existing hierarchy in order to be accessible via tracker capture/capture apps. @@ -193,22 +193,22 @@ The program and the data sets must be assigned to organisation units within exis > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the Program { #adapting-the-program } -Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that *could* be made include: +Una vez que se haya importado el programa, es posible que desee realizar ciertas modificaciones en él. Algunos ejemplos de adaptaciones locales que *podrían* realizarse son: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. -## Removing metadata { #removing-metadata } +## Eliminar metadatos { #removing-metadata } In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md index ab7baea38..7f45553f6 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__ENTOMOLOGY-AND-VECTOR-CONTROL__INSECTICIDE-TREATED-NETS__MASS-DISTRIBUTION-CAMPAIGN__installation-md @@ -11,7 +11,7 @@ You will have to follow the instructions in full for each separate package that ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. 2. [Importing](#generic-metadata) the metadata file into DHIS2. @@ -20,41 +20,41 @@ Installation of the module consists of several steps: It is recommended to first read through each section before starting the installation and configuration process in DHIS2. Sections that are not applicable have been identified, depending on if you are importing into a new instance of DHIS2 or a DHIS2 instance with metadata already present. The procedure outlined in this document should be tested in a test/staging environment before either being repeated or transferred to a production instance of DHIS2. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/en/home.html). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the "Preparing the metadata file" section and move immediately to the section on "[Importing a metadata file into DHIS2](#generic-metadata)." -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. -### Default data dimension { #default-data-dimension } +### Dimensión de datos predeterminada { #default-data-dimension } In early versions of DHIS2, the UID of the default data dimension was auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |-----------------------------|-------------|----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default`| For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |------------|-------------|--------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -62,15 +62,15 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |---------------|-------------|-----------------------------------------------------------| | VC- Household | fT6xzEDXQAu | `../api/trackedEntityTypes.json?filter=name:eq:Household` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. -### Importing metadata { #importing-metadata } +### Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](#import_export) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#additional-configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. @@ -79,39 +79,39 @@ If the "dry run"/"validate" import works without error, attempt to import the me For generic metadata overview (identical metadata objects used by several packages), please refer to the installation annex of the individual package. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to to conflict with. Follow the instructions to import the metadata then please proceed to the [“Additional configuration”](#additional-configuration) section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -#### Sharing { #sharing } +#### Compartir { #sharing } First, you will have to use the *Sharing* functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -124,12 +124,12 @@ A metadata package usually contains several user groups: By default the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | VC-ITN Access | VC-ITN Admin | VC-ITN Data Capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | Please refere to the individual package installation annex for information about user groups. @@ -142,36 +142,36 @@ If your TET Household already matches the one in the package and you want to avo * Import the package * Update sharing properties for this TET using the table above. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](#manage_user_role_group) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to "[Adapting the tracker program](#adapting-the-tracker-program)." -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ### Adapting the tracker and event programs { #adapting-the-tracker-and-event-programs } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that *could* be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. * Adapting the Category Combo used in the Event program to use category options for the years you are doing the campaigns -* Adding translations to variables and/or the data entry form. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-110__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-110__installation-md index 414e465e0..4801b73e2 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-110__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-110__installation-md @@ -61,7 +61,7 @@ The [Configuration](https://who.dhis2.org/documentation/installation_guide_compl **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Default data dimension { #default-data-dimension } @@ -69,12 +69,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. @@ -82,9 +82,9 @@ For example, if importing a configuration package into [https://play.dhis2.org/d Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -111,16 +111,16 @@ Rename the existing object for which there is a conflict. The advantage of this Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: - it requires expert knowledge of the detail metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. - as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -- future updates to the configuration package will be complicated. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -155,7 +155,7 @@ The user groups that usually come with the package include: We recommend to provide the following access to these groups -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _{Package Name} access_ | _{Package Name} admin_ | _{Package Name} data capture_ | | _Data Elements/Data element group_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-120__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-120__installation-md index 2ac7e52e1..ec8b58a11 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-120__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-AGGREGATE__VERSION-120__installation-md @@ -3,148 +3,148 @@ edit_url: "https://github.com/dhis2-metadata/HIV_AGG/blob/master/docs/hiv_agg-in revision_date: "2022-06-16" --- -# HIV HMIS Aggregate Installation Guide { #hiv-agg-installation } +# Guía de instalación Agregados VIH HMIS { #hiv-agg-installation } -This document includes an installation guide for the HIV aggregate packages. +Este documento incluye una guía de instalación para los paquetes agregados VIH. -System default language: English +Idioma predeterminado del sistema: Inglés ## Visión general { #overview } -The package metadata json files contain a "package" component that provides technical details on package version and content. The files available in the current version of the package are listed below. +Los archivos json de metadatos del paquete contienen un componente "paquete" que proporciona detalles técnicos sobre la versión y el contenido del paquete. Los archivos disponibles en la versión actual del paquete se enumeran a continuación. ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: -1. [Preparing the metadata file with DHIS2 metadata](#preparing-the-metadata-file). -2. [Importing the metadata file into DHIS2](#importing-metadata). -3. [Configuring the imported metadata](#configuration). -4. [Adapting the program after import](#adapting-the-program) +1. [Preparar el archivo de metadatos con metadatos DHIS2](#preparing-the-metadata-file). +2. [Importar el archivo de metadatos en DHIS2](#importing-metadata). +3. [Configurar los metadatos importados](#configuration). +4. [Adaptar el programa después de la importación](#adapting-the-program) -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: -1. import into a blank DHIS2 instance -2. import into a DHIS2 instance with existing metadata. +1. importar a una instancia DHIS2 en blanco +2. importar a una instancia DHIS2 con metadatos existentes. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. ## Requisitos { #requirements } -In order to install the module, an administrator user account on DHIS2 is required. +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. -Great care should be taken to ensure that the server itself and the DHIS2 application are well secured, access rights to collected data should be defined. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](https://docs.dhis2.org/). +Se debe tener mucho cuidado para garantizar que el servidor en sí y la aplicación DHIS2 estén bien protegidos, asimismo se deben definir los derechos de acceso a los datos recopilados. Los detalles sobre cómo proteger un sistema DHIS2 están fuera del alcance de este documento, por lo que remitimos a la [documentación de DHIS2](https://docs.dhis2.org/). ## Metadata files { #metadata-files } -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Preparing the metadata file { #preparing-the-metadata-file } -It is required to apply some changes to the metadata file before it can be imported. The scope of work may vary from package to package. +Es necesario aplicar algunos cambios al archivo de metadatos antes de poder importarlo. El alcance del trabajo puede variar de un paquete a otro. ### Default data dimension { #default-data-dimension } -In early versions of DHIS2, the UIDs of the default data dimensions were auto-generated. Thus, while all DHIS2 instances have a default category option, data element category, category combination and category option combination, the UIDs of these defaults can be different. Later versions of DHIS2 have hardcoded UIDs for the default dimension, and these UIDs are used in the configuration packages. +En las primeras versiones de DHIS2, los UID de las dimensiones de datos predeterminadas se generaban automáticamente. Por lo tanto, si bien todas las instancias de DHIS2 tienen una opción de categoría predeterminada, una categoría de elemento de datos, una combinación de categoría y una combinación de opciones de categoría, los UID de estos valores predeterminados pueden ser diferentes. Las versiones posteriores de DHIS2 tienen UID codificados para la dimensión predeterminada y estos UID se utilizan en los paquetes de configuración. -To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs from the instance in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs +Para evitar conflictos al importar los metadatos, es recomendable buscar y reemplazar en todo el archivo .json todas las apariciones de estos objetos predeterminados, reemplazando los UID del archivo .json con los UID de la instancia en la que se importará el archivo. La Tabla 1 muestra los UID que deben reemplazarse, así como los API endpoints para identificar los UID existentes -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | `GLevLNI9wkl` | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | `xYerKDKCefk` | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | `bjDvmb4bfuf` | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | `HllvX50cXC0` | `../api/categoryOptionCombos.json?filter=name:eq:default` | -Identify the UIDs of the default dimesions in your instance using the listed API requests and replace the UIDs in the json file with the UIDs from the instance. +Identifique los UID de las dimensiones predeterminadas en su instancia utilizando las solicitudes API enumeradas y reemplace los UID en el archivo json con los UID de la instancia. -> **NOTE** +> **NOTA** > -> Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. +> Tenga en cuenta que esta operación de búsqueda y reemplazo debe realizarse con un editor de texto plano, no con un procesador de textos como Microsoft Word. ### Indicator types { #indicator-types } -Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined by their factor (including 1 for "numerator only" indicators), they are unambiguous and can be replaced through a search and replace of the UIDs. This method helps avoid potential import conflicts, and prevents the implementer from creating duplicate indicator types. The table below contains the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs: +El tipo de indicador es otro tipo de objeto que puede crear conflictos de importación porque ciertos nombres se utilizan en diferentes bases de datos DHIS2 (por ejemplo, "Porcentaje"). Dado que los tipos de indicadores se definen por su factor (incluido 1 para indicadores "solo numerador"), no son ambiguos y se pueden reemplazar mediante una búsqueda y reemplazo de los UID. Este método ayuda a evitar posibles conflictos de importación y evita que el implementador cree tipos de indicadores duplicados. La siguiente tabla contiene los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes: -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | +| Sólo numerador (número) | `CqNPn5KzksS` | `../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1` | ### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. ## Importing metadata { #importing-metadata } -Use [Import/Export](#import_export) DHIS2 app to import metadata packages. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configuring](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. +Utilice la aplicación DHIS2 [Importar/Exportar](#import_export) para importar paquetes de metadatos. Es recomendable utilizar la función de proceso de prueba "dry run" para identificar problemas antes de intentar realizar una importación real de los metadatos. Si el "dry run" informa algún problema o conflicto, consulte la sección [conflictos de importación](#handling-import-conflicts) más abajo. Si la importación "dry run"/"validar" funciona sin errores, intente importar los metadatos. Si la importación se realiza correctamente sin errores, puede proceder a [configurar](#configuration) el módulo. En algunos casos, los conflictos o problemas de importación no se muestran durante el proceso de prueba "dry run", pero aparecen cuando se intenta la importación real. En este caso, el resumen de la importación enumerará los errores que deben resolverse. ### Handling import conflicts { #handling-import-conflicts } -> **NOTE** +> **NOTA** > -> If you are importing the package into a new DHIS2 instance, you will not experience import conflicts, as there is no metadata in the target database. After import the metadata, proceed to the “[Configuration](#configuration)” section. +> Si está importando el paquete a una nueva instancia de DHIS2, no experimentará conflictos de importación, ya que no hay metadatos en la base de datos de destino. Después de importar los metadatos, vaya a la sección “[Configuración](#configuration)”. -There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exist in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. +Pueden ocurrir varios conflictos diferentes, aunque el más común es que haya objetos de metadatos en el paquete de configuración con un nombre, nombre corto y/o código que ya existe en la base de datos de destino. Hay un par de soluciones alternativas a estos problemas, con diferentes ventajas y desventajas. Cuál sea la más adecuada dependerá, por ejemplo, del tipo de objeto para el que se produce un conflicto. #### Alternative 1 { #alternative-1 } -Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when updates to the package are released. The original package objects are also often referenced in training materials and documentation. +Cambiar el nombre del objeto existente en su base de datos DHIS2 para el cual existe un conflicto. La ventaja de este enfoque es que no es necesario modificar el archivo .json, ya que los cambios se realizan a través de la interfaz de usuario de DHIS2. Es probable que esto sea menos propenso a errores. También significa que el paquete de configuración se deja como está, lo que puede ser una ventaja, por ejemplo, cuando se publican actualizaciones del paquete. Con frecuencia también se hace referencia a los objetos del paquete original en la documentación y los materiales de formación. #### Alternative 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Configuration { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the program as well as who can register/enter data into the program. By default, sharing has been configured for the following: - Tableros -- Visualizations, maps, event reports and report tables -- Data sets -- Category options +- Visualizaciones, mapas, informes de eventos y tablas de informes +- Sets de datos +- Opciones de categoría -Please refer to the [DHIS2 documentation](#sharing) for more information on sharing. +Consulte la [documentación DHIS2]](#sharing) para obtener más información sobre compartir. -Three core user groups are included in the packages: +Los paquetes incluyen tres grupos de usuarios principales: -- HIV access (view metadata/view data) -- HIV admin (view and edit metadata/no access to data) -- HIV data capture - (view metadata/capture and view data) +- VIH Acceso (ver metadatos/ver datos) +- VIH admin (ver y editar metadatos/sin acceso a datos) +- VIH captura de datos - (ver metadatos/capturar y ver datos) -For HIV Stock package the groups are: +Para el paquete Stock VIH, los grupos son: -- HIV access (view metadata/view data) -- HIV admin (view and edit metadata/no access to data) -- HIV stock data capture - (view metadata/capture and view data) +- VIH Acceso (ver metadatos/ver datos) +- VIH admin (ver y editar metadatos/sin acceso a datos) +- VIH captura de datos de stock - (ver metadatos/capturar y ver datos) -The users are assigned to the appropriate user group based on their role within the system. Sharing for other objects in the package may be adjusted depending on the setup. Refer to the [DHIS2 Documentation on sharing](#sharing) for more information. +Los usuarios se asignan al grupo de usuarios apropiado según su función dentro del sistema. El uso compartido de otros objetos del paquete se puede ajustar en función de la configuración. Consulte la [Documentación de DHIS2 sobre compartir](#sharing) para obtener más información. ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker -Refer to the [DHIS2 Documentation](https://docs.dhis2.org/) for more information on configuring user roles. +Consulte la [Documentación de DHIS2](https://docs.dhis2.org/) para obtener más información sobre la configuración de roles de usuario. ### Organisation unit assignment { #organisation-unit-assignment } -The data sets must be assigned to organisation units within existing hierarchy in order to be accessible via capture app. +Los sets de datos deben asignarse a unidades organizativas dentro de la jerarquía existente para que sean accesibles a través de la aplicación capturar. ### Indicator mapping { #indicator-mapping } @@ -156,21 +156,21 @@ When implementing the _dashboard package_ only, the indicator numerators and den > > This section only applies if you are importing into a DHIS2 database with existing metadata. If you are working with a new/blank DHIS2 instance, please skip this section and go to [Adapting the program](#adapting-the-program). If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. -One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](#sharing). +Una cosa importante a tener en cuenta es que DHIS2 tiene herramientas que pueden ocultar algunas de las complejidades de posibles duplicaciones en los metadatos. Por ejemplo, cuando existen set de opciones duplicados, se pueden ocultar para grupos de usuarios mediante [compartir](#sharing). ## Adapting the program { #adapting-the-program } Once the program has been imported, you might want to make certain modifications to the program. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. -- Modifying indicators based on local case definitions +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. +- Modificación de indicadores basados ​​en definiciones de casos locales -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Removing metadata { #removing-metadata } -In order to keep your instance clean and avoid errors, it is recommended that you remove the unnecessary metadata from your instance. Removing unnecessary metadat requires advanced knowledge of DHIS2 and various dependenies. +Para mantener su instancia limpia y evitar errores, se recomienda eliminar los metadatos innecesarios de su instancia. La eliminación de metadatos innecesarios requiere conocimientos avanzados de DHIS2 y varias dependencias. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE-TRACKER__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE-TRACKER__installation-md index 334849a6e..258fc5f91 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE-TRACKER__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE-TRACKER__installation-md @@ -19,7 +19,7 @@ You will have to follow the instructions to ensure that the package is installed ## Installation { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. @@ -38,7 +38,7 @@ Great care should be taken to ensure that the server itself and the DHIS2 applic **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section [Importing a metadata file into DHIS2](#importing-metadata) -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension (if applicable) { #default-data-dimension-if-applicable } @@ -46,12 +46,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | :-- | :-- | :-- | | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into , the UID of the default category option combination could be identified through as bRowv6yZOF2. @@ -61,7 +61,7 @@ You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | :-- | :-- | :-- | | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | @@ -69,9 +69,9 @@ Indicator type is another type of object that can create import conflict because Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | :-- | :-- | :-- | -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | ## Importing metadata { #importing-metadata } @@ -91,27 +91,27 @@ Rename the existing object in your DHIS2 database for which there is a conflict. **_Alternative 2_** -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. **_Alternative 3_** -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -- it requires expert knowledge of the detailed metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -- future updates to the configuration package will be complicated. +- requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +- las futuras actualizaciones del paquete de configuración serán complicadas. ### Additional configuration { #additional-configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. ### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -- Tracked entity type +- Tipo de entidad Tracked - Programa - Program stages - Tableros @@ -124,10 +124,10 @@ There are four user groups that come with the package: By default the following is assigned to these user groups -| Object | User groups | | | | +| Objeto | User groups | | | | | --- | --- | --- | --- | --- | | | HIV - CS Admin | HIV CS- Data capture | HIV CS - Data analytics | | -| Tracked entity type | XXX | Metadata: can edit and view Data: can view | Metadata: can view Data: can capture and view | Metadata: can view Data: ca view | +| Tipo de entidad Tracked | XXX | Metadata: can edit and view Data: can view | Metadata: can view Data: can capture and view | Metadata: can view Data: ca view | | Programa | XXX | Metadata: can edit and view Data: can view | Metadata: can view Data: can capture and view | Metadata: can view Data: can view | | Tableros | XXX | Metadata: can edit and view Data: can view | Metadata: can view Data: can view | Metadata: can view Data: can view | | | | | | | @@ -136,10 +136,10 @@ You will want to assign your users to the appropriate user group based on their ### User Roles { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. @@ -151,7 +151,7 @@ You must assign the program to organisation units within your own hierarchy in o **NOTE:** This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, you may skip this section. -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. One important thing to keep in mind is that DHIS2 has tools that can hide some of the complexities of potential duplications in metadata. For example, where duplicate option sets exist, they can be hidden for groups of users through [sharing](https://docs.dhis2.org/master/en/user/html/sharing.html). @@ -185,12 +185,12 @@ Captura de Pantalla Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -- Adding additional variables to the form. -- Adapting data element/option names according to national conventions. -- Adding translations to variables and/or the data entry form. +- Añadir variables adicionales al formulario. +- Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +- Añadir traducciones a las variables y/o al formulario de entrada de datos. - Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. ## Event Reports { #event-reports } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__design-md index 9560b0ef5..e7c9425d7 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__design-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__design-md @@ -45,7 +45,7 @@ Por lo tanto, el kit de herramientas de Vigilancia de Casos de VIH aprovecha tod El kit de herramientas de Vigilancia de Casos de VIH está diseñado para respaldar la recopilación de datos de rutina para programas que ayudan a las personas que viven con el VIH a inscribirse en un programa de VIH y recibir servicios de pruebas, atención y tratamiento del VIH. El sistema está diseñado para reunir datos con el fin de generar indicadores granulares de vigilancia de casos de VIH y sus desgloses para análisis de datos de rutina, monitoreo centrado en la persona e información estratégica a través de tableros flexibles y análisis ad hoc con herramientas de análisis DHIS2. -Los componentes de captura de datos del diseño del sistema permiten al personal de los sitios de prestación de servicios, o a niveles superiores dependiendo de los contextos locales, capturar los elementos de datos básicos durante las interacciones rutinarias con los participantes del programa de atención y tratamiento del VIH que permitirán al personal del programa generar indicadores clave de desempeño, tal como se detalla en las [Directrices consolidadas para la información estratégica sobre el VIH centrada en la persona (OMS, 2022)] de la OMS (https://www.who.int/publications/i/item/9789240055315). Este componente utiliza el modelo de datos Tracker DHIS2. Aunque el programa Tracker de Vigilancia de Casos de VIH DHIS2 no está optimizado para respaldar la gestión de casos clínicos o el apoyo a la toma de decisiones, sirve como un registro electrónico útil que da soporte a la captura electrónica descentralizada de datos de vigilancia de casos hasta el establecimiento de salud o cualquier otro punto de servicio procedente de todo tipo de actores, incluidos los servicios prestados a nivel comunitario. Los datos de seguimiento a nivel individual se agregan utilizando los indicadores de programa DHIS2, que se asignan a elementos de datos agregados y set de datos para completar los indicadores básicos y servir a los tableros analíticos con datos anónimos. +Los componentes de captura de datos del diseño del sistema permiten al personal de los sitios de prestación de servicios, o a niveles superiores dependiendo de los contextos locales, capturar los elementos de datos básicos durante las interacciones rutinarias con los participantes del programa de atención y tratamiento del VIH que permitirán al personal del programa generar indicadores clave de desempeño, tal como se detalla en las [Directrices consolidadas sobre información estratégica del VIH centrada en la persona (OMS, 2022)] de la OMS (https://www.who.int/publications/i/item/9789240055315). Este componente utiliza el modelo de datos Tracker DHIS2. Aunque el programa Tracker de Vigilancia de Casos de VIH DHIS2 no está optimizado para respaldar la gestión de casos clínicos o el apoyo a la toma de decisiones, sirve como un registro electrónico útil que da soporte a la captura electrónica descentralizada de datos de vigilancia de casos hasta el establecimiento de salud o cualquier otro punto de servicio procedente de todo tipo de actores, incluidos los servicios prestados a nivel comunitario. Los datos de seguimiento a nivel individual se agregan utilizando los indicadores de programa DHIS2, que se asignan a elementos de datos agregados y set de datos para completar los indicadores básicos y servir a los tableros analíticos con datos anónimos. La estructura del programa Tracker DHIS2 se ha armonizado y sigue la misma lógica que el Tracker de prevención del VIH, lo que permite que una persona inscrita en un programa de prevención ingrese al programa de vigilancia de casos con un diagnóstico positivo de VIH. En algunos contextos, puede ser conveniente integrar la prevención y la vigilancia de casos en un único programa de seguimiento. La armonización de los elementos de datos entre los dos seguimientos permitirá la adaptación e integración local, que se describe más adelante en la sección "Implementar" de este documento. @@ -451,7 +451,7 @@ En el numerador de este indicador debemos contar las MVVS con diagnóstico de c ### Indicadores de programa { #program-indicators } -Los **indicadores del programa** se utilizan para agregar datos a nivel individual capturados en el modelo de datos del tracker; y asignarlos al modelo de datos agregados para su presentación, consumo y uso en las aplicaciones y tableros de análisis de DHIS2. El uso de la aplicación intercambio de datos DHIS2 para transferir valores de los indicadores de programa a elementos de datos agregados se describe con más detalle en la sección sobre Mapeo de metadatos e intercambio de datos. +Los **indicadores del programa** se utilizan para agregar datos a nivel individual capturados en el modelo de datos del tracker; y asignarlos al modelo de datos agregados para su presentación, consumo y uso en las aplicaciones y tableros de análisis de DHIS2. El uso de la aplicación Data Exchange DHIS2 para transferir valores de los indicadores de programa a elementos de datos agregados se describe con más detalle en la sección sobre mapeo de metadatos e intercambio de datos. Los indicadores de programa se organizan en dos grupos de indicadores de programa: - *Vigilancia de casos de VIH - Intercambio de datos* [s7DBTTX68Lk] contiene todos los IP que están asignados a los elementos de datos agregados de destino correspondientes para su análisis. @@ -463,11 +463,11 @@ Los indicadores de programa se organizan en dos grupos de indicadores de program #### Filtro de población clave en indicadores de programa{ #key-population-filter-in-program-indicators } -Como se describe en la sección sobre *Elementos de datos ocultos y valores asignados*, las reglas del programa se utilizan para asignar y copiar el grupo de población clave de la TEI registrado en el informe de caso inicial a un campo de elemento de datos ocultos en la etapa de programa de visita repetible. Esto permite configurar todos los cálculos de indicadores de programa basados ​​en el grupo de población clave, concretamente utilizando el elemento de datos asignado automáticamente como filtro en el indicador de programa. +Como se describe en la sección sobre *Elementos de datos ocultos y valores asignados*, las reglas del programa se utilizan para asignar y copiar el grupo de población clave de la TEI registrado en el informe de caso inicial a un campo de elemento de datos ocultos en la etapa de programa visita repetible. Esto permite configurar todos los cálculos de indicadores de programa basados ​​en el grupo de población clave, concretamente utilizando el elemento de datos asignado automáticamente como filtro en el indicador de programa. Tenga en cuenta que al ajustar los indicadores de programa que filtran en función del grupo de población clave, debe utilizar el conjunto de elementos de datos que contienen el sufijo “- VISITA”: -- IH - Población clave - Hombres que tienen relaciones sexuales con hombres - VISITAS [kXutCUTOxcq] +- VIH - Población clave - Hombres que tienen relaciones sexuales con hombres - VISITAS [kXutCUTOxcq] - VIH - Población clave - Personas que se inyectan drogas - VISITAS [GSSOfwzb0DQ] - VIH - Población clave - Personas que viven en prisiones y otros entornos cerrados - VISITAS [iqXxZbRDhYG] - VIH - Población clave - Trabajador sexual - VISITAS [kICLXq7IEuP] @@ -527,7 +527,7 @@ Se crea un elemento de datos que informa VERDADERO en caso de que la primera pru Además, se crea otro elemento de datos que informa la fecha de la primera prueba de TB (si es un mWRD) y el valor reportado en los siguientes eventos **ITS.8 Repetición del diagnóstico del síndrome de ITS** -El período del informe del indicador se ha establecido como los “últimos 12 meses”, por lo que el resultado será la proporción de clientes diagnosticados con un síndrome de ITS concreto dos o más veces en los últimos 12 meses. +El período de informe del indicador se ha establecido como los “últimos 12 meses”, por lo que el resultado será la proporción de clientes diagnosticados con un síndrome de ITS concreto dos o más veces en los últimos 12 meses. En el numerador necesitamos calcular el número de personas que asisten a los servicios de prevención del VIH diagnosticadas con un síndrome de ITS concreto dos o más veces. Este filtro se basa en los elementos de datos ocultos asignados con valores para la "fecha del último diagnóstico": @@ -559,13 +559,13 @@ Este elemento de datos *VIH - Cáncer de cuello uterino: último diagnóstico de As described above, all the dashboards and indicators are supported by an aggregate data model. This allows for mixed methods of reporting from various electronic and paper-based sources, enabling all data to be brought together for the purpose of analysis and use such as in an integrated HMIS. -Cuando los elementos de datos agregados objetivo se pueden completar agregando los datos de seguimiento subyacentes desde el tracker de vigilancia de casos de VIH, hemos preconfigurado un conjunto de indicadores de programa e incluido el mapeo de las dimensiones agregadas objetivo (CÓDIGO de elemento de datos y CÓDIGO de Combinación de Opciones de Categoría). +Donde los elementos de datos agregados objetivo se pueden completar agregando los datos de seguimiento subyacentes desde el tracker de vigilancia de casos de VIH, hemos preconfigurado un conjunto de indicadores de programa e incluido el mapeo de las dimensiones agregadas objetivo (CÓDIGO de elemento de datos y CÓDIGO de Combinación de Opciones de Categoría). Véase [Documentación para el usuario DHIS2 sobre cómo utilizar la aplicación Data Exchange](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-240/exchanging-data/data-exchange.html). Véase [Documentación para desarrolladores de DHIS2 sobre las API de DHIS2 para el intercambio de datos agregados](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-240/data-exchange.html?h=aggregate+data+exchange+2.40#create-aggregate-data-exchange) para obtener más información. -Los metadatos se han alineado con los diccionarios de datos y las referencias de indicadores publicados en el kit de adaptación digital (DAK) para el VIH de la OMS, segunda edición (véase el Anexo A de la Web del kit de adaptación digital para el diccionario de datos). Tenga en cuenta que el Tracker no está diseñado para respaldar todos los aspectos de las directrices de atención clínica y la gestión de casos, algunos de los cuales están contenidos en el VIH DAK, ni para reemplazar los EMR sólidos de los establecimeintos; sin embargo, los datos de los EMR se pueden incorporar al registro nacional del VIH para su análisis y uso. +Los metadatos se han alineado con los diccionarios de datos y las referencias de indicadores publicados en el kit de adaptación digital (DAK) para el VIH de la OMS, segunda edición (véase el Anexo A de la Web del kit de adaptación digital para el diccionario de datos). Tenga en cuenta que el Tracker no está diseñado para respaldar todos los aspectos de las directrices de atención clínica y la gestión de casos, algunos de los cuales están contenidos en el DAK VIH, ni para reemplazar los EMR sólidos de los establecimeintos; sin embargo, los datos de los EMR se pueden incorporar al registro nacional del VIH para su análisis y uso. [Aquí](resources/files/data_exchange_mapping_cs.xlsx) puede encontrar la correlación entre los metadatos de DHIS2 y el diccionario de datos del DAK VIH. @@ -585,7 +585,7 @@ Cuando la seguridad y la posibilidad de desalentar el acceso a los servicios sea ### Adaptación de la estructura del tracker { #tracker-structure-adaptation } -La estructura de seguimiento de la vigilancia de casos de VIH es en su mayor parte una estructura plana con una sola etapa principal repetible para registrar las actividades de cualquier tipo de visita de prevención. Esta estructura intencionalmente simplificada permite una mayor flexibilidad para la adaptación y personalización local. Por ejemplo: +La estructura de seguimiento de la vigilancia de casos de VIH es principalmente una estructura plana con una sola etapa principal repetible para registrar las actividades de cualquier tipo de visita de prevención. Esta estructura intencionalmente simplificada permite una mayor flexibilidad para la adaptación y personalización local. Por ejemplo: - Las secciones se pueden traducir fácilmente en etapas en caso de que distintos usuarios tengan que ingresar información diferente (como se ha detallado anteriormente, el servicio de vigilancia de casos de VIH es muy transversal y puede tener varios actores involucrados en la distribución de los servicios) - Cantidad reducida de reglas de programa y bien identificadas por la sección a la que se dirige @@ -623,9 +623,9 @@ Los indicadores de programa pueden definir qué **dimensión de unidad organizat Encontrará información más detallada sobre el análisis de la propiedad en la [Guía de diseño del Tracker](https://docs.dhis2.org/en/implement/database-design/tracker-system-design/tracker-analytics.html#common-challenge-3-transfers-and-ownership). ->**Note:** +>**Nota:** > ->for implementations using DHIS2 software version 2.39 or lower, program indicators generated at any level below national will not reflect the current ‘ownership’ org unit. This means that if a TEI (person) who has been permanently transferred from one organisation unit (Health Facility A) to another (Health Facility B) for a given Tracker program enrollment *will still be counted as belonging to Health Facility A* for the purposes of program indicators. In practical terms, this means that when a patient has moved between sites, all longitudinal indicators for this patient are not re-assigned to the patient’s latest site, and remain assigned to the initial site where the patient first entered the program. This is a critical limitation for typical HIV use cases, where site level performance metrics such as lost-to-follow-up must be generated accurately at a subnational or facility level. If your implementation uses DHIS2 v2.39 or lower, please review your configuration carefully to see if you have accounted for the exclusion of persons ‘transferred out’ based on the org unit enrollment ownership. +>para implementaciones que utilicen el software DHIS2 versión 2.39 o inferior, los indicadores de programa generados en cualquier nivel por debajo del nacional no reflejarán la unidad organizativa de "propiedad" actual. Esto significa que si un TEI (persona) que ha sido transferido permanentemente de una unidad organizativa (Establecimiento de salud A) a otro (Establecimiento de salud B) para una determinada inscripción en el programa Tracker *aún se contará como perteneciente al Establecimiento de salud A* para el propósitos de los indicadores de programa. En términos prácticos, esto significa que cuando un paciente se ha movido entre sitios, todos los indicadores longitudinales para este paciente no se reasignan al último sitio del paciente y permanecen asignados al sitio inicial donde el paciente ingresó por primera vez al programa. Esta es una limitación crítica para los casos de uso típicos del VIH, donde las métricas de desempeño a nivel de sitio, como las pérdidas de seguimiento, deben generarse con precisión a nivel subnacional o de establecimiento. Si su implementación utiliza DHIS2 v2.39 o anterior, revise su configuración cuidadosamente para comprobar si ha tenido en cuenta la exclusión de personas "transferidas" en función de la propiedad de inscripción de la unidad organizativa. #### Fecha del evento vs fecha personalizada { #event-date-vs-custom-date } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__installation-md index c903620ba..b0f24f0db 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-CASE-SURVEILLANCE__installation-md @@ -9,36 +9,36 @@ tags: Package Version 2.0.0 -System default language: English +Idioma predeterminado del sistema: Inglés ## Instalación { #installation } -Installation of the module consists of several steps: +La instalación del módulo consta de varios pasos: 1. [Preparing](#preparing-the-metadata-file) the metadata file. 2. [Importing](#importing-metadata) the metadata file into DHIS2. 3. [Configuring](#configuration) the imported metadata. 4. [Adapting](#adapting-the-tracker-program) the program after being imported -It is recommended to first read through each section of the installation guide before starting the installation and configuration process in DHIS2. Identify applicable sections depending on the type of your import: +Se recomienda leer primero cada sección de la guía de instalación antes de comenzar el proceso de instalación y configuración en DHIS2. Identifique las secciones aplicables según el tipo de su importación: 1. Import into a blank DHIS2 instance 2. Import into a DHIS2 instance with existing metadata (No other versions of HIV Case Surveillance tracker imported previously). 3. Update existing/older version of the HIV Case Surveillance tracker. -The steps outlined in this document should be tested in a test/staging DHIS2 instance and only then applied to a production environment. +Los pasos descritos en este documento deben probarse en una instancia de prueba/preparación de DHIS2 y solo luego aplicarse a un entorno de producción. -## Requirements { #requirements } +## Requisitos { #requirements } In order to install the module, an administrator user account on DHIS2 is required. The procedure outlined in this document should be tested in a test/staging environment before being performed on a production instance of DHIS2. Great care should be taken to ensure that the server itself and the DHIS2 application is well secured, to restrict access to the data being collected. Details on securing a DHIS2 system is outside the scope of this document, and we refer to the [DHIS2 documentation](http://dhis2.org/documentation). -## Preparing the metadata file { #preparing-the-metadata-file } +## Preparar el archivo de metadatos { #preparing-the-metadata-file } **NOTE:** If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section [Importing a metadata file into DHIS2](#importing-metadata) -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ### Default data dimension (if applicable) { #default-data-dimension-if-applicable } @@ -46,39 +46,39 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:----------------------------|:------------|:----------------------------------------------------------| | Categoría | GLevLNI9wkl | `../api/categories.json?filter=name:eq:default` | | Opción de categoría | xYerKDKCefk | `../api/categoryOptions.json?filter=name:eq:default` | | Combinación de categoría | bjDvmb4bfuf | `../api/categoryCombos.json?filter=name:eq:default` | -| Category option combination | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | +| Combinación de opciones de categoría | HllvX50cXC0 | `../api/categoryOptionCombos.json?filter=name:eq:default` | For example, if importing a configuration package into , the UID of the default category option combination could be identified through as bRowv6yZOF2. You could then search and replace all occurrences of HllvX50cXC0 with bRowv6yZOF2 in the .json file, as that is the ID of default in the system you are importing into. **_Note that this search and replace operation must be done with a plain text editor_**, not a word processor like Microsoft Word. -### Indicator types { #indicator-types } +### Tipos de indicadores { #indicator-types } Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numbers without a denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-----------|:------------|:-------------------------------------------------------------------------| | Porcentaje | hmSnCXmLYwt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100` | | Rate (factor=1)| k4RGC3sMTzO | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:1`| | Per 10 000 | FWTvArgP0jt | `../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:10000`| -| Numerator only (number) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| +| Sólo numerador (número) | kHy61PbChXr | `..api/indicatorTypes.json?filter=number:eq:true`| ### Tipo de entidad Tracked { #tracked-entity-type } Like indicator types, you may have already existing tracked entity types in your DHIS2 database. The references to the tracked entity type should be changed to reflect what is in your system so you do not create duplicates. Table 3 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | |:-------|:------------|:-------------------------------------------------------| -| Person | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | +| Persona | MCPQUTHX1Ze | `../api/trackedEntityTypes.json?filter=name:eq:Person` | -### Visualizations using Root Organisation Unit UID { #visualizations-using-root-organisation-unit-uid } +### Visualizaciones utilizando el UID de la unidad organizativa raíz { #visualizations-using-root-organisation-unit-uid } -Visualizations, event reports, report tables and maps that are assigned to a specific organisation unit level or organisation unit group, have a reference to the root (level 1) organisation unit. Such objects, if present in the metadata file, contain a placeholder ``. Use the search function in the .json file editor to possibly identify this placeholder and replace it with the UID of the level 1 organisation unit in the target instance. +Las visualizaciones, informes de eventos, tablas de informes y mapas que están asignados a un nivel de unidad organizativa específico o grupo de unidades organizativas tienen una referencia a la unidad organizativa raíz (nivel 1). Dichos objetos, si están presentes en el archivo de metadatos, contienen un marcador de posición ``. Utilice la función de búsqueda en el editor de archivos .json para identificar este marcador de posición y reemplazarlo con el UID de la unidad organizativa de nivel 1 en la instancia de destino. Some visualizations and maps may contain references to organisation unit levels. Maps that consist of several map views may contain various Organisation unit level references based on the configuration of the map layer. Adjust the organisation unit level references in the metadata json file to match the organisation unit structure in the target instance before importing the metadata file. @@ -92,45 +92,45 @@ The process of upgrading an existing package to a newer version in a working DHI - the new objects are created; - assignment of users to relevant user groups is reviewed. -## Importing metadata { #importing-metadata } +## Importar metadatos { #importing-metadata } The .json metadata file is imported through the [Import/Export](https://docs.dhis2.org/master/en/user/html/import_export.html) app of DHIS2. It is advisable to use the "dry run" feature to identify issues before attempting to do an actual import of the metadata. If "dry run" reports any issues or conflicts, see the [import conflicts](#handling-import-conflicts) section below. If the "dry run"/"validate" import works without error, attempt to import the metadata. If the import succeeds without any errors, you can proceed to [configure](#configuration) the module. In some cases, import conflicts or issues are not shown during the "dry run", but appear when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. -### Handling import conflicts { #handling-import-conflicts } +### Gestión de conflictos de importación { #handling-import-conflicts } > NOTE: If you are importing into a new DHIS2 instance, you will not have to worry about import conflicts, as there is nothing in the database you are importing to conflict with. Follow the instructions to import the metadata then please proceed to the “[Configuration](#configuration)” section. There are a number of different conflicts that may occur, though the most common is that there are metadata objects in the configuration package with a name, shortname and/or code that already exists in the target database. There are a couple of alternative solutions to these problems, with different advantages and disadvantages. Which one is more appropriate will depend, for example, on the type of object for which a conflict occurs. -#### Alternative 1 { #alternative-1 } +#### Alternativa 1 { #alternative-1 } Rename the existing object in your DHIS2 database for which there is a conflict. The advantage of this approach is that there is no need to modify the .json file, as changes are instead done through the user interface of DHIS2. This is likely to be less error prone. It also means that the configuration package is left as is, which can be an advantage for example when training material and documentation based on the configuration package will be used. -#### Alternative 2 { #alternative-2 } +#### Alternativa 2 { #alternative-2 } -Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. +Cambiar el nombre del objeto para el que existe un conflicto en el archivo .json. La ventaja de este enfoque es que los metadatos DHIS2 existentes se dejan como están. Este puede ser un factor cuando existe material de formación o documentación como SOPs de diccionarios de datos vinculados al objeto en cuestión, y no implica ningún riesgo de confundir a los usuarios al modificar los metadatos con los que están familiarizados. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. -#### Alternative 3 { #alternative-3 } +#### Alternativa 3 { #alternative-3 } -A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an option set already exists for a certain concept (e.g. "sex"), that option set could be removed from the .json file and all references to its UID replaced with the corresponding option set already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. There are some key considerations to make when performing this type of modification: +Un tercer enfoque, más complicado, es modificar el archivo .json para reutilizar los metadatos existentes. Por ejemplo, en los casos en los que ya existe un set de opciones para un determinado concepto (por ejemplo, "sexo"), ese set de opciones podría eliminarse del archivo .json y todas las referencias a su UID podrían reemplazarse con el set de opciones correspondiente que ya se esté en la base de datos. La gran ventaja de esto (que no se limita a los casos en los que existe un conflicto de importación directo) es evitar la creación de metadatos duplicados en la base de datos. Hay algunas consideraciones clave que se deben tener en cuenta al realizar este tipo de modificación: -* it requires expert knowledge of the detailed metadata structure of DHIS2 -* the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. -* future updates to the configuration package will be complicated. +* requiere conocimiento especializado de la estructura detallada de metadatos de DHIS2 +* el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. +* las futuras actualizaciones del paquete de configuración serán complicadas. -## Configuration { #configuration } +## Configuración { #configuration } -Once all metadata has been successfully imported, there are a few steps that need to be taken before the module is functional. +Una vez que todos los metadatos se hayan importado correctamente, hay algunos pasos que deben seguirse antes de que el módulo sea funcional. -### Sharing { #sharing } +### Compartir { #sharing } First, you will have to use the _Sharing_ functionality of DHIS2 to configure which users (user groups) should see the metadata and data associated with the programme as well as who can register/enter data into the program. By default, sharing has been configured for the following: -* Tracked entity type +* Tipo de entidad Tracked * Programa * Program stages * Tableros @@ -143,46 +143,46 @@ A metadata package usually contains several user groups: By default, the following is assigned to these user groups -| Object | User Groups | | | +| Objeto | Grupos de usuarios | | | |---------------------|-----------------------------------------|--------------------------------------------------|-----------------------------------------------------| | | HIV CS - Access | HIV CS - Admin | HIV CS - Data capture | -| Tracked entity type | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Tipo de entidad Tracked | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | -| Program Stages | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | +| Etapas del programa | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can capture and view | | Tableros | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | You will want to assign your users to the appropriate user group based on their role within the system. You may want to enable sharing for other objects in the package depending on your set up. Refer to the [DHIS2 Documentation](https://docs.dhis2.org/master/en/dhis2_user_manual_en/about-sharing-of-objects.html) for more information on configuring sharing. -### User Roles { #user-roles } +### Roles de usuario { #user-roles } -Users will need user roles in order to engage with the various applications within DHIS2. The following minimum roles are recommended: +Los usuarios necesitarán roles de usuario para poder interactuar con las diversas aplicaciones dentro de DHIS2. Se recomiendan los siguientes roles mínimos: -1. Tracker data analysis : Can see event analytics and access dashboards, event reports, event visualizer, data visualizer, pivot tables, reports and maps. -2. Tracker data capture : Can add data values, update tracked entities, search tracked entities across org units and access tracker capture +1. Análisis de datos Tracker: puede ver análisis de eventos y acceder a tableros, informes de eventos, visualizador de eventos, visualizador de datos, tablas dinámicas, informes y mapas. +2. Captura de datos Tracker: puede agregar valores de datos, actualizar entidades de tracker, buscar entidades de tracker en unidades organizativas y acceder a la captura de tracker Refer to the [DHIS2 Documentation](http://dhis2.org/documentation) for more information on configuring user roles. -### Organisation Units { #organisation-units } +### Unidades organizativas { #organisation-units } You must assign the program to organisation units within your own hierarchy in order to be able to see the program in tracker capture. -### Duplicated metadata { #duplicated-metadata } +### Metadatos duplicados { #duplicated-metadata } > **NOTE** > > This section only applies if you are importing into a DHIS2 database in which there is already meta-data present. If you are working with a new DHIS2 instance, please skip this section and go to [Adapting the tracker program](#adapting-the-tracker-program). > If you are using any third party applications that rely on the current metadata, please take into account that this update could break them” -Even when metadata has been successfully imported without any import conflicts, there can be duplicates in the metadata - data elements, tracked entity attributes or option sets that already exist. As was noted in the section above on resolving conflict, an important issue to keep in mind is that decisions on making changes to the metadata in DHIS2 also needs to take into account other documents and resources that are in different ways associated with both the existing metadata, and the metadata that has been imported through the configuration package. Resolving duplicates is thus not only a matter of "cleaning up the database", but also making sure that this is done without, for example, breaking potential integrating with other systems, the possibility to use training material, breaking SOPs etc. This will very much be context-dependent. +Incluso cuando los metadatos se han importado exitosamente sin ningún conflicto de importación, puede haber duplicados en los metadatos: elementos de datos, atributos de entidad tracker o set de opciones que ya existen. Como se señaló en la sección anterior sobre resolución de conflictos, una cuestión importante a tener en cuenta es que las decisiones sobre la realización de cambios en los metadatos en DHIS2 también deben tener en cuenta otros documentos y recursos que están asociados de diferentes maneras tanto con los metadatos existentes, como con los metadatos que se han importado a través del paquete de configuración. Por lo tanto, resolver duplicados no es sólo una cuestión de "limpiar la base de datos", sino también de asegurarse de que esto se haga sin, por ejemplo, romper la posible integración con otros sistemas, la posibilidad de utilizar material de capacitación, romper los SOP, etc. Esto dependerá en gran medida del contexto. ## Adapting the tracker program { #adapting-the-tracker-program } Once the programme has been imported, you might want to make certain modifications to the programme. Examples of local adaptations that _could_ be made include: -* Adding additional variables to the form. -* Adapting data element/option names according to national conventions. -* Adding translations to variables and/or the data entry form. +* Añadir variables adicionales al formulario. +* Adaptar los nombres de los elementos de datos/opciones según las convenciones nacionales. +* Añadir traducciones a las variables y/o al formulario de entrada de datos. * Modifying program indicators based on local case definitions. -However, it is strongly recommended to take great caution if you decide to change or remove any of the included form/metadata. There is a danger that modifications could break functionality, for example program rules and program indicators. +Sin embargo, se recomienda fuertemente tener mucho cuidado si decide cambiar o eliminar cualquiera de los formularios/metadatos incluidos. Existe el peligro de que las modificaciones puedan alterar la funcionalidad, por ejemplo las reglas y los indicadores de programa. diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__installation-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__installation-md index b84f707d2..f013eccca 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__installation-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__installation-md @@ -64,7 +64,7 @@ The [Configuration](https://who.dhis2.org/documentation/installation_guide_compl **NOTE**: If you are installing the package on a new instance of DHIS2, you can skip the “Preparing the metadata file” section and move immediately to the section on “[Importing a metadata file into DHIS2](#importing-a-metadata-file-into-DHIS2).” -While not always necessary, it can often be advantageous to make certain modifications to the metadata file before importing it into DHIS2. +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. ## Default data dimension { #default-data-dimension } @@ -72,12 +72,12 @@ In early versions of DHIS2, the UID of the default data dimension was auto-gener To avoid conflicts when importing the metadata, it is advisable to search and replace the entire .json file for all occurrences of these default objects, replacing UIDs of the .json file with the UIDs of the database in which the file will be imported. Table 1 shows the UIDs which should be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | | Categoría | GLevLNI9wkl | ../api/categories.json?filter=name:eq:default | | Opción de categoría | xYerKDKCefk | ../api/categoryOptions.json?filter=name:eq:default | | Combinación de categoría | bjDvmb4bfuf | ../api/categoryCombos.json?filter=name:eq:default | -| Category option combination | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | +| Combinación de opciones de categoría | HllvX50cXC0 | ../api/categoryOptionCombos.json?filter=name:eq:default | For example, if importing a configuration package into [https://play.dhis2.org/demo](https://play.dhis2.org/demo), the UID of the default category option combination could be identified through [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) as `bRowv6yZOF2`. You could then search and replace all occurences of `HllvX50cXC0` with `bRowv6yZOF2` in the .json file. Note that this search and replace operation must be done with a plain text editor, not a word processor like Microsoft Word. @@ -85,9 +85,9 @@ For example, if importing a configuration package into [https://play.dhis2.org/d Indicator type is another type of object that can create import conflict because certain names are used in different DHIS2 databases (.e.g "Percentage"). Since Indicator types are defined simply by their factor and whether or not they are simple numers without denominator, they are unambiguous and can be replaced through a search and replace of the UIDs. This avoids potential import conflicts, and avoids creating duplicate indicator types. Table 2 shows the UIDs which could be replaced, as well as the API endpoints to identify the existing UIDs. -| Object | UID | API endpoint | +| Objeto | UID | API endpoint | | --- | --- | --- | -| Numerator only (number) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | +| Sólo numerador (número) | kHy61PbChXr | ../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1 | | Porcentaje | hmSnCXmLYwt | ../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100 | **Note 1**: by replacing the UIDs as described and importing the .json file, the name (including any translations) of the indicator types in question will be updated to those included in the configuration packages. @@ -114,16 +114,16 @@ Rename the existing object for which there is a conflict. The advantage of this Rename the object for which there is a conflict in the .json file. The advantage of this approach is that the existing DHIS2 metadata is left as-is. This can be a factor when there is training material or documentation such as SOPs of data dictionaries linked to the object in question, and it does not involve any risk of confusing users by modifying the metadata they are familiar with. At the same time, modifying object of the .json file means that using the associated documentation and training material might become more complicated. -Note that for both alternative 1 and 2, the modification can be as simple as adding a small pre/post-fix to the name, to minimise the risk of confusion. +Tenga en cuenta que, tanto para la alternativa 1 como para la 2, la modificación puede ser tan simple como agregar un pequeño pre/post-fijo al nombre, para minimizar el riesgo de confusión. #### Alternative 3 { #alternative-3 } A third and more complicated approach is to modify the .json file to re-use existing metadata. For example, in cases where an indicator already exists for a certain concept (e.g. "ANC 1 coverage"), that indicator could be removed from the .json file and all references to its UID replaced with the corresponding indicator already in the database. The big advantage of this (which is not limited to the cases where there is a direct import conflict) is to avoid creating duplicate metadata in the database. However, it is generally not recommended for several reasons: - it requires expert knowledge of the detail metadata structure of DHIS2 -- the approach does not work for all types of objects. In particular, certain types of objects have dependencies which are complicated to solve in this way, for example related to disaggregations. +- el enfoque no funciona para todos los tipos de objetos. En particular, ciertos tipos de objetos tienen dependencias que son complicadas de resolver de esta manera, por ejemplo relacionadas con desagregaciones. - as with alternative 2, it means that the result of the installation is not entirely according to the standard configuration, and training material and documentation developed for the configuration might not be usable without modifications. -- future updates to the configuration package will be complicated. +- las futuras actualizaciones del paquete de configuración serán complicadas. ## Additional Configuration { #additional-configuration } @@ -158,7 +158,7 @@ The user groups that usually come with the package include: We recommend to provide the following access to these groups -| Object | User Group | | | +| Objeto | User Group | | | | --- | --- | --- | --- | | | _{Package Name} access_ | _{Package Name} admin_ | _{Package Name} data capture_ | | _Data Elements/Data element group_ | Metadata : can view
Data: can view | Metadata : can edit and view
Data: can view | Metadata : can view
Data: can view | diff --git a/projects/docs-full-site/fr/.cache_timestamp b/projects/docs-full-site/fr/.cache_timestamp index c96db16b3..d81c7e5c5 100644 --- a/projects/docs-full-site/fr/.cache_timestamp +++ b/projects/docs-full-site/fr/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:21:30Z \ No newline at end of file +2024-07-17T21:21:43Z \ No newline at end of file diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index 63a510266..f96c14c65 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configurer les métadonnées { #maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index f67de7a4c..4d6afb433 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configurer les programmes dans l'application Maintenance { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 872401aee..585729967 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configurer la fonctionnalité de rapport { #setting_up_reporting } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 4377d075b..6d08fc79d 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Paramètres du système { #settings } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 6bda5815a..95bc108de 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Autorités des utilisateurs { #user_authorities } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index b9e58bc7f..a2f1d952a 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Administration des données { #data_admin } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 5df8e77ba..3f6f05e50 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- > **Attention** diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 26cd39814..b2f777997 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Mobile { #mobile } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index 141e42377..6ae88ca85 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Programmation { #scheduling } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 6d79a61b2..434973314 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utilisation de l'application Saisie { #capture_app } @@ -39,7 +39,7 @@ Dans l'application Saisie d'événements, vous pouvez enregistrer des événemen du champ. Cela ouvrira une carte sur laquelle vous pouvez rechercher un emplacement et saisir un polygone (bouton dans le coin supérieur droit de la carte). -7. Vous pouvez ajouter un commentaire en cliquant sur le bouton **Écrire un commentaire** au bas du formulaire. Notez que les Commentaires sur les évènements sont attribués à un utilisateur et ne peuvent être retirés. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. Si vous le souhaitez, vous pouvez ajouter une relation en cliquant sur le bouton **Ajouter une relation** au bas du formulaire. Voir la section**Ajouter une relation** pour plus d'informations. @@ -128,7 +128,7 @@ La seconde consiste à enregistrer une instance d'entité suivi et à l'inscrire 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![créer un nouvel événement](resources/images/register-and-enroll-program-selection.png) @@ -233,8 +233,8 @@ Lorsque les "Jours programmés depuis le début" ne contiennent pas de nombre ou ### Détection d'éventuels doublons { #possible-duplicates-detection } -Dans les deux cas d'enregistrement d'une instance d'entité suivie (avec ou sans inscription), le système commencera à rechercher d'éventuels doublons. -Il convient de noter que les programmes doivent être correctement configurés via l'application de maintenance pour que le système commence à détecter les doublons lors de l'inscription d'une nouvelle personne à un programme. +In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. Pour configurer un programme via l'application de maintenance, il vous faudra: @@ -281,8 +281,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### Exécution des règles du programme { #program-rules-execution } -Dans les deux cas d'enregistrement d'une instance d'entité suivie (avec ou sans inscription), le système mettra en application les règles de programme que vous avez configurées. -Notez que les règles peuvent être configurées dans l'application de maintenance. +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. Pour voir qu'une règle est en cours d'application lors de l'inscription d'une instance d'entité suivie, vous devez suivre les étapes suivantes. @@ -1000,13 +1000,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Widget de commentaires sur les inscriptions { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } + +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -![](resources/images/enrollment-widget-comment.png) +![](resources/images/enrollment-widget-note.png) -Le widget des commentaires sur les inscriptions affiche les commentaires et donne la possibilité d'en ajouter d'autres en rapport avec l'inscription en cours. +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -En cliquant dans le champ de texte, vous pourrez saisir un nouveau texte et voir les boutons d'action **Enregistrer le commentaire** et **Annuler**. Notez que les commentaires sur les inscriptions sont attribués à un utilisateur et ne peuvent être supprimés. ### Widget de relation { #relationship-widget } @@ -1265,7 +1266,7 @@ Si une étape de programme a une prochaine date fixée par défaut configurée, L'utilisateur peut également trouver plus d'informations sur le nombre d'événements programmés à la même date sélectionnée ou dans l'intervalle entre la date sélectionnée et la date suggérée dans la boîte d'informations. -Au bas de la date fixée, l'utilisateur peut ajouter un commentaire sur l'événement programmé. +Below the schedule date entry, user can choose to add a note to the scheduled event. Après avoir cliqué sur le bouton **Programmer**, l'utilisateur sera redirigé vers la page d'aperçu de l'inscription. diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 1b6f25326..894f0cace 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # À propos des dimensions de donnée { #data_dimensions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 81025fc6e..60b8d2a66 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: - Utilisation - Version Master de DHIS2 Central @@ -39,7 +39,7 @@ Dans l'application Saisie d'événements, vous pouvez enregistrer des événemen du champ. Cela ouvrira une carte sur laquelle vous pouvez rechercher un emplacement et saisir un polygone (bouton dans le coin supérieur droit de la carte). -7. Vous pouvez ajouter un commentaire en cliquant sur le bouton **Faire un commentaire** au bas du formulaire. Notez que les Commentaires sur les évènements sont attribués à un utilisateur et ne peuvent être supprimés. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. Si vous le souhaitez, vous pouvez ajouter une relation en cliquant sur le bouton **Ajouter une relation** au bas du formulaire. Voir la section**Ajouter une relation** pour plus d'informations. @@ -128,7 +128,7 @@ La seconde consiste à enregistrer une instance d'entité suivi et à l'inscrire 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![créer un nouvel événement](resources/images/register-and-enroll-program-selection.png) @@ -233,8 +233,8 @@ Lorsque les "Jours programmés depuis le début" ne contiennent pas de nombre ou ### Détection d'éventuels doublons { #possible-duplicates-detection } -Dans les deux cas d'enregistrement d'une instance d'entité suivie (avec ou sans inscription), le système commencera à rechercher d'éventuels doublons. -Il convient de noter que les programmes doivent être correctement configurés via l'application de maintenance pour que le système commence à détecter les doublons lors de l'inscription d'une nouvelle personne à un programme. +In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. Pour configurer un programme via l'application de maintenance, il vous faudra: @@ -281,8 +281,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### Exécution des règles du programme { #program-rules-execution } -Dans les deux cas d'enregistrement d'une instance d'entité suivie (avec ou sans inscription), le système mettra en application les règles de programme que vous avez configurées. -Notez que les règles peuvent être configurées dans l'application de maintenance. +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. Pour voir qu'une règle est en cours d'application lors de l'inscription d'une instance d'entité suivie, vous devez suivre les étapes suivantes. @@ -1000,13 +1000,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Widget de commentaires sur les inscriptions { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } -![](resources/images/enrollment-widget-comment.png) +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -Le widget des commentaires sur les inscriptions affiche les commentaires et donne la possibilité d'en ajouter d'autres en rapport avec l'inscription en cours. +![](resources/images/enrollment-widget-note.png) + +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -En cliquant dans le champ de texte, vous pourrez saisir un nouveau texte et voir les boutons d'action **Enregistrer le commentaire** et **Annuler**. Notez que les commentaires sur les inscriptions sont attribués à un utilisateur et ne peuvent être supprimés. ### Widget de relation { #relationship-widget } @@ -1265,7 +1266,7 @@ Si une étape de programme a une prochaine date fixée par défaut configurée, L'utilisateur peut également trouver plus d'informations sur le nombre d'événements programmés à la même date sélectionnée ou dans l'intervalle entre la date sélectionnée et la date suggérée dans la boîte d'informations. -Au bas de la date fixée, l'utilisateur peut ajouter un commentaire sur l'événement programmé. +Below the schedule date entry, user can choose to add a note to the scheduled event. Après avoir cliqué sur le bouton **Programmer**, l'utilisateur sera redirigé vers la page d'aperçu de l'inscription. diff --git a/projects/docs-full-site/pt/.cache_timestamp b/projects/docs-full-site/pt/.cache_timestamp index 75015d9c7..8694a4ba0 100644 --- a/projects/docs-full-site/pt/.cache_timestamp +++ b/projects/docs-full-site/pt/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:21:38Z \ No newline at end of file +2024-07-17T21:21:59Z \ No newline at end of file diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md index 963766067..415da39a0 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-validation.md" revision_date: '2022-02-23' tags: -- Desenvolver - DHIS core version 2.38 +- Desenvolver --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md index 6c13a9b42..fd469ecc7 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/overview.md" revision_date: '2022-02-28' tags: -- Desenvolver - DHIS core version 2.38 +- Desenvolver --- # Visão Geral { #webapi } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md index 400dbd104..f814d40d5 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Desenvolver - DHIS core version 2.38 +- Desenvolver --- # Partilha { #sharing } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__apps-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__apps-md index 255f59ca2..9aab9f1dc 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__apps-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.39 - Desenvolver +- DHIS core version 2.39 --- # Apps { #apps } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-entry-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-entry-md index a7f0f51f3..aa7bd0a95 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-entry-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS core version 2.39 - Desenvolver +- DHIS core version 2.39 --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__settings-and-configuration-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__settings-and-configuration-md index 8a604703f..ee9fbd743 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__settings-and-configuration-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/settings-and-configuration.md" revision_date: '2023-12-14' tags: -- DHIS core version 2.39 - Desenvolver +- DHIS core version 2.39 --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md index 91b9ec575..e43d47519 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS core version 2.39 - Desenvolver +- DHIS core version 2.39 --- # Tracker { #tracker } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md index 75b7785ca..1dd3dbf1d 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Analytics { #analytics } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md index 0d461299f..a545775d1 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Apps { #apps } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md index 4aeffad1d..6d32c3819 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-store.md" revision_date: '2023-05-02' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Banco de dados { #data-store } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md index 8b320c585..63410c8e0 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-validation.md" revision_date: '2023-04-14' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md index a2a611ca5..10350badb 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # O email { #email } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md index be4a57120..6244780f1 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Visão Geral { #webapi } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md index 1d2ee515a..c6e97c42a 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/maintenance.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Manutenção { #maintenance } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md index 7bd253e7a..32930369f 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Organisation unit profile { #org_unit_profile } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 3512a48f8..580b35697 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/route.md" revision_date: '2023-05-09' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md index 7e39ae726..e6b691b58 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/scheduling.md" revision_date: '2023-04-14' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Agendamento { #webapi_scheduling } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index 5b39fc028..5e2a0d57a 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-01-26' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md index e1dabaf82..ce6d11f2a 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Partilha { #sharing } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md index 041189213..f82fd891b 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # SMS { #sms } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md index 9754feee5..e39930ff8 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker-old.md" revision_date: '2024-02-12' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index 10a720535..19b06c7e5 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" -revision_date: '2024-05-23' +revision_date: '2024-07-02' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Tracker { #tracker } @@ -2145,7 +2145,11 @@ This, along with the Program's [Access Level](#webapi_nti_access_level) configur A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured with access level *OPEN* or *AUDITED* , the Owner OrganisationUnit has to be in the user's search scope. For Programs that are configured with access level *PROTECTED* or *CLOSED* , the Owner OrganisationUnit has to be in the user's capture scope to be able to access the corresponding program data for the specific tracked entity. -#### Substituição de propriedade do rastreador: Quebre o vidro { #webapi_nti_tracker_ownership_override } +When requesting tracked entities without specifying a program, the response will include only tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and one of the following criteria: +- The tracked entity is enrolled in at least one program the user has data access to, and the user has access to the owner organisation unit. +- The tracked entity is not enrolled in any program the user has data access to, but the user has access to the tracked entity registering organisation unit. + +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md index 68abb40b3..efa32abae 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/users.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Comercial { #users } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md index ebc6aff58..c0b8e72a5 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 --- # Visualizações { #visualizations } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md index e446aa203..fcfdbcb6f 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Desenvolver - DHIS core version 2.41 +- Desenvolver --- # Apps { #apps } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md index 21ded85e1..19cae612a 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Desenvolver - DHIS core version 2.41 +- Desenvolver --- # Auditoria { #audit } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md index 1e9d1e82a..f0820ea85 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Desenvolver - DHIS core version 2.41 +- Desenvolver --- # Aprovação de dados { #data-approval } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md index d9c79e084..32862c5c2 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Desenvolver - DHIS core version 2.41 +- Desenvolver --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md index 6cceec0e8..dcca0a064 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker-old.md" revision_date: '2024-05-23' tags: -- Desenvolver - DHIS core version 2.41 +- Desenvolver --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md index 66a5fad6b..2e83bcd67 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- DHIS core version 2.41 - Desenvolver +- DHIS core version 2.41 --- # Comercial { #users } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index 362b037c1..961fbbdda 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/analytics.md" revision_date: '2024-05-31' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Analytics { #analytics } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index 9e7d6942a..a569f0765 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Apps { #apps } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index 0bcdcb827..5a7313229 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" revision_date: '2024-06-24' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Auditoria { #audit } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 3e6f1a9d1..29f8c0d43 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Aprovação de dados { #data-approval } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index 02872c3af..864c53050 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index 67ed6b99b..833a5d422 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" revision_date: '2024-06-26' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index 1c6759b20..d55f1ef1f 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Data { #data } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index 551241757..966174ddc 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Banco de dados { #data-store } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index 5ac66fbf4..63e3739ca 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md index c1c1ebea0..20665e745 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # O email { #email } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index d9ebedcbb..90dfaab0c 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 23199cbe8..027dca99b 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # I18n { #i18n } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index c06d8cac3..0b3d7754b 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Visão Geral { #webapi } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index dac366ca8..8ef2d425a 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Manutenção { #maintenance } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md index de235d935..0cd131548 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Mensagens { #messaging } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index fe3a49696..4d60d3ede 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index 512c76021..edf67c4d5 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" -revision_date: '2024-06-03' +revision_date: '2024-07-12' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Metadata { #webapi_metadata } @@ -1629,6 +1629,226 @@ following payload to change the style: } ``` +## Elementos de Dados { #data-elements } + +### Merge data elements { #data_element_merge } + +> **Caution** +> +> Merging DataElements should be carried out with the utmost care. Particular attention +> should be given to the merging of data values that have data element references involved in the +> merge. Knowing the potential side effects of a merge should be fully understood before performing +> the merge. The merging of DataElements has far-reaching effects. The information below +> will try to help show what's involved in a DataElement merge. A DataElement merge +> touches all the major parts of the system (metadata, data, tracker, analytics and audit). +> +> System performance may be impacted if the source DataElements are linked to large amounts of Data/Audit records particularly. + +The data element merge endpoint allows you to merge a number of data elements (sources) into a target data element. + +#### Authorisation { #authorisation } + +The main authority required to perform a data element merge is `F_DATA_ELEMENT_MERGE`. +Other authorities required relate to the general sharing and access of data elements, `F_DATAELEMENT_PUBLIC_ADD` and `F_DATAELEMENT_DELETE`. + +#### Request { #request } + +Merge data elements with a POST request: + +``` +POST /api/dataElements/merge +``` + +The payload in JSON format looks like the following: + +```json +{ + "sources": [ + "jNb63DIHuwU", + "WAjjFMDJKcx" + ], + "target": "V9rfpjwHbYg", + "deleteSources": true, + "dataMergeStrategy": "DISCARD" +} +``` + +The JSON properties are described in the following table. + +Table: Merge payload fields + +| Campo | Requerido | Valor | +|-------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sources | sim | Array of identifiers of the data elements to merge (the source data elements) | +| target | sim | Identifier of the data element to merge the sources into (the target data element) | +| deleteSources | Não | Whether to delete the source data elements after the operation. Default is false. If true is chosen, then all source audit records will also be deleted. | +| dataMergeStrategy | sim | How to handle merging of data values. Options are 'DISCARD' or 'LAST_UPDATED'. DISCARD will delete all source data values. LAST_UPDATED will use the data value which was last updated. | + +The merge operation will merge the source data elements into the target data element. One or many source data elements can be specified. Only one target should be specified. + +The merge operation will transfer all source data element metadata associations to the target data element. +The following metadata get updated: + + +| Metadados | Property | Action taken | +|-----------------------------------|---------------------------|----------------------------| +| DataDimensionItem | dataElement | set to target | +| EventVisualization | dataElementValueDimension | set to target | +| ProgramStageDataElement | dataElement | set to target | +| ProgramNotificationTemplate | recipientDataElement | set to target | +| ProgramRuleVariable | dataElement | set to target | +| ProgramRuleAction | dataElement | set to target | +| TrackedEntityDataElementDimension | dataElement | set to target | +| MinMaxDataElement | dataElement | set to target | +| SMSCode | dataElement | set to target | +| SMSCode | dataElement | set to target | +| Predictor | output | set to target | +| DataSetElement | dataElement | set to target | +| DataElementOperand | dataElement | set to target | +| ProgramStageDataElement | dataElements | remove sources, add target | +| Section | dataElements | remove sources, add target | +| DataElementGroup | members | remove sources, add target | +| Evento | eventDataValues | remove sources, add target | +| Indicador | numerator | replace source with target | +| Indicador | denominator | replace source with target | +| Predictor | generator | replace source with target | +| Predictor | sampleSkipTest | replace source with target | +| DataEntryForm | htmlCode | replace source with target | +| ProgramIndicator | expression | replace source with target | +| ProgramIndicator | filter | replace source with target | +| DataValue | dataElement | | + + +| Dados | Property | Action taken | +|---------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Evento | eventDataValues | action based on merge strategy (DISCARD / LAST_UPDATED). DISCARD will delete all source event data values. LAST_UPDATED will use the event data value which was last updated, when more than one exists. | +| DataValue | dataElement | action based on merge strategy (DISCARD / LAST_UPDATED). DISCARD will delete all source data values. LAST_UPDATED will use the data value which was last updated, when more than one exists. | +| TrackedEntityDataValueChangeLog | | deleted if sources are being deleted, otherwise no action. | +| DataValueAudit | | deleted if sources are being deleted, otherwise no action. | + + +#### Validation { #validation } + +The following constraints and error codes apply. + +Table: Constraints and error codes + +| Erro de código | Descrição | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| E1550 | At least one source data element must be specified | +| E1551 | Target data element must be specified | +| E1552 | Target data element cannot be a source indicator | +| E1553 | Source/Target data element does not exist: `{uid}` | +| E1554 | All source ValueTypes must match target ValueType: `ValueType`. Other ValueTypes found: `ValueType` | +| E1555 | All source DataElementDomains must match target DataElementDomain: `DataElementDomain`. Other DataElementDomains found: `DataElementDomain` | +| E1556 | dataMergeStrategy field must be specified. With value `DISCARD` or `LAST_UPDATED` | + +#### Database constraints { #database-constraints } +There are unique constraints in place that can prevent a successful merge. These constraints are set by DHIS2 in order to maintain a logical domain model. +Below are a list of the known database unique key constraints at the time of writing. For example, you +can only have 1 data set element with the same dataset and data element. + +Table: Database table unique key constraints + +| Table | Unique key constraint | +|-------------------------|-------------------------------------------| +| minmaxdataelement | orgunit, dataelement, categoryoptioncombo | +| programstagedataelement | programstage, dataelement | +| datasetelement | dataset, dataelement | + + +#### Response { #response } +##### Success { #success } +Sample success response looks like: + +```json +{ + "httpStatus": "OK", + "httpStatusCode": 200, + "status": "OK", + "response": { + "mergeReport": { + "mergeErrors": [], + "mergeType": "DATA_ELEMENT", + "sourcesDeleted": [ + "vQ0dGV9EDrw" + ], + "message": "DATA_ELEMENT merge complete" + } + } +} +``` + +##### Failure { #failure } +Sample error response looks like: + +```json +{ + "httpStatus": "Conflict", + "httpStatusCode": 409, + "status": "WARNING", + "message": "One or more errors occurred, please see full details in merge report.", + "response": { + "mergeReport": { + "mergeErrors": [ + { + "message": "At least one source data element must be specified", + "errorCode": "E1550", + "args": [] + }, + { + "message": "Target data element does not exist: `abcdefg1221`", + "errorCode": "E1553", + "args": [ + "Target", + "abcdefg1221" + ] + } + ], + "mergeType": "DATA_ELEMENT", + "sourcesDeleted": [], + "message": "DATA_ELEMENT merge has errors" + } + } +} +``` + +Another sample validation error response: + +```json +{ + "httpStatus": "Conflict", + "httpStatusCode": 409, + "status": "WARNING", + "message": "One or more errors occurred, please see full details in merge report.", + "response": { + "mergeReport": { + "mergeErrors": [ + { + "message": "All source ValueTypes must match target ValueType: `TEXT`. Other ValueTypes found: `NUMBER`", + "errorCode": "E1554", + "args": [] + } + ], + "mergeType": "DATA_ELEMENT", + "sourcesDeleted": [], + "message": "DATA_ELEMENT merge has errors" + } + } +} +``` + +A database constraint sample error response: + +```json +{ + "httpStatus": "Conflict", + "httpStatusCode": 409, + "status": "ERROR", + "message": "ERROR: duplicate key value violates unique constraint \"minmaxdataelement_unique_key\"\n Detail: Key (sourceid, dataelementid, categoryoptioncomboid)=(193236, 1148617, 167661) already exists." +} +``` + ## Indicadores { #webapi_indicators } Esta seção descreve indicadores e expressões de indicadores. diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md index e1403e5de..4bb08dab1 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Organisation unit profile { #org_unit_profile } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index f82b6532f..d42c2ef5e 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index b5d552904..03541e847 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/route.md" revision_date: '2024-05-15' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Route { #route } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index 6b71049bf..c853ca48e 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Agendamento { #webapi_scheduling } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index cb4f90f99..fd9c1e092 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index c40dd89ec..661936350 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Partilha { #sharing } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 3d0e1df97..0cc810192 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # SMS { #sms } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index 32bd8678f..445138c2e 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Sincronização { #webapi_synchronization } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md index e698b679d..e82c4515e 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-07-02' +revision_date: '2024-07-08' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Tracker { #webapi_tracker } @@ -2851,7 +2851,8 @@ Organisation units are one of the most fundamental objects in DHIS2. They define which a user is allowed to record and/or read data. There are three types of organisation units that can be assigned to a user. These are data capture, data view (not used in tracker), and tracker search. As the name implies, these organisation units define a scope under which a user is allowed -to conduct the respective operations. +to conduct the respective operations. A user can search for data in their search scope and capture +scope organisation units. However, to further fine-tune the scope, DHIS2 Tracker introduces a concept that we call **OrganisationUnitSelectionMode**. Such a mode is often used at the time exporting tracker objects. @@ -2927,14 +2928,19 @@ falls under the user's organisation unit scope (Search/Capture). For Programs th with access level *OPEN* or *AUDITED* , the Owner OrganisationUnit has to be in the user's search scope. For Programs that are configured with access level *PROTECTED* or *CLOSED* , the Owner OrganisationUnit has to be in the user's capture scope to be able to access the corresponding -program data for the specific tracked entity. Irrespective of the program access level, to access -Tracker objects, the requested organisation unit must always be within the user's search scope. A -user cannot request objects outside its search scope unless it's using the organisation unit mode -ALL and has enough privileges to use that mode. - -When requesting tracked entities without specifying a program, the response will include only tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and one of the following criteria: -- The tracked entity is enrolled in at least one program the user has data access to, and the user has access to the owner organisation unit. -- The tracked entity is not enrolled in any program the user has data access to, but the user has access to the tracked entity registering organisation unit. +program data for the specific tracked entity. Irrespective of the program access level, to access +Tracker objects, the requested organisation unit must always be within either the user's search +scope or capture scope. A user cannot request objects outside these two scopes unless they are +using the organisation unit mode ALL and have sufficient privileges to use that mode. + +When requesting tracked entities without specifying a program, the response will include only +tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and +one of the following criteria: + +* The tracked entity is enrolled in at least one program the user has data access to, and the user + has access to the owner organisation unit. +* The tracked entity is not enrolled in any program the user has data access to, but the user has + access to the tracked entity registering organisation unit. #### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index ab4748229..61f9e622f 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Comercial { #users } diff --git a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index 40872d5e2..4cc8c3b5b 100644 --- a/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/pt/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- DHIS core version master - Desenvolver +- DHIS core version master --- # Visualizações { #visualizations } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md index 03c0cd601..05106afff 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/audit.md" revision_date: '2021-12-02' tags: -- Gerir - DHIS core version 2.38 +- Gerir --- # Auditoria { #audit } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md index 55e5ecd37..c94695965 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/installation.md" revision_date: '2024-02-16' tags: -- Gerir - DHIS core version 2.38 +- Gerir --- # Instalação { #installation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md index 6ebeaef1f..d771c929a 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- Gerir - DHIS core version 2.38 +- Gerir --- # Monitoramento { #monitoring } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md index bb67cef06..79cfc2e75 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/upgrading.md" revision_date: '2021-08-18' tags: -- Gerir - DHIS core version 2.38 +- Gerir --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md index d24e390c7..e943cbef8 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-238__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/sysadmin/SMS-reporting.md" revision_date: '2021-06-14' tags: -- Gerir - DHIS core version 2.38 +- Gerir --- # Usando Gateways para relatórios de SMS { #sms_report_sending } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md index e94d1b80a..49e15b6a9 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- Gerir - DHIS core version 2.39 +- Gerir --- # Auditoria { #audit } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md index 69a01ab92..467e1b8ae 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/installation.md" revision_date: '2024-02-16' tags: -- Gerir - DHIS core version 2.39 +- Gerir --- # Instalação { #installation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md index 823247b66..48caff767 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- Gerir - DHIS core version 2.39 +- Gerir --- # Monitoramento { #monitoring } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md index 413231600..d6acfe3a2 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Gerir - DHIS core version 2.39 +- Gerir --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md index 9687bd228..2936c960d 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Gerir - DHIS core version 2.39 +- Gerir --- # Usando Gateways para relatórios de SMS { #sms_report_sending } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md index 4e5e4e261..ce10596e0 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- Gerir - DHIS core version 2.40 +- Gerir --- # Auditoria { #audit } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md index d55ba4f5e..0dac5fb43 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Gerir - DHIS core version 2.40 +- Gerir --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md index c64b8b870..38bcde796 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- Gerir - DHIS core version 2.40 +- Gerir --- # Instalação { #installation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md index 783d7795d..d906957dc 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- Gerir - DHIS core version 2.40 +- Gerir --- # Monitoramento { #monitoring } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md index fc0a2523e..6245c51fd 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Gerir - DHIS core version 2.40 +- Gerir --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md index 8fd18d279..12bebcd37 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Gerir - DHIS core version 2.40 +- Gerir --- # Usando Gateways para relatórios de SMS { #sms_report_sending } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md index 37107ba25..ae0899b18 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- Gerir - DHIS core version 2.41 +- Gerir --- # Auditoria { #audit } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md index 1eb9f20a3..60c83bdd1 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Gerir - DHIS core version 2.41 +- Gerir --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md index 88f9df652..b38a328a5 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- Gerir - DHIS core version 2.41 +- Gerir --- # Instalação { #installation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md index cb6f241d0..f2a94d70a 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/monitoring.md" revision_date: '2023-09-25' tags: -- Gerir - DHIS core version 2.41 +- Gerir --- # Monitoramento { #monitoring } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md index 7997e0574..547b4b88a 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Gerir - DHIS core version 2.41 +- Gerir --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md index be8498f9b..57e976608 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Gerir - DHIS core version 2.41 +- Gerir --- # Usando Gateways para relatórios de SMS { #sms_report_sending } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index ec03fafc4..6b8227d6b 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- Gerir - DHIS core version master +- Gerir --- # Auditoria { #audit } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index 0bd915a63..691270d4c 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Gerir - DHIS core version master +- Gerir --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index 748c3eca3..db7fdb055 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/installation.md" revision_date: '2024-06-18' tags: -- Gerir - DHIS core version master +- Gerir --- # Instalação { #installation } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index 0e76be0c0..6f96b867e 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/monitoring.md" revision_date: '2023-09-25' tags: -- Gerir - DHIS core version master +- Gerir --- # Monitoramento { #monitoring } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index 749cfed23..2b64a8321 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Gerir - DHIS core version master +- Gerir --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index 5f6536fdc..1433a9e49 100644 --- a/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/pt/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Gerir - DHIS core version master +- Gerir --- # Usando Gateways para relatórios de SMS { #sms_report_sending } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index 832536960..c92cdbf3f 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-browsing.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.0 +- Usar --- ## Navegando no Action Tracker { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index 12c44e7d5..900c8ba9c 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-introduction.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.0 +- Usar --- # Painel de controle do Action Tracker e servidor de demonstração vinculados { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index 04ebbf15b..d679fd9ae 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-maintenance.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.0 +- Usar --- # Manutenção do aplicativo Action Tracker { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index febe45108..d09f1c32d 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-planning.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.0 +- Usar --- # Planejamento de ação no rastreador de ação { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index ea958260c..3a929e13f 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-tracking.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.0 +- Usar --- # Rastreamento de ação no rastreador de ação { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index e7bdf02bc..d97005ce4 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-installation.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Instalando o App BNA { #installing-the-bna-app } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index a8b2cd39e..8e1f2439b 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-maintenance.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Manutenção do Aplicativo BNA { #bna-app-maintenance } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index 2d87f0e90..77e08970f 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-analysis-and-interpretation.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.2.2 +- Usar --- # Análise e Interpretação BNA { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index 7f4b5d1cd..55dd70fd3 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-architecture.md" revision_date: '2022-03-10' tags: -- Usar - App version 1.2.2 +- Usar --- # Arquitetura do aplicativo BNA { #bna-app-architecture } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index d16764268..8621c8db8 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bottleneck-analysis-dashboard-and-demo-server.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.2.2 +- Usar --- # Painel de análise de gargalo e servidor de demonstração { #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index cee0a9dba..8ce166974 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/navigating-the-bna-app.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.2.2 +- Usar --- # Configurações de intervenções do App BNA { #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index 7d24023a9..9c26a67d9 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/visualization-operations.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Operações de visualização { #visualization-operations } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index 8a7d6978a..382db11f6 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/adopting-the-use-of-the-bna-app.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Adoção da utilização da App BNA { #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index d07657608..125f650b1 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/capacity-building.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.2.2 +- Usar --- # Capacitação { #capacity-building } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index 47e4d03bf..b326a06a0 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/end-user-training.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Treinamento de usuário final { #end-user-training } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index eb773c4f5..dd5a70418 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/guide-to-bna-app-implementation.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Guia para implementação de aplicativos BNA { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index 5105b9f21..b48575a5c 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/integration-concepts-for-the-bna-app.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.2.2 +- Usar --- # Conceitos de Integração para a App BNA. { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index f29d5d215..0da84be39 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/opportunities-and-challenges.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.2.2 +- Usar --- # Oportunidades e desafios { #opportunities-and-challenges } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index 8a5ae8a81..317c8daa4 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/planning-and-organising.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Planejando e organizando { #planning-and-organising } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index c4269f31e..7377f6833 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/setting-up-a-new-bna-app.md" revision_date: '2021-09-09' tags: -- Usar - App version 1.2.2 +- Usar --- # Configurando um novo aplicativo BNA { #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index 9eb289abf..e0beb5898 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-support-and-scale-up.md" revision_date: '2022-03-22' tags: -- Usar - App version 1.2.2 +- Usar --- # BNA App Support e Scale-up { #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index 1d47b5ab5..2e47aa297 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/scale-up-and-sustainability.md" revision_date: '09-09-2021' tags: -- Usar - App version 1.2.2 +- Usar --- # Ampliação e sustentabilidade { #scale-up-and-sustainability } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index f0048f0c5..4f92c7846 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index 460a66978..9f4d1b9c5 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index d600df3cf..6669e1fbd 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index d5cb29b6f..4a1baf088 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index 78e859866..0ba734f8a 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- # Sobre este guião { #about_this_guide_ } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index 08faa4cf3..de54813c6 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index 4833960dd..e783a47cf 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index b2d0de3ce..e995879ef 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index 10b448890..1367685df 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md index dfd238f76..b3d2c6f03 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/map-view.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Usar +- App version 1.4.0 --- Map View diff --git a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index 97b625859..91f3adbb9 100644 --- a/projects/docs-full-site/pt/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/pt/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- App version 1.0.3 - Usar +- App version 1.0.3 --- # User Manual for the DHIS2 Immunisation Analysis App { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 8acd79fa5..5c93bbe4c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: - DHIS core version 2.38 - Usar @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl the field. This will open a map where you can search for a location and capture a polygon (button in the upper right corner of the map). -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. If desired you can add a relationship by clicking the **Add relationship** button at the bottom of the form. See the section about **Adding a relationship** for more information. @@ -128,7 +128,7 @@ The second option, is to register a tracked entity instance with program and enr 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ When the "Scheduled days from start" does not contain a number or contains 0 the ### Possible duplicates detection { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. To configure a program through the maintenance app you will have to: @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### Program rules execution { #program-rules-execution } -In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will run program rules you have configured. -Note that, rules can be configured in the maintenance app. +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. To see a rule being executed while enrolling a tracked entity instance you will have to take the following steps. @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } -![](resources/images/enrollment-widget-comment.png) +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +![](resources/images/enrollment-widget-note.png) + +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 2df5d1901..5f29f5e7c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Usar - DHIS core version 2.39 +- Usar --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 9f1e51d88..20515079d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # DHIS2 Perguntas Freqüentes { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index a7bb34671..c5dae71cb 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Glossário DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 45849afea..01207a71d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Tutoriais DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 069538d4c..8e2cae436 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Notas de lançamento e atualização { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index 1abc56914..be469ae60 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Gerir painéis { #dashboard } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index f0c857758..feeed21d5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index 43752b501..7ca9837ac 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo Relatórios de eventos { #event_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index 1093cca63..36d9c02bd 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index 49438aa61..3afbf42c0 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index 07f07a5d6..40842e8e4 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo Maps { #using_maps } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index c567abf7e..5d81ff608 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Funcionalidade de relatórios no aplicativo de relatórios { #using_the_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index 5dabcbebd..50a1f43ff 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index e57bdf320..b243dcd01 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index 401d7dc16..53e8b462d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index 1c3cd25e2..334713c2c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" -revision_date: '2021-06-14' +revision_date: '2024-07-12' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo de entrada de dados { #data_entry_app } @@ -279,12 +279,9 @@ case, you can enable multi-organisation unit data entry. ## Veja também { #data_entry_app_see_also } - - [Control data - quality](https://docs.dhis2.org/master/en/user/html/control_data_quality.html) + - [Control data quality](#control_data_quality) - - [Manage data sets and data entry - forms](https://docs.dhis2.org/master/en/user/html/manage_data_set.html) + - [Manage data sets and data entry forms](#manage_data_set) - - [Using the Maintenance - app](https://docs.dhis2.org/master/en/user/html/maintenance_app.html) + - [Using the Maintenance app](#maintenance_app) diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index bd0d43a82..2552ef6be 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Controle de qualidade de dados { #control_data_quality } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 2b355ddfc..3df429617 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Sobre o compartilhamento de objetos { #sharing } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index e7dac09f3..bb2776e8b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index cc36d1fd4..ae2b0840a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Configurar metadados { #maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index ac16be0c9..ffc3d91c0 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" -revision_date: '2024-01-03' +revision_date: '2024-07-12' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Configure programas no aplicativo de manutenção { #configure_programs_in_maintenance_app } @@ -1783,16 +1783,16 @@ programs. search**. This specifies the amount of attributes that need to be filled out in order to be able to search for this **tracked entity type** in a *global search*. See [Configure - Search](../search/search.xml#configure_search) for more information. + Search](#configure_search) for more information. 7. (Optional) Enter a **Maximum number of tracked entity instances to return in search**. This specifies the amount of tracked entity instances that will be returned in a *global search*. See [Configure - Search](../search/search.xml#configure_search) for more information. + Search](#configure_search) for more information. 8. (Optional) Add **Tracked entity type attributes**. This is used to configure search, see [Configure - Search](configure_search) for more information. + Search](#configure_search) for more information. 9. (Opcional) Insira um ** Nome alternativo ** da entidade rastreada. diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index c3ecb4dba..eb4d3d107 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Configure a funcionalidade de relatório { #setting_up_reporting } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index 1a816c7ad..7df15dfe3 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Configurações do sistema { #settings } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index 2e7b46c8c..71b05bf86 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Autoridades do usuário { #user_authorities } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 3eb5af42a..f424dbd73 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Gerenciar usuários, funções e grupos de usuários { #manage_user_role_group } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index 0cd46747b..7312a2cdb 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index 0a6d4a6d3..5c3e21611 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Importar / Exportar aplicativo { #import_export } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index 59d8d8124..452ba4759 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Configure a sincronização de metadados { #metadata_sync } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index 59fc38736..b77cdfe2f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index e522fb24b..e19a7a8f2 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Administração de Dados { #data_admin } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 6c9bc0f59..f180d74d5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index 457f782a7..b50812e64 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Usar - DHIS core version 2.39 +- Usar --- > **Caution** diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index 22f703e4e..1a72844f7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Móvel { #mobile } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index fbafa6efa..a282c43da 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Agendamento { #scheduling } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index e74396ca8..2fd3a4738 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Visualize estatísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 980d87156..dbfa06d59 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo Capture { #capture_app } @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl the field. This will open a map where you can search for a location and capture a polygon (button in the upper right corner of the map). -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. If desired you can add a relationship by clicking the **Add relationship** button at the bottom of the form. See the section about **Adding a relationship** for more information. @@ -128,7 +128,7 @@ The second option, is to register a tracked entity instance with program and enr 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ When the "Scheduled days from start" does not contain a number or contains 0 the ### Possible duplicates detection { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. To configure a program through the maintenance app you will have to: @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### Program rules execution { #program-rules-execution } -In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will run program rules you have configured. -Note that, rules can be configured in the maintenance app. +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. To see a rule being executed while enrolling a tracked entity instance you will have to take the following steps. @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } + +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -![](resources/images/enrollment-widget-comment.png) +![](resources/images/enrollment-widget-note.png) -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index db3e16360..f0f721b2d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index da30217c0..731e81747 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Usando o aplicativo Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 38adbba8e..15759603c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Sobre dimensões de dados { #data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index b28a4a32e..a06f30ad6 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Dimensões de dados adicionais { #additional_data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index a28cc29f1..d0c837e51 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Modelo de relacionamento { #relationship_model } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 7a5382d31..d0d899b5b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Mensagens { #messages } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 12ed40929..05b09e240 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 60c957571..789ef186a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Usar - DHIS core version 2.39 +- Usar --- # Definir as preferências da conta do usuário { #user_account_preferences } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md index ec79b6060..675736440 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-data-entry-app.md" -revision_date: '2021-06-14' +revision_date: '2024-07-12' tags: - DHIS core version 2.40 - Usar @@ -279,12 +279,9 @@ case, you can enable multi-organisation unit data entry. ## Veja também { #data_entry_app_see_also } - - [Control data - quality](https://docs.dhis2.org/master/en/user/html/control_data_quality.html) + - [Control data quality](#control_data_quality) - - [Manage data sets and data entry - forms](https://docs.dhis2.org/master/en/user/html/manage_data_set.html) + - [Manage data sets and data entry forms](#manage_data_set) - - [Using the Maintenance - app](https://docs.dhis2.org/master/en/user/html/maintenance_app.html) + - [Using the Maintenance app](#maintenance_app) diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index a6574b4c7..a58e8273e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" -revision_date: '2024-01-03' +revision_date: '2024-07-12' tags: - DHIS core version 2.40 - Usar @@ -1792,16 +1792,16 @@ programs. search**. This specifies the amount of attributes that need to be filled out in order to be able to search for this **tracked entity type** in a *global search*. See [Configure - Search](../search/search.xml#configure_search) for more information. + Search](#configure_search) for more information. 7. (Optional) Enter a **Maximum number of tracked entity instances to return in search**. This specifies the amount of tracked entity instances that will be returned in a *global search*. See [Configure - Search](../search/search.xml#configure_search) for more information. + Search](#configure_search) for more information. 8. (Optional) Add **Tracked entity type attributes**. This is used to configure search, see [Configure - Search](configure_search) for more information. + Search](#configure_search) for more information. 9. (Opcional) Insira um ** Nome alternativo ** da entidade rastreada. diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 76c1980ab..39e21444e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: - DHIS core version 2.40 - Usar @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl the field. This will open a map where you can search for a location and capture a polygon (button in the upper right corner of the map). -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. If desired you can add a relationship by clicking the **Add relationship** button at the bottom of the form. See the section about **Adding a relationship** for more information. @@ -128,7 +128,7 @@ The second option, is to register a tracked entity instance with program and enr 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ When the "Scheduled days from start" does not contain a number or contains 0 the ### Possible duplicates detection { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. To configure a program through the maintenance app you will have to: @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### Program rules execution { #program-rules-execution } -In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will run program rules you have configured. -Note that, rules can be configured in the maintenance app. +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. To see a rule being executed while enrolling a tracked entity instance you will have to take the following steps. @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } -![](resources/images/enrollment-widget-comment.png) +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +![](resources/images/enrollment-widget-note.png) + +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 73dfc958b..40f1b3837 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 08c38084b..145dc521c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # DHIS2 Perguntas Freqüentes { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 1e0c6d6e7..827aca6f2 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Glossário DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f271a1acf..4a17d9dba 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Tutoriais DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 092034558..d470f4b96 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Notas de lançamento e atualização { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 7fcf4e7a1..b35613f98 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Gerir painéis { #dashboard } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 946e6194d..9e1896c71 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Uso do aplicativo Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index 4898d23b8..7b09e217f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Relatórios de eventos { #event_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 8e74f6050..53b5c69de 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index f06f44946..88bb52fe0 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 0b9515ba3..c39f31c48 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Maps { #using_maps } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index 6748a73c9..c185be12e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Funcionalidade de relatórios no aplicativo de relatórios { #using_the_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index ac1c455fd..5775cb022 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index 6dbbfe0d0..eb2d75ad6 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index 77e97ab75..83cee1c9a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index fe366c51c..f1ce88e54 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo de entrada de dados { #data_entry_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index 43ad5d569..ff581854c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Controle de qualidade de dados { #control_data_quality } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 22e9c7690..c108d4fea 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Sobre o compartilhamento de objetos { #sharing } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index e0b08b40f..b6d35aebe 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index d091c92b8..a912ca8f3 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configurar metadados { #maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 5211f3cbb..50b7b6e33 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure programas no aplicativo de manutenção { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index f934d6270..341138133 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure a funcionalidade de relatório { #setting_up_reporting } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 938205165..ee9d519ff 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configurações do sistema { #settings } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index d41eef82f..2bc79f3a3 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Autoridades do usuário { #user_authorities } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 4b20626af..bec4cf48f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Gerenciar usuários, funções e grupos de usuários { #manage_user_role_group } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index dff53f5a4..69db13e31 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 45dbb0a87..183aa6462 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Importar / Exportar aplicativo { #import_export } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index 86798d433..d0568ec08 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure a sincronização de metadados { #metadata_sync } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index 51a17482e..cfd884364 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 9734504a5..3141f2883 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Administração de Dados { #data_admin } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 5c032bac7..c0e69a06f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index e91defd33..600752d3f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Usar - DHIS core version 2.41 +- Usar --- > **Caution** diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 39e7629a4..fed0edef5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Móvel { #mobile } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index 3ed55865b..6f85907d9 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Agendamento { #scheduling } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index b24f5bbb0..0ea320b0b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Visualize estatísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 64fbea523..52ab6b3c5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Capture { #capture_app } @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl the field. This will open a map where you can search for a location and capture a polygon (button in the upper right corner of the map). -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. If desired you can add a relationship by clicking the **Add relationship** button at the bottom of the form. See the section about **Adding a relationship** for more information. @@ -128,7 +128,7 @@ The second option, is to register a tracked entity instance with program and enr 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ When the "Scheduled days from start" does not contain a number or contains 0 the ### Possible duplicates detection { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. To configure a program through the maintenance app you will have to: @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### Program rules execution { #program-rules-execution } -In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will run program rules you have configured. -Note that, rules can be configured in the maintenance app. +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. To see a rule being executed while enrolling a tracked entity instance you will have to take the following steps. @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } + +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -![](resources/images/enrollment-widget-comment.png) +![](resources/images/enrollment-widget-note.png) -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 7046fcbf4..2129b61a0 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 1f37ba1e8..589ed2da8 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index ea92fab54..3f829ad1e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Sobre dimensões de dados { #data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index a90b7c11d..8198ec36b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Dimensões de dados adicionais { #additional_data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index d5e9ab73b..e120dc605 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Modelo de relacionamento { #relationship_model } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 691b3af2f..c519bd81a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Mensagens { #messages } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 7906daa99..64c0367f5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index e78af83d7..76a4febd7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Definir as preferências da conta do usuário { #user_account_preferences } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index 82d3e8359..8f531f6a2 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Glossário DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 5496a05a5..b1365816a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Tutoriais DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 976a432be..b328a67cc 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Notas de lançamento e atualização { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index 795bf7854..06895d779 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Gerir painéis { #dashboard } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index 1f2488f93..33242e81d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Uso do aplicativo Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index 9c756cb1d..1f950011f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Usando o aplicativo Relatórios de eventos { #event_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index 031bc6b40..dcf002b27 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Usando o aplicativo Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index 17e1c0d0f..d4a7b6387 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 33df46133..917086f3b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Usando o aplicativo Maps { #using_maps } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index 29d829030..0e7b0adb7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Funcionalidade de relatórios no aplicativo de relatórios { #using_the_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index cbe7a4675..8f5d036ee 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index 08ae613cf..37eb24c84 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index 966839773..a941ab885 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index 2243fa450..da82224bc 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-data-entry-app.md" revision_date: '2024-06-18' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Usando o aplicativo de entrada de dados { #data_entry_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index b816e9311..3a0949faf 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Controle de qualidade de dados { #control_data_quality } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 5877a64c5..659261835 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Sobre o compartilhamento de objetos { #sharing } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 7e2e939e6..6a8f60eeb 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index e1df15fb1..5ed71ae92 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Configurar metadados { #maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index b56ad3572..089fa9a07 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-06-18' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Configure programas no aplicativo de manutenção { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index 7f4bd4c31..992428044 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Configure a funcionalidade de relatório { #setting_up_reporting } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index 6230c95d7..51289a54d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Configurações do sistema { #settings } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index b774c041f..ebddabd81 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Autoridades do usuário { #user_authorities } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 5bdebead4..4fd774164 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Gerenciar usuários, funções e grupos de usuários { #manage_user_role_group } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 8045de7fd..a6068a78f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index 7cafa9db8..2a629c755 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Importar / Exportar aplicativo { #import_export } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index 8e3fbc9db..ff0e70808 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Configure a sincronização de metadados { #metadata_sync } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index 8e06a8e05..0baa051fc 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index 9f0ad668a..68cec1e83 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Administração de Dados { #data_admin } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md index f5debc5a2..5adadb13b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index b8e58e7c9..9d3919a50 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- DHIS core version master - Usar +- DHIS core version master --- > **Caution** diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index 4e37ee1db..9bba11e39 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/mobile.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Móvel { #mobile } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 76760ed04..20373a891 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Agendamento { #scheduling } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 99e734cf8..acd75d749 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Visualize estatísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 7b6ee0db7..abb50c911 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Usando o aplicativo Capture { #capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 4f70c82c8..f38aad7bd 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Usando o aplicativo Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 9a934e16f..22f4695bc 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Usando o aplicativo Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 5035fa029..1cef6fc95 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Sobre dimensões de dados { #data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index f9a7bedf2..60816821e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Dimensões de dados adicionais { #additional_data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 8817abb81..7793bce52 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Modelo de relacionamento { #relationship_model } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 58560974f..7499b7cb7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Mensagens { #messages } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index b22dba41e..e40fad0ac 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index f5f348c57..c5f572be3 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- DHIS core version master - Usar +- DHIS core version master --- # Definir as preferências da conta do usuário { #user_account_preferences } diff --git a/projects/docs-full-site/ru/.cache_timestamp b/projects/docs-full-site/ru/.cache_timestamp index 976a10bcd..5b7cf485f 100644 --- a/projects/docs-full-site/ru/.cache_timestamp +++ b/projects/docs-full-site/ru/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:21:53Z \ No newline at end of file +2024-07-17T21:23:19Z \ No newline at end of file diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index 4892892f6..bc5135c7d 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index ff571e35f..542b67824 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index 676407f2f..4d50efd7d 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index a583eca0b..551f92cc4 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index b3f7caea7..da5b4df78 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- # About this guide { #about_this_guide_ } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index 85a593c33..6132a7668 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index d906a186e..6c94f44ca 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index b6f34058d..698a84d6e 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index 2756c3a4d..83b70de2c 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md index 661a481af..d9fb9cdb7 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/map-view.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - Использовать +- App version 1.4.0 --- Map View diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index 1a2ad5471..18a90b574 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- App version 1.0.3 - Использовать +- App version 1.0.3 --- # User Manual for the DHIS2 Immunisation Analysis App { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md index 8e2cedaaf..7504a0a4b 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/about-this-guide.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # About this guide { #about-this-guide } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md index af7423f5b..59aabd77e 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-and-translating-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Accessing and translating the Scorecard { #accessing-and-translating-the-scorecard } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md index 5b610f401..eba8461e9 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-scorecard-app.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Login DHIS2 system { #login-dhis2-system } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md index 2597831aa..05d6ac2d1 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/creating-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- ## Creating the Scorecard { #creating-the-scorecard } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md index 4bd04cd6c..712d6525f 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/introduction-to-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Introduction to the Scorecard App { #introduction-to-the-scorecard-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md index f35b5a4e4..095602ad4 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/saving-configurations.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- ## Saving configuration and load the scorecard { #saving-configuration-and-load-the-scorecard } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md index 1c994d2ab..24c13ce20 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/scorecard-app-architecture.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Scorecard App architecture { #scorecard-app-architecture } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md index 8c8646259..4f0dca211 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/support-and-maintanace-options.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Scorecard App Built-in Support and Maintenance Options { #scorecard-app-built-in-support-and-maintenance-options } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md index b88e1494f..12ed8307f 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/viewing-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Viewing the Scorecard App Analysis outputs { #viewing-the-scorecard-app-analysis-outputs } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md index a5f36267d..25d55ecbb 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-maintenance.md" revision_date: '2024-02-27' tags: -- Использовать - App version 2.0 +- Использовать --- If a Standalone action tracker application is taking too long to load, and you’re not on a slow network, make sure you have cleared your browser cache. diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md index e44e0259c..995b9aa9d 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-architecture-and-installation.md" revision_date: '2024-02-22' tags: -- Использовать - App version 2.0 +- Использовать --- The Standalone Action Tracker Application is built on an architecture that eases user interactions by having a design concept that promotes the user to follow their intuition complemented with high performance that considers the lowest internet connection scenarios with descriptive notification messages if the user misses a step along the way. diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md index 8389a0e0f..428b608e1 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-browsing.md" revision_date: '2024-02-23' tags: -- Использовать - App version 2.0 +- Использовать --- The Standalone Action Tracker App can be found in the Apps menu. if the application has not yet been installed in your DHIS2 instance or the installation has issues, refer to the installation instructions (Section 3.5) of this documentation for further guidance, or contact the DHIS2 administrator for your instance. diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md index f77448b9d..de6cb6a8a 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-introduction.md" revision_date: '2024-02-22' tags: -- Использовать - App version 2.0 +- Использовать --- # Introduction to the Standalone Action Tracker App { #introduction-to-the-standalone-action-tracker-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md index cec40877c..98ea8261e 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-configuration.md" revision_date: '2024-02-27' tags: -- Использовать - App version 2.0 +- Использовать --- The Standalone Action Tracker App includes a module for administrators to configure key metadata for the normal user. The administration configurable options include:- diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 7dca89511..b01f742a0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 3b38f0152..f5fc61a2b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2024-06-07' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index c338d0256..95f829fd6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index b29fc8207..99942e293 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index b0b52e995..5c6300784 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index 933b2566c..7680ff307 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index ede7841d4..99244685c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index fd7cc9be3..fdbd0c730 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index 267007b55..db7a93d6d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index fd5284a1b..074642146 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index 862e73717..70867e4bd 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-maps-app.md" revision_date: '2022-03-23' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index cc75c95c1..71b7089a6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md index cb3f1e435..540ffe848 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index 44c63addf..5938411c3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index dd6c55600..0219ad956 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index 997978523..e2294a540 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index a04fb8b1b..83fa2957f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index 06ad9b37a..543aafc46 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-the-gis-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure the Maps app { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index a0f9badaf..579657daf 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata.md" revision_date: '2022-10-02' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index cf8ee4ae4..66bd0d80c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index bc2ca1d30..2d20f766d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index 0b3d20d42..8c2c4bbea 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/system-settings.md" revision_date: '2022-04-27' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index c2f2e4294..3ae2bead1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 6f9e08ff9..c7cd05d5d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index 0f53f25f3..7a3b1f40b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/importexport-app.md" revision_date: '2022-02-23' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index cbeb5f419..dd88cac7e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index ae2069fe4..1ca053598 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index b3538e57f..ff12c7f9f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index fc9707fc9..817e3480c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index c92a359ed..10eb23838 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index 5c52cef73..a032717c9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index db22d97d8..fe13ba9a5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 555ebb93f..d31573614 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 6c6a6ef4d..979f77575 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index c55599452..6ecaa0cb5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 45bc62d4d..e3053c545 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 8e5d0d6b6..ad03eb3db 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 2ae4a48f3..0d7ab33ec 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 41114b5ca..db3413e3a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index ef5fd8b5e..269105b37 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 19f69258b..3f4841c15 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index beb171c0f..d7215fd8f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 498e913e2..82c3006f6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 6b7a05ab4..51ce1268c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index 75d9e7eab..b223a45fb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f9a1488cd..5176eb20f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index bb077ce43..814b1570d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index d30dbc2b1..bd643f5d1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index 7c5668ca8..eec3b0641 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index 87d9b4d60..f806b5eb2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index eb302d2d3..3cefbfa71 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index bc0cfa36b..664f1b3e0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index 23448afdb..48f8e3dc0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index edf82fc50..562c8fed8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index 2ef792342..87a004942 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index 159d7a159..550a391ab 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index c8687445f..632a634e2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index 88d2d5a63..ef53947ea 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" revision_date: '2024-07-12' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index 7f8dc09ea..7391cea50 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index f04a34831..31444679c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index cdfa27290..2eaf180d0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index a60b33572..409832227 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index 57746376e..5ab1dc17b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-07-12' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index 5ab9b0d68..065de4ffa 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index b3e8a8901..394f787a8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index e13509bce..d3ed54fe0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 733c2eb33..ab2ec14bf 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index c855dfca0..918df03a4 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index 8a233478a..7c0e2942b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index 34a156e86..2e9929998 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index 1c5dea55d..bd8ff9767 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index 9526da350..bc5bee39f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 36e97d0a9..a64941b98 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index 2925045ee..6baab624b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index a13babe13..d8620f0af 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index a9b0517b5..230f2fbea 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 1f1bf3bc6..f54a46745 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index dd28d610e..3fe9f8078 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 3ad9d1569..1b7bd9485 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index c7831cae0..1c4a653b6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 15a411afc..f81e5195c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 0dd1d0d2e..f39789bf6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 29bb0f8ae..08993b81f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index ef2431005..81fe43e7d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index eee45808c..a0c040ee3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 1df47dc24..5203d779a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 0a198a9d1..0e20528b9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 826b7e6ed..cb7130215 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 4970aa890..4331e0b02 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f0c4a25a3..09a902817 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 13d92a5e9..e482b20c2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 0bd631a51..3580a92c6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 5db4ec8a2..d31598f6f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index d7689421c..399cf443d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 23ae7616f..76a283d5a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index 1bce94aef..edb1976dd 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 195fe4b9d..7ea240c3e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index 9d9e1e19a..8ff7b6f2b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index 95478d0d4..151338ba5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index df62e36eb..cfe04401f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index 983cf4adc..7b1ec651d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index ad65159c3..03916b3c0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index b914d55a9..5f71408f6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index ade9a97e7..1c3113813 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 0ad1cc5ac..6ce3665ab 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index fd2b1c027..9d476de72 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 49d3c6368..2932b1be9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index bb63e94d8..1c6ab6604 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 78cd3550b..6357bf9c5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 29f571687..d5eaa5e0b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 3441178e2..964e4cf2c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index f9e8cf226..3909ef060 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 9c9afb997..5ef413e4a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index eda53ca28..ccc9cca24 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index de8bd3b90..095dd9857 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 88f3d7357..6128c4215 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 527114593..8456df8b1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index f47685e94..e36bbe294 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 09f2ac277..d30b6d0d3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index ca6d9ef17..e4705ef26 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index bfefd7c53..6147e907c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index f8798d3db..083007090 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index bbf170837..89a5d1f06 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 7cee24ef1..e01ea9808 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index ae0c98394..a26f30384 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index b68cfa3c6..07b835fb8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index cfa2b712f..33a5d44bb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 07e3b735b..0c611a854 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 3d05a998d..4a442c3be 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index e82d3eb9f..9f3722eab 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index d240517e3..fa2c354d9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 6aae25efa..ffe055450 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2024-06-07' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index bba99cf04..b94c87cb6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 7f9f74550..01b4be345 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 282caafe6..b1560c848 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index 54ed567ed..685af79b0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index 353b3c612..3404a989c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index 6a87d2411..32a49b369 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index c0854d5c4..c3c06f063 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index 095cc26e1..b60d406b8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 015b23cf4..651ce0c4f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index ab202eec6..02affac86 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index b44d8a5cb..ddbd84538 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index 419a225fa..1b99e3fe9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index e88087290..941831bc7 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index a0decc726..9e0aa2f61 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-data-entry-app.md" revision_date: '2024-06-18' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index 397b76d31..e2400e36b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index d0c9815b9..1bd112ce3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 1fc652b49..dd72e9985 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index b164a52d8..bb49fd0d7 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index 0f502a634..c81547d0f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-06-18' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index 335c6ef78..a2554ad99 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index 9f289ea21..99de21dfe 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index 72b38cdd9..7ee1adcb4 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 3bc67765f..567e374d9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 0e6b2e71d..973bfd87c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index 46b68df9d..3bbac50bb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index 276f791f5..be7f34332 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index f371cb7e4..0346a963a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index a919de599..b3f29d8c2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md index d018ee200..615761dd5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index 00bc5c563..02b4cf167 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- DHIS core version master - Использовать +- DHIS core version master --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index aec6a8d3c..490549f23 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/mobile.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 11dcc999a..3932bafcc 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 81410bb6e..f912cb6b9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 811aa077e..90e167bc0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-07-15' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index ce82c026c..60584f858 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index cf6a904a5..39a03d6d9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index b5e2cda30..45e796e03 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index cce545aac..2aed8eea8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 4c808f81d..c489cefcb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 049d3b998..469a57230 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index a8804234e..8c8d81105 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 40fc44a6c..2b24156f1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- DHIS core version master - Использовать +- DHIS core version master --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/si/.cache_timestamp b/projects/docs-full-site/si/.cache_timestamp index 1b05c955d..7a1b0b573 100644 --- a/projects/docs-full-site/si/.cache_timestamp +++ b/projects/docs-full-site/si/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:22:21Z \ No newline at end of file +2024-07-17T21:23:58Z \ No newline at end of file diff --git a/projects/docs-full-site/zh/.cache_timestamp b/projects/docs-full-site/zh/.cache_timestamp index 1b05c955d..7a1b0b573 100644 --- a/projects/docs-full-site/zh/.cache_timestamp +++ b/projects/docs-full-site/zh/.cache_timestamp @@ -1 +1 @@ -2024-07-16T21:22:21Z \ No newline at end of file +2024-07-17T21:23:58Z \ No newline at end of file diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md index 523347c06..3ccf3605a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 分析工具 { #analytics } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md index 4e1dad77d..152c10d0a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 应用 { #apps } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md index 2c77c1bea..304ddeb05 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/audit.md" revision_date: '2021-06-14' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md index 44f12b808..8a9466310 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 数据审批 { #data-approval } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md index c300274f2..4e9166bb7 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data.md" revision_date: '2022-04-04' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 数据 { #data } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md index 9ec3b7cc2..a34b502e7 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-store.md" revision_date: '2022-03-24' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 数据存储 { #data-store } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md index 1496e8213..80248b6b6 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/data-validation.md" revision_date: '2022-02-23' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 数据验证 { #data-validation } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md index 76270f2e9..bcc1a924b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 电子邮件 { #email } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md index 9cc399c82..ebcde38da 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/i18n.md" revision_date: '2022-04-27' tags: -- Develop - DHIS core version 2.38 +- Develop --- # I18n { #i18n } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md index cd93f40f5..4a3dcfa9c 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/overview.md" revision_date: '2022-02-28' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 总览 { #webapi } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md index a04c75a9b..1884a9b60 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/maintenance.md" revision_date: '2021-06-14' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 保养 { #maintenance } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md index 24f2f40fd..c3a2633be 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 讯息传递 { #messaging } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md index 840c7a4cf..1108605e1 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/metadata-gist.md" revision_date: '2021-11-23' tags: -- Develop - DHIS core version 2.38 +- Develop --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md index a070868cf..7ae377019 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/metadata.md" revision_date: '2023-08-03' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 元数据 { #metadata } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md index 1b239e7d7..ea105a668 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/new-tracker.md" revision_date: '2024-05-21' tags: -- Develop - DHIS core version 2.38 +- Develop --- # New Tracker { #new-tracker } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md index c502e570e..89090cebf 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- Develop - DHIS core version 2.38 +- Develop --- # Organisation unit profile { #org_unit_profile } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md index 0d633fe89..38987e321 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/scheduling.md" revision_date: '2022-05-05' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 排程 { #webapi_scheduling } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md index 6bcbd7b28..42bd8a5da 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/settings-and-configuration.md" revision_date: '2023-12-14' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 设置和配置 { #settings-and-configuration } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md index 0f510d3cc..5de85a0d4 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 分享中 { #sharing } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md index 914b673c5..dc8210471 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 短信 { #sms } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md index 1682f2951..0dd443117 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 同步化 { #webapi_synchronization } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md index 30897c242..81b95cef8 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/tracker.md" revision_date: '2024-01-05' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 追踪器 { #tracker } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md index a16506a80..9c3f9a76b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/users.md" revision_date: '2021-11-04' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 用户数 { #users } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md index f12e9ab9b..d08eee7c2 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/developer/web-api/visualizations.md" revision_date: '2022-03-24' tags: -- Develop - DHIS core version 2.38 +- Develop --- # 可视化 { #visualizations } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md index a6128aaef..13cb220cb 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-validation.md" revision_date: '2023-04-14' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 数据验证 { #data-validation } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md index 6a5e9357a..694fc736d 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 电子邮件 { #email } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md index 615f5efec..9b6bbbfc1 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 总览 { #webapi } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md index b671704c1..50c49c15c 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 分享中 { #sharing } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index 5725ad87a..7fd121044 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" -revision_date: '2024-05-23' +revision_date: '2024-07-02' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 追踪器 { #tracker } @@ -2145,7 +2145,11 @@ This, along with the Program's [Access Level](#webapi_nti_access_level) configur A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured with access level *OPEN* or *AUDITED* , the Owner OrganisationUnit has to be in the user's search scope. For Programs that are configured with access level *PROTECTED* or *CLOSED* , the Owner OrganisationUnit has to be in the user's capture scope to be able to access the corresponding program data for the specific tracked entity. -#### 跟踪器所有权优先：打破常规 { #webapi_nti_tracker_ownership_override } +When requesting tracked entities without specifying a program, the response will include only tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and one of the following criteria: +- The tracked entity is enrolled in at least one program the user has data access to, and the user has access to the owner organisation unit. +- The tracked entity is not enrolled in any program the user has data access to, but the user has access to the tracked entity registering organisation unit. + +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md index 5a9d4cb0d..7b674ac3f 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/users.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 用户数 { #users } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md index 9db863ab3..c8cff68cf 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 可视化 { #visualizations } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md index a65ccbc3f..4f26f52bc 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Develop - DHIS core version 2.41 +- Develop --- # 应用 { #apps } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md index e355be2a3..0e0c4b88a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Develop - DHIS core version 2.41 +- Develop --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md index cee8e7f38..9e7d8fe72 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Develop - DHIS core version 2.41 +- Develop --- # 数据审批 { #data-approval } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md index fa7b458a8..e932dd3e4 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Develop - DHIS core version 2.41 +- Develop --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md index 549ac66a7..5cae72a00 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker-old.md" revision_date: '2024-05-23' tags: -- Develop - DHIS core version 2.41 +- Develop --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index 83eed395e..f1cd1d71c 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index 464fd167f..779042358 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index f2267d55f..d282ad18e 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index 47bd351c6..0ad78cfca 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index f449f5759..02e6249c0 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- # 关于本指南 { #about_this_guide_ } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index 05cb2b570..2d3350791 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index 3ab0774f7..c1be7f271 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index 3189b9e11..143fe9f8c 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index 790ca7215..1f4cf5cb1 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md index 7e5cffff7..5d32ee180 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/map-view.md" revision_date: '2022-12-20' tags: -- App version 1.4.0 - 使用 +- App version 1.4.0 --- Map View diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index 94686c0b6..d6e128453 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- App version 1.0.3 - 使用 +- App version 1.0.3 --- # User Manual for the DHIS2 Immunisation Analysis App { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md index eba7113c7..c9a6db94c 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/about-this-guide.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- # 关于本指南{ #about-this-guide } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md index 5b7a0e74e..8b40305ed 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-and-translated-scorecard.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- # 访问和翻译记分卡{ #accessing-and-translating-the-scorecard } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md index 0ed9737ea..7e78c9b02 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-scorecard-app.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- # 登录DHIS2系统{ #login-dhis2-system } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md index 63f76cd11..dd1ed45ce 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/creating-scorecard.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- ## 创建记分卡{ #creating-the-scorecard } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md index 0252adb37..2fde2c8a9 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/introduction-to-scorecard.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- # 记分卡应用简介 { #introduction-to-the-scorecard-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md index 8000796f4..e89a17b90 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/ saving-configurations.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- ## 保存配置并加载记分卡{ #saving-configuration-and-load-the-scorecard } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md index aabe35610..abf98ac4d 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/scorecard-app-architecture.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- # 记分卡应用架构{ #scorecard-app-architecture } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md index f57bcca1b..43e819a4e 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/support-and-maintanace-options.md" revision_date: '2021-10-04' tags: -- 使用 - App version 2.5.0 +- 使用 --- # 记分卡应用内置支持和维护选项{ #scorecard-app-built-in-support-and-maintenance-options } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 865da5df4..d808f0120 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: - DHIS core version 2.38 - 使用 @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl 场。这将打开一个地图，您可以在其中搜索位置并捕获 一个多边形（地图右上角的按钮）。 -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. 如果需要，您可以通过单击表单底部的**添加关系**按钮来添加关系。 有关更多信息，请参见关于**添加关系**的部分。 @@ -128,7 +128,7 @@ In the Capture app you register events that occurred at a particular time and pl 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ In the example below we increase the due date by 30 days. ### 可能的重复检测 { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. 要通过维护应用程序配置程序，您必须： @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### 程序规则执行 { #program-rules-execution } -在注册跟踪实体实例的两种情况下（有注册或没有注册），系统将运行您配置的程序规则。 -请注意，可以在维护应用程序中配置规则。 +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. 要在注册跟踪实体实例时查看正在执行的规则，您必须执行以下步骤。 @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } -![](resources/images/enrollment-widget-comment.png) +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +![](resources/images/enrollment-widget-note.png) + +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index c015a1987..2e5fe2fd6 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index bba328039..58b6f83d2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # DHIS2常见问题 { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index 679115ef9..aa9669198 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # DHIS2词汇表 { #dhis2_glossary } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index dd993f813..c9843fd33 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # DHIS2教程 { #dhis2_tutorials } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 91ff97b1b..99edf1f14 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 发布和升级说明 { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index 29d4de3a5..a5e8d84ba 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 管理仪表板 { #dashboard } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index 010026bed..be5b5faa6 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用数据可视化器应用 { #data_visualizer } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index d977d525f..52ad36cf5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用事件报告应用 { #event_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index 8441c2aa7..91a8ef8a9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用事件可视化器应用 { #event_visualizer_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index 877308b28..e12c4b5ac 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index 07bc02391..3599d303c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用地图应用 { #using_maps } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index 0325ef12c..2701e5f88 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 报告应用程序中的报告功能 { #using_the_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index b894cb817..0c8f70620 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index b2688629f..e89cbd97c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index eacd12dbe..f0d36d566 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index f62f85b66..088483a82 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" -revision_date: '2021-06-14' +revision_date: '2024-07-12' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用数据输入应用 { #data_entry_app } @@ -279,12 +279,9 @@ Internet连接恢复，该应用会将数据推送到服务器。 ## 也可以看看 { #data_entry_app_see_also } - - [控制数据 - 质量](https://docs.dhis2.org/master/en/user/html/control_data_quality.html) + - [Control data quality](#control_data_quality) - - [管理数据集和数据输入 - 表格](https://docs.dhis2.org/master/en/user/html/manage_data_set.html) + - [Manage data sets and data entry forms](#manage_data_set) - - [使用维护 - 应用程序](https://docs.dhis2.org/master/en/user/html/maintenance_app.html) + - [Using the Maintenance app](#maintenance_app) diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index 044fd1388..4140fbbb1 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 控制数据质量 { #control_data_quality } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index c0611ffab..320716cb2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 关于对象共享 { #sharing } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index 1c3746af8..31efb4f33 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index 2300ec08e..74613f82e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 配置元数据 { #maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index 2cfe3528d..2f5153bd7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" -revision_date: '2024-01-03' +revision_date: '2024-07-12' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 在维护应用中配置程序 { #configure_programs_in_maintenance_app } @@ -1783,16 +1783,16 @@ For more information about configuration and the meaning of 'From constraint' an 搜索**。这指定了需要设置的属性数量 填写以便能够搜索此**跟踪的实体 type** in a *global search*. See [Configure - 搜索]（../ search / search.xml＃configure_search）了解更多信息。 + Search](#configure_search) for more information. 7. （可选）输入**要跟踪的实体实例的最大数量 返回搜索**。这指定了被跟踪实体的数量 实例将在*全局搜索*中返回。请参阅[配置 - 搜索]（../ search / search.xml＃configure_search）了解更多信息。 + Search](#configure_search) for more information. 8. (Optional) Add **Tracked entity type attributes**. This is used to 配置搜索，请参阅[配置 - 搜索]（configure_search）了解更多信息。 + Search](#configure_search) for more information. 9. (Optional) Enter an **Alternative name** of the tracked entity. diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index 6acba0566..5c2f213d8 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 配置报告功能 { #setting_up_reporting } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index a9f66a0c3..60137b024 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 系统设置 { #settings } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index 22e8165b5..53ec10671 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 用户权限 { #user_authorities } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index c1626500e..756f328c9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 管理用户，用户角色和用户组 { #manage_user_role_group } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index 931c2b977..fced41c4d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index cc008d682..646126a89 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 导入/导出应用 { #import_export } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index 7b3135ef0..99151fd8d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 配置元数据同步 { #metadata_sync } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index 0e6fb8cbe..e37ad36e9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index 6154c34bb..80988f341 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 资料管理 { #data_admin } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 1722bad91..bcd0e3aa2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 数据存储管理器 { #datastore_manager_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index 06a1176cc..4a0aab89e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- > **Caution** diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index 71b46b4e7..55ff741b2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 移动 { #mobile } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index 85d736bff..8802520ce 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 排程 { #scheduling } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index d2044dacc..248ef0b70 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 可视化使用情况统计 { #using_usage_analytics } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index a24bbd7a7..5bddec3f5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用捕获应用 { #capture_app } @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl 场。这将打开一个地图，您可以在其中搜索位置并捕获 一个多边形（地图右上角的按钮）。 -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. 如果需要，您可以通过单击表单底部的**添加关系**按钮来添加关系。 有关更多信息，请参见关于**添加关系**的部分。 @@ -128,7 +128,7 @@ In the Capture app you register events that occurred at a particular time and pl 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ In the example below we increase the due date by 30 days. ### 可能的重复检测 { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. 要通过维护应用程序配置程序，您必须： @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### 程序规则执行 { #program-rules-execution } -在注册跟踪实体实例的两种情况下（有注册或没有注册），系统将运行您配置的程序规则。 -请注意，可以在维护应用程序中配置规则。 +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. 要在注册跟踪实体实例时查看正在执行的规则，您必须执行以下步骤。 @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } + +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -![](resources/images/enrollment-widget-comment.png) +![](resources/images/enrollment-widget-note.png) -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 95d29ef18..030bb05dd 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用事件捕获应用 { #event_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index f5a551c52..4454b93b7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用Tracker Capture应用 { #tracker_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index b19041fbf..6b3ab9b31 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 关于数据维度 { #data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 7916a6d8f..3d38b12fa 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 附加数据维度 { #additional_data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index ad5ef66a7..05abd14ea 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 关系模型 { #relationship_model } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index c8087722f..4fb2b59a2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 讯息传递 { #messages } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 8da462e93..981fdbd8f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 14ff4270f..8056e6271 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 设置用户帐户首选项 { #user_account_preferences } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md index 683a9cf9c..78ec06a59 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-data-entry-app.md" -revision_date: '2021-06-14' +revision_date: '2024-07-12' tags: - DHIS core version 2.40 - 使用 @@ -279,12 +279,9 @@ Internet连接恢复，该应用会将数据推送到服务器。 ## 也可以看看 { #data_entry_app_see_also } - - [控制数据 - 质量](https://docs.dhis2.org/master/en/user/html/control_data_quality.html) + - [Control data quality](#control_data_quality) - - [管理数据集和数据输入 - 表格](https://docs.dhis2.org/master/en/user/html/manage_data_set.html) + - [Manage data sets and data entry forms](#manage_data_set) - - [使用维护 - 应用程序](https://docs.dhis2.org/master/en/user/html/maintenance_app.html) + - [Using the Maintenance app](#maintenance_app) diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index f0ec81df8..409700b05 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" -revision_date: '2024-01-03' +revision_date: '2024-07-12' tags: - DHIS core version 2.40 - 使用 @@ -1792,16 +1792,16 @@ For more information about configuration and the meaning of 'From constraint' an 搜索**。这指定了需要设置的属性数量 填写以便能够搜索此**跟踪的实体 type** in a *global search*. See [Configure - 搜索]（../ search / search.xml＃configure_search）了解更多信息。 + Search](#configure_search) for more information. 7. （可选）输入**要跟踪的实体实例的最大数量 返回搜索**。这指定了被跟踪实体的数量 实例将在*全局搜索*中返回。请参阅[配置 - 搜索]（../ search / search.xml＃configure_search）了解更多信息。 + Search](#configure_search) for more information. 8. (Optional) Add **Tracked entity type attributes**. This is used to 配置搜索，请参阅[配置 - 搜索]（configure_search）了解更多信息。 + Search](#configure_search) for more information. 9. (Optional) Enter an **Alternative name** of the tracked entity. diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index d779b88b9..dffe671f0 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: - DHIS core version 2.40 - 使用 @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl 场。这将打开一个地图，您可以在其中搜索位置并捕获 一个多边形（地图右上角的按钮）。 -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. 如果需要，您可以通过单击表单底部的**添加关系**按钮来添加关系。 有关更多信息，请参见关于**添加关系**的部分。 @@ -128,7 +128,7 @@ In the Capture app you register events that occurred at a particular time and pl 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ In the example below we increase the due date by 30 days. ### 可能的重复检测 { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. 要通过维护应用程序配置程序，您必须： @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### 程序规则执行 { #program-rules-execution } -在注册跟踪实体实例的两种情况下（有注册或没有注册），系统将运行您配置的程序规则。 -请注意，可以在维护应用程序中配置规则。 +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. 要在注册跟踪实体实例时查看正在执行的规则，您必须执行以下步骤。 @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } -![](resources/images/enrollment-widget-comment.png) +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +![](resources/images/enrollment-widget-note.png) + +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index ef788bd45..6b59d7c52 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index c3aaa7b43..2dce7b051 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # DHIS2常见问题 { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 183bfdd07..6238a81d7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # DHIS2词汇表 { #dhis2_glossary } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 9a3b63ca2..ead525f7e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # DHIS2教程 { #dhis2_tutorials } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 993d29c40..b55ebbee8 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 发布和升级说明 { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index fb54f1f8c..9bd74d5cd 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 管理仪表板 { #dashboard } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 46627c354..fd78efdcc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用数据可视化器应用 { #data_visualizer } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index fe937e3bf..b5edb0cef 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用事件报告应用 { #event_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 25e7c678c..9fc8fc63b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用事件可视化器应用 { #event_visualizer_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index dd9fa767d..df34bb0ba 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-06-26' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index ff08ba0f1..97e00b9dc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用地图应用 { #using_maps } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index cd73b6c4d..664794372 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 报告应用程序中的报告功能 { #using_the_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index 99f7e657e..0e61fec09 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index 4bbabf7cd..a70ea2663 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index 1564ece6f..909becf79 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index 43b59eb99..7602c63be 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用数据输入应用 { #data_entry_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index d1a42bc10..211b6a740 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 控制数据质量 { #control_data_quality } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index e83830a74..3f842219d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 关于对象共享 { #sharing } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 252d15dd7..9e64af6de 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index b028ae8ff..cf44ae57d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 配置元数据 { #maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 650bc115f..3bf5b4e68 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 在维护应用中配置程序 { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 312d92e14..42dd7da4a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 配置报告功能 { #setting_up_reporting } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index b98d58e11..6596bb0c5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 系统设置 { #settings } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 2c4198a45..99ad5ed0e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 用户权限 { #user_authorities } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index fb749398c..662a0644f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 管理用户，用户角色和用户组 { #manage_user_role_group } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index 2139652fe..b03d51488 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 37588bfc0..50e56b6b3 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 导入/导出应用 { #import_export } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index c6e41f0af..72795b10c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 配置元数据同步 { #metadata_sync } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index 1005a7914..fdb39857f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index e7441dbe7..416187d1f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 资料管理 { #data_admin } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index df6b972d3..fa2b60ddb 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 数据存储管理器 { #datastore_manager_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 765228b85..eef87c234 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- > **Caution** diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 83bb02176..7f90d87f7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 移动 { #mobile } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index ed81ec4e5..7def58024 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 排程 { #scheduling } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index fd57e6fc9..4f354e83a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 可视化使用情况统计 { #using_usage_analytics } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index c596f236b..b43f5e456 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用捕获应用 { #capture_app } @@ -39,7 +39,7 @@ In the Capture app you register events that occurred at a particular time and pl 场。这将打开一个地图，您可以在其中搜索位置并捕获 一个多边形（地图右上角的按钮）。 -7. If desired you can add a comment by clicking the **Write comment** button at the bottom of the form. Note that Event comments are attributed to a user and cannot be deleted. +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. 如果需要，您可以通过单击表单底部的**添加关系**按钮来添加关系。 有关更多信息，请参见关于**添加关系**的部分。 @@ -128,7 +128,7 @@ In the Capture app you register events that occurred at a particular time and pl 3. Select a tracker program of your choice. -4. Click **Create new person**. Please note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![create new event](resources/images/register-and-enroll-program-selection.png) @@ -241,7 +241,7 @@ In the example below we increase the due date by 30 days. ### 可能的重复检测 { #possible-duplicates-detection } In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. -Note that, programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. 要通过维护应用程序配置程序，您必须： @@ -288,8 +288,8 @@ Click **Save person**. The system will start looking for possible duplicates tha ### 程序规则执行 { #program-rules-execution } -在注册跟踪实体实例的两种情况下（有注册或没有注册），系统将运行您配置的程序规则。 -请注意，可以在维护应用程序中配置规则。 +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. 要在注册跟踪实体实例时查看正在执行的规则，您必须执行以下步骤。 @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } + +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -![](resources/images/enrollment-widget-comment.png) +![](resources/images/enrollment-widget-note.png) -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page. diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 13bcd2101..beebc3e6f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用事件捕获应用 { #event_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index a8bce7a57..480c0448c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用Tracker Capture应用 { #tracker_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index fd1d1e651..e417fbfe5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 关于数据维度 { #data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 1570053ca..6132afce3 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 附加数据维度 { #additional_data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index d667de86a..86c3f6d60 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 关系模型 { #relationship_model } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 25370ed68..2a28aa142 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 讯息传递 { #messages } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index f60ec8ef7..9abb94c7c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 73196f084..300c14661 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 设置用户帐户首选项 { #user_account_preferences } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index d922061f0..9ed2a6ece 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" -revision_date: '2024-06-24' +revision_date: '2024-07-15' tags: - 使用 - DHIS核心 主版 @@ -39,7 +39,7 @@ tags: 场。这将打开一个地图，您可以在其中搜索位置并捕获 一个多边形（地图右上角的按钮）。 -7. 如果需要，您可以通过单击表单底部的 **写评论** 按钮来添加评论。请注意，事件评论属于用户，无法删除。 +7. If desired, you can add a note by clicking the **Write note** button at the bottom of the form. Be aware that Event notes are attributed to a user and cannot be deleted. 8. 如果需要，您可以通过单击表单底部的**添加关系**按钮来添加关系。 有关更多信息，请参见关于**添加关系**的部分。 @@ -128,7 +128,7 @@ tags: 3. 选择您选择的跟踪器程序。 -4. 单击**创建新人**。请注意，此按钮的标签对应于程序的跟踪实体类型，该类型可能会有所不同，例如“建筑物”、“人”等。 +4. Click **Create new person**. Note that the label of this button corresponds to the tracked entity type of the program, which could vary, such as "Building," "Person," etc. ![创建新活动](resources/images/register-and-enroll-program-selection.png) @@ -240,8 +240,8 @@ tags: ### 可能的重复检测 { #possible-duplicates-detection } -在注册跟踪实体实例的两种情况下（注册或未注册）系统将开始寻找可能的重复项。 -请注意，需要通过维护应用程序正确配置程序，以便系统在将新人员注册到程序中时开始检测重复项。 +In both cases of registering a tracked entity instance, (with enrollment or without enrollment) the system will start looking for possible duplicates. +Note that programs need to be correctly configured through the maintenance app for the system to start detecting duplicates when enrolling a new person in a program. 要通过维护应用程序配置程序，您必须： @@ -288,8 +288,8 @@ tags: ### 程序规则执行 { #program-rules-execution } -在注册跟踪实体实例的两种情况下（有注册或没有注册），系统将运行您配置的程序规则。 -请注意，可以在维护应用程序中配置规则。 +In both cases of registering a tracked entity instance (with enrollment or without enrollment), the system will run program rules you have configured. +Note that rules can be configured in the maintenance app. 要在注册跟踪实体实例时查看正在执行的规则，您必须执行以下步骤。 @@ -1010,13 +1010,14 @@ You can complete the enrollment by clicking the complete button. When there are ![](resources/images/enrollment-dash-enrollment-widget-4.png) -### Enrollment comment widget { #enrollment-comment-widget } +### Enrollment note widget { #enrollment-note-widget } -![](resources/images/enrollment-widget-comment.png) +The enrollment note widget displays notes and allows addition of notes, associated with the current enrollment. -The enrollment comment widget displays comments and allows addition of comments, associated with the current enrollment. +![](resources/images/enrollment-widget-note.png) + +By clicking in the text field, you will be able to enter new text and see action buttons **Save note** and **Cancel**. Be aware that Enrollment notes are attributed to a user and cannot be deleted. -By clicking in the text field, you will be able to enter new text and see action buttons **Save comment** and **Cancel**. Note that Enrollment comments are attributed to a user and cannot be deleted. ### Relationship widget { #relationship-widget } @@ -1276,7 +1277,7 @@ If a program stage has a default next scheduled date configured, the suggested d User can also find more information about how many events that scheduled on the same selected date or the interval of selected date and the suggested date from the information box. -Below the schedule date entry, user can choose to add a comment to the scheduled event. +Below the schedule date entry, user can choose to add a note to the scheduled event. After clicking **Schedule** button, user will be navigated back to enrollment overview page.